d61b4adadf
Without this patch, puppet does not idempotently create the openstackci and openstackjenkins users. Puppet will create the openstackci and openstackjenkins users, but won't assign them any kind of membership in the openstackci and openstackjenkins projects. Then on the second puppet run, puppet tries to check the users' passwords by issuing an 'openstack token issue' command. Without a role, the users can't authenticate and receive a 401. Puppet then reports that it 'changed password' because the password check failed. The name of the role, 'user', is not significant. The strange syntax of the keystone_user_role resource is explained in the keystone module[1]. [1] http://git.openstack.org/cgit/openstack/puppet-keystone/tree/examples/user_project_user_role_composite_namevar.pp Change-Id: I4fb94722ccafb80cdbefa9500b2124a82ddd57cf
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://docs.openstack.org/infra/system-config for more information.
Documentation
The documentation presented at http://docs.openstack.org/infra/system-config comes from git://git.openstack.org/openstack-infra/system-config repo's docs/source. To build the documentation use
$ tox -evenv python setup.py build_sphinx