The available actions also depend on what your administrator entitled you to run.
As an administrator or project administrator, you can set up Day 2 Actions policies in Service Broker. See How do I entitle consumers to Service Broker day 2 action policies.
|Action||Applies to these resource types||For these cloud accounts or integrations||Description|
||Add additional disks to existing virtual machines.|
Change the lease expiration date and time.
When a lease expires, the deployment is destroyed and the resources are reclaimed.
Lease policies are set in Service Broker.
|Connect to Remote Console||Machines||
||Open a remote session on the selected machine.
Review the following requirements for a successful connection.
If your connection attempt indicates that a connection could not be established with the host, you might be required to accept the self-signed certificate.
As an administrator, if you prefer to ensure trusted certificates, see KB2113926 to configure CA signed certificates for ESXi hosts.
|| Create a snapshot of the virtual machine.
If you are allowed only two snapshots in vSphere and you already have them, this command is not available until you delete a snapshot.
||Destroy a deployment.
All the resources are deleted and the reclaimed.
If a delete fails, you can run the delete action on a deployment a second time. During the second attempt, you can select Ignore Delete Failures. If you select this option, the deployment is deleted, but the resources might not be reclaimed. You should check the systems on which the deployment was provisioned to ensure that all resources are removed. If they are not, you must manually delete the residual resources on those systems.
|Machines and load balancers||
||Delete a machine or load balancer from a deployment. This action might result in an unusable deployment.|
||Delete a snapshot of the virtual machine.|
||Add or modify resource tags that are applied to individual deployment resources.|
||Power off the deployment without shutting down the guest operating systems.|
||Power off the machine without shutting down the guest operating systems.|
||Power on the deployment. If the resources were suspended, normal operation resumes from the point at which they were suspended.|
||Power on the machine. If the machine was suspended, normal operation resumes from the point at which the machine was suspended.|
Reboot the guest operating system on a virtual machine.
For a vSphere machine, VMware Tools must be installed on the machine to use this action.
||Change the load balancer protocol, port, health configuration, and member pool settings.|
||Remove disks from existing virtual machines.|
Force a virtual machine restart without shutting down the guest operating system.
Increase or decrease the CPU and memory of a virtual machine.
|Resize Boot Disk||Machines||
||Increase or decrease the size of your boot disk medium.|
|Resize Disk||Storage disk||
Increase the capacity of a storage disk.
||Shut down and restart a running machine.|
|Revert to Snapshot||Machines||
|| Revert to a previous snapshot of the machine.
You must have an existing snapshot to use this action.
|Run Puppet Task||Managed resources||
||Run the selected task on machines in your deployment.
The tasks are defined in your Puppet instance. You must be able to identify the task and provide the input parameters.
||Shut down the guest operating system and power off the machine. VMware Tools must be installed on the machine to use this action.|
||Pause the machine so that it cannot be used and does not consume any system resources other than the storage it is using.|
||Change the deployment based on the input parameters.
For an example, see How to move a deployed machine to another network.
|Update Tags||Machines and disks||
||Add, modify, or delete a tag that is applied to an individual resource.|