[ovs-discuss] help: OVS distributed support questions

Kris zhang zhang.kris at gmail.com
Thu Apr 12 07:18:04 UTC 2012


Thanks a lot, guys,

I still have a question: the libvirt will support the openvswitch in
version 0.9.11 ( http://www.libvirt.org/news.html ) , then why Ovirt need
quantum?
The quantum has the openvswitch plugin too, so is it conflict or duplicate
with the OVS in libvirt?

Thanks,
Kris

On Thu, Apr 12, 2012 at 2:02 AM, Gurucharan Shetty <gshetty at nicira.com>wrote:

> I am copy pasting a draft version of the document. It still needs
> work. It will eventually include information about the C and Python
> bindings that can be used to write to the ovsdb.
>
> --------*---------
> Open vSwitch integrates smoothly with XenServer.  The externally
> visible interface to this integration is hypervisor-agnostic.  We
> encourage anyone who integrates Open vSwitch with a hypervisor to use
> the same interface, because keeping a uniform interface means that
> controllers require less customization for individual hypervisor
> platforms (perhaps no customization at all).
>
> This document describes the suggested Open vSwitch interface to
> hypervisors and the rationale behind it.  The XenServer integration is
> the most mature implementation, so most of the examples are drawn from
> it.
>
> Hypervisor integration centers around the Open vSwitch database and in
> particular the "external-ids" column in several of its tables.  Each
> "external-ids" column contains string key-value pairs.  Nothing inside
> Open vSwitch itself interprets these key-value pairs.  Instead, they
> provide information to a controller that permits the controller to
> associate a database record with a more meaningful entity.  The main
> job of the integrator, then, is to ensure that the various
> "external-ids" are corectly populated and maintained.
>
> For more details about the database and each individual column, please
> refer to the ovs-vswitchd.conf.db(5) manpage.
>
> Open_vSwitch table
> ------------------
> The 'external_ids' column in the 'Open_vSwitch' table can be used to set
> multiple key-value pairs with information about the host/hypervisor running
> OpenvSwitch.  One example for the key is 'system-id' which can uniquely
> identify the hypervisor.
>
> As an example, you can set this using the following ovs-vsctl command.
> ovs-vsctl set bridge xapi2 \
> external-ids:system-id='"1187c97b-9b61-beb3-126f-e53441da9115"'
>
> In XenServer, this will likely be the same as the UUID returned by
> 'xe host-list'.  In a data-center environment, this key may help one to
> distinguish between multiple hosts/hypervisors.
>
> You can set the 'other_config' column with a key-value pair of
> 'enable-statistics="true"'.  This will let you collect hypervisor
> statistics
> like number of CPUs, memory, system load, etc.
>
> You can also set some appropriate values to the 'system_type' and
> 'system_version' columns through ovs-ctl tool that will let you
> differentiate
> between different hosts and different OS versions.
>
> Bridge table
> ------------
> The 'external_ids' column in the 'Bridge' table can be used to set multiple
> key-value pairs with information about a particular bridge.  One example
> for
> the key is 'bridge-id' which can uniquely identify a bridge.  In XenServer,
> this will likely be the same as the UUID returned by 'xe network-list' for
> that particular bridge.  An administrator or controller can use this
> unique key
> to identify a bridge, get its name, and then run some commands for that
> particular bridge.
> ex:
> ovs-vsctl -- --columns=name find bridge \
> external-ids:bridge-id='"1187c97b-9b61-beb3-126f-e53441da9115"'
>
> You can also set the 'other_config' column with a key-value pair of
> 'hwaddr="xx:xx:xx:xx:xx:xx"'.  This field can have the MAC address of the
> bridge.
>
> Interface table
> ---------------
> The 'external_ids' column in the 'Interface' table can be used to set
> multiple
> key-value pairs with information about a particular interface.  Some of the
> examples for the keys are:
>
> attached-mac:
> This field can contain the MAC address of this interface as seen inside a
> VM.
> Typically in Linux based hypervisors, a tap interface is created and the VM
> sees this as a physical NIC with a valid MAC address.  The VM’s kernel
> writes
> L2 frames to this interface and the packet makes it to the bridge.
>
> iface-id:
> This field can contain a value that uniquely identifies the interface.
> In XenServer, this field has the UUID returned by 'xe vif-list' for this
> interface.
>
> vm-id:
> This field can contain a value that uniquely identifies the VM to which
> this
> interface belongs.  A single VM can have multiple interfaces attached to
> it.
> This value can be used to configure or add flows to the bridge based on the
> VMs to which they belong.
>
> An administrator/controller can use the above identifiers to get the
> 'ofport'
> associated with this interface and then manage an OpenFlow flow (?).
> Ex: ovs-vsctl -- --columns=ofport find interface \
> external-ids:attached-mac='"92:a8:d3:65:3f:33"'
>
> Thanks,
> Guru
>
> On Wed, Apr 11, 2012 at 10:31 AM, Ben Pfaff <blp at nicira.com> wrote:
> > Guru (CC'd) is actually working on a document that gives some advice
> > on how we suggest OVS be integrated into a larger system.  Guru, do
> > you have a draft of the document that we can share with Kris and the
> > list?
> >
> > Thanks,
> >
> > Ben.
> >
> > On Wed, Apr 11, 2012 at 11:31:26AM +0800, Kris zhang wrote:
> >> Thank you, Gary and Ben, and do you have any documents to guide me?
> >> Or which project can i get more information about the integrated with
> >> OpenvSwtich?
> >>
> >>
> >> On Wed, Apr 11, 2012 at 1:55 AM, Gary Kotton <gkotton at redhat.com>
> wrote:
> >>
> >> > **
> >> > On 04/10/2012 06:43 AM, Kris zhang wrote:
> >> >
> >> > Actually i want to integrate OVS to Ovirt, is that possible?
> >> >
> >> > Yes, this is certainly possible. At the moment we have a POC with the
> >> > integration of Quantum into oVirt. This is up and running with the OVS
> >> > plugin. Please note that this is in its initial stages and there are
> still
> >> > a number of items that need to be addressed by the Quantum interface.
> >> > Hopefully these will be addressed at the up and coming Folsom summit.
> >> >
> >> > Thanks
> >> > Gary
> >> >
> >> >
> >
> >> _______________________________________________
> >> discuss mailing list
> >> discuss at openvswitch.org
> >> http://openvswitch.org/mailman/listinfo/discuss
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20120412/965a8bd5/attachment.html>


More information about the discuss mailing list