Browse Source

Add OVNEncapType option to the ovn controller template

Since OVN 2.13 it is possible to use vxlan encapsulation in the OVN
tunnel networks.
To do that, it has to be set in the external_ids:ovn-encap-type. There
is support for that in the puppet-ovn module already.
This patch adds missing TripleO-heat-template variable.

Related-bz: #1881697
Change-Id: I54e617745e76f27a4c88156a9b1b17d0255ec837
changes/12/788212/2
Slawek Kaplonski 9 months ago
parent
commit
1542df355b
  1. 8
      deployment/ovn/ovn-controller-container-puppet.yaml

8
deployment/ovn/ovn-controller-container-puppet.yaml

@ -61,6 +61,13 @@ parameters:
If True, then allow plugins that support it to create VLAN
transparent networks.
type: boolean
OVNEncapType:
description: >
Type of encapsulation used in OVN. It can be "geneve" or "vxlan".
type: string
default: "geneve"
constraints:
- allowed_values: ["geneve", "vxlan"]
OVNIntegrationBridge:
description: >
Name of the OVS bridge to use as integration bridge by OVN Controller.
@ -179,6 +186,7 @@ outputs:
"%{hiera('$NETWORK')}"
params:
$NETWORK: {get_param: [ServiceNetMap, NeutronTenantNetwork]}
ovn::controller::ovn_encap_type: {get_param: OVNEncapType}
ovn::controller::ovn_bridge: {get_param: OVNIntegrationBridge}
ovn::controller::hostname: "%{hiera('fqdn_canonical')}"
ovn::controller::ovn_remote_probe_interval: {get_param: OVNRemoteProbeInterval}

Loading…
Cancel
Save