Description of problem: Need ML2 plugin improvements to support port groups (aka link aggregation and bonding), so as to increase network throughput for demanding workloads Version-Release number of selected component (if applicable): Neutron version in OpenStack Ocata release How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Workloads can get added network capacity by, for example, bonding four 1Gbit links to create a 4Gbit capacity Additional info:
Ironic upstream work: https://review.openstack.org/#/c/360647/ Nova upstream work: https://review.openstack.org/#/c/206163/
Any Neutron references?
(In reply to Assaf Muller from comment #2) > Any Neutron references? From my understanding, the Intel engg team hasn't committed resources to the Neutron changes and we'd like Red Hat to take the lead (or support a submission by someone else in the community). We will ensure there are people to review the submissions. Am not able to find a submission for Neutron yet
Upstream Neutron is not accepting new RFEs at this point in the release cycle, certainly not new APIs. To that end I'll remove the OSP 11 target. We can take this RFE under consideration when we do feature planning for new releases. Can you please add additional information? What is the use case? What exactly is asked from OpenStack, and from Neutron specifically?
this is an Ironic feature support https://review.openstack.org/#/q/topic:bug/1618754 this feature also has a dependency on https://review.openstack.org/#/q/topic:bp/ironic-portgroups-support
All changes have landed already.
Hello, which ML2 driver is this being tested with? Could you let us know the details of the test plans? Many thanks
RH OSP 12 RC contents are up on the RH OSP beta channel. This bug is marked as OtherQA. If you can take a look at the packages and content and test this bug to see if it is resolved. It would be much appreciated to get feedback on if this is verified or if there is an issue before we get to GA.
This feature was driven by Mirantis developers as well. At this time we may not have the hardware to test this end to end.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days