Monitor the Quarantine Tenancy#

Note

Tenants, tenancies, and other features are available if you have paid for multi-tenant support. Contact Penguin Solutions to learn more.

All multi-tenant clusters have a Quarantine tenancy that is created during the multi-tenancy setup process. After initial creation, the Quarantine tenancy only contains a head node and gateway node. All bare metal compute nodes that will be added to tenancies should be added to the Quarantine tenancy. See Add Compute Nodes to Quarantine and Available Tenancies for details.

The Quarantine tenancy is used to run health and performance checks on bare metal compute nodes, wipe any customer data, and verify the node's firmware. See Available and Quarantine Tenancies for additional information about the Quarantine tenancy.

Add Nodes to Quarantine Tenancy#

When a tenancy is decommissioned, the compute nodes associated with that tenancy are automatically moved to the Quarantine tenancy. You may also need to move nodes to the Quarantine tenancy manually, such as when adding new bare metal nodes to the super-cluster to be used in tenancies or if a compute node assigned to a tenancy requires frequent remediation.

To add nodes to the Quarantine tenancy:

cw-clusterctl tenancies -i Quarantine assign <node list>

After the compute nodes are added to the Quarantine tenancy, the nodes are:

  • Powered on and booted to a known good image.

  • Wiped completely to ensure no customer data remains, including programs, user and temporary files, customer application data, and so on.

  • Reverted to a known good firmware state.

  • Run through a series of health and performance checks.

Monitor Node Status in Quarantine Tenancy#

The superadministrator can monitor node health check status within the Quarantine tenancy. Node status values are updated automatically as health checks run. See ARS State Map for details.

Move Healthy Nodes to Available Tenancy#

A node is healthy when it has a status of Available. The time it takes from when the node is added to the Quarantine tenancy to when it is ready to move to the Available tenancy can vary, but typically should not take more than a few minutes.

  1. Remove the node from the Quarantine tenancy:

    cw-clusterctl tenancies -i Quarantine unassign <healthy node>

  2. Add the node to the Available tenancy:

    cw-clusterctl tenancies -i Available assign <healthy node>