tripleo-heat-templates

History

Ryan Hefner e284daa1ff Fix Puppet Configuring NetApp Cinder Backend It was incorrectly assumed that Puppet variables assigned to a defined class (as seen in cinder-netapp.yaml) would be applied to any resources created with that type. This is not how Puppet works. The full range of configuration parameters to cinder::backend::netapp have been added back in. They are still pulling from Hiera like they were intended before, but it needs to be a little more explicit for Puppet to be happy. Change-Id: I2e00eae829713b2dbb1e4a5f296b6d08d0c21100		2015-07-20 11:09:44 -04:00
..
controller	Fix Puppet Configuring NetApp Cinder Backend	2015-07-20 11:09:44 -04:00
default.yaml	Wire in Controller pre-deployment extraconfig	2015-07-06 10:56:11 -04:00
README	Wire in Controller pre-deployment extraconfig	2015-07-06 10:56:11 -04:00

README

This tree contains additional configuration which happens "pre deployment",
e.g before the OpenStack services themselves are configured but after the
nodes themselves have been provisioned and initially configured.

Typically for puppet deployments these additional configs will put in place
hieradata which is then consumed by the subsequent puppet configuration
which occurs during the post-deployment phase.

If you need to specify multiple configs, you can chain them together in a
template, see the multiple.yaml example:

  OS::TripleO::ControllerExtraConfigPre: puppet/extraconfig/pre_deploy/controller/multiple.yaml