Disable Cloud Bursting

Disable cloud bursting by disabling bursting scenarios, letting the cloud queues drain and allowing all cloud nodes to unburst.

All cloud bursting for an HPC complex must be disabled before any of the following activities:
  • upgrading PBS Professional
  • performing PBS maintenance
  • reconfiguring PBS execution hosts
  • changing the amount of PBSWorksBurstNodeHours licenses

Cloud bursting associated to a bursting scenario must be disabled before a bursting scenario can be edited.

  1. Choose one of the following options:
    • Disable all bursting scenarios before any PBS maintenance activities or changing the amount of PBSWorksBurstNodeHours licenses.
    • Disable a bursting scenario before editing the bursting scenario.
  2. Allow all cloud queues (those associated with cloud bursting) to drain by allowing time for the jobs that are waiting in the queues to run and complete.
    Tip: If a running job is taking a long time to complete, it can be deleted using the PBS qdel command or through the Control Monitor tab.

Verify that all cloud nodes are unburst.

  1. Login to Control.
  2. Click the Cloud tab.
  3. Click Bursting from the Infrastructure menu located on the left-hand side of the web page.
  4. Select a bursting scenario by clicking its name.
  5. Click Node.
    When the following message is displayed for both the automatically and manually burst categories, all cloud nodes are unburst.
    No machines are available
  6. When disabling all cloud bursting, verify that all cloud nodes are unburst for every bursting scenario.