Migrate Secondary Network Devices with NodePolicy

Products

• VMware Telco Cloud Automation

Issue/Introduction

• Starting from TCA 3.2, users can attach a nodepolicy to a nodepool and secondary network devices can be defined in the nodepolicy.
• As seen in step 6 when adding a secondary network devices, many advanced features are exposed in nodepolicy, like creating VLAN subinterfaces, toggle ethernet arguments GRO/GSO etc.
• If there’re any existing secondary network adapters after upgrading to TCA 3.2, it’s recommended to migrate them with the nodepolicy.

Environment

3.2

Resolution

Migration Steps:

1.  Edit NodePool
   
   Click the “Configure” button in “1. Node Pool”
   
   
   Remove secondary network devices under Network, Apply and Next
   
   
   
   
2. Attach NodePolicy
   
   In “2. Node Policy” choose profile “tca-multi-interface-profile-1.0.0”
   
    
   
   Click “+ Add” button to add a network adapter
   
   
   
   Input the same interface name and choose the original network it connected to.
   If user want to enable GRO/GSO, toggle “Network Configuration”
   
   
   
   Click “SAVE” and “Next”
   
   
3. Review CR before Apply
   
   Click on the tab “Custom Resoures(CR)”, verify node-policy content.
   
   
   
   
4. Apply changes
   
   Click on the button “UPDATE NODE POOL”.
   
   
   
   
   Navigate to the “Policies” tab under cluster to check nodepolicy status. There should be 2 nodepolicy for the nodepool, one suffix is “-nf” and another suffix is “-caas”.
   
   
   
   Wait for the nodepool status to provisioned.
   
   
   
   
   
5. Verified in worker node
   Use ethtool command to verify GRO/GSO settings.