Hi Mark. Thanks for this review and your other one on this commit. For most of your comments, the answer is that I should add some more documentation, or some more clarifications to the existing documentation. I'll do that in a patch a little bit later. For the moment, since the overall design seems solid, I've pushed this commit as a new branch "ovn".
On Thu, Feb 26, 2015 at 04:08:47PM +0000, Gray, Mark D wrote: > Hi Ben, > > > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ben Pfaff > > Sent: Friday, February 20, 2015 7:20 AM > > To: dev@openvswitch.org > > Cc: Ben Pfaff > > Subject: [ovs-dev] [PATCH v3] [RFC] ovn: Start work on design > > documentation. > > <snip> > > > + <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? > > 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)? > > Thanks, _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
