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

[test-operator][bgp] test pod IPs should be exposed via BGP

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • None
    • test-operator
    • None
    • 8
    • False
    • Hide

      None

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

      On OSP18+BGP setups the CRC/OCP worker is not directly connected (at L2-level) to the external provider network that OSP uses for its FIPs and/or provider network VMs.

      Without any extra configuration, the test pod cannot connect with the VMs on a BGP setup. The problem is that the spine/leaf infrastructure (the routes) don't have the reverse route to the tempest/tobiko pod IP.

       

      This problem can be resolved configuring the test pods with hostNetwork set to True.

      We think this could be the default configuration, not only for BGP, but also to be used with any setup.

              eolivare Eduardo Olivares Toledo
              eolivare Eduardo Olivares Toledo
              rhos-tempest
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: