> -----Original Message----- > From: Gary Kotton [mailto:gkot...@redhat.com] > Sent: Tuesday, June 25, 2013 3:48 PM > To: OpenStack Development Mailing List > Cc: Chandan Dutta Chowdhury > Subject: Re: [openstack-dev] [Networking] Question on portbinding > > On 06/25/2013 07:59 AM, Chandan Dutta Chowdhury wrote: > > Hello All, > > > > > > While going through the portbinding extension I noticed that a patch > > has been proposed for calls from nova to checks and updates the port > binding attributes for a plugin which supports this extension. > > > > https://review.openstack.org/#/c/29767/ > > > > > > While going through the code, I don't see the same changes for dhcp > and l3 agents. > > These agents while creating ports don't provide portbinding > attributes. > > The support to Quantum was added a while ago (it was part of the agent > scheduling blueprint that Yong (aka gongysh) did towards the end of the > Grizzly cycle). When a DHCP agent creates a port, it passes the host as > one of the parameters. Similarly with the l3-agent. > > Thanks > Gary
Hello Gary, Thanks for the quick reply. I was looking at the code for dhcp agent rpc handling at https://github.com/openstack/quantum/blob/master/quantum/db/dhcp_rpc_base.py#L119 and https://github.com/openstack/quantum/blob/master/quantum/db/dhcp_rpc_base.py#L119 For l3 agent at https://github.com/openstack/quantum/blob/master/quantum/db/l3_db.py#L366 I don't see the host being passed as port parameter in the actual port create call, although the agents do pass the host information in the rpc calls. Regards Chandan _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
