RETIRED, A service to process unstructured serialized configuration data and facilitate exchange of this data between deployment services such as Fuel or Puppet Master and deployed OpenStack components.
Go to file
Andreas Jaeger 3e4362f2d8 Prepare for using standard python tests
Add simple script to setup mysql and postgresql databases, this script
can be run by users during testing and will be run by CI systems for
specific setup before running unit tests. This is exactly what is
currently done by OpenStack CI in project-config.

This allows to change in project-config the python-db jobs to
python-jobs since python-jobs will call this script initially.

See also
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html

Needed-By: I32f02e904d36ed21a22a1e535b35a15318e1ee16
Change-Id: I70e83ea22be75e6c31428f56c6e68c49976d1eab
(cherry picked from commit 08f2401ddb)
2017-02-08 21:24:12 +01:00
doc/source Add CLI update screencast 2016-04-18 18:25:00 +03:00
examples Put, post operations implemented for environments 2016-08-15 18:54:06 +03:00
specs Scripts for upgrade/downgrade tuningbox DB added 2016-05-31 23:13:40 +03:00
tools Prepare for using standard python tests 2017-02-08 21:24:12 +01:00
tuning_box Resource value modification enhanced in the fuel2 2016-12-09 11:49:11 +00:00
.coveragerc Initial Cookiecutter Commit. 2015-11-25 18:20:28 -08:00
.gitignore Add testdb and .cache to .gitignore 2016-04-12 17:10:14 +03:00
.gitreview Adjust project name in .gitreview 2016-03-18 22:39:37 +03:00
.mailmap Initial Cookiecutter Commit. 2015-11-25 18:20:28 -08:00
.testr.conf Add logging capture to tests 2016-03-13 18:47:43 +03:00
CONTRIBUTING.rst Initial Cookiecutter Commit. 2015-11-25 18:20:28 -08:00
HACKING.rst Initial Cookiecutter Commit. 2015-11-25 18:20:28 -08:00
LICENSE Initial Cookiecutter Commit. 2015-11-25 18:20:28 -08:00
MAINTAINERS Maintainers file added to project 2016-05-22 12:29:01 +00:00
MANIFEST.in Fix MANIFEST.in to inlcude migrations 2016-04-04 14:25:21 +03:00
README.rst Readme file updated 2016-09-16 15:22:01 +00:00
TODO Add template value compilation 2016-01-19 17:14:23 +03:00
alembic.ini Add version_table to alembic.ini for autogenerate to work locally 2016-03-18 22:39:37 +03:00
babel.cfg Initial Cookiecutter Commit. 2015-11-25 18:20:28 -08:00
bindep.txt libpq-dev requirement added 2016-11-18 09:00:27 +00:00
openstack-common.conf Initial Cookiecutter Commit. 2015-11-25 18:20:28 -08:00
requirements.txt Environments operations handled in the fuel2 2016-08-23 17:37:40 +03:00
setup.cfg Hierarchy levels API handled in the fuel2 2016-11-22 04:51:00 +00:00
setup.py Fix tox run issues 2015-11-25 18:33:38 -08:00
test-requirements.txt Components operations handled in the fuel2 2016-08-24 16:51:09 +03:00
tox.ini Ignore warning from a known issue in flask-sqlalchemy in tests 2016-03-23 11:55:04 +03:00

README.rst

Tuning Box

Tuning Box is a configuration storage for your clouds.

Tuning Box can be used as a centralized storage for all configurations. It supports Keystone authentication. By default, Tuning Box installs as a Fuel extension but also it can be run as a service.

Features

ConfigDB entities:

  • Environment
  • Component
  • Hierarchy level
  • Resource definition
  • Resource value
  • Resource value override

Installation

  1. Download Tuning Box RPM package or code to the Fuel Master node. The package can be built from the source code using:

    $ python setup.py bdist_rpm
  2. Tuning Box installs as a Fuel Nailgun extension. Therefore, perform the DB migration and restart the Nailgun service:

    $ nailgun_syncdb
    $ systemctl restart nailgun.service
  3. Configure the Tuning Box keystone service:

    $ export OS_USERNAME=admin OS_PASSWORD=admin OS_PROJECT_NAME=admin OS_AUTH_URL=http://10.20.0.2:5000
    $ openstack service create --name tuning-box config
    $ openstack endpoint create --publicurl http://10.20.0.2:8000/api/config --region RegionOne tuning-box

Now, you have enabled a set of config commands in the fuel2 CLI.

Commands groups for fuel2 CLI

The fuel2 CLI commands groups are the following:

  • config comp - CRUD operations for components
  • config def - CRUD operations for resource definitions
  • config env - CRUD operations for environments
  • config get, config set, config del - CRUD operations for resource values
  • config override, config rm override - operations for resource values overrides