settingsLogin | Registersettings

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

0 votes

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

--
Andreas
(IRC: scheuran)


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Jun 26, 2015 in openstack-dev by Andreas_Scheuring (6,240 points)   2 9 14

5 Responses

0 votes

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.

Neil

[1] https://bugs.launchpad.net/neutron/+bug/1460222


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Jun 26, 2015 by Neil_Jerram (8,580 points)   1 4 11
0 votes

That bug is about adding things that the user can pass to the port. I think
Andreas is just talking about passing data to Nova that his ML2 plugin
generates. The key difference would be that adding key/value pairs to the
port API that the user populates would be exposing implementation details
to users.

An ML2 driver adding data to the binding information that a Nova VIF driver
leverages shouldn't be a problem because the user API interaction wouldn't
change.

On Fri, Jun 26, 2015 at 8:14 AM, Neil Jerram Neil.Jerram@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.

    Neil

[1] https://bugs.launchpad.net/neutron/+bug/1460222


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Kevin Benton


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Jun 26, 2015 by Kevin_Benton (24,800 points)   3 5 6
0 votes

On Fri, Jun 26, 2015 at 8:14 AM, Neil Jerram Neil.Jerram@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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Jun 26, 2015 by Kyle_Mestery (16,960 points)   3 3 6
0 votes

Hi Andreas,

On Fri, Jun 26, 2015 at 4:04 PM, Andreas Scheuring <
scheuran@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@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Jun 28, 2015 by irenab.dev_at_gmail. (1,480 points)   2
0 votes

Kevin, you're right. My use case is that the plugin enriches the vif
binding information. The value is generated along the ml2 agents
configuration files (the name of the interface to plug the port to).
There's no input coming from the user via API.

Irina, thanks for clarification. binding:vif_details is exactly what I
need!

Thanks, Andreas
(IRC: scheuran)

On Fr, 2015-06-26 at 11:18 -0600, Kevin Benton wrote:
That bug is about adding things that the user can pass to the port. I
think Andreas is just talking about passing data to Nova that his ML2
plugin generates. The key difference would be that adding key/value
pairs to the port API that the user populates would be exposing
implementation details to users.

An ML2 driver adding data to the binding information that a Nova VIF
driver leverages shouldn't be a problem because the user API
interaction wouldn't change.

On Fri, Jun 26, 2015 at 8:14 AM, Neil Jerram
Neil.Jerram@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.

Neil


[1] https://bugs.launchpad.net/neutron/+bug/1460222


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Kevin Benton


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Andreas
(IRC: scheuran)


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Jun 29, 2015 by Andreas_Scheuring (6,240 points)   2 9 14
...