Worker Node Life Cycle

Prerequisites

A system controller or subclouds where worker will be installed to is in a healthy state, operational and accessible.
WRC already has the deployment of system controller and/or subclouds
the latest WRCP plugin is uploaded to Conductor.

Workflow execution from Maintenance Page

Inputs to the add_nodes workflow

Worker Node Name:

The hostname for the worker node to be added (e.g., worker-node-1).

Worker Deployment Config:

Generally, a correct and valid YAML configuration for adding a worker node generally consists of three key sections:

Secret Configuration: Defines authentication credentials (e.g., username and password) required for board management.
Host Profile: Specifies hardware settings, networking configurations, boot options, and provisioning details for the worker node.
Host Definition: Links the worker node to a specific profile and assigns network-related overrides (e.g., boot MAC address, board management IP).

This structured approach ensures proper worker node deployment within the cluster.

---
apiVersion: v1
data:
  password: TGk2OW51eCo=
  username: c3lzYWRtaW4=
kind: Secret
metadata:
  name: bmc-secret-c0
  namespace: deployment
type: kubernetes.io/basic-auth
---
apiVersion: starlingx.windriver.com/v1
kind: HostProfile
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
  name: compute-0-profile
  namespace: deployment
spec:
  administrativeState: unlocked
  boardManagement:
    credentials:
      password:
        secret: bmc-secret-c0
    type: dynamic
  bootDevice: /dev/disk/by-path/pci-0000:43:00.0-nvme-1
  clockSynchronization: ntp
  console: ttyS0,115200n8
  installOutput: text
  interfaces:
    bond:
      - class: platform
        dataNetworks: []
        members:
          - enp202s0f2
          - enp202s0f3
        mode: active_standby
        name: pxeboot0
        platformNetworks:
          - pxeboot
      - class: platform
        dataNetworks: []
        members:
          - enp202s0f0
          - enp202s0f1
        mode: 802.3ad
        mtu: 9000
        name: nfsbond0
        platformNetworks: []
        transmitHashPolicy: layer2
        ptpRole: none
    ethernet:
      - class: none
        dataNetworks: []
        mtu: 9000
        name: enp202s0f2
        platformNetworks: []
        port:
          name: enp202s0f2
      - class: none
        dataNetworks: []
        mtu: 9000
        name: enp202s0f3
        platformNetworks: []
        port:
          name: enp202s0f3
      - class: none
        dataNetworks: []
        name: enp202s0f0
        platformNetworks: []
        port:
          name: enp202s0f0
      - class: none
        dataNetworks: []
        name: enp202s0f1
        platformNetworks: []
        port:
          name: enp202s0f1
    vlan:
      - class: platform
        dataNetworks: []
        lower: pxeboot0
        name: mgmt0
        platformNetworks:
          - mgmt
        ptpRole: none
        vid: 41
      - class: platform
        dataNetworks: []
        lower: pxeboot0
        name: cluster0
        platformNetworks:
          - cluster-host
        ptpRole: none
        vid: 42
  personality: worker
  powerOn: true
  provisioningMode: static
  rootDevice: /dev/disk/by-path/pci-0000:43:00.0-nvme-1
  storage:
    filesystems:
      - name: docker
        size: 60
      - name: kubelet
        size: 30
  subfunctions:
    - worker
---
apiVersion: starlingx.windriver.com/v1
kind: Host
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
  name: compute-0
  namespace: deployment
spec:
  overrides:
    bootMAC: 50:7c:6f:53:b2:f2
    boardManagement:
      address: 10.64.9.223
  profile: compute-0-profile
---

Secret Name of Worker’s BMC Username:

The BMC username secret ‘bmc_username’ for accessing the node containing value (e.g., admin).

Secret Name of Worker’s BMC Password:

The BMC password secret ‘bmc_password’ for accessing the node containing value (e.g., password123).

Example BMC Password

BMC Address:

The IP address of the BMC for the node (e.g., 192.168.1.100).

Running Add nodes workflow

On WRC, click on the Maintenance to navigate to Maintenance page

Example Conductor Nav page

On Maintenance page, you would find information for all the maintenance objects. To add a worker node on specific system controller or subcloud (in the example below. dc25) then click on the hamburger menu and then click on the Manage Worker Nodes option.

Example Maintenance page

Click on the Add Worker Node button.

Example Add Worker Node

Input the parameters. In this example, the new worker node is ‘compute-1’. After inputting the parameters, click on the ‘Add a Worker Node’ button to execute the workflow.

Example Worker Node Parameters

Inputs of delete_nodes workflow

Secret Name of Worker’s BMC Username:

The BMC username secret bmc_username for accessing the node containing value (e.g., admin).

Secret Name of Worker’s BMC Password:

The BMC password secret bmc_password for accessing the node containing value (e.g., password123).

Example Delete Node Parameters

BMC Address:

The IP address of the BMC for the node (e.g., 192.168.1.100).

Running Delete nodes workflow (Step by Step)

On Studio Conductor, click on Maintenance to navigate to Maintenance page

Example Conductor Nav page

The Maintenance page contains information for all the maintenance objects. To delete a worker node on specific system controller or subcloud (in this case dc25), click on the hamburger menu and then click on Manage Worker Nodes option.

Example Delete Node on Maintance page

Click on the Delete icon.

Example Delete icon

Input the parameters and click on Delete a Worker Node. In this example, worker node compute-0 is deleted.

Example Delete Worker Node

Workflow execution directly on WRC deployment

The workflow should always be run from the main deployment level. Do not run the add/delete workflow under a sub-environment.
subcloud_deployment_id is an optional field. To add worker node via add_nodes workflow on system controller, leave the subcloud_deployment_id field blank. In case, you are adding a node on a specific subcloud, identify the subcloud_deployment_id. Similarly, if you want to delete worker node via delete_nodes workflow on system controller, then leave the subcloud_deployment_id field blank. To delete a node on a specific subcloud enter the subcloud_deployment_id.

Inputs for add_nodes workflow

host:

The hostname for the worker node to be added (e.g., worker-node-1).

deploymentconfig:

---
apiVersion: v1
data:
  password: TGk2OW51eCo=
  username: c3lzYWRtaW4=
kind: Secret
metadata:
  name: bmc-secret-c0
  namespace: deployment
type: kubernetes.io/basic-auth
---
apiVersion: starlingx.windriver.com/v1
kind: HostProfile
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
  name: compute-0-profile
  namespace: deployment
spec:
  administrativeState: unlocked
  boardManagement:
    credentials:
      password:
        secret: bmc-secret-c0
    type: dynamic
  bootDevice: /dev/disk/by-path/pci-0000:43:00.0-nvme-1
  clockSynchronization: ntp
  console: ttyS0,115200n8
  installOutput: text
  interfaces:
    bond:
      - class: platform
        dataNetworks: []
        members:
          - enp202s0f2
          - enp202s0f3
        mode: active_standby
        name: pxeboot0
        platformNetworks:
          - pxeboot
      - class: platform
        dataNetworks: []
        members:
          - enp202s0f0
          - enp202s0f1
        mode: 802.3ad
        mtu: 9000
        name: nfsbond0
        platformNetworks: []
        transmitHashPolicy: layer2
        ptpRole: none
    ethernet:
      - class: none
        dataNetworks: []
        mtu: 9000
        name: enp202s0f2
        platformNetworks: []
        port:
          name: enp202s0f2
      - class: none
        dataNetworks: []
        mtu: 9000
        name: enp202s0f3
        platformNetworks: []
        port:
          name: enp202s0f3
      - class: none
        dataNetworks: []
        name: enp202s0f0
        platformNetworks: []
        port:
          name: enp202s0f0
      - class: none
        dataNetworks: []
        name: enp202s0f1
        platformNetworks: []
        port:
          name: enp202s0f1
    vlan:
      - class: platform
        dataNetworks: []
        lower: pxeboot0
        name: mgmt0
        platformNetworks:
          - mgmt
        ptpRole: none
        vid: 41
      - class: platform
        dataNetworks: []
        lower: pxeboot0
        name: cluster0
        platformNetworks:
          - cluster-host
        ptpRole: none
        vid: 42
  personality: worker
  powerOn: true
  provisioningMode: static
  rootDevice: /dev/disk/by-path/pci-0000:43:00.0-nvme-1
  storage:
    filesystems:
      - name: docker
        size: 60
      - name: kubelet
        size: 30
  subfunctions:
    - worker
---
apiVersion: starlingx.windriver.com/v1
kind: Host
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
  name: compute-0
  namespace: deployment
spec:
  overrides:
    bootMAC: 50:7c:6f:53:b2:f2
    boardManagement:
      address: 10.64.9.223
  profile: compute-0-profile
---

bmc_username:

The BMC username secret bmc_username for accessing the node containing value (e.g., admin).

bmc_password:

The BMC password secret bmc_password' for accessing the node containing value (e.g., password123).

Example BMC Password

bmc_address:

The IP address of the BMC for the node (e.g., 192.168.1.100).

subcloud_deployment_id:

(Optional) The deployment ID for the subcloud (e.g., subcloud3_dc-lab).

Running Add nodes workflow

Navigate to the main deployment and click on the Add_Nodes workflow.

Example Add Nodes

Input the parameters. In this example, a new worker node compute-0 on subcloud with deployment id subcloud1_main is added.

Example Add Worker

After inputting the parameters, click on Execute button to start the workflow execution.

Example Workflow Execution

New worker node will be successfully added as shown below.

Example Successful Workflow Execution

Inputs of delete_nodes workflow

host:

The hostname for the worker node to be added (e.g., worker-node-1).

bmc_username:

The BMC username secret bmc_username for accessing the node containing value (e.g., admin).

bmc_password: The BMC password secret ‘bmc_password’ for accessing the node containing value (e.g., password123).

Example BMC Password

bmc_address:

The IP address of the BMC for the node (e.g., 192.168.1.100).

subcloud_deployment_id:

(Optional) The deployment ID for the subcloud (e.g., subcloud3_dc-lab).

Running Delete nodes workflow (Step by Step)

Navigate to the main deployment and click on the Delete Nodes workflow.

Example Delete Node Workflow

Input the parameters. In this example, worker node compute-0 on subcloud with deployment id subcloud1_main is deleted.

Example Delete Node Workflow

After inputting the parameters, click the Execute button, to start the workflow.

Example Delete Node Workflow Execution

The worker node will be successfully deleted as shown below.

Example Successful Delete Node Workflow