[ovs-dev] [PATCH v3] [RFC] ovn: Start work on design documentation.
Ben Pfaff
blp at nicira.com
Fri Feb 27 05:22:57 UTC 2015
On Thu, Feb 26, 2015 at 04:08:47PM +0000, Gray, Mark D wrote:
> > + <li>
> > + Eventually, a user powers on the VM that owns the VIF. On the
> > hypervisor
> > + where the VM is powered on, the integration between the hypervisor
> > and
> > + Open vSwitch (described in <code>IntegrationGuide.md</code>) adds
> > the VIF
> > + to the OVN integration bridge and stores <var>vif-id</var> in
>
> <snip>
>
> What do you mean by OVN integration bridge here? Is it a bridge
> instantiated on the OVS instance running on the host?
Yes.
> Also, will the underlying setup of OVS be the same that is currently set up
> using neutron (i.e. integration bridge with tenants separated by vlans, and
> a physical bridge doing tunnel termination connected by a patch port)?
I don't think that patch ports are necessary for a tunnel-based setup.
I sent out a patch describing what I have in mind:
http://openvswitch.org/pipermail/dev/2015-February/051748.html
More information about the dev
mailing list