[openstack-dev] [neutron] enriching port binding extension API dictionaries with key-values

Irena Berezovsky irenab.dev at gmail.com
Sun Jun 28 08:12:07 UTC 2015


Hi Andreas,

On Fri, Jun 26, 2015 at 4:04 PM, Andreas Scheuring <
scheuran at linux.vnet.ibm.com> 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].
>
binding:profile is an input dictionary, that should tell neutron how to
bind the port.
binding:vif_details is an output dictionary that should provide nova  (or
other) with enough details to plug the port properly.

>
> 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
>
>
> --
> Andreas
> (IRC: scheuran)
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150628/bba43833/attachment.html>


More information about the OpenStack-dev mailing list