Actions Library Overview

Overview

The Actions Library is the Workload Manager data structure for storing on-demand actions and lifecycle actions. Users with the WM_ADMIN or WM_DEV_OPS role can view, create and share custom actions using the Actions Library page which is accessible from the Actions Library tab of the main menu. The Actions Library includes a set of OOB on-demand actions which are also referred to as platform actions.

Characteristics of on-demand actions, lifecycle actions, and the out-of-box platform actions are summarized below.

On-Demand Actions

On-Demand actions have the following characteristics:

  • Are manually invoked by the user from various screens in Workload Manager UI, including the Deployments List page, Deployment Details page, Virtual Machines List page, Virtual Machine Details page, and Application Profiles page.

  • Include Workload Manager OOB platform actions and custom on-demand actions.

  • Platform actions:

    • Are visible to all users and subtenants by default but can be restricted to certain users and subtenants by a root tenant administrator.

  • Custom on-demand actions:

    • May be one of these action types:

      • Invoke Web service

      • Command or script

      • Puppet

      • UCS Director workflow 

      • Chef

      • Ansible

    • The Invoke Web service action type may be executed against a VM, a deployment, or an application profile. All other action types are only executed against a VM. 

    • Action types executed against a VM can be defined to be executed on the VM if the management agent is installed on the VM (agent actions), or externally (external actions).

    • May include custom fields that are entered by the user at the time of action execution.

Lifecycle Actions

Lifecycle actions:

  • Are automatically invoked by Workload Manager when a deployment initiated through Workload Manager passes through a specific phase of its lifecycle.

  • Are always custom actions defined by the user.

  • Are always of type Command or script.

  • Are always executed against VMs deployed through Workload Manager.

  • Can be defined to be executed on the VM if the management agent is installed on the VM (agent actions), or externally (external actions).

  • Can be made available to only certain VMs based on the VM's associated service or application profile, and, for external actions, the associate cloud region.

  • Agent actions:

    • Execute in the target VM.

    • May be referenced in:

      • Node Initialization and Cleanup settings of a tier in the Application Profile Topology Modeler tab.

      • Agent Lifecycle Actions section of the Service Definition form.

  • External actions:

    • Execute in a container in Cloud Remote if Cloud Remote is deployed in the region where the VM is deployed.

    • Execute in a container in the management cluster if Cloud Remote is not deployed in the region where the VM is deployed.

    • May be referenced in:

      • External Initialization settings of a tier in the Application Profile Topology Modeler tab.

      • External Lifecycle Actions section of the Service Definition form.

      • External Lifecycle Actions section of the Regions tab for a cloud region.

  • May include custom fields which are entered by the user when the action is referenced in an application profile, a service definition, or a regions tab.

Platform Actions

Platform action refer to OOB on-demand action. These actions are always executed against a particular VM. Like custom on-demand actions executed against a VM, the platform actions are visible as entries in the VM action dropdown menu in the Virtual Machines List page and the VMs tab of the Tiers tab of the Deployment Details page. They are also visible as action buttons on the right panel of the VM Details page.

Platform actions are visible to all users and subtenants by default, but visibility and use of platform actions can be restricted to only certain users and subtenants by a root tenant administrator. The following table summarizes properties of the platform actions.

All platform actions require the VM to be a managed VM except:

  • Terminate, which can be applied to both managed and unmanaged VMs, and

  • Import, which can only be applied to unmanaged VMs.

Action Name

DescriptionRequired VM State 1Supported Clouds
StartPowers on the VMStoppedAll













StopPowers off the VMRunning
Reboot

Reboots the VM.

While VMware and OpenStack support both soft and hard reboot, the CloudCenter Suite performs a soft reboot on OpenStack environments and a hard reboot on VMware environments.

Here is how each cloud currently handles a reboot operation:

  • OpenStack has both soft and hard reboot options.
  • VMware has a separate option for graceful (GuestOS) reboot/shutdown and supports it only when VMware tools is installed.
  • Google cloud issues a warning in their UI that they implement a hard reboot.
  • AWS performs a hard reboot if the instance does not cleanly shut down within four minutes.
  • Azure RM attempts a graceful shutdown by default and if it does not complete in 5 minutes they perform a hard shutdown.
Running
Terminate

Stops (if running) and removes the VM from the cloud

Running or stopped

ImportMoves a VM from the Unmanaged category into the Managed category. See Virtual Machine Management for additional context.Running or stopped
Install Agent

Installs the management agent on an Imported VM from the Workload Manager UI. See Virtual Machine Management > Install Agent for additional details.

If any version of the agent is already installed on a VM, then this action will not be available for this VM.

The Install Agent action requires the user to specify the OS type and login credentials during submission.


Running
Upgrade Agent

Upgrades the agent on a Managed VM to the latest released Workload Manager agent version from the Workload Manager UI. See Virtual Machine Management > Upgrade Agent for additional details.

You can only upgrade a VM running CloudCenter Legacy 4.7.3 or later versions. See Virtual Machine Management > Install Agent for additional details.

If the latest version of the agent is already installed on a VM, then this action will not be available for this VM.

Running

Create and Attach Volume


Creates and attache a volume of a storage type defined in Workload Manager. The user specifies the storage type and size via a dialog box when the action is initiated. Cisco does not support the attachment of volumes created outside of Workload Manager.

Requires at least one storage type to be define for the region where the VM is deployed. Upon execution of this action you are prompted for volume type and size.

Running or stopped

Detach VolumeDetaches volumes from the existing VM.

Running or stopped

Sync VM information

Updates the current VM information from Workload Manager so the latest VM metadata information is visible.

Running, stopped, or started

Resize Instance Type

Lets you select a different instance type from among the instance types defined fior


Stopped


Create SnapshotCreates the image snapshot for the given VM.

Running or stopped

vCenter

1 For more information on VM states, see Deployment, VM, and Container States.


  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks