RETIRED, CLI supporting kolla-ansible deployment project
Go to file
jacky06 cb017ed845 Use unittest.mock instead of third party mock
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.

Change-Id: I6101cb044ee0fc2a7be95352569782eaf0b938aa
2020-04-06 12:33:06 +08:00
doc [ussuri][goal] Drop python 2.7 support and testing 2020-03-01 10:46:00 +00:00
kolla-cli/locale Updating the cli to work against kolla-ansible 2018-04-17 09:45:35 -07:00
kolla_cli Use unittest.mock instead of third party mock 2020-04-06 12:33:06 +08:00
releasenotes [ussuri][goal] Drop python 2.7 support and testing 2020-03-01 10:46:00 +00:00
tools Merge "Check passwords.yml exist before init action" 2018-06-20 18:45:23 +00:00
.gitignore Add cover into zuul check 2019-07-12 09:45:09 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:32:44 +00:00
.stestr.conf Align tests with how functional tests are handled 2018-05-16 16:13:54 -04:00
.zuul.yaml [ussuri][goal] Drop python 2.7 support and testing 2020-03-01 10:46:00 +00:00
LICENSE Adding the Apache LICENSE file, required to be included in the RPM 2015-08-27 13:39:31 -07:00
README.rst Update sphinx for doc/requirements.txt 2020-01-14 21:36:14 +08:00
babel.cfg Initial commit 2015-07-15 13:34:36 -07:00
cli_setup.py Do not always copy files 2019-08-13 14:24:15 +08:00
lower-constraints.txt Use unittest.mock instead of third party mock 2020-04-06 12:33:06 +08:00
requirements.txt Bump docker_version_min to 1.10.0 2019-07-21 17:43:38 +08:00
setup.cfg [ussuri][goal] Drop python 2.7 support and testing 2020-03-01 10:46:00 +00:00
setup.py fixed the property code to work with mainstream kolla changes. ordered property output. 2015-08-20 13:05:04 -07:00
test-requirements.txt Use unittest.mock instead of third party mock 2020-04-06 12:33:06 +08:00
tox.ini Use unittest.mock instead of third party mock 2020-04-06 12:33:06 +08:00

README.rst

Kolla-CLI

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.

Installing

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 cli_setup.py 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 cli_setup.py 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 cli_setup.py 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 setup.py install
  • python ./cli_setup.py
  • 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 setup.py extract_messages command and check in the files generated in openstack-kollacli.

API

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:

CLIENT.host_add(['host_name'])

Generating Documentation

We use Sphinx to maintain the documentation. You can install Sphinx using pip.

$ pip install -U Sphinx

In addition to Sphinx you will also need the following requirements (covered by doc/requirements.txt):

$ pip install openstackdocstheme reno 'reno[sphinx]'

The source code of the documentation are under doc, you can generate the html files using the following command. If the generation succeeds,a build/html dir will be created under doc.

$ cd doc
$ make html

Now you can serve the documentation at http://localhost:8080 as a simple website.

$ cd build/html
$ python -m SimpleHTTPServer 8080

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.

Contributors

Check out who is contributing code and contributing reviews.

Troubleshooting

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.