Add hook to generate metadata from service profiles
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Thu, 15 Dec 2016 12:28:57 +0000 (14:28 +0200)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Thu, 22 Dec 2016 10:06:17 +0000 (10:06 +0000)
commitd2da59065dd11cbfb6845040697e21e4def35b8f
treee70ffefa9644d8bedffdfce0f59101370536467f
parent33bdba26d668d91f213515a91f8797b9b249d84a
Add hook to generate metadata from service profiles

This enables the deployer to dynamically add nova metadata to the
servers based on the output of service profiles that implement the
metadata_settings key in the role_data output for the profiles.

One can set an implementation via the OS::TripleO::ServerMetadataHook
resource, which currently is set as OS::Heat::None. So, because of
the default implementation, if left untouched it actually does
nothing.

Currently, besides the list, which is metadata_settings, this hook also
takes the name of the node that it's setting the metadata for.

This is useful for nova vendordata plugins that can parse said metadata.

Change-Id: I8a937f711f0b90156fbb6c4632760435ef846474
overcloud-resource-registry-puppet.j2.yaml
overcloud.j2.yaml
puppet/blockstorage-role.yaml
puppet/cephstorage-role.yaml
puppet/compute-role.yaml
puppet/controller-role.yaml
puppet/objectstorage-role.yaml
puppet/role.role.j2.yaml
puppet/services/README.rst
puppet/services/services.yaml