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

Explain ipMasq setting and mention it is not mandatory for all the network-attachment-definitions

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • rhos-18.0.13
    • None
    • documentation
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • BGP sprint 14
    • 1
    • Important

      https://docs.redhat.com/de/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/deploying_a_rhoso_environment_with_distributed_zones/index#proc_attaching-service-pods-to-the-isolated-networks_for_bgp_network_prepare_dz

      we should add a note that explains what the ipMasq does:

      Optional: Set to true to enable IP 
      masquerading for traffic that leaves the virtual network. The source IP 
      address for all traffic is rewritten to the bridge’s IP address. If the 
      bridge does not have an IP address, this setting has no effect. The 
      default value is false.

      with a brief explanation of why this may be needed in certain conditions, for example when the edpm nodes do not have the necessary routes or connectivity to the ctlplane network before frr is configured.

      We could also split the example between ctlplane (where ipMasq: true could be useful, as mentioned) and internalapi and other networks, where we don't need it so it can be set to fale. 

              grakausk@redhat.com Greg Rakauskas
              rhn-support-lmiccini Luca Miccini
              rhos-dfg-networking-squad-bgp
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: