Enable Octavia in DCN

Author: gthiemonge

dt/dcn/control-plane/kustomization.yaml

@@ -77,6 +77,17 @@ replacements:
           - spec.ovn.template.ovnController.external-ids
         options:
           create: true
+  - source:
+      kind: ConfigMap
+      name: service-values
+      fieldPath: data.ovn.template.ovnController.nicMappings
+    targets:
+      - select:
+          kind: OpenStackControlPlane
+        fieldPaths:
+          - spec.ovn.template.ovnController.nicMappings
+        options:
+          create: true
   - source:
       kind: ConfigMap
       name: service-values
@@ -220,3 +231,27 @@ replacements:
           - spec.extraMounts
         options:
           create: true
+
+  - source:
+      kind: ConfigMap
+      name: service-values
+      fieldPath: data.octavia.enabled
+    targets:
+      - select:
+          kind: OpenStackControlPlane
+        fieldPaths:
+          - spec.octavia.enabled
+        options:
+          create: true
+
+  - source:
+      kind: ConfigMap
+      name: service-values
+      fieldPath: data.octavia.template
+    targets:
+      - select:
+          kind: OpenStackControlPlane
+        fieldPaths:
+          - spec.octavia.template
+        options:
+          create: true

dt/dcn/kustomization.yaml

@@ -82,6 +82,7 @@ replacements:
         fieldPaths:
           - spec.networks.[name=storagemgmt].subnets
 
+  # Octavia support
   - source:
       kind: ConfigMap
       name: network-values

examples/dt/dcn/README.md

@@ -20,6 +20,7 @@ This is a collection of CR templates that represent a Red Hat OpenStack Services
     - Cinder Backup using RBD for backend
     - Glance using Multi Store Support and RBD for backend
     - Nova using RBD for ephemeral storage
+- Octavia enabled in DCN sites with split management networks (one management network per DCN site)
 
 ## Considerations
 

examples/dt/dcn/control-plane/scaledown/service-values.yaml

@@ -190,6 +190,40 @@ data:
         network_vlan_ranges = datacentre:1:1000,leaf1:1:1000,leaf2:1:1000
         [neutron]
         physnets = datacentre,leaf1,leaf2
+  octavia:
+    enabled: true
+    template:
+      amphoraImageContainerImage: quay.io/gthiemonge/octavia-amphora-image
+      lbMgmtNetwork:
+        createDefaultLbMgmtNetwork: false
+        lbMgmtRouterGateway: 172.23.0.150
+        availabilityZones:
+          - az0
+      octaviaAPI:
+        networkAttachments:
+          - internalapi
+        customServiceConfig: |
+          [controller_worker]
+          loadbalancer_topology=ACTIVE_STANDBY
+      octaviaHousekeeping:
+        networkAttachments:
+          - octavia
+        customServiceConfig: |
+          [controller_worker]
+          loadbalancer_topology=ACTIVE_STANDBY
+      octaviaHealthManager:
+        networkAttachments:
+          - octavia
+        customServiceConfig: |
+          [controller_worker]
+          loadbalancer_topology=ACTIVE_STANDBY
+      octaviaWorker:
+        networkAttachments:
+          - octavia
+        customServiceConfig: |
+          [controller_worker]
+          loadbalancer_topology=ACTIVE_STANDBY
+
   ovn:
     template:
       ovnController:
@@ -199,6 +233,9 @@ data:
           ovn-bridge: br-int
           ovn-encap-type: geneve
           system-id: random
+        nicMappings:
+          datacentre: ocpbr
+          octavia: octbr
   nova:
     customServiceConfig: |
       [DEFAULT]

examples/dt/dcn/dataplane-post-ceph.md

@@ -104,4 +104,22 @@ of how to DTs should look when AZ1 is removed. To view them run the following co
 
 ```shell
 kustomize build architecture/examples/dt/dcn/control-plane/scaledown/
-```
+```
+
+## Octavia with Availability Zones
+
+When using Octavia with Availability Zones, it needs additional configuration for each AZ in the control plane during the post-Ceph deployment.
+
+For instance, after deploying AZ1:
+
+```yaml
+spec:
+  octavia:
+    enabled: true
+    ...
+    lbMgmtNetwork:
+      availabilityZoneCIDRs:
+        az1: 172.34.0.0/16
+```
+
+The availabilityZoneCIDRs setting creates the Octavia management networks that are used between the control plane and the Octavia Amphora VMs in remote AZs.

examples/dt/dcn/service-values.yaml

@@ -262,6 +262,29 @@ data:
         network_vlan_ranges = datacentre:1:1000,leaf1:1:1000,leaf2:1:1000
         [neutron]
         physnets = datacentre,leaf1,leaf2
+
+  octavia:
+    enabled: true
+    template:
+      amphoraImageContainerImage: quay.io/gthiemonge/octavia-amphora-image
+      lbMgmtNetwork:
+        createDefaultLbMgmtNetwork: false
+        lbMgmtRouterGateway: 172.23.0.150
+        availabilityZones:
+          - az0
+      octaviaAPI:
+        networkAttachments:
+          - internalapi
+      octaviaHousekeeping:
+        networkAttachments:
+          - octavia
+      octaviaHealthManager:
+        networkAttachments:
+          - octavia
+      octaviaWorker:
+        networkAttachments:
+          - octavia
+
   ovn:
     template:
       ovnController:
@@ -271,6 +294,9 @@ data:
           ovn-bridge: br-int
           ovn-encap-type: geneve
           system-id: random
+        nicMappings:
+          datacentre: ocpbr
+          octavia: octbr
   nova:
     customServiceConfig: |
       [DEFAULT]