Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-10991

"Preparing networks for Red Hat OpenStack Services on OpenShift" - is missing routed network DCN/Spine-and-Leaf options

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rhos-18.0.4
    • rhos-18.0.2
    • documentation
    • None
    • 8
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Moderate

      This guide should have more details on advanced configuration:

      https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/assembly_preparing-rhoso-networks#proc_creating-the-data-plane-network_preparing_networks

      Please add information on how to configure routes in NNCP, NAD and NetConfig - this is a requirement for DCN and Spine-and-Leaf, but there are also other use-cases - like "I need a special route to reach some server/or network.

      NNCP example:

      We need to explain that thee routes field exist, and how to use it.

      ---
      apiVersion: nmstate.io/v1
      kind: NodeNetworkConfigurationPolicy
      metadata:
        labels:
          osp/nncm-config-type: standard
        name: master-2
        namespace: openstack
      spec:
        desiredState:
          interfaces:
            <....>
          routes:
            config:
            - destination: 192.168.123.0/24
              metric: 150
              next-hop-address: 192.168.122.1
              next-hop-interface: ospbr
            - destination: 192.168.124.0/24
              metric: 150
              next-hop-address: 192.168.122.1
              next-hop-interface: ospbr
            - destination: 172.17.1.0/24
              metric: 150
              next-hop-address: 172.17.0.1
              next-hop-interface: internalapi
            - destination: 172.17.2.0/24
              metric: 150
              next-hop-address: 172.17.0.1
              next-hop-interface: internalapi
            - destination: 172.18.1.0/24 

      NAD example:

      We need to explain that thee routes field exist, and how/when to use it.

      ---
      apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        labels:
          osp/net: tenant
          osp/net-attach-def-type: standard
        name: tenant
        namespace: openstack
      spec:
        config: |
          {
            "cniVersion": "0.3.1",
            "name": "tenant",
            "type": "macvlan",
            "master": "tenant",
            "ipam": {
              "type": "whereabouts",
              "range": "172.19.0.0/24",
              "range_start": "172.19.0.30",
              "range_end": "172.19.0.70",
              "routes": [
                {
                  "dst": "172.19.1.0/24",
                  "gw": "172.19.0.1"
                },
                {
                  "dst": "172.19.2.0/24",
                  "gw": "172.19.0.1"
                }
              ]
            }
          } 

      NetConf example:

      We need to explain that thee routes field exist, and how/when to use it.

      ---
      apiVersion: network.openstack.org/v1beta1
      kind: NetConfig
      metadata:
        name: netconfig
        namespace: openstack
      spec:
        networks:
        - dnsDomain: ctlplane.openstack.lab
          mtu: 1500
          name: ctlplane
          subnets:
          - allocationRanges:
            - end: 192.168.122.120
              start: 192.168.122.100
            - end: 192.168.122.200
              start: 192.168.122.150
            cidr: 192.168.122.0/24
            gateway: 192.168.122.1
            name: subnet1
            routes:
            - destination: 192.168.123.0/24
              nexthop: 192.168.122.1
            - destination: 192.168.124.0/24
              nexthop: 192.168.122.1
          - allocationRanges:
            - end: 192.168.123.120
              start: 192.168.123.100
            - end: 192.168.123.200
              start: 192.168.123.150
            cidr: 192.168.123.0/24
            gateway: 192.168.123.1
            name: subnet2
            routes:
            - destination: 192.168.122.0/24
              nexthop: 192.168.123.1
            - destination: 192.168.124.0/24
              nexthop: 192.168.123.1
          - allocationRanges:
            - end: 192.168.124.120
              start: 192.168.124.100
            - end: 192.168.124.200
              start: 192.168.124.150
            cidr: 192.168.124.0/24
            gateway: 192.168.124.1
            name: subnet3
            routes:
            - destination: 192.168.122.0/24
              nexthop: 192.168.124.1
            - destination: 192.168.123.0/24
              nexthop: 192.168.124.1 

              igallagh@redhat.com Irina Gallagher
              rhn-gps-hjensas Harald Jensas
              rhos-dfg-df
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: