(Click to open topic with navigation)

10 – Reservations > 10.2 Reservation tasks > Preparing for maintenance

Preparing for maintenance

Context

One of the most helpful features of Viewpoint for Moab Cloud Suite is that it allows you to create maintenance reservations on particular nodes. When you create these reservations, Moab evacuates the current workload off of the node so that you can perform your maintenance. These steps explain how to create a maintenance reservation in Viewpoint.

To prepare your system for maintenance

  1. Navigate to the New Reservation page (Datacenter > New Reservation). For details, see Fields: New Reservation.
  2. (Optional) Specify a name for your maintenance reservation.
  3. Under Advanced Settings, do the following:
    1. (Optional) Specify a text description of the maintenance reservation.
    2. Clear the Dedicated resource specification option.
    3. Select the Evacuate workload specification option.
  4. (Optional) Use the Access Controls to grant access to the reservation to specific groups, users, or accounts.
  5. Use the Scheduling options to specify the start and end time of the maintenance window.
  6. Under Resources, specify the nodes you want Moab to create the maintenance reservation on.

    7. You must specify the nodes using the Select Nodes option. The Node Count option is disabled when you choose to evacuate workload from the node.

  7. Save the reservation.

Sometimes, Moab may refuse to migrate one or more of the VMs off of the reserved node and will generate an error with the message: "Unable to find destination for VM '<name>' (Reservation, Attributes)."

"Attributes" refers to the fact that Moab cannot find an eligible machine based on the datacenter attribute requirement.

If you create a maintenance reservation and the any of the affected VMs is on the Migration Exclusion list (see Configuring the Migration Exclusion policy for more information), Viewpoint returns an error message. To resolve this, you must first remove the VM(s) from the list or disable the Migration Exclusion policy.

Related topics