Chapter 8. Configuring network settings after installing OpenStack

1. Show the port:

   $ openstack port show <cluster_name>-<cluster_ID>-ingress-port

2. Attach the port to the IP address:

   $ openstack floating ip set --port <ingress_port_ID> <apps_FIP>

3. Add a wildcard

   A

   record for

   *apps.

   to your DNS file:

   *.apps.<cluster_name>.<base_domain>  IN  A  <apps_FIP>

Procedure

1. Create an

   SriovNetworkNodePolicy

   policy for the two

   hw-offload

   type VF interfaces that are on your cluster:

   The first virtual function interface

   apiVersion: sriovnetwork.openshift.io/v1
   kind: SriovNetworkNodePolicy 

   1

   
   metadata:
     name: "hwoffload9"
     namespace: openshift-sriov-network-operator
   spec:
     deviceType: netdevice
     isRdma: true
     nicSelector:
       pfNames: 

   2

   
       - ens6
     nodeSelector:
       feature.node.kubernetes.io/network-sriov.capable: 'true'
     numVfs: 1
     priority: 99
     resourceName: "hwoffload9"

   1

   Insert the SriovNetworkNodePolicy value here.

   2

   Both interfaces must include physical function (PF) names.

   The second virtual function interface

   apiVersion: sriovnetwork.openshift.io/v1
   kind: SriovNetworkNodePolicy 

   1

   
   metadata:
     name: "hwoffload10"
     namespace: openshift-sriov-network-operator
   spec:
     deviceType: netdevice
     isRdma: true
     nicSelector:
       pfNames: 

   2

   
       - ens5
     nodeSelector:
       feature.node.kubernetes.io/network-sriov.capable: 'true'
     numVfs: 1
     priority: 99
     resourceName: "hwoffload10"

   1

   Insert the SriovNetworkNodePolicy value here.

   2

   Both interfaces must include physical function (PF) names.

2. Create

   NetworkAttachmentDefinition

   resources for the two interfaces:

   A NetworkAttachmentDefinition resource for the first interface

   apiVersion: k8s.cni.cncf.io/v1
   kind: NetworkAttachmentDefinition
   metadata:
     annotations:
       k8s.v1.cni.cncf.io/resourceName: openshift.io/hwoffload9
     name: hwoffload9
     namespace: default
   spec:
       config: '{ "cniVersion":"0.3.1", "name":"hwoffload9","type":"host-device","device":"ens6"
       }'

   A NetworkAttachmentDefinition resource for the second interface

   apiVersion: k8s.cni.cncf.io/v1
   kind: NetworkAttachmentDefinition
   metadata:
     annotations:
       k8s.v1.cni.cncf.io/resourceName: openshift.io/hwoffload10
     name: hwoffload10
     namespace: default
   spec:
       config: '{ "cniVersion":"0.3.1", "name":"hwoffload10","type":"host-device","device":"ens5"
       }'

3. Use the interfaces that you created with a pod. For example:

   A pod that uses the two OVS offload interfaces

   apiVersion: v1
   kind: Pod
   metadata:
     name: dpdk-testpmd
     namespace: default
     annotations:
       irq-load-balancing.crio.io: disable
       cpu-quota.crio.io: disable
       k8s.v1.cni.cncf.io/resourceName: openshift.io/hwoffload9
       k8s.v1.cni.cncf.io/resourceName: openshift.io/hwoffload10
   spec:
     restartPolicy: Never
     containers:
     - name: dpdk-testpmd
       image: quay.io/krister/centos8_nfv-container-dpdk-testpmd:latest

Procedure

1. Create a file named

   network.yaml

   from the following template:

   spec:
     additionalNetworks:
     - name: hwoffload1
       namespace: cnf
       rawCNIConfig: '{ "cniVersion": "0.3.1", "name": "hwoffload1", "type": "host-device","pciBusId": "0000:00:05.0", "ipam": {}}' 

   1

   
       type: Raw

   where:

   pciBusId

   Specifies the device that is connected to the offloading network. If you do not have it, you can find this value by running the following command:

   $ oc describe SriovNetworkNodeState -n openshift-sriov-network-operator

2. From a command line, enter the following command to patch your cluster with the file:

   $ oc apply -f network.yaml

Procedure

1. Define pods that use your IPv6 namespace and the annotation

   k8s.v1.cni.cncf.io/networks: <additional_network_name>

   , where

   <additional_network_name

   is the name of the additional network. For example, as part of a

   Deployment

   object:

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: hello-openshift
     namespace: ipv6
   spec:
     affinity:
       podAntiAffinity:
         requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
               matchExpressions:
               - key: app
                 operator: In
                 values:
                 - hello-openshift
     replicas: 2
     selector:
       matchLabels:
         app: hello-openshift
     template:
       metadata:
         labels:
           app: hello-openshift
         annotations:
           k8s.v1.cni.cncf.io/networks: ipv6
       spec:
         securityContext:
           runAsNonRoot: true
           seccompProfile:
             type: RuntimeDefault
         containers:
         - name: hello-openshift
           securityContext:
             allowPrivilegeEscalation: false
             capabilities:
               drop:
               - ALL
           image: quay.io/openshift/origin-hello-openshift
           ports:
           - containerPort: 8080

2. Create the pod. For example, on a command line, enter the following command:

   $ oc create -f <ipv6_enabled_resource> 

   1

   1

   Specify the file that contains your resource definition.

Procedure

1. To edit the Cluster Network Operator (CNO), enter the following command:

   $ oc edit networks.operator.openshift.io cluster

2. Specify your CNI configuration under the

   spec

   field. For example, the following configuration uses a SLAAC address mode with MACVLAN:

   ...
   spec:
     additionalNetworks:
     - name: ipv6
       namespace: ipv6 

   1

   
       rawCNIConfig: '{ "cniVersion": "0.3.1", "name": "ipv6", "type": "macvlan", "master": "ens4"}' 

   2

   
       type: Raw

   1

   Be sure to create pods in the same namespace.

   2

   The interface in the network attachment "master" field can differ from "ens4" when more networks are configured or when a different kernel driver is used.

   Note

   If you are using stateful address mode, include the IP Address Management (IPAM) in the CNI configuration.

   DHCPv6 is not supported by Multus.

3. Save your changes and quit the text editor to commit your changes.