Open Stack

Hi Jim,

Neutron is supporting resource tagging [1] which is support currently  network resource_type
With a simple change is neutron you can also allow resource tagging for port resource_type [2]

This will allow you to tags ports and indicate that they are in the same group
maybe that can work better the ironic port group concept.


[1] - https://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/tag-instances.html
[2] - https://github.com/openstack/neutron/blob/master/neutron/extensions/tag.py#L38-L41


From: Armando M. [mailto:armamig at gmail.com]
Sent: Tuesday, May 24, 2016 10:19 PM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [ironic][neutron] bonding?



On 24 May 2016 at 04:51, Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>> wrote:
Hi,

There's rumors floating around about Neutron having a bonding model in
the near future. Are there any solid plans for that?

Who spreads these rumors :)?

To the best of my knowledge I have not seen any RFE proposed recently along these lines.


For context, as part of the multitenant networking work, ironic has a
portgroup concept proposed, where operators can configure bonding for
NICs in a baremetal machine. There are ML2 drivers that support this
model and will configure a bond.

Some folks have concerns about landing this code if Neutron is going to
support bonding as a first-class citizen. So before we delay any
further, I'd like to find out if there's any truth to this, and what the
timeline for that might look like.

Thanks!

// jim

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@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/20160527/90255130/attachment.html>