On Thu, Jan 09, 2014 at 01:04:33AM -0200, Flavio Leitner wrote: > There is a chicken and egg issue where common OVS > configuration uses a controller which is only accessible > via the network. So starting OVS before network.target > would break those configurations. > > However, the network doesn't come up after boot because > OVS isn't started until after the network scripts tries > to configure the ovs. > > This is partially fixed by commits: > commit: 602453000e28ec1076c0482ce13c284765a84409 > rhel: Automatically start openvswitch service before bringing an ovs > interfa > > commit: 3214851c31538e8690e31f95702f8927a8c0838b > rhel: Add OVSREQUIRES to automatically bring up OpenFlow interface > dependencies > > But still there is the dependency issue between network.target > and openvswitch which this patch fixes it. It provides two systemd > service units. One to run at any time (openvswitch-nonetwork.service) > which runs 'ovs-ctl start' and the other one (openvswith.service) to > run after network.target which works as a frontend to the admin. > > The openvswitch-nonetwork.service is used internally by the > 'ifup-ovs/ifdown-ovs' scripts when adding or removing ports to > the bridge or when the openvswitch.service is enabled by the admin. > > Signed-off-by: Flavio Leitner <f...@redhat.com>
Guru, I guess that you will review this? Thanks, Ben. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
