Bug 1658195 - Backport NIC Partitioning RFE to OSP13
Summary: Backport NIC Partitioning RFE to OSP13
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: os-net-config
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z5
: 13.0 (Queens)
Assignee: Karthik Sundaravel
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1664933
TreeView+ depends on / blocked
 
Reported: 2018-12-11 13:40 UTC by Karthik Sundaravel
Modified: 2019-12-05 18:05 UTC (History)
8 users (show)

Fixed In Version: os-net-config-8.4.3-5.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1664933 (view as bug list)
Environment:
Last Closed: 2019-03-14 13:55:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 629775 0 'None' MERGED Remove mox usage 2021-01-18 11:25:58 UTC
OpenStack gerrit 629804 0 'None' MERGED Adding VLAN support and other configs for sriov_vf 2021-01-18 11:25:58 UTC
OpenStack gerrit 629817 0 'None' MERGED Add sriov_vf type as member of ovs_dpdk_port 2021-01-18 11:25:58 UTC
OpenStack gerrit 629820 0 'None' MERGED Add default VF configs for ovs and ovs_user bridges 2021-01-18 11:25:58 UTC
OpenStack gerrit 630636 0 'None' MERGED NIC Partitioning works with NM enabled 2021-01-18 11:25:58 UTC
OpenStack gerrit 632080 0 'None' MERGED Sample templates for linux_bond, ovs_bond, dpdkbond using VFs 2021-01-18 11:25:58 UTC
OpenStack gerrit 632081 0 'None' MERGED NIC-Partitioning: DPDK devices comes up properly after reboot 2021-01-18 11:25:59 UTC
OpenStack gerrit 632217 0 'None' MERGED Updating requirements for pyudev 2021-01-18 11:25:59 UTC
Red Hat Product Errata RHBA-2019:0448 0 None None None 2019-03-14 13:55:19 UTC

Description Karthik Sundaravel 2018-12-11 13:40:58 UTC
Backport NIC Partitioning to OSP13. BZ: 1534587

Comment 1 Bob Fournier 2018-12-11 14:26:38 UTC
Will also need to clone this bug for OSP-14.

Comment 2 Bob Fournier 2019-01-02 21:48:33 UTC
So https://bugzilla.redhat.com/show_bug.cgi?id=1534587 is an RFE, so setting the FutureFeature keyword.  It is also quite an extensive fix - 9 patches.  Is there buy-in from QE that this can be tested in OSP-13 and OSP-14 z releases?

Comment 3 Karthik Sundaravel 2019-01-10 04:53:42 UTC
(In reply to Bob Fournier from comment #2)
> So https://bugzilla.redhat.com/show_bug.cgi?id=1534587 is an RFE, so setting
> the FutureFeature keyword.  It is also quite an extensive fix - 9 patches. 
> Is there buy-in from QE that this can be tested in OSP-13 and OSP-14 z
> releases?

The QE will definitely test the regression part for every Z release. I'll do the development testing of this feature.

Yariv,
Can you please advise on the QE bandwidth of the feature testing on OSP13/14 ?

Comment 21 errata-xmlrpc 2019-03-14 13:55:07 UTC
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/RHBA-2019:0448

Comment 22 Yariv 2019-06-23 15:07:44 UTC
(In reply to Karthik Sundaravel from comment #3)
> (In reply to Bob Fournier from comment #2)
> > So https://bugzilla.redhat.com/show_bug.cgi?id=1534587 is an RFE, so setting
> > the FutureFeature keyword.  It is also quite an extensive fix - 9 patches. 
> > Is there buy-in from QE that this can be tested in OSP-13 and OSP-14 z
> > releases?
> 
> The QE will definitely test the regression part for every Z release. I'll do
> the development testing of this feature.
> 
> Yariv,
> Can you please advise on the QE bandwidth of the feature testing on OSP13/14
> ?

This features tested manually by vkhitrin, templates are in CI 
please refer patch https://code.engineering.redhat.com/gerrit/gitweb?p=nfv-qe.git;a=commitdiff;h=d1251a3e98474caeb95921e4f3121baaaa2e8bdd


Note You need to log in before you can comment on or make changes to this bug.