On Fri, Jun 26, 2015 at 8:14 AM, Neil Jerram <neil.jer...@metaswitch.com> wrote:
> Hi Andreas, > > On 26/06/15 14:04, Andreas Scheuring wrote: > >> Hi together, >> for a new ml2 plugin I would like to pass over some data from neutron to >> nova on port creation and update (exploiting port binding extension >> [1]). For my prototype I thought of using one of the following response >> dictionaries to add my information: >> >> - binding:vif_details >> - binding:profile >> >> The API ref describes these attributes (port create / port update - both >> response) as dictionaries, but without restricting the key-value pairs >> or naming a defined number [1]. >> >> I've also seen some other ml2 plugins enriching those fields with unique >> data. So I assuming this is not considered as an API change, isn't it? >> >> Important: It's only about the response. The input comes from a >> configuration file. >> >> >> Thanks >> >> >> [1] http://developer.openstack.org/api-ref-networking-v2-ext.html >> > > I think the discussion at [1] is broadly in the same area, so you might > find some relevant input there. > > This RFE bug [1] isn't going anywhere because it wants to expose data to the underlying drivers, which is a huge -2 from me because it will allow complete circumvention of the Neutron API. Thanks, Kyle Neil > > > [1] https://bugs.launchpad.net/neutron/+bug/1460222 > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev