A lot of this comes down to how OVS is an infrastructure layer. Like GCC or another compiler, it generally has to have a program to run before it is very useful. The documentation for using it in particular scenarios generally belongs in the systems (controllers, etc.) that layer on top of it to accomplish specific tasks.
On Fri, Oct 13, 2017 at 01:31:40PM +0000, Bruce Hartpence wrote: > I have similar questions - it seems as though there is information everywhere > but sometimes you have to dig it out. Does anyone know about a repo that has > a collection of "standard" configs? One example I could use might be when > deploying NFV OVS instances among different hypervisor chassis. > > Bruce Hartpence > Professor, IST Dept., RIT > 585-475-7938 > [email protected] > > CONFIDENTIALITY NOTE: The information transmitted, including attachments, is > intended only for the person(s) or entity to which it is addressed and may > contain confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon this > information by persons or entities other than the intended recipient is > prohibited. If you received this in error, please contact the sender and > destroy any copies of this information. > > From: [email protected] > [mailto:[email protected]] On Behalf Of Omar Ramadan > Sent: Thursday, October 12, 2017 7:55 PM > To: Guru Shetty <[email protected]> > Cc: [email protected] > Subject: Re: [ovs-discuss] OVS bridge on boot in Debian > > > A related question: What is the best way to configure a set of controllers? > Can I specify a set of controllers for my bridge to use in a similar fashion > in networking? > > ________________________________ > From: > [email protected]<mailto:[email protected]> > > <[email protected]<mailto:[email protected]>> > on behalf of Omar Ramadan <[email protected]<mailto:[email protected]>> > Sent: Thursday, October 12, 2017 4:47:10 PM > To: Guru Shetty > Cc: [email protected]<mailto:[email protected]> > Subject: [Potential Spoof] Re: [ovs-discuss] OVS bridge on boot in Debian > > > Looks like I was missing the kernel module. Added "openvswitch-datapath-dkms" > and it works now. > > > > Thanks! > > ________________________________ > From: > [email protected]<mailto:[email protected]> > > <[email protected]<mailto:[email protected]>> > on behalf of Omar Ramadan <[email protected]<mailto:[email protected]>> > Sent: Thursday, October 12, 2017 4:31:24 PM > To: Guru Shetty > Cc: [email protected]<mailto:[email protected]> > Subject: [Potential Spoof] Re: [ovs-discuss] OVS bridge on boot in Debian > > > Hi Guru, Ben, > > > > Thanks for the responses. I originally did a "make install" though I realized > there may be some packaging postinst scripts that may need to be run for it > to work. I built and installed openvswitch-common and openvswitch-switch. > > > "ifup --allow=ovs br0" still fails to find br0 but I've made progress > nonetheless in the networking journal > > vagrant@magma-dev:/etc/network$ sudo journalctl -u networking > Oct 12 23:27:29 magma-dev ovs-vsctl[2127]: ovs|00001|vsctl|INFO|Called as > ovs-vsctl --timeout=5 -- --may-exist add-port br0 eth0 -- > Oct 12 23:27:29 magma-dev networking[1875]: ovs-vsctl: Error detected while > setting up 'eth0'. See ovs-vswitchd log for details. > Oct 12 23:27:29 magma-dev networking[1875]: ovs-vsctl: The default log > directory is "/var/log/openvswitch". > Oct 12 23:27:29 magma-dev ovs-vsctl[2202]: ovs|00001|vsctl|INFO|Called as > ovs-vsctl --timeout=5 -- --may-exist add-port br0 eth0 -- > > vagrant@magma-dev:/var/log/openvswitch$ sudo less ovs-vswitchd.log > 2017-10-12T23:27:31.123Z|00112|ofproto|ERR|failed to open datapath br0: No > such file or directory > 2017-10-12T23:27:31.123Z|00113|bridge|ERR|failed to create bridge br0: No > such file or directory > > What could be missing? > > Best, > Omar > > ________________________________ > From: Guru Shetty <[email protected]<mailto:[email protected]>> > Sent: Thursday, October 12, 2017 10:50:38 AM > To: Omar Ramadan > Cc: [email protected]<mailto:[email protected]> > Subject: Re: [ovs-discuss] OVS bridge on boot in Debian > > > > On 12 October 2017 at 10:29, Omar Ramadan > <[email protected]<mailto:[email protected]>> wrote: > > Hi list, > > > > I am using OVS 2.7.90 with Debian 8.7 and want to configure the switch to be > loaded on system initialization. I have installed the service > "openvswitch-switch" and added the following in /etc/network/interfaces > > How did you install OVS 2.7.90? By 'make install' or via debian packages? > > > > allow-ovs br0 > iface br0 inet dhcp > ovs_type OVSBridge > ovs_ports eth0 > > allow-br0 eth0 > iface eth0 inet manual > ovs_bridge br0 > ovs_type OVSPort > > I am still unable to load br0 with ifup. > > > vagrant@magma-dev:/etc/network/interfaces.d$<mailto:vagrant@magma-dev:/etc/network/interfaces.d$> > sudo ifup br0 > Lets try with: > ifup --allow=ovs br0 > > > Cannot find device "br0" > Bind socket to interface: No such device > > exiting. > Failed to bring up br0. > > How do these interfaces get set up? Is there anyway to debug this? I've built > this package from source, so I want to make sure I am not missing > dependencies. Also should I be adding any additional systemctl units or > should adding "openvswitch-switch" be enough? > > Best, > Omar > > _______________________________________________ > discuss mailing list > [email protected]<mailto:[email protected]> > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=07s_Z0lQVjg7gmpzZt5Yog&m=cIvIKPE2b3yN4d3z9aOIwbQM0etdwuEs_AYVr7Q2Clo&s=-hNIrnwJO4HaR86DPjqOcRpQS_6pBzteYzzhFAFf3yU&e=> > > _______________________________________________ > discuss mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
