RETIRED, further work has moved to Debian project infrastructure
Go to file
Motohiro OTSUKA d1cc364e04 Modify gitignore to ignore cover
Prevent generated coverage report files from being imported.

Change-Id: I9b69c91c95e5dbaac8c52cdc461dd89abd0f4d1c
2014-09-12 15:57:10 +09:00
doc/source Adding timeout parameters to init-keystone 2014-08-26 06:38:30 -07:00
os_cloud_config Merge "Run pki init conditionally" 2014-09-11 08:12:58 +00:00
.coveragerc First post. 2014-03-02 18:05:06 +13:00
.gitignore Modify gitignore to ignore cover 2014-09-12 15:57:10 +09:00
.gitreview Added .gitreview 2014-03-01 01:17:27 +00:00
.mailmap First post. 2014-03-02 18:05:06 +13:00
.testr.conf First post. 2014-03-02 18:05:06 +13:00
CONTRIBUTING.rst First post. 2014-03-02 18:05:06 +13:00
HACKING.rst First post. 2014-03-02 18:05:06 +13:00
LICENSE First post. 2014-03-02 18:05:06 +13:00
MANIFEST.in First post. 2014-03-02 18:05:06 +13:00
README.rst Add some prose to the README 2014-08-28 10:02:56 +10:00
babel.cfg First post. 2014-03-02 18:05:06 +13:00
openstack-common.conf Initial Keystone users, roles, domains, projects 2014-03-24 16:24:06 +01:00
requirements.txt Updated from global requirements 2014-09-03 07:40:51 +00:00
setup.cfg Fix ordering in setup.cfg 2014-08-28 09:52:26 +10:00
setup.py Updated from global requirements 2014-06-20 06:50:11 +00:00
test-requirements.txt Updated from global requirements 2014-09-03 07:40:51 +00:00
tox.ini Fix coverage report generation 2014-07-30 10:39:28 +10:00

README.rst

os-cloud-config

Configuration for OpenStack clouds.

os-cloud-config grew out of the need to call common cloud bring-up tasks, such as initializing Keystone, or configuring Neutron from different code bases. The original code was written in shell, and poorly tested, which led to the need to rewriting it in Python and provided by a distinct module.

Features

  • generate-keystone-pki:
    • Generate a certificate authority and a signing key for use with Keystone Public Key Infrastructure token signing.
  • init-keystone:
    • Initialize Keystone on a host with a provided admin token, admin e-mail and admin password. Also allows optionally changing the region and the public endpoint that Keystone registers with itself.
  • register-nodes:
    • Register nodes with a baremetal service, such as Nova-baremetal or Ironic.
  • setup-endpoints:
    • Register services, such as Glance and Cinder with a configured Keystone.
  • setup-neutron:
    • Configure Neutron at the cloud (not the host) level, setting up either a physical control plane network suitable for deployment clouds, or an external network with an internal floating network suitable for workload clouds.