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

Investigate if it would be possible to not strictly bound ovn-controller pod to the host

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Normal Normal
    • 2023Q4
    • None
    • openstack-neutron
    • None
    • 2024Q1

      Currently OVNController pods are using HostPath as volumes where ovsdb is stored and it "mimics" behaviour of ovs from OSP-17 and older where ovs is not containerized. But maybe if we would:

      • use some shared storage as volumes to store ovsdb,
      • use persistent hostnames for pods, but not related to the host on which it runs,

      it would be possible to make it more like cloud native application and be able to restart it on new host if needed.

      We need to test that.

              ihrachys Ihar Hrachyshka
              skaplons@redhat.com Slawomir Kaplonski
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: