Monty Taylor baaddcc7c0 Only build tarball once for client libs.
For any given revision, we should only ever create one tarball.
Similarly, we should upload that tarball and only that tarball to
tarballs.openstack.org as well as pypi if it's appropriate to do so.

Library projects are sufficiently different at this point that I made a
different template for them. It would be neat if we could get nested
templates.

Change-Id: Iec81d0d5c0c3a4a8021213fe4bb6884c45fb483a
2012-07-04 11:27:38 -05:00
2012-06-19 16:02:35 +00:00
2012-05-28 16:44:33 +01:00
2011-10-20 13:37:04 -04:00
2012-02-28 16:24:18 -08:00
2012-06-15 23:27:21 -07:00
2012-06-15 23:27:21 -07:00

These are a set of puppet manifests and modules that are currently being used to manage some of the efforts of the OpenStack CI project. They are quite bare and crappy at the moment, but should grow soon.

Additionally, there is a script, make_puppet_lp.py which is used to generate a few lists of users from launchpad teams, to make management and population of user accounts on different types of servers easier.

There are currently two different entry points, the slave.pp and the server.pp manifest.

slave.pp is intended to be for jenkins slaves and adds all members of ~openstack-ci-admins

server.pp is intended as the base for other servers and adds members of ~openstack-admins

Puppet needs to be installed via gems, because we use the pip package provider for one of the packages and that is only in 2.7.

For instance:

/var/lib/gems/1.8/bin/puppet apply --modulepath=pwd/modules manifests/slave.pp

or

/var/lib/gems/1.8/bin/puppet apply --modulepath=pwd/modules manifests/server.pp

Description
System configuration for the OpenDev Collaboratory
Readme 154 MiB
Languages
Jinja 37%
Python 36.7%
Shell 13.6%
Dockerfile 3.9%
JavaScript 3%
Other 5.8%