Configure Accelerator Cards on Subclouds

Prerequisites

1. Wind River Conductor already has the deployment of system controller and/or subclouds
2. sriov-fec-operator (version: 24.09-37) is available in helm applications as part of the Wind River Cloud Platform deployment.

Preparation

To trigger the workflow enable_acc or disable_acc and configure the accelerator cards on the subclouds, Maintenance Groups should be created and deleted. To create the Maintenance Groups, the following should be prepared.

WRCP plugin

Upload the latest wrcp plugin to Conductor.

Managing Accelerator cards using Maintenance Groups Page

Notes

• Workflows “acc_enable” & “acc_disable” should not be triggered by the user directly. Accelerator Cards should only be managed via Maintenance Groups
• ACC Enable workflow is triggered upon Maintenance Group Creation
• ACC Disable workflow is triggered upon Maintenance Group Deletion

Creating Maintenance Group to trigger enable ACC workflow on subclouds (Step by Step)

1. On WRC, click on the ‘Maintenance Group’ to navigate to Maintenance Group page.

2. On the Maintenance Group page, you would find information for all the maintenance group objects. To add a new maintenance group, then first click button Add Maintenance Group.

The Add Maintenance Group Widget appears.

3. Input the required parameters. In this example, a new maintenance group “maintenancegroup1” is added. After inputting the parameters, click on ‘Add’ button, to start the workflow(s) execution. The length of the execution will depend on how many subclouds are in the scope of the maintenance group selectors.

Inputs of Create Maintenance Group

Name

The name of the maintenance group (e.g., maintenancegroup1).

ACC Config Groups

A correct and valid dictionary for adding a maintenance group consists of three key sections in the Acc Config Groups section:

• accConfig: String which defines the path to the configuration file. For the URL links only http is supported and secured(https) links are not supported. The structure for the accConfig File for ACC200 card is shown below:

apiVersion: sriovfec.intel.com/v2
kind: SriovFecClusterConfig
metadata:
  name: config
  namespace: sriov-fec-system
spec:
  priority: 1
  physicalFunction:
    pfDriver: "vfio-pci"
    vfDriver: "vfio-pci"
    vfAmount: 2
    bbDevConfig:
      acc200:
        downlink4G:
          aqDepthLog2: 4
          numAqsPerGroups: 16
          numQueueGroups: 4
        downlink5G:
          aqDepthLog2: 4
          numAqsPerGroups: 16
          numQueueGroups: 0
        maxQueueSize: 1024
        numVfBundles: 2
        qfft:
          aqDepthLog2: 4
          numAqsPerGroups: 16
          numQueueGroups: 4
        uplink4G:
          aqDepthLog2: 4
          numAqsPerGroups: 16
          numQueueGroups: 4
        uplink5G:
          aqDepthLog2: 4
          numAqsPerGroups: 16
          numQueueGroups: 0
  drainSkip: true

• nodeSelector: Dictionary of the selectors used to match the specific nodes under the subclouds. Default value to select all the nodes under the subclouds:

"nodeSelector": {
      "kubernetes.io/hostname": ""
}

• acceleratorSelector: Dictionary of selectors used to match the specific nodes under the subclouds. Supported keys are deviceID, driver, maxVirtualFunctions, pciAddress & vendorID. Default value to select all the accelerator cards under the matching nodes:

"acceleratorSelector": {
      "deviceID": ""
}

The following is a complete example of the ACC Config Group.

[
  {
    "accConfig": "http://12.22.33.44:9080/acc_config.yaml",
    "nodeSelector": {
      "kubernetes.io/hostname": "controller-0"
    },
    "acceleratorSelector": {
      "deviceID": "57c0",
      "driver": "vfio-pci",
      "maxVirtualFunctions": 4,
      "pciAddress": "0000:03:00.0",
      "vendorID": "8086"
    }
  }
]

Selectors

The dictionary of System Inventory labels to be matched for maintenance group. A subcloud can be tagged to a Maintenance Group only if all of the Maintenance Group selectors match the subcloud’s labels.

An example of the Selectors is shown below.

{
  "system-controller": "lab1",
  "oam-floating-ip": "12.22.33.44"
}

Deleting Maintenance Group (Step by Step)

1. In Wind River Conductor, click on the Maintenance Group to navigate to Maintenance Group page.

2. On the Maintenance Group page, click on the trash icon from the Actions Tab. In the following example, maintenancegroup1 is deleted.

3. Click on the Yes tab to confirm the deletion of the Maintenance Group (e.g. maintenancegroup1).

Show Maintenance Group Details (Step by Step)

1. In Wind River Conductor, click on the Maintenance Group to navigate to Maintenance Group page.

2. Navigate to the maintenance groups list and, for the specific maintenance group (e.g. maintenancegroup1), click on the info action from the Actions tab signified by the Info icon.

The following example shows the details of the ACC Config Groups related to the specific maintenance group (e.g. maintenancegroup5).