Uploaded image for project: 'ovsdb'
  1. ovsdb
  2. OVSDB-491

Optimize the OvsdbPortUpdateCommand during the ODL reboot/Ovsdb connection

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Medium
    • Resolution: Done
    • None
    • None
    • None
    • None

    Description

      When the Compute is connected or flapped, ODL will retrieve all the Ovsdb
      configuration from the Compute with MonitorCallBack and process the these configurations
      and updates them into the topology operational datastore.
      Currently OvsdbPortUpdateCommand will extract the port information that retrieved from
      compute and update the same to topology operational datastore. Each port update is resulting in
      one database operations.
      In scale setup the number ports will be in big number and will result in huge number of
      database operations to update these port informations.
      It will give us the perfomance improvement if the number of database operations for the
      port updates is done per bridge instead of per port, during Ovsdb connection.
      This will reduce the number of db operations to number bridges instead of number of ports.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            chandra.shekar.s Chandra Shekar S
            chandra.shekar.s Chandra Shekar S
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days
                3d