Hi Tomoe, I don't think we, as a community, have discussed this requirement. In general, for plugin-specific features, there is always an option to expose/implement them as extensions. Check the section on API Extensions here: http://wiki.openstack.org/QuantumDevelopment
Thanks, ~Sumit. > -----Original Message----- > From: netstack-bounces+snaiksat=cisco....@lists.launchpad.net > [mailto:netstack-bounces+snaiksat=cisco....@lists.launchpad.net] On > Behalf Of Tomoe Sugihara > Sent: Sunday, March 11, 2012 8:02 PM > To: netstack@lists.launchpad.net > Subject: [Netstack] Mac address in quantum port > > Hi everyone, > > I just looked at quantum code and leaned that quantum port doesn't > care about the mac addresses. > I think it's true that switch port doesn't necessarily have mac > address in general, but normally switches learn mac addresses per > port. > So I thought it would be useful for some implementation of plugins, > for example to optimize mac learning, to get mac address as a > parameter for create port API. > > Was there any related discussion about this? I'd appreciate any > comments on this. > > Cheers, > Tomoe > > -- > Mailing list: https://launchpad.net/~netstack > Post to : netstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~netstack > More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
