James Slagle cba00abb75 Separate config_volume for ringbuilder ... Use a separate config_volume for swift_ringbuilder puppet_config tasks. This is necessary so that the swift_ringbuilder and swift-storage services don't both rsync files to the same bind mounted directory. The rsync command from docker-puppet.py uses --delete-after, so when they both use the same config_volume, they can end up deleting the files generated by the other (depending on the order of execution). Even though a separate config_volume is used, the rings must still end up in /etc/swift for the swift services containers. An additional container init task is used to copy the ring files into /var/lib/config-data/puppet-generated/swift/etc/swift so that they will be present when the actual swift services containers are started. Change-Id: I05821e76191f64212704ca8e3b7428cda6b3a4b7 Closes-Bug: #1710952		2017-08-28 16:04:45 +00:00
..
process-templates.py	Render isolated network templates using jinja2	2017-07-26 11:43:12 -07:00
releasenotes_tox.sh	Add ReNo support	2017-01-13 14:35:27 -05:00
roles-data-generate-samples.sh	Add in roles data validation	2017-07-07 09:51:40 -06:00
roles-data-generate.py	Add in roles data validation	2017-07-07 09:51:40 -06:00
roles-data-validation.sh	Add in roles data validation	2017-07-07 09:51:40 -06:00
tox_install.sh	Add ReNo support	2017-01-13 14:35:27 -05:00
yaml-nic-config-2-script.py	Replace six.iteritems() with .items()	2017-04-07 15:23:50 +08:00
yaml-validate.py	Separate config_volume for ringbuilder	2017-08-28 16:04:45 +00:00