Deploying action scripts

Action scripts provide an interface that can add custom processing to Turbonomic actions.

Action scripts execute on a remote server (a VM or a container) that you have configured as a Turbonomic target. That server includes a manifest file that identifies the scripts you have deployed, as well the entities and actions they can respond to. Turbonomic discovers these scripts via the manifest and presents them as orchestration options for actions in automation policies.

For example, assume you have defined a script with:

  • name: MyVmMoveAction

  • entityType: VIRTUAL_MACHINE

  • actionType: MOVE

Following this example, you can use the API to add orchestration to a policy for move actions on VMs. Because you have defined a script for that action, you can specify Action Script as the orchestration type, and you can choose the MyVmMoveAction script as the orchestration workflow to perform.