Follow

Managing compute nodes

To perform an action on a specific compute node, open the compute node's profile page and click Actions, click ... beside the compute node on the Hardware page, or click ... beside the compute node on the Nodes page. The actions available on a compute node vary depending on the node's state.

compute_actions.PNG

Connecting to a node's console

  • Select Connect to console from the Actions drop-down menu. Ignite will create a secure VNC connection to the compute node and open the console in a new window.

Restarting a compute node

  1. Select Restart from the Actions drop-down menu.
  2. Select an action plan for each affected application instance. An action plan tells Cloudistics how you want to handle application instances that will be affected by an action you are trying to perform. When you restart a node, Ignite offers the following action plans for each affected instance:
    • Migrate - Ignite will attempt to migrate the instance to another compute node that meets its compute requirements.
    • Relax profile & migrate - Ignite will remove compute category and tag requirements from the instance's compute profile. Ignite will then attempt to migrate the instance to an available compute node in the current virtual datacenter and migration zone.
    • Shut down - Ignite will shut down the instance.
    • Force shut down - Ignite will force shut down the application instance.
  3. Click Continue.

When you click Continue, Ignite attempts to perform the selected action plan(s). If an action plan fails, you will be asked to select a different plan.

Forcing a restart

  1. Select Force restart from the Actions drop-down menu.
  2. Click Continue.

Note: Ignite will force all running application instances on the compute node to shut down.

Powering a node on

  • Select Power on from the Actions drop-down menu. The compute node will immediately power on.

Powering a node off

Instructions:

  1. Select Power off from the Actions drop-down menu.
  2. Select an action plan for each affected application instance. An action plan tells Cloudistics how you want to handle application instances that will be affected by an action you are trying to perform. When you power off a compute node, Ignite offers the following action plans for each affected instance:
    • Migrate - Ignite will attempt to migrate the instance to another compute node that meets its compute requirements.
    • Relax profile & migrate - Ignite will remove compute category and tag requirements from the instance's compute profile. Ignite will then attempt to migrate the instance to an available compute node in the current virtual datacenter and migration zone.
    • Shut down - Ignite will shut down the instance.
    • Force shut down - Ignite will force shut down the application instance.
  3. Click Continue.

When you click Continue, Ignite will attempt to perform the selected action plans. If an action plan fails, you will be asked to select a different plan.

Forcing a node to power off

  1. Select Force power off from the Actions drop-down menu.
  2. Click Continue.

Note: Ignite will force all running application instances on the compute node to shut down.

Turning maintenance mode on

  1. Select Turn on maintenance mode from the Actions drop-down menu.
  2. Select an action plan for each affected application instance. An action plan tells Cloudistics how you want to handle application instances that will be affected by an action you are trying to perform. When you put a compute node into maintenance mode, Ignite offers the following action plans for each affected instance:
    • Migrate - Ignite will attempt to migrate the instance to another compute node that meets its compute requirements.
    • Relax profile & migrate - Ignite will remove compute category and tag requirements from the instance's compute profile. Ignite will then attempt to migrate the instance to an available compute node in the current virtual datacenter and migration zone.
    • Shut down - Ignite will shut down the instance.
    • Force shut down - Ignite will force shut down the application instance.
  3. Click Continue.

When you click Continue, Ignite attempts to perform the selected action plan(s). If an action plan fails, you will be asked to select a different plan.

 

Turning maintenance mode off

  1. Select Turn off maintenance mode from the Actions drop-down menu.
  2. Click Continue.

Renaming a node

  1. Select Rename from the Actions drop-down menu.
  2. Enter a new name for the compute node.
    • Note: The compute node name must be unique across all compute nodes in your cloud infrastructure.
  3. Click Update.

Changing the description of a node

  1. Select Change description from the Actions drop-down menu.
  2. Enter a description for the compute node.
  3. Click Update.

Resetting the manager password for the node

The manager password is used to log into the physical compute node via monitor and keyboard or SSH.

  1. Select Reset manager password from the Actions drop-down menu.
  2. Enter a new password.
  3. Click Reset Password.

The updated password will be pushed to the physical compute node.

  • Note: Hardware passwords are not stored on Cloudistics servers.

Adding compute tags to a node

  1. Select Add compute tags from the Actions drop-down menu.
  2. Enter the name of the desired compute tag(s).
  3. Click Add Compute Tags.

Removing compute tags from a node

  1. Select Remove compute tags from the Actions drop-down menu.
  2. Select the compute tag(s) you wish to remove from the compute node.
  3. Select an action plan for each affected application instance. An action plan tells Cloudistics how you want to handle application instances that will be affected by an action you are trying to perform. When you remove compute tags from a compute node, Ignite offers the following action plans for each affected instance:
    • Migrate - Ignite will attempt to migrate the instance to another compute node that meets its compute requirements.
    • Relax profile & migrate - Ignite will remove compute category and tag requirements from the instance's compute profile. Ignite will then attempt to migrate the instance to an available compute node in the current virtual datacenter and migration zone.
    • Shut down - Ignite will shut down the instance.
    • Force shut down - Ignite will force shut down the application instance.
  4. Click Continue.

When you click Continue, Ignite attempts to perform the selected action plan(s). If an action plan fails, you will be asked to select a different plan.

 

Changing a compute category for a node

To successfully remove a compute node from its original compute category, your infrastructure must have sufficient unused resources in that category.

Note: You cannot change a compute category for a compute node while application instances are running on the compute node.

  1. Put the compute node in maintenance mode.
  2. Select Change compute category from the Actions drop-down menu.
  3. Select a new compute category for the compute node.
  4. Indicate how Cloudistics should reduce the original compute category's allocations (left column).
  5. Indicate how Cloudistics should distribute the updated compute category's allocations (right column).
  6. Click Change Compute Category.

Moving a node to a different migration zone

To successfully remove a compute node from its original migration zone, your infrastructure must have sufficient unused resources in that migration zone.

Note: You cannot change a migration zone for a compute node while application instances are running on the compute node.

  1. Put the compute node in maintenance mode.
  2. Select Move to from the Actions drop-down menu.
  3. Select a new migration zone for the compute node.
  4. Indicate how Cloudistics should reduce the original migration zone's allocations (left column).
  5. Indicate how Cloudistics should increase the updated migration zone's allocations (right column).
  6. Click Move.

 

Learn more:

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments