WIP: Add BGP DT03 IPv6

automation/mocks/bgp_dt03_ipv6.yaml

@@ -0,0 +1,2 @@
+---
+cifmw_ci_gen_kustomize_values_primary_ip_version: 6

automation/vars/bgp.yaml

@@ -129,3 +129,81 @@ vas:
           - name: edpm-deployment-values
             src_file: values.yaml
         build_output: edpm-deployment.yaml
+  bgp_dt03_ipv6:
+    stages:
+      - pre_stage_run:
+          - name: Apply taint on worker-3
+            type: cr
+            definition:
+              spec:
+                taints:
+                  - effect: NoSchedule
+                    key: testOperator
+                    value: 'true'
+                  - effect: NoExecute
+                    key: testOperator
+                    value: 'true'
+            kind: Node
+            resource_name: worker-3
+            state: patched
+        path: examples/dt/bgp/bgp_dt03_ipv6/control-plane/nncp
+        wait_conditions:
+          - >-
+            oc -n openstack wait nncp
+            -l osp/nncm-config-type=standard
+            --for jsonpath='{.status.conditions[0].reason}'=SuccessfullyConfigured
+            --timeout=60s
+        values:
+          - name: network-values
+            src_file: values.yaml
+        build_output: nncp.yaml
+
+      - path: examples/dt/bgp/bgp_dt03_ipv6/control-plane
+        wait_conditions:
+          - >-
+            oc -n openstack wait openstackcontrolplane
+            controlplane
+            --for condition=Ready
+            --timeout=30m
+        values:
+          - name: network-values
+            src_file: nncp/values.yaml
+          - name: service-values
+            src_file: service-values.yaml
+        build_output: control-plane.yaml
+
+      - path: examples/dt/bgp/bgp_dt03_ipv6/edpm/networkers
+        wait_conditions:
+          - >-
+            oc -n openstack wait openstackdataplanenodeset
+            networker-nodes
+            --for condition=SetupReady
+            --timeout=600s
+        values:
+          - name: edpm-networker-nodeset-values
+            src_file: values.yaml
+        build_output: edpm-networker-nodeset.yaml
+
+      - path: examples/dt/bgp/bgp_dt03_ipv6/edpm/computes
+        wait_conditions:
+          - >-
+            oc -n openstack wait openstackdataplanenodeset
+            compute-nodes
+            --for condition=SetupReady
+            --timeout=600s
+        values:
+          - name: edpm-compute-nodeset-values
+            src_file: values.yaml
+        build_output: edpm-compute-nodeset.yaml
+
+      - path: examples/dt/bgp/bgp_dt03_ipv6/edpm/deployment
+        wait_conditions:
+          - >-
+            oc -n openstack wait openstackdataplanedeployment
+            edpm-deployment
+            --for condition=Ready
+            --timeout=3800s
+        values:
+          - name: edpm-deployment-values
+            src_file: values.yaml
+        build_output: edpm-deployment.yaml

examples/dt/bgp/bgp_dt03_ipv6/README.md

@@ -0,0 +1,109 @@
+# RHOSO Deployed Topology - BGP DT01 - Kernel routing and OVN NB DB driver
+
+This document describes the first BGP Deployed Topology (DT), used to test the
+BGP Dynamic Routing functionality on Red Hat OpenStack Services on OpenShift
+(RHOSO).
+
+The CRs included within this DT should be applied on an environment where EDPM
+and OCP nodes are connected through a spine/leaf network. The BGP protocol
+should be enabled on those spine and leaf routers.
+
+## Purpose
+
+This first BGP DT (DT01) tests default BGP configuration:
+* Kernel routing (instead of OVN routing)
+* OVN NB DB driver (instead of OVN SB DB driver)
+
+The OCP cluster consists on the following nodes:
+* 3 OCP master nodes
+* 3 OCP worker nodes
+* 1 OCP worker node with special configuration (OCP tester node)
+
+This DT creates an OCP cluster that includes both master and worker nodes,
+instead of the usual master/worker combo nodes. The reason for this is to run
+disruptive tests only on the OCP workers, which host the Openstack Control
+Plane services, avoiding potential issues when OCP master nodes are disrupted
+that would not be relevant when testing RHOSO high availability scenarios.
+
+The extra OCP worker (OCP tester) is needed to run tests from it because:
+* disruptive tests can be run from this worker on the other workers without
+  affecting the test exection
+* this worker is connected to the spine/leaf routers with a special routing
+  configuration, so that it can reach the Openstack provider network
+The OCP tester is configured so that only test pods (created by the
+Openstack test-operator) run on it.
+
+This DT configures both compute and networker EDPM nodes. So far, networker
+nodes are needed when BGP is used on RHOSO, in order to expose routes to SNAT
+traffic (OVN Gateway IPs). In other words, when RHOSO is used with BGP, the OCP
+workers cannot be configured as OVN Gateways.
+
+The OCP and EDPM nodes deployed with this DT are distributed into three
+different racks. Each rack is connected to two leaves.
+Hence, the distribution of the nodes in the racks is the following one:
+* rack0: compute-0, networker-0, ocp-master-0, ocp-worker-0, leaf-0, leaf-1
+* rack1: compute-1, networker-1, ocp-master-1, ocp-worker-1, leaf-2, leaf-3
+* rack2: compute-2, networker-2, ocp-master-2, ocp-worker-2, leaf-4, leaf-5
+
+The OCP tester (ocp-worker-3) is not included into any rack. It is not
+connected to any leaves, but to a router connected to the spines, due to the
+reasons described before (it needs special connectivity to reach the provider
+network).
+
+## Node topology
+| Node role               | bm/vm | amount |
+| ----------------------- | ----- | ------ |
+| Openshift master nodes  | vm    | 3      |
+| Openshift worker nodes  | vm    | 4      |
+| Openstack Computes      | vm    | 3      |
+| Openstack Networker     | vm    | 3      |
+| Leaf routers            | vm    | 6      |
+| Spine routers           | vm    | 2      |
+| External routers        | vm    | 1      |
+| Ansible Controller      | vm    | 1      |
+
+### Networks
+
+| Name                     | Type     | CIDR             |
+| ------------------------ | -------- | ---------------- |
+| Provisioning             | untagged | 192.168.122.0/24 |
+| Provider network         | untagged | 192.168.133.0/24 |
+| RH OSP                   | untagged | 192.168.111.0/24 |
+| edpm/ocp to left leaves  | untagged | 100.64.x.y/30    |
+| edpm/ocp to right leaves | untagged | 100.65.x.y/30    |
+
+## Services, enabled features and configurations
+
+| Service          | configuration    | Lock-in coverage?  |
+| ---------------- | ---------------- | ------------------ |
+| Glance           | Swift            | Must have          |
+| Swift            | (default)        | Must have          |
+| Octavia          | (default)        | Must have          |
+| Heat             | (default)        | Must have          |
+| frr              | dataplane        | Must have          |
+| ovn-bgp-agent    | dataplane        | Must have          |
+
+## Considerations/Constraints
+
+1. Virtual networks should be created to connect the nodes to the routers.
+2. All the VMs that are neither Openstack nor Openshift nodes, i.e. those that
+   act as routers, need to be properly configured in order to support the BGP
+   protocol.
+3. The spine/leaf topology separates the overcloud nodes into different L2
+   network segments, called racks. Each rack includes two leaves, some OCP
+   nodes and some EDPM nodes.
+4. A separate provisioning network is necessary to install Openstack on those
+   nodes.
+5. Once Openstack is installed on them, dataplane connectivity is achieved
+   using the BGP protocol.
+6. Tests are executed from the OCP worker to verify external connectivity.
+
+## Stages
+
+All stages must be executed in the order listed below. Everything is required unless otherwise indicated.
+
+1. [Configure taints on the OCP worker](configure-taints.md)
+2. [Install the OpenStack K8S operators and their dependencies](../../../common/)
+3. [Apply metallb customization required to run a speaker pod on the OCP tester node](metallb/)
+4. [Configuring networking and deploy the OpenStack control plane](control-plane.md)
+5. [Configure and deploy the dataplane - networker and compute nodes](data-plane.md)

examples/dt/bgp/bgp_dt03_ipv6/configure-taints.md

@@ -0,0 +1,21 @@
+# Apply taints on OCP tester node
+
+This OCP worker node should not run any Openstack service apart from those
+created by the test-operator.
+It should also run a metallb's speaker pod, in order to obtain the proper
+network configuration.
+Due to this, taints should be configured on this worker.
+
+Execute the following command:
+```
+oc patch node/worker-3 --type merge --patch '
+  spec:
+    taints:
+      - effect: NoSchedule
+        key: testOperator
+        value: "true"
+      - effect: NoExecute
+        key: testOperator
+        value: "true"
+'
+```

examples/dt/bgp/bgp_dt03_ipv6/control-plane.md

@@ -0,0 +1,57 @@
+# Configuring networking and deploy the OpenStack control plane
+
+## Assumptions
+
+- A storage class called `local-storage` should already exist.
+- An infrastructure of spine/leaf routers exists, is properly connected to the
+  OCP nodes and the routers are configured to support BGP.
+
+## Initialize
+
+Switch to the "openstack" namespace
+```
+oc project openstack
+```
+Change to the bgp_dt01/control-plane directory
+```
+cd architecture/examples/dt/bgp/bgp_dt01/control-plane
+```
+Edit the [nncp/values.yaml](control-plane/nncp/values.yaml) and
+[service-values.yaml](control-plane/service-values.yaml) files to suit 
+your environment.
+```
+vi nncp/values.yaml
+vi service-values.yaml
+```
+
+## Apply node network configuration
+
+Generate the node network configuration
+```
+kustomize build nncp > nncp.yaml
+```
+Apply the NNCP CRs
+```
+oc apply -f nncp.yaml
+```
+Wait for NNCPs to be available
+```
+oc wait nncp -l osp/nncm-config-type=standard --for jsonpath='{.status.conditions[0].reason}'=SuccessfullyConfigured --timeout=300s
+```
+
+## Apply networking and control-plane configuration
+
+Generate the control-plane and networking CRs.
+```
+kustomize build > control-plane.yaml
+```
+Apply the CRs
+```
+oc apply -f control-plane.yaml
+```
+
+Wait for control plane to be available
+```
+oc wait osctlplane controlplane --for condition=Ready --timeout=600s
+```
+