[ovs-discuss] Bulding OVS network in KVM

Scott Lowe scott.lowe at scottlowe.org
Thu Dec 17 15:33:54 UTC 2015


Please see my responses inline, prefixed by [SL].


> On Dec 17, 2015, at 8:31 AM, Tomasz Osiński <osinstom at gmail.com> wrote:
> 
> Thanks for quick reply! Does this solution allow me to set unique Datapath IDs for each "switch VM" to proper work of my floodlight controller?


[SL] Each "switch VM" will be running its own copy of OVS, so I'm guessing the answer to your question is yes.


> 2015-12-17 16:18 GMT+01:00 Scott Lowe <scott.lowe at scottlowe.org>:
> Please see my response below.
> 
> 
>>> On Dec 17, 2015, at 8:10 AM, Tomasz Osiński <osinstom at gmail.com> wrote:
>>> 
>>> Hello everyone,
>>> 
>>> So far, I have been using mininet with OVS to test my SDN application. Now, i have to configure a test network in my faculty's laboratory.
>>> 
>>> I have access to one server. On this server I have to run 8 virtual machines - 6 VMs with Open vSwitch on them, 1 as VM for controller and 1 for simple HTTP server.
>>> 
>>> I'm pretty new in OVS networking. So my question is how to configure my network? How to configure networking between switches? Every tip/tutorial will be useful!
>> 
>> 
>> What I would probably do would be to run KVM+Libvirt+OVS on the one server in your lab. Define Libvirt networks that are associated with OVS (the Libvirt-OVS integration is fairly well-documented) for the various types of traffic your VMs will need---perhaps you'll need a "management network" and a "data network". For simplicity's sake, I'd probably use different bridges for each network. Then create your VMs and attach them to the appropriate host networks. For example, your "switch VMs" running OVS might have two interfaces: one connected to a management network (over which they'll talk to the controller VM) and one connected to a data network (over which they'll communicate with other switches).
>> 
>> I hope this helps.


--
Scott




More information about the discuss mailing list