5f313f27c9
Presently the ovn-controller service (puppet/services/neutron-compute-plugin-ovn.yaml) is started only on compute nodes. But for the cases where the controller nodes provide the north/south traffic, we need ovn-controller service runninng in controller nodes as well. This patch - Renames the neutron-compute-plugin-ovn.yaml to ovn-controller.yaml which makes more sense and sets the service name as 'ovn-controller'. - Adds the service 'ovn-controller' to Controller and Compute roles. - Adds the missing 'upgrade_tasks' section in ovn-dbs.yaml and ovn-controller.yaml Depends-On: Ie3f09dc70a582f3d14de093043e232820f837bc3 Depends-On: Ide11569d81f5f28bafccc168b624be505174fc53 Change-Id: Ib7747406213d18fd65b86820c1f86ee7c39f7cf5
26 lines
1.1 KiB
YAML
26 lines
1.1 KiB
YAML
# A Heat environment file which can be used to enable OVN
|
|
# extensions, configured via puppet
|
|
resource_registry:
|
|
OS::TripleO::Services::NeutronCorePlugin: OS::TripleO::Services::NeutronCorePluginML2OVN
|
|
OS::TripleO::Services::OVNController: ../puppet/services/ovn-controller.yaml
|
|
OS::TripleO::Services::OVNDBs: ../puppet/services/pacemaker/ovn-dbs.yaml
|
|
# Disabling Neutron services that overlap with OVN
|
|
OS::TripleO::Services::NeutronOvsAgent: OS::Heat::None
|
|
OS::TripleO::Services::ComputeNeutronOvsAgent: OS::Heat::None
|
|
OS::TripleO::Services::NeutronL3Agent: OS::Heat::None
|
|
OS::TripleO::Services::NeutronMetadataAgent: OS::Heat::None
|
|
OS::TripleO::Services::NeutronDhcpAgent: OS::Heat::None
|
|
OS::TripleO::Services::ComputeNeutronCorePlugin: OS::Heat::None
|
|
|
|
parameter_defaults:
|
|
NeutronMechanismDrivers: ovn
|
|
OVNVifType: ovs
|
|
OVNNeutronSyncMode: log
|
|
OVNQosDriver: ovn-qos
|
|
OVNTunnelEncapType: geneve
|
|
NeutronEnableDHCPAgent: false
|
|
NeutronTypeDrivers: 'geneve,vxlan,vlan,flat'
|
|
NeutronNetworkType: 'geneve'
|
|
NeutronServicePlugins: 'qos,ovn-router'
|
|
NeutronVniRanges: ['1:65536', ]
|