← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1607724] [NEW] OVS Mech: Set hybrid plug based on agent config

 

Public bug reported:

https://review.openstack.org/327996
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 7a969d4b0a5ae902695b3204a858305b5122c5ff
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Fri Apr 29 18:01:51 2016 -0700

    OVS Mech: Set hybrid plug based on agent config
    
    This adjusts the logic in the OVS mechanism driver to determine
    what the ovs_hybrid_plug value should be set to in the VIF details.
    Previously it was based purely on the firewall driver configured on
    the server side. This prevented a mixed environment where some agents
    might be running a native OVS firewall driver while others are still
    based on the IPTables hybrid driver.
    
    This patch has the OVS agents report back whether they want hybrid
    plugging in their configuration dictionary sent during report_state.
    The OVS agent sets this based on an explicit attribute on the firewall
    driver requesting OVS hybrid plugging.
    
    To maintain backward compat, if an agent doesn't report this, the old
    logic of basing it off of the server-side config is applied.
    
    DocImpact: The server no longer needs to be configured with a firewall
               driver for OVS. It will read config from agent state reports.
    Closes-Bug: #1560957
    Change-Id: Ie554c2d37ce036e7b51818048153b466eee02913
    (cherry picked from commit 2f17a30ba04082889f3a703aca1884b031767942)

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: doc neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1607724

Title:
      OVS Mech: Set hybrid plug based on agent config

Status in neutron:
  New

Bug description:
  https://review.openstack.org/327996
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 7a969d4b0a5ae902695b3204a858305b5122c5ff
  Author: Kevin Benton <kevin@xxxxxxxxxx>
  Date:   Fri Apr 29 18:01:51 2016 -0700

      OVS Mech: Set hybrid plug based on agent config
      
      This adjusts the logic in the OVS mechanism driver to determine
      what the ovs_hybrid_plug value should be set to in the VIF details.
      Previously it was based purely on the firewall driver configured on
      the server side. This prevented a mixed environment where some agents
      might be running a native OVS firewall driver while others are still
      based on the IPTables hybrid driver.
      
      This patch has the OVS agents report back whether they want hybrid
      plugging in their configuration dictionary sent during report_state.
      The OVS agent sets this based on an explicit attribute on the firewall
      driver requesting OVS hybrid plugging.
      
      To maintain backward compat, if an agent doesn't report this, the old
      logic of basing it off of the server-side config is applied.
      
      DocImpact: The server no longer needs to be configured with a firewall
                 driver for OVS. It will read config from agent state reports.
      Closes-Bug: #1560957
      Change-Id: Ie554c2d37ce036e7b51818048153b466eee02913
      (cherry picked from commit 2f17a30ba04082889f3a703aca1884b031767942)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1607724/+subscriptions


Follow ups