Reprogram flows when ovs-vswitchd restarts

Bug #1327489 reported by OpenStack Infra
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description
commit d00446be1739c93921e3b88763e05fc194ea9b2b
Author: Kyle Mestery <email address hidden>
Date: Fri May 16 04:21:32 2014 +0000

    Reprogram flows when ovs-vswitchd restarts

    When OVS is restarted, by default it will not reprogram flows which were
    programmed. For the case of the OVS agent, this means a restart will cause
    all traffic to be switched using the NORMAL action. This is undesirable for
    a number of reasons, including obvious security reasons.

    This change provides a way for the agent to check if a restart of ovs-vswitchd
    has happened in the main agent loop. If a restart of ovs-vswitchd is detected,
    the agent will run through the setup of the bridges on the host and reprogram
    flows for all the ports connected.

    This changes adds a new table (table 23) to the integration bridge, with a
    single 'drop' flow. This is used to monitor OVS restarts and to reprogram
    flows from the agent.


    Change-Id: If9e07465c43115838de23e12a4e0087c9218cea2
    Closes-Bug: #1290486
    (cherry picked from commit 8e9f00a19dab98e5cfc7ca32beb9f17ebb5bc1bb)

Tags: neutron
Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

Do we document the flows in the OVS bridges? If not we can set this bug as invalid I guess.

Changed in openstack-manuals:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Tom Fifield (fifieldt) wrote :

confirmed - no action required

Changed in openstack-manuals:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers