Andreas Jaeger 3b7a40d7c1 Fix publishing of API Reference
We are publishing at api.openstack.org top-level but the job
is copying to an api-ref subdirectory. Changing the Jenkins setup is the
better solution here than copying directly into publish-docs - it would
create a more complex script.

Remove macro upload-to-api-site and add the publisher directly to the
openstack-api-ref job since this is an exception from the other rules -
and this is the only job publishing to api.o.o.

Change-Id: Ib5511ed7cbf8dfc90cb42e295fe68f39aa1e0a8f
2014-02-22 19:53:22 +01:00
2014-02-22 19:53:22 +01:00
2014-01-28 09:32:09 -08:00
2012-11-30 20:56:32 +00:00
2012-09-22 17:32:02 +00:00
2013-09-23 18:29:18 +00:00
2013-09-23 18:29:18 +00:00
2013-12-10 08:36:42 -08:00
2012-09-10 15:58:27 +00:00
2013-11-12 11:30:34 -05:00

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.

Description
System configuration for the OpenDev Collaboratory
Readme 153 MiB
Languages
Python 37.1%
Jinja 36.7%
Shell 13.6%
Dockerfile 3.8%
JavaScript 3%
Other 5.8%