With OVS, plug_vifs is responsible for attaching the VM interface to the integration bridge. The neutron agent is then responsible for setting up the flows to direct traffic to the appropriate network.
On Fri, Jul 18, 2014 at 9:05 AM, Peng Gu <gp_st...@163.com> wrote: > Hi, all > > The comment in of plug_vifs in ComputeDriver indicates that this method is > responsible for plugging the vif into network, > but when working with neutron, this work has alreay been done by agents in > the compute node. > > Actually, I noticed that plug_vifs in LibvirtDriver did nothing in the > neutron environment with linux bridge plugin, because > the work of creating bridges and adding tap interface to bridges was done > by linux bridge agent. > > So it confused me a lot if plug_vifs has lost its semantic or am I missing > something, or plug_vifs has its meaning in other > scenarios ? > > Thanks! > > Peng Gu > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kevin Benton
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev