RETIRED, further work has moved to Debian project infrastructure
Go to file
Steve Kowalik d1a2269186 Revert "Make keystone_pki less keystone specific"
This breaks the world due to parameters changing.

This reverts commit e5f844d126.

Change-Id: Iad76855a02779018c2e2d3b0b65790ab9c7f7c99
2014-10-10 17:03:20 +11:00
doc/source Sprinkle :: throughout the setup-neutron docs 2014-10-08 11:12:26 +11:00
os_cloud_config Revert "Make keystone_pki less keystone specific" 2014-10-10 17:03:20 +11: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
babel.cfg 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
openstack-common.conf Initial Keystone users, roles, domains, projects 2014-03-24 16:24:06 +01:00
README.rst fix formatting issues in README.rst 2014-10-02 16:42:09 -04:00
requirements.txt Updated from global requirements 2014-09-24 09:01:57 +00:00
setup.cfg Revert "Make keystone_pki less keystone specific" 2014-10-10 17:03:20 +11:00
setup.py Updated from global requirements 2014-06-20 06:50:11 +00:00
test-requirements.txt Updated from global requirements 2014-09-24 09:01:57 +00:00
tox.ini Work toward Python 3.4 support and testing 2014-09-03 19:04:23 +00:00

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.