Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-959

Configure graceful restart for ovn-controller via ovsdb instead of --restart

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • OVN
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Given the system administrator has configured external-ids:ovn-cleanup-on-exit in OVS DB, 

      When they stop ovn-controller on a node, 

      Then:

      • If ovn-cleanup-on-exit=true, the chassis records should be cleaned up on stop.
      • If ovn-cleanup-on-exit=false, the chassis records should not be cleaned up on stop.
      • If the --restart flag is used alongside external-ids:ovn-cleanup-on-exit=false, a warning is issued, and chassis cleanup is performed.
      • If the --restart flag is used alongside external-ids:ovn-cleanup-on-exit=true, chassis cleanup is not performed.
      Show
      Given the system administrator has configured external-ids:ovn-cleanup-on-exit in OVS DB,  When they stop ovn-controller on a node,  Then: If ovn-cleanup-on-exit=true, the chassis records should be cleaned up on stop. If ovn-cleanup-on-exit=false, the chassis records should not be cleaned up on stop. If the --restart flag is used alongside external-ids:ovn-cleanup-on-exit=false, a warning is issued, and chassis cleanup is performed. If the --restart flag is used alongside external-ids:ovn-cleanup-on-exit=true, chassis cleanup is not performed.
    • rhel-sst-network-fastdatapath
    • ssg_networking

      The service already supports avoiding chassis record cleanup with --restart CLI option. It may be useful, in some scenarios, to be able to control this behavior via ovsdb.

       

      The proposal is to make this possible: ovs-vsctl  -- set Open_vSwitch . external-ids:ovn-cleanup-on-exit=false

       

      The exact behavior proposed is:

       

      1. bare stop_controller - cleanup chassis
      2. stop_controller --restart - don't cleanup chassis
      3. stop_controller + ext_ids:ovn-cleanup-on-exit=true - cleanup chassis
      4. stop_controller + ext_ids:ovn-cleanup-on-exit=false - don't cleanup
      5. stop_controller + ext_ids:ovn-cleanup-on-exit=false  + --restart - warn about mutually exclusive requests; still cleanup
      6. stop_controller + ext_ids:ovn-cleanup-on-exit=true  + --restart - don't cleanup

       

      1-2 are currently implemented. 3 kinda is too since the attribute is not read anyway. 4-6 should be implemented.

       

      This was discussed in Slack.

              ovnteam@redhat.com OVN Team
              ihrachys Ihar Hrachyshka
              Jianlin Shi Jianlin Shi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: