aboutsummaryrefslogtreecommitdiffstats
path: root/overcloud-source.yaml
diff options
context:
space:
mode:
authorDan Prince <dprince@redhat.com>2014-10-22 14:22:44 -0400
committerDan Prince <dprince@redhat.com>2015-01-05 13:53:24 -0500
commit6812f6f644914da6d4b1c62230517cdd29b1e5f9 (patch)
tree330bd827e6f890e8d420c079194caef3229b75fb /overcloud-source.yaml
parent733339df912c2d8a488c2e823c83904febed8581 (diff)
Puppet: overcloud compute config
This patch provides an alternate implementation of the OS::TripleO::Compute::SoftwareConfig which uses Puppet to drive the configuration. Using this it is possible to create a fully functional overcloud compute instance which has the compute node configured via Puppet stackforge modules. This includes all the Nova, Neutron, and Ceilometer configuration required to make things work. In order to test this you'll want to build your images with these elements: os-net-config heat-config-puppet puppet-modules hiera None of the OpenStack specific TripleO elements should be used with this approach (the nova/neutron/ceilometer elements were NOT used to build the compute image). Also, rather than use neutron-openvswitch-agent to configure low level networking it is recommended that os-net-config by configured directly via heat modeling rather than parameter passing to init-neutron-ovs. This allows us to configure the physical network while avoiding the coupling to the neutron-openvswitch-element that our standard parameter driven networking currently uses. (We still need to move init-neutron-ovs so that it isn't coupled and/or deprecate its use entirely because the heat drive stuff is more flexible.) Packages may optionally be pre-installed via DIB using the -p option (-p openstack-neutron,openstack-nova). Change-Id: Ic36be25d70f0a94ca07ffda6e0005669b81c1ac7
Diffstat (limited to 'overcloud-source.yaml')
0 files changed, 0 insertions, 0 deletions