49b7064601
For compatibility with the custom-roles patches which convert hard-coded hiera mappings (such as opendaylight_api_node_ips) to data generated based on the service_name, we need to either change this name to match the hiera (node_ips and vip) keys, or change the hiera keys to match the service. I took the former approach because it involves less juggling patch dependencies between t-h-t and p-t. Change-Id: Ic179550027f37946097afe0e5b9f504ea19fa7bc Partially-Implements: blueprint custom-roles
15 lines
674 B
YAML
15 lines
674 B
YAML
# A Heat environment that can be used to deploy OpenDaylight with L3 DVR
|
|
resource_registry:
|
|
OS::TripleO::Services::NeutronOvsAgent: OS::Heat::None
|
|
OS::TripleO::Services::ComputeNeutronOvsAgent: OS::Heat::None
|
|
OS::TripleO::Services::OpenDaylight: puppet/services/opendaylight-api.yaml
|
|
OS::TripleO::Services::OpenDaylightOvs: puppet/services/opendaylight-ovs.yaml
|
|
OS::TripleO::Services::NeutronL3Agent: OS::Heat::None
|
|
|
|
parameter_defaults:
|
|
EnableOpenDaylightOnController: true
|
|
NeutronEnableForceMetadata: true
|
|
NeutronMechanismDrivers: 'opendaylight'
|
|
NeutronServicePlugins: "networking_odl.l3.l3_odl.OpenDaylightL3RouterPlugin"
|
|
OpenDaylightEnableL3: "'yes'"
|