On Thu, Jul 10, 2014 at 02:38:00PM -0700, Gurucharan Shetty wrote: > >> > What about when the controller is on network? You have to have that up > >> > (networking-wise) before bring up the bridge, right? > >> Can you elaborate with an example? > >> > >> I don't know of a use case yet where the controller wants to control a > >> OVS bridge that is also responsible for SSH (or network connections) > >> to the machine (Is there any?). If OVS starts before networking, it > >> can be setup (e.g: through 'interfaces') to have all other bridges in > >> secure mode and they will keep retrying till they get controller > >> connection. > > > > Isn't that the most common use-case? You have a host with ovs bridge > > that needs networking up & running to be able to connect to the > > controller. If you start OVS before that, then it will fail and > > the switch creates flows as needed. > > > > It's possible to use secure mode, but the admin has to consider the > > initialization order to remember to use that option. Maybe secure > > mode should be assumed when a controller is configured into the bridge. > Yes. Otherwise, if you loose connectivity to the controller (assume a > transient network failure), you will start acting like a mac learning > bridge anyways.
I can see pros and cons having either one as default. Also, the Open Flow v1.4.0 6.3.2 "Connection Interruption" let it open to pick any of those modes, so whatever is the default now, it seems fine to me. fbl _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
