Feature Overview 

If a NIC port is used for baremetal provisioning for the node, same NIC port must be allowed to be configured for NIC partitioning

The control plane configured by cloud-init scripts is done on PF. Later, when os-net-config comes up, the control plane is moved from PF to the VFs. The ifdown <PF> does not remove the IP address from the NM connection associated. This results in an error when the VFs were bound with the same IP address. 

This feature deals with "thin footprint" cases where compute nodes are equipped with very few resources (NIC in this case). In such cases, customers have to run all traffic (OSP provision, control plane, data plane) over shared NIC resources. NIC Partition (GAed feature) comes to the rescue here. Customers can take advantage of NIC Partition to partition NIC to isolate each traffic over created VFs. 

However, the challenge here is that NIC ports would be used for provisioning as well (which is before the NIC part comes into the picture of deployment), and its provision network config needs to remain the same while running on newly created VFs. This ticket covers this case. A successful delivery of this mandate below "Acceptance Criteria"

1) After successful deployment, compute node should have provision traffic running over bond (active-backup) with member interfaces having VF from each Port 

2) If PIXe/Provision traffic runs over vlan, make sure same VLAN configured over bond after deployment

3) If customer has configured qos values for VF, they must be configured accordingly on the VFs

4) Provide appropriate failure logs in the os-net-config logging system. 

5) This feature should support both pre-provisioned and un-provisioned nodes. 

6) This feature is applicable only for "greenfield" deployments. No support for upgrade from 17.1. 

7) All persistent cases (reboot, update, link redundancy) should pass 

Goals

Allow the NIC port to be configured for NIC partitioning if the same NIC port was used for baremetal provisioning earlier. 

Requirements 

This is an engineering-driven feature, and details are primarily on the implementation side rather than customer requirements. The customer requirement is mainly to be able to use the NIC port for NIC partitioning. 

Done - Acceptance Criteria 

1) Document all the limitations encountered while implementing/testing this feature

2) Document "config guide" for this feature (along with topology if possible)

3) All QE test should have been automated, executed, and passed in CI

Documentation Considerations 

The known issue list must be updated to reflect the support. 

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

• …