Sean Dague 376582d98b Create stable order for CI results stable
One of the regressions in our pipeline fix was that Jenkins no longer
ends up on top of the results list. From a UX perspective pinning
first party results to the top of the list was very important, because
that's the first thing most people are looking for.

This reintroduces that, plus creates a stable (alphabetic) ordering of
all non first party reporters so that we get a stable reporting order,
and not an order that is merely based on who showed up first.

Change-Id: Idd38a047bc73bfe3d7ecc89291c10c0fefbfe665
2016-05-12 13:00:52 -04:00
2016-05-06 19:43:35 -07:00
2015-09-02 22:44:56 -04:00
2016-03-30 10:10:12 -04:00
2015-02-26 15:20:38 -08:00
2016-05-02 18:48:38 -07:00
2014-09-30 12:40:59 -07:00
2013-09-23 18:29:18 +00:00
2015-12-28 19:43:23 +01:00

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

Description
System configuration for the OpenDev Collaboratory
Readme 154 MiB
Languages
Jinja 36.9%
Python 36.8%
Shell 13.6%
Dockerfile 3.8%
JavaScript 3%
Other 5.9%