Feature Overview:

NIC partition is GAed featured since 16.1.4. Customer can use SRIOV functionality of the vendor's NIC for RHOSP network separation/isolation on the controller nodes and compute nodes. While compute nodes's NIC partition is already present in NFV CI suite, Controller nodes are not. Customer use NIC partition for Controller nodes with Support exception as feature suppose to work for both types of roles/nodes.  ** 

This is the support exception [1] raised for Airtel (India Telco customer) for using NIC partition for Controller nodes. 

[1]: https://issues.redhat.com/browse/SUPPORTEX-20428 

Goals:

This feature request has been raised to provide full adoption support to the customers who are using NIC Partition for controller nodes with support exception right now. Goal here to identify gaps (Now when we dont have os-net-config on OCP worker nodes), how to fix them.  

Acceptance Criteria 

1) Successful adoption of 17.1 environment with controllers having NIC Partition to RHOSO 18.0.14
2) Same level of OSP traffic isolation and any other features of SRIOV (qos, vlan etc.) after moving to RHOSO 18.0.14
3) Possible roll back in case of failures  
4) CI jobs for adoption with NIC Partition at controller nodes 

Definition of Done:

1) Document/Release-notes all the limitations encountered while implementing/testing this feature
2) All QE test should have been automated, executed and passed in CI

Documentation Considerations 

If any open/known issue to be noted

Customer Considerations 

KDDI and Airtel are using NIC Partition for controller nodes in production

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone