Centralized user documentation

Introduction

Versions

• Pre 1.0 are before the project was open sourced and won't be documented here. Work started summer 2017.
• 1.0 - June 23rd 2019.
• 1.1 - August 21st 2019.

Status

• Github and Bitbucket supported, gitlab coming, kubernetes in study.
• There is no graphical management interface as of now, it’s in development. So all management is done through CLI.

Description and idea.

• Code is now used to manage infrastructures and servers with tools such as terraform, docker, kubernetes, ansible, puppet, chef, salt, cfengine, even some things run with vagrant.
• Those tools, while great are not designed for access management.
• So people who have access to servers have access to code and code lives in repositories.
  
• Git is the most used with services such as github, bitbucket, gitlab, etc…
• The use of SSH keys is mainstream to push and pull code.

Since devops, everyone interacting with servers have a username and key in the code repository, why not using those on servers?
If keeping things in sync, removing a user from your repository access would also remove access from servers.

Welcome to centralized!

Here is a diagram on what happens when a new employee joins the team.

Code is here

Installation and administration

Here's the documentation map:

• Concepts
• Preparation
  • github
  • bitbucket
  • Python 3
    • CentOS7
• Run from binaries
  • Run the service from prepared images stored in dockerhub
  • Install clients from signed binaries either manually or from ansible.
    • Ansible role
    • Manual clients install
• Run from source
  • Run the service from source (Not yet documented)
  • Install clients from source (Not yet documented)
• Admin tool usage