Example of passing per-node config data in pre_deploy config
authorSteven Hardy <shardy@redhat.com>
Thu, 20 Aug 2015 12:30:00 +0000 (13:30 +0100)
committerGiulio Fidente <gfidente@redhat.com>
Fri, 25 Sep 2015 18:07:08 +0000 (20:07 +0200)
commit109931bca3e9403abf468f371d9f118e0b5cacf3
tree7ed451501cf06c1ef660d8bd15bff617a2229bf5
parent760fba51566531bef50c2b54eff391dea41a49b6
Example of passing per-node config data in pre_deploy config

Shows one method of passing a map of data in to the pre_deploy extraconfig
interface, such that it could be used in combination with
https://review.openstack.org/#/c/215013/ to create a node uuid specific
hieradata file, or to perform some other non-puppet per-node configuration.

This would be used by specifying an environment file like:
resource_registry:
      OS::TripleO::ControllerExtraConfigPre: puppet/extraconfig/pre_deploy/per_node.yaml
parameter_defaults:
      NodeDataLookup: |
        {"AB4114B1-9C9D-409A-BEFB-D88C151BF2C3": {"foo": "bar"},
         "8CF1A7EA-7B4B-4433-AC83-17675514B1B8": {"foo2": "bar2"}}

Change-Id: I62e344669e0ca781dd93d3f7d2190b70299877c2
puppet/extraconfig/pre_deploy/per_node.yaml [new file with mode: 0644]