Preparing RHOCP for RHOSP Network Isolation

Networking IP ranges table:

VLAN CIDR NetConfig allocationRange MetalLB IPAddressPool range net-attach-def ipam range OCP worker nncp range

ctlplane

n/a

172.22.0.0/24

172.22.0.100 - 172.22.0-120 172.22.0.150 - 172.22.0.200

172.22.0.80 - 172.22.0.90

172.22.0.30 - 172.22.0.70

172.22.0.10 - 172.22.0.12

external

n/a

172.21.0.0/24

172.21.0.61 - 172.21.0.90

n/a

n/a

n/a

internalapi

20

172.17.0.0/24

172.17.0.100 - 172.17.0.250

172.17.0.80 - 172.17.0.90

172.17.0.30 - 172.17.0.70

172.17.0.10 - 172.17.0.12

storage

21

172.18.0.0/24

172.18.0.100 - 172.18.0.250

172.18.0.80 - 172.18.0.90

172.18.0.30 - 172.18.0.70

172.18.0.10 - 172.18.0.12

tenant

22

172.19.0.0/24

172.19.0.100 - 172.19.0.250

172.18.0.80 - 172.18.0.90

172.19.0.30 - 172.19.0.70

172.19.0.10 - 172.19.0.12

We will be using a preconfigured set of yaml files in the files directory which start with osp-ng-nncp-. There are 3 files for worker nodes.

Change to the files directory:

cd ~/labrepo/content/files

Replace the UUID to the GUID of your environment in the repo files:

find . -type f -exec sed -i 's/UUID/my-guid/g' {} +

Apply preconfigured yamls indivdually:

oc apply -f osp-ng-nncp-w1.yaml
oc apply -f osp-ng-nncp-w2.yaml
oc apply -f osp-ng-nncp-w3.yaml

Wait until they are in an available state before proceeding:

oc get nncp -w

Type Control + C when you see that the nncp has moved to SuccessfullyConfigured state

Sample Output
NAME                                STATUS      REASON
osp-multi-nic-worker-ocp4-worker1   Available   SuccessfullyConfigured
osp-multi-nic-worker-ocp4-worker2   Available   SuccessfullyConfigured
osp-multi-nic-worker-ocp4-worker3   Available   SuccessfullyConfigured

Before proceeding configure a nad resource for each isolated network to attach a service pod to the network:

oc apply -f osp-ng-netattach.yaml

Once the nodes are available and attached configure the MetalLB IP address range using a preconfigured yaml file:

oc apply -f osp-ng-metal-lb-ip-address-pools.yaml

Configure a L2Advertisement resource which will define which node advertises a service to the local network which has been preconfigured for your demo environment:

oc apply -f osp-ng-metal-lb-l2-advertisements.yaml

Run the following command to enable global IP forwarding:

oc patch network.operator cluster -p '{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"gatewayConfig":{"ipForwarding": "Global"}}}}}' --type=merge