Change key release policies of a machine group on CloudLink Center

For a machine group, you can modify the key release policies that must be met for a machine in that group to start automatically.

Here are two examples where default policy settings cause CloudLink Center to prevent a machine from starting up automatically:

  • A machine attempts to start up with a different IP address than the IP address recorded for that machine in the CloudLink Center database. CloudLink Center puts this machine in the pending state.
  • A machine that is registered with CloudLink Center cannot boot, so you move its encrypted data volume or VxFlex OS SDS device to another registered machine. When this machine attempts to start, CloudLink Center detects that the data volume or VxFlex OS SDS device is associated with a different machine than the machine recorded in the CloudLink Center database. CloudLink Center allows the machine to start up, but puts it in the pending state and locks the moved data volume or VxFlex OS SDS device to make it inaccessible.

When machines are in the pending state, you can manually accept or reject the startup. For more information, see Accept or reject pending machines in CloudLink.

To avoid having to manually accept each startup, you can change the default key release policy to allow CloudLink Center to release keys for volumes or devices of a machine when machines start up. For example, you can allow CloudLink Center to release the key for moved data volumes on startup. CloudLink Center also updates its database to associate the moved data volume with the current machine and automatically unlocks data volumes.

NOTE: For instructions about unlocking a moved volume or a device, see Unlock a moved volume or a device. For instructions about moving a data volume or a VxFlex OS SDS device, see Move an encrypted disk to another machine.