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

Documentation feedback: Multiple OVNAvailabilityZone Example will not work as expected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • rhos-17.1.4
    • rhos-17.1.4
    • documentation
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Low

      Document link:

      https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/configuring_red_hat_openstack_platform_networking/use-azs-make-network-nodes-ha_rhosp-network#config-network-service-azs-ovn_config_azs

       

      Details:

      Above document includes an example to set multiple OVNAvailabilityZone parameter like OVNAvailabilityZone: 'az-central,az-datacenter2,az-datacenter1' .

      However, this parameter will not set az-datacenter2/az-datacenter1 availability zone as expected.

      This parameter modifies external-ids:ovn-cms-options and colon separated strings are required for openvswitch option like external-ids:ovn-cms-options="enable-chassis-as-gw,availability-zones=az-central:az-datacenter2:az-datacenter1" as documented in  [1].

      When we specified OVNAvailabilityZone parameter according to doc example, external-ids:ovn-cms-options will be set like external-ids:ovn-cms-options="enable-chassis-as-gw,availability-zones=az-central,az-datacenter2,az-datacenter1".

       

      I've tested on my env and colon separated  OVNAvailabilityZone parameter is setting multiple NetworkAZ as I expected.

       

      Thus document example should be changed from comma separated to colon separated.

       

       [1] https://docs.openstack.org/neutron/wallaby/admin/ovn/router_availability_zones.html

       

              grakausk@redhat.com Greg Rakauskas
              jishii@redhat.com1 Jun Ishii
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: