To gain access to the cookiecutter repository, please send a request to email@example.com.
To prepare the configuration repository, you need the tool Cookiecutter.
You need a Git repository to store the configuration of the environment. It has to be accessible from the manager node. A SSH deploy key for read-only access is sufficient.
Before you create the configuration, you need some basic information:
FQDNs and IP addresses for the API endpoints
desired versions of OSISM, OpenStack, Ceph and Docker
CIDRs of networks for Ceph
SSL certificate, if one is used
After the deployment of the manager, it is possible to generate a self-signed SSL certificate using an included Ansible playbook. See Generate self-signed certificates for more information.
Usually you prepare and edit the configuration on your workstation. It is pushed to a central Git server and pulled from the manager node later.
It is recommended to always use a virtual environment when you install packages from PyPI.
$ virtualenv -p python3 .venv $ source .venv/bin/activate $ pip3 install \ ansible \ cookiecutter \ cryptography \ oslo.utils \ paramiko \ passlib \ pycrypto \ pykeepass \ python-gilt \ pyyaml \ ruamel.yaml \ yamllint
When you run cookiecutter, you are asked for the information you collected before.
A list with all parameters can be found in the
cookiecutter.json configuration file.
A description of the individual parameters can be found in the README file of the repository.
$ cookiecutter ssh://firstname.lastname@example.org:10022/generic/cookiecutter.git with_ceph : with_monitoring : with_vault : ceph_fsid [Use a great UUID here]: [...]
Push the contents of the newly created
cfg-customer directory to your Git repository. Be careful
not to forget dotfiles like
.gitignore. The directory itself is not stored in the repository.