[ovs-dev] [PATCH 14/14] ofproto: Add support for master/slave controller coordination.

Jeremy Stribling strib at nicira.com
Fri Apr 9 02:47:45 UTC 2010


That's definitely how we'll use it for now, but I thought we had talked 
about not conflating those just in case we wanted to do it differently 
in future.  I don't have a strong opinion about it, though.  I just 
wanted to make sure that those events could be turned off for slaves.

Ben Pfaff wrote:
> I had the notion that slaves didn't receive asynchronous events and that
> masters do.  If that's wrong then I'll update the patch.  We just need
> another bit.
>
> On Thu, Apr 08, 2010 at 05:54:33PM -0700, Jeremy Stribling wrote:
>   
>> This isn't a review, but awesome, this looks like a good set of
>> changes.  One question: I didn't see anything related to subscribing
>> (or not) to asynchronous events.  Did you decide we don't need that
>> after all, or can I expect that in a later patch set?  Thanks,
>>
>> Jeremy
>>
>> Ben Pfaff wrote:
>>     
>>> Now that Open vSwitch has support for multiple simultaneous controllers,
>>> there is some need for a degree of coordination among them.  For now, the
>>> plan is for the controllers themselves to take the lead on this.  This
>>> commit adds a small bit of OVS infrastructure: the ability for a controller
>>> to designate itself as a "master" or a "slave".  There may be at most one
>>> master at a time; when a controller designates itself as the master, then
>>> any existing master is demoted to slave status.  Slave controllers are not
>>> allowed to modify the flow table or global configuration; any attempt to
>>> do so is rejected with a "bad request" error.
>>>
>>> Feature #2495.
>>>       





More information about the dev mailing list