CLI supporting kolla-ansible deployment project
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 88e28815ac OpenDev Migration Patch 1 month ago
doc Updating the cli to work against kolla-ansible 1 year ago
kolla-cli/locale Updating the cli to work against kolla-ansible 1 year ago
kolla_cli Fix bug in updating inventory file from an existing inventory 6 months ago
tools Merge "Check passwords.yml exist before init action" 11 months ago
.gitignore Add .project and .pydevproject into .gitignore 8 months ago
.gitreview OpenDev Migration Patch 1 month ago
.stestr.conf Align tests with how functional tests are handled 1 year ago
.zuul.yaml Gate python3 unittests 11 months ago
LICENSE Adding the Apache LICENSE file, required to be included in the RPM 3 years ago
README.rst Update README.rst 10 months ago
babel.cfg Initial commit 3 years ago Added initial sphinx documentation support for the python api 3 years ago Add ssh key generation to setup script 11 months ago
requirements.txt Update the ansible min version to 2.2.0 10 months ago
setup.cfg Drop py34 target in tox.ini and Python 3.5 is added 9 months ago fixed the property code to work with mainstream kolla changes. ordered property output. 3 years ago
test-requirements.txt Bump ansible_version_min to 2.4 9 months ago
tox.ini fix tox python3 overrides 11 months ago



The Kolla-CLI project provides the ability to more easily manage Kolla-Ansible deployments. It provides both a CLI and a python API that you can use to configure and deploy OpenStack using Kolla-Ansible.

Kolla-Ansible requires that hosts, groups, and services are specified in an inventory file. With Kolla-CLI, you can add/remove hosts, change group associations, etc from the CLI or API. Kolla-Ansible also maintains passwords and various configuration variables in a variety of global, group and host files. With Kolla-CLI, you can now view and change these from the CLI/API.

Finally, Kolla-CLI provides commands to setup the SSH keys on hosts, run deployments and perform upgrades.


The installation process below assumes that the kolla-ansible repository exists at the same level as the kolla-cli repository. This is made clear in the script which makes a relative '../' reference to the kolla-ansible repository. If your kolla-ansible directory is somewhere else then that location can be passed as an argument to the script. The location on the system where the kolla-cli expects the kolla-ansible files to be and installs them to can be tweaked by setting the KOLLA_HOME and KOLLA_ETC environment variables before running the script, and while running the kolla-cli command itself. The default value for KOLLA_HOME is /usr/share/kolla-ansible and the default value for KOLLA_ETC is /etc/kolla.

The following steps can be used to build / run the kolla-cli

  • install ansible and docker
  • virtualenv .venv
  • . .venv/bin/activate
  • pip install -r requirements.txt
  • python install
  • python ./
  • kolla-cli

At that point you will be dropped into the kollacli shell where you can run commands like help or ? to see what commands are available and any of the sub commands can be executed directly.

Alternately you can not use the shell and just execute commands directly via kollacli host add, etc.

If you make changes to the i18n strings (denoted by methods like _("message")) make sure to re-generate the i18n files with the python extract_messages command and check in the files generated in openstack-kollacli.


To use the API, import the ClientAPI into your module:

from kolla_cli.api.client import ClientApi

Then define a global:

CLIENT = ClientApi()

And then you can use that global to execute API commands, for example, to add a host to the inventory:


Getting Involved

Need a feature? Find a bug? Let us know! Contributions are much appreciated and should follow the standard Gerrit workflow.

  • We communicate using the #openstack-kolla irc channel.
  • File bugs, blueprints, track releases, etc on Launchpad.
  • Attend weekly meetings.
  • Contribute code.


Check out who is contributing code and contributing reviews.


If you get an error about missing python.h install the python-dev package via apt-get or yum or whatever mechanism is appropriate for your platform.