Add additional disks to existing virtual machines.

If you add a disk to an Azure machine, the persistent disk or non-persistent disk is deployed in the resource group that includes the machine.

When you add a disk to an Azure machines, you can also encrypt the new disk using the Azure disk encryption set configured in the storage profile.

You cannot add a disk to an Azure machine with an unmanaged disk.

When you add a disk to vSphere machines, you can select the SCSI controller, the order of which was set in the cloud template and deployed. You can also specify the unit number for the new disk. You cannot specify a unit number without a selected controller. If you do not select a controller or provide a unit number, the new disk is deployed to first available controller and assigned then next available unit number on that controller.

If you add a disk to a vSphere machine for a project with defined storage limits, the added disk must not exceed the storage limits. Storage limits consider the actual capacity for thick and thin resource provisioning so that you cannot over-provision using thin provisioning.

If you use VMware Storage DRS (SDRS) and the datastore cluster is configured in the storage profile, you can add disks on SDRS to vSphere machines.

Attach a SaltStack Resource to a deployment resource so that you can install a Salt minion and update the Salt configuration on the virtual machine. You can use this action to update a configuration on a resource or attach the resource and install the minion on another resource in the deployment.

The Attach Salt Resource action is available if you configured the SaltStack Config integration.

To apply a configuration, you must select an authentication method. The

Remote access with existing credentials

uses the remote access credentials that are included in the deployment. If you changed the credentials on the machine after deployment, the action can fail. If you know the new credentials, use the Password authentication method.

The

Password

and

Private key

use the user name and the password or key to validate your credentials and then connect to the virtual machine using SSH.

If you do not provide a value for the Master ID and Minion ID, Salt creates the values for you.

You can cancel the request on the deployment card or in the deployment details. After you cancel the request, it appears as a failed request on the

Deployments

page. Use the

Delete

action to release any deployed resources and clean up your deployment list.

Canceling a request that you think has been running too long is one method for managing deployment time. However, it is more efficient to set the

Request Timeout

in the projects. The default timeout is two hours. You can set if for a longer period of time if the workload deployment for a project requires more time.

Change the name of a disk to a meaningful display name.

This action changes the display name in:

Topology (Node view)
Topology (Tree view)
Side panel
Resource name is day 2 actions, such as "Resize Disk"
All Resources grid view
Volumes gride view

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

Automation Service Broker

.

Changes the deployment owner to the selected user or Active Directory group. The selected user or AD group must be an administrator or a member of the same project that deployed the request. Only users or AD groups defined in the project are available to become the owner. Custom groups are not eligible to be the target owner.

When a cloud template designer deploys a template, the designer is both the requester and the owner. However, a requester can make another project member the owner.

You can use policies to control what an owner can do with a deployment, giving them permissions that are more restrictive or less restrictive.

You use the change project action to move a deployment from one project to another project.

The change project action is available for deployments with deployed resources, migrated resources, onboarded resources, and deployments with a mixture of deployed, migrated, and onboarded resources.

Supported resources include the following resource types and constraints:

Deployments with deployed resources can contain virtual machines, disks, load balancers, networks, security groups, Azure groups, NATs, gateways, custom resources, Terraform configurations, and Ansible and Ansible Tower resources.
Deployments with migrated resources can contain virtual machines, disks, load balancers, networks, security groups, NATs, gateways, and custom resources.
Deployments with onboarded resources can contain virtual machines, disks, and networks.
If you add an unsupported resource type in any deployment type, deployed, migrated, or onboarded resources, you cannot run the change project action.

Roles, considerations, and constraints for deployments with deployed, migrated, onboarded, and hybrid/mixed resources:

To change the project of a deployment with deployed or migrated resources, the initiating user must have the following role:
Cloud administrator.
You can only change the project when the target project contains all the cloud zones where the deployment's machines and disks are deployed. The moved deployment is then subject to the configured limits of the target project, including instance count, memory, CPU, and storage. After the move, the current usage is released from the source project.
After you move a deployment to the target project, it is subject to the policies of target project. For example, lease, day 2 actions, resource quota, and other polices. To move a deployment, the deployment lease defined by the lease policy of the target project cannot expire in the next 24 hours.
The Change Project action is available for deployments where the custom resources are scoped to be available to any project. The lifecycle and day 2 actions for each custom resource in the deployment must be shared with all projects to ensure that you can continue to manage the custom resource using lifecycle actions or day 2 actions after you move the deployment to the new project.
The extensibility constraints of the target project must match the vRO integration or the same ABX FaaS provider as the source project. The integrations and providers must match so that you can manage the custom resource using lifecycle actions or day 2 actions after you move the deployment to the new project.
The Change Project action is available for deployments with Terraform configurations where all the content sources are shared. If any content sources used in the deployment are not shared, the Change Project action fails validation and does not run.
If a Change Project action fails because a Terraform GitHub repository content source was not shared, you can note the corresponding ID that you must share and then share the source. To share the source repository, select
Infrastructure
Integrations
and select the GitHub integration. In the open integration page, click the Projects tab, expand the project that contains the repository for the failed action and turn on the sharing for that repository. You can also use the API to share the content source repositories.
The Change Project action might not be available if you migrated a deployment that contains a custom resource, where the custom resource includes an update action, and you have performed an iterative update of the deployment by redeploying the cloud template.

Roles, considerations, and constraints for deployments with onboarded resources:

To move a deployment with onboarded resources, the initiating user must have at least one of the following roles:
Cloud administrator.
Manage Deployments permission. This permission can be defined as a custom role.
Project administrator of the target project.
Project member of the target project and the deployments are shared between all users in the target project.
While you can move onboarded resources to a project that does not contain the same cloud zones, if the target project does not have the same cloud zones, any future day 2 actions involving cloud account / region resources that you run might not work.

General considerations:

If you are an administrator who is moving the deployment, you might move the deployment to a project where the owner is not a member and therefore loses access. To resolve the problem, you can add the owner to the target project, move the deployment to a project where they are a member, or use the Change Owner action.

To associate a security group with the machine network, the security group must be present in the deployment.

Dissociating a security group from all networks of all machines in a deployment does not remove the security group from the deployment.

These changes do not affect security groups applied as part of the network profiles.

This action changes the machine's security group configuration without recreating the machine. This is a non-destructive change.

Review the following requirements for a successful connection.

Create a snapshot of a virtual machine disk or a storage disk.

In addition to providing a snapshot name, you can also provide the following information for the snapshot:

If you are allowed only two snapshots in vSphere and you already have them, this command is not available until you delete a snapshot.

When creating a snapshot for a Google Cloud Platform machine, you can also create a disk snapshot of the attached disks. The combined snapshot allows you to manage the machine as the attached disks as a single entity.

Deployments

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 disks

Delete an Azure virtual machine disk or managed disk snapshot.

This action is available when there is at least one snapshot.

This option is only available if the feature is turned on.

Turn off the ability to run log queries on Azure virtual machine logs.

Select the name of the extension that you want to deactivate. If there is no extension name to select, then the log analytics are not currently enabled on this machine.

To work with the log analytics, Azure Monitor and the cloud template must be configure to support the workspace. See Log Analytics.

The Enable option is only available if the feature is not currently turned on.

Turn on the Azure virtual machine to edit and run log queries on data collected by Azure Monitor logs.

You provide the extension name. The workspace ID and key must be the values that are configured in Azure.

To work with the log analytics, Azure Monitor and the cloud template must be configure to support the workspace. See Log Analytics.

To view any changes that were made to the Terraform machines on the cloud platforms that they were deployed on and update the deployment, you first run the Refresh Terraform State action, and then run this Get Terraform State action.

When the file is displayed in a dialog box. The file is available for approximately 1 hour before you need to run a new refresh action. You can copy it if you need it for later.

You can also view the file on the deployment History tab. Select the Get Terraform State event on the Events tab, and then click

Request Details

. If the file is not expired, click

View content

. If the file is expired, run the Refresh and Get actions again.

You can run other day 2 action on the Terraform resources that are embedded in the configuration. The available actions depend on the resource type, the cloud platform that they are deployed on, and whether you are entitled to run the actions based on a day 2 policy.

Deployments

Power off the deployment after first attempting to shutdown the guest operating systems. If the soft power off fails, a hard power off still runs.

Machines

Power off the machine after first attempting to shut down the guest operating systems. If the soft power off fails, the hard power off still runs.

Deployments

Machines

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.

Rebuild several or all virtual machines in the deployment where the deployment failed or not all requested VMs are provisioned successfully.

The rebuild process keeps the same configuration, such as name, ID, IP address, machine data store, and custom properties for each selected machine.

A non-persistent disk that is attached to a virtual machine is wiped clean and then recreated as part of the build action. Any attached first class disks are detached and the contents is retained. After you rebuild the machine, you can re-attach the disk.

For machines with a missing image, you must select a valid image to rebuild.

Rebuild a virtual machine where the deployment resulted in a partial deployment, the virtual machine is not usable, or to reprovision a problematic virtual machine after a successful deployment.

The rebuild process keeps the same configuration, such as name, ID, IP address, machine data store, and custom properties.

A non-persistent disk that is attached to a virtual machine is wiped clean and then recreated as part of the build action. Any attached first class disks are detached and the contents is retained. After you rebuild the machine, you can re-attach the disk.

Change the load balancer size and logging level.

You can also add or remove routes, and change the protocol, port, health configuration, and member pool settings.

For NSX load balancers, you can enable or deactivate the health check and modify the health options. For NSX-T, you can set the check to active or passive. NSX-V does not support passive health checks.

Add, edit, or remove firewall rules or constraints based on whether the security group is an on-demand or an existing security group.

To retrieve any changes that were made to the Terraform machines on the cloud platforms that they were deployed on and update the deployment, you first run this Refresh Terraform State action.

To view the file, run the

Get Terraform State

action on the configuration.

Use the deployment history tab to monitor the refresh process.

Remove disks from existing virtual machines.

If you run the day 2 action on a deployment that is deployed as vSphere machines and disks, the disk count is reclaimed as it applies to project storage limits. Storage limits consider the actual capacity for thick and thin resource provisioning so that you cannot over-provision using thin provisioning. The project storage limits do not apply to additional disks that you added after deployment as a day 2 action.

Force a virtual machine restart without shutting down the guest operating system.

Increase or decrease the CPU and memory of a virtual machine.

Increase or decrease the size of your boot disk medium.

If you run the day 2 action on a deployment that is deployed as vSphere machines and disks, and the action fails with a message similar to “The requested storage is more than the available storage placement,” it is likely due to the defined storage limits on your vSphere VM templates and the content library that are defined in the project. Storage limits consider the actual capacity for thick and thin resource provisioning so that you cannot over-provision using thin provisioning. The project storage limits do not apply to additional disks that you added after deployment as a day 2 action.

Increase the capacity of a storage disk.

If you run the day 2 action on a deployment that is deployed as vSphere machines and disks, and the action fails with a message similar to “The requested storage is more than the available storage placement,” it is likely due to the defined storage limits on your vSphere VM templates and the content library that are defined in the project. Storage limits consider the actual capacity for thick and thin resource provisioning so that you cannot over-provision using thin provisioning. The project storage limits do not apply to additional disks that you added after deployment as a day 2 action.

For the vSphere Storage DRS, you can relocate the virtual machine within the cluster of the current LUN lacks sufficient space.

You must have an existing snapshot to use this action.

If you created a snapshot for a Google Cloud Platform machine that included the attached disks, the full snapshot is reverted.

The tasks are defined in your Puppet instance. You must be able to identify the task and provide the input parameters.

Increase or decrease the number of Tanzu Kubernetes worker node virtual machines in your deployment.

For an example, see How to move a deployed machine to another network.

If the deployment is based on vSphere resources, and the machine and disks include the count option, storage limits defined in the project might apply when you increase the count. If the action fails with a message similar to “The requested storage is more than the available storage placement,” it is likely due to the defined storage limits on your vSphere VM templates that are defined in the project. The project storage limits do not apply to additional disks that you added after deployment as a day 2 action.

There are some properties that cannot be updated using this action. See Deployment properties that you cannot update using day 2 actions in VMware Aria Automation.

Unregister machines to remove them from

VMware Aria Automation

management and inventory. The machines are not removed from the cloud platform.

Unregistered machines are available for onboarding. You can run the onboarding workflow to bring them back under management. For example, you might want to onboard a machine into a new project or a different

VMware Aria Automation

instance.