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

Consider keeping PVCs with OVN databases on OVNDbCluster:NB/SB removal

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • ovn-operator
    • None
    • 5
    • Neutron Sprint 7, Neutron Sprint 20
    • 2

      Right now we delete the PVC on Cluster removal. An argument can be made that this is correct, because the NB DB can later be reconstructed by Neutron API as needed, and then SB DB can be reconstructed from it too.

       

      There are two counter-arguments for this though:

       

      1. The reconstruction takes a significant time, during which workloads are not connected.
      2. AFAIU Octavia also stores its resources in OVN DB, and it does not run a maintenance task to sync Octavia and OVN databases, so this PVC removal may affect the service.

       

      We should understand the following:

      • what's the general approach for NextGen for PVCs;
      • is it safe to remove OVN NB database;
      • is it safe to remove OVN SB database;
      • is it optimal to do so.

       

      The result of this Spike would be figuring out if this is something that we should change. If so, a separate task should be created to handle the problem. We should also decide if we'd like to keep none, only NB, or both databases.

              egarciar@redhat.com Elvira Garcia
              ihrachys Ihar Hrachyshka (Inactive)
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: