Oracle Cloud Infrastructure Documentation

Compute Node Provisioning and Life Cycle State

The compute nodes must be provisioned to contribute to the compute capacity of Private Cloud Appliance, and host compute instances. Provisioning is an administrator task performed from the Service Enclave, which is also used to deprovision a node, and to control the life cycle state.

Provisioning a Compute Node

The appliance software detects the compute nodes that are installed in the rack and cabled to the switches, meaning they appear in the Rack Units list as Ready to Provision. You can provision them from the Service Web UI or Service CLI.

Using the Service Web UI

  1. In the navigation menu, click Rack Units.

  2. In the Rack Units table, click the host name of the compute node you want to provision.

    The compute node detail page appears.

  3. In the top-right corner of the page, click Controls and select the Provision command.

Using the Service CLI

  1. Display the list of compute nodes.

    Copy the ID of the compute node you want to provision.

    PCA-ADMIN> list ComputeNode
Data:
  id                                     name       provisioningState   provisioningType
  --                                     ----       -----------------   ----------------
  29f68a0e-4744-4a92-9545-7c48fa365d0a   pcacn001   Ready to Provision  Unspecified
  7a0236f4-b00e-461d-93a0-b22673a18d9c   pcacn003   Ready to Provision  Unspecified
  dc8ae567-b07f-48e0-89bd-e57069c20010   pcacn002   Ready to Provision  Unspecified

  2. Provision the compute node with this command:

    PCA-ADMIN> provision id=7a0236f4-b00e-461d-93a0-b22673a18d9c
JobId: ea93cac4-4430-4663-aafd-d70701593fb2

    Use the job ID to check the status of your provision command.

    PCA-ADMIN> show Job id=ea93cac4-4430-4663-aafd-d70701593fb2
[...]
  Done = true
  Name = MODIFY_TYPE
  Run State = Succeeded

  3. Repeat the provision command for any other compute nodes you want to provision at this time.

  4. Confirm that the compute nodes have been provisioned.

    PCA-ADMIN> list ComputeNode
Data:
  id                                     name       provisioningState   provisioningType
  --                                     ----       -----------------   ----------------
  29f68a0e-4744-4a92-9545-7c48fa365d0a   pcacn001   Provisioned         KVM
  7a0236f4-b00e-461d-93a0-b22673a18d9c   pcacn003   Provisioned         KVM
  dc8ae567-b07f-48e0-89bd-e57069c20010   pcacn002   Provisioned         KVM

Starting, Resetting, or Stopping a Compute Node

Using the Service Web UI

  1. Ensure that the compute node is locked for maintenance.

    See Locking a Compute Node for Maintenance.

  2. In the navigation menu, click Rack Units.

  3. In the Rack Units table, locate the compute node you want to start, reset or stop.

  4. Click the Action menu (three vertical dots) and select the appropriate action: Start, Reset, or Stop.

  5. When the confirmation window appears, click the appropriate action button to proceed.

    A pop-up window appears for a few seconds to confirm that the compute node is starting, stopping, or restarting.

  6. When the compute node is up and running again, release the maintenance and provisioning locks.

Using the Service CLI

  1. Display the list of compute nodes.

    Copy the ID of the compute node that you want to start, reset or stop.

    PCA-ADMIN> list ComputeNode
Data:
  id                                     name       provisioningState   provisioningType
  --                                     ----       -----------------   ----------------
  3e62bf25-a26c-407e-ab8b-df01a4ad98b6   pcacn002   Provisioned         KVM
  f7b8356b-052f-4911-babb-447e6ab9c78d   pcacn003   Provisioned         KVM
  4e06ebdf-faed-484e-996d-d77af786f123   pcacn001   Provisioned         KVM

  2. Ensure that the compute node is locked for maintenance.

    See Locking a Compute Node for Maintenance.

  3. Start, reset or stop the compute node using the corresponding command:

    PCA-ADMIN> start ComputeNode id=f7b8356b-052f-4911-babb-447e6ab9c78d
PCA-ADMIN> reset id=f7b8356b-052f-4911-babb-447e6ab9c78d
PCA-ADMIN> stop ComputeNode id=f7b8356b-052f-4911-babb-447e6ab9c78d

  4. When the compute node is up and running again, release the maintenance and provisioning locks.

Deprovisioning a Compute Node

If you need to take a compute node out of service, for example to replace a defective one, you must deprovision it first, so that its data is removed cleanly from the system databases.

Using the Service Web UI

  1. In the navigation menu, click Rack Units.

  2. In the Rack Units table, click the host name of the compute node you want to deprovision.

    The compute node detail page appears.

  3. In the top-right corner of the page, click Controls and select the Provisioning Lock command.

    When the confirmation window appears, click Lock to proceed.

    After successful completion, the Compute Node Information tab shows Provisioning Locked = Yes.

  4. Ensure that no more compute instances are running on the compute node.

    Click Controls and select the Migrate All Vms command. The system migrates the instances to other compute nodes.

  5. To deprovision the compute node, click Controls and select the Deprovision command.

    When the confirmation window appears, click Deprovision to proceed.

    After successful completion, the Compute Node Information tab shows Provisioning State = Ready to Provision.

Using the Service CLI

  1. Display the list of compute nodes.

    Copy the ID of the compute node you want to deprovision.

    PCA-ADMIN> list ComputeNode
Data:
  id                                     name       provisioningState   provisioningType
  --                                     ----       -----------------   ----------------
  29f68a0e-4744-4a92-9545-7c48fa365d0a   pcacn001   Provisioned         KVM
  7a0236f4-b00e-461d-93a0-b22673a18d9c   pcacn003   Provisioned         KVM
  dc8ae567-b07f-48e0-89bd-e57069c20010   pcacn002   Provisioned         KVM

  2. Set a provisioning lock on the compute node.

    PCA-ADMIN> provisioningLock id=7a0236f4-b00e-461d-93a0-b22673a18d9c
JobId: ed4a4646-6d73-41f9-9cb0-73ea35e0d766

    Use the job ID to check the status of your command.

    PCA-ADMIN> show Job id=ed4a4646-6d73-41f9-9cb0-73ea35e0d766
[...]
  Done = true
  Name = MODIFY_TYPE
  Run State = Succeeded

  3. Confirm that the compute node is under provisioning lock.

    PCA-ADMIN> show ComputeNode id=7a0236f4-b00e-461d-93a0-b22673a18d9c
[...]
  Provisioning Locked = true

  4. Migrate all running compute instances off the compute node you want to deprovision.

    PCA-ADMIN> migrateVm id=7a0236f4-b00e-461d-93a0-b22673a18d9c
JobId: 6f1e94bc-7d5b-4002-ada9-7d4b504a2599

    Use the job ID to check the status of your command.

    PCA-ADMIN> show Job id=6f1e94bc-7d5b-4002-ada9-7d4b504a2599
Data:
[...]
  Done = true
  Name = MODIFY_TYPE
  Run State = Succeeded

  5. Deprovision the compute node with this command:

    PCA-ADMIN> deprovision id=7a0236f4-b00e-461d-93a0-b22673a18d9c
JobId: 9868fdac-ddb6-4260-9ce1-c018cf2ddc8d

    Use the job ID to check the status of your deprovision command.

    PCA-ADMIN> show Job id=9868fdac-ddb6-4260-9ce1-c018cf2ddc8d
[...]
  Done = true
  Name = MODIFY_TYPE
  Run State = Succeeded

  6. Confirm that the compute node has been deprovisioned.

    PCA-ADMIN> list ComputeNode
Data:
  id                                     name       provisioningState   provisioningType
  --                                     ----       -----------------   ----------------
  29f68a0e-4744-4a92-9545-7c48fa365d0a   pcacn001   Provisioned         KVM
  7a0236f4-b00e-461d-93a0-b22673a18d9c   pcacn003   Ready to Provision  Unspecified
  dc8ae567-b07f-48e0-89bd-e57069c20010   pcacn002   Provisioned         KVM