485539f618
Our nsd setup relies on the distro provided nsd unit file which doesn't force nsd to wait for networking to be online before starting the service. This is fine if listening on ::1 or :: (or ipv4 equivalents) because those special addrs don't need network to be fully onling. However, we don't listen on those addrs because we have unbound performing local dns for us. Instead we listen on our public interfaces which does require networking to be online first. Thankfully freedesktop.org has a great faq page about this [0] and that basically describes the addition of wanting and aftering network-online.target. We do that through the unit config mechanism described here [1]. [0] https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ [1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-Managing_Services_with_systemd-Unit_Files#brid-Managing_Services_with_systemd-Extending_Unit_Config Change-Id: Ieffe2e239048394e27bd0baf63387f819b17db9c
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