
The OpenStack Identity (Keystone) team has decided to split the packaging of the middleware used by external services (both from Keystone and python-keystoneclient) into it's own separate packaging. This is to enable the reduction in dependencies required by the keystoneclient library (some dependencies are specific to servers such as memcache) and allow for releasing fixes to the various middleware code without needing to also release either a fix to Keystone or a fix to the keystoneclient library. The new keystonemiddleware project will be released independent of the OpenStack named-cycle (similar to the client libraries). Further details on this change can be seen in the approved Keystone specification: https://review.openstack.org/#/c/95987/ The upstream repository is an extraction of the middleware from the respective repositories maintaining the commit history. Change-Id: I44a0d59999c720fe9eee99e322138818080b41e0
Puppet Modules
These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.
The main entry point is in manifests/site.pp.
In general, most of the modules here are designed to be able to be run either in agent or apply mode.
These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.
See http://ci.openstack.org for more information.
Documentation
The documentation presented at http://ci.openstack.org comes from git://git.openstack.org/openstack-infra/config repo's docs/source. To build the documentation use
$ tox -evenv python setup.py build_sphinx
Description
Languages
Jinja
36.9%
Python
36.8%
Shell
13.6%
Dockerfile
3.8%
JavaScript
3%
Other
5.9%