From lrichard at redhat.com Thu Feb 16 20:22:34 2017 Content-Type: multipart/mixed; boundary="===============5897403359908664071==" MIME-Version: 1.0 From: Lance Richardson To: users at ovirt.org Subject: Re: [ovirt-users] questions on OVN Date: Thu, 16 Feb 2017 15:22:33 -0500 Message-ID: <1532365570.108175775.1487276553676.JavaMail.zimbra@redhat.com> In-Reply-To: CAG2kNCy3v37fvp5Pi=Lx3Fug-ykmqZOvPnmCerZxXSEJnruPng@mail.gmail.com --===============5897403359908664071== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable > From: "Gianluca Cecchi" > To: "Marcin Mirecki" > Cc: "Ovirt Users" > Sent: Thursday, February 16, 2017 4:40:46 AM > Subject: Re: [ovirt-users] questions on OVN > = > On Thu, Feb 16, 2017 at 9:54 AM, Marcin Mirecki < mmirecki(a)redhat.com > > wrote: > = > = > = > OVN is aleady using GENEVE, VXLAN or STT tunnels (the user can choose any= ), > so the isolation is already assured. > The scripts provided by ovirt configure a geneve tunnel. > You are free so override this manually to vxlan or stt if you want, let me > know if you need any howto info. > = A small correction/clarification: for hypervisor-hypervisor tunnels, the only tunnel encapsulations that are currently supported are GENEVE and STT. The rationale is explained in detail at http://openvswitch.org/support/dist-docs/ovn-architecture.7.html in the "Design Decisions" section. VXLAN tunnels are supported for hypervisor-gat= eway tunnels only. > yes, please. > I have used in the mean time the vdsm-tool command that takes care of > creating the default geneve tunnel > In my case > vdsm-tool ovn-config 10.4.168.80 10.4.168.81 > = > but I would like to know how to manually use other types too. > I watched the deep dive demo about ovn but at the bottom of the related s= lide > there are three lines that should be equivalent to the above command, > something like > = > ovs-vsctl set open ? external-ids:ovn-remote=3Dtcp: 10.4.168.80:6642 > ovs-vsctl set open ? external-ids:ovn-encap=3Dtype=3Dgeneve > ovs-vsctl set open ? external-ids:ovn-encap-ip=3D10.4.168.81 > = > The ? character seems a dot or a comma, I have not understood the syntax.= ... > (what are the accepted words for type=3D in the second line?) > = The syntax here is "ovs-vsctl set [:]=3D...". In this case, the table name is "Open_vSwitch", "open" can be used as a shorthand because the table name is not case-sensitive and prefixes of the table name are accepted as long as they are unique. The "." character specifies the record name as explained in the ovs-vsctl m= an page at http://openvswitch.org/support/dist-docs-2.5/ovs-vsctl.8.txt: Open_vSwitch Global configuration for an ovs-vswitchd. This table conta= ins exactly one record, identified by specifying . as the rec= ord name. Valid settings for external-ids:ovn-encap-type=3D are given in the ovn-cont= roller man page http://openvswitch.org/support/dist-docs-2.5/ovn-controller.8.txt: external_ids:ovn-encap-type The encapsulation type that a chassis should use to c= on=E2=80=90 nect to this node. Multiple encapsulation types may = be specified with a comma-separated list. Each lis= ted encapsulation type will be paired with ovn-encap-ip. Supported tunnel types for connecting hypervisors = are geneve and stt. Gateways may use geneve, vxlan, or st= t. Due to the limited amount of metadata in vxlan, the ca= pa=E2=80=90 bilities and performance of connected gateways will = be reduced versus other tunnel formats. Hope this helps, Lance > Thanks again, > Gianluca > = > = > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >=20 --===============5897403359908664071==--