Map Heat services to isolated networks
authorDan Sneddon <dsneddon@redhat.com>
Wed, 27 May 2015 01:49:24 +0000 (18:49 -0700)
committerDan Sneddon <dsneddon@redhat.com>
Wed, 27 May 2015 07:45:16 +0000 (07:45 +0000)
commit41f0b76907416b8e6ea0f7a7b9de9985b77e79e7
tree63c26dad2b36c1db44a26b7591901cdefa0263aa
parent80b30983386466f08f11c285627c99f7d16d3448
Map Heat services to isolated networks

This change adds parameters to specify which networks the Heat services
will use. If the internal_api network exists, the Heat API, Heat Cloud
Formations, and Heat Cloudwatch services will bind to the IP address on
that network, otherwise the services will default to the IP on the
Undercloud 'ctlplane' network.

Change-Id: I5febe1b9071600b43fa76c6cf415db83cad472ab
overcloud-resource-registry-puppet.yaml
puppet/controller-puppet.yaml