Ian Wienand 84e69a9dd1 Workaround potential systemd failures with a pre-upgrade
As described in the comments, there is potential for systemd to not be
able to enable services after it is upgraded until it is restarted.

I do not think we see this during puppet runs in the gate because we
disable selinux, but it can be triggered (see
I0750de9e75b63190531a3d39a5fcbb19f8e8c49e)

This is a small work-around to pre-install systemd and restart it
before doing the rest of the system upgrades

Change-Id: Ibcb27199f0ecf3b1e3d927be42112e2ebcb5cd79
2015-09-10 16:39:07 +10:00
2014-06-27 12:48:59 -07:00
2015-08-28 12:49:52 +02:00
2015-02-26 15:20:38 -08:00
2014-09-30 12:40:59 -07:00
2013-09-23 18:29:18 +00:00
2015-07-02 12:25:24 -07: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 153 MiB
Languages
Python 37.1%
Jinja 36.7%
Shell 13.6%
Dockerfile 3.8%
JavaScript 3%
Other 5.8%