On Thu, Aug 23, 2012 at 6:56 PM, Gurucharan Shetty <gshe...@nicira.com> wrote: > > Does this help for your use case? > http://openvswitch.org/pipermail/dev/2012-May/016972.html > > The scripts are all there. But, someone needs to call it. > > ifup --allow=ovs $list_of_bridges
Interesting. I haven't applied this to my system but if I am understanding it correctly, this actually configures OVS on boot via /etc/network/interfaces. I'm still not convinced it would work since /etc/init.d/networking is called before openvswitch is running. I like the idea of configuring openvswitch in this manner however it would kill any ability to make permanent changes via the ovs-* commands which is a paradigm shift from what I have gathered from the documentation. Maybe I am wrong but it seems like the expected workflow is something on the order of: 0) Install OVS 1) Configure OVS resources (using: ovs-vsctl ...) 2) Configure /etc/network/interfaces to generically reference OVS resources 3) Cross fingers and reboot The above would modify it to: 0) Install OVS 1) Configure /etc/network/interfaces to configure OVS 2) Cross fingers and reboot Thus eliminating any direct interaction with OVS. Thanks, -Tim _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
