Configuring Automated Deployment for Approved Service Requests

Embotics® vCommander® can automatically deploy new service requests once they are approved. When automated deployment is configured, new service requests can move from approval to completion with no intervention. Automated deployment means that administrators are freed from decisions related to capacity, storage and networking. vCommander emails you when automated deployment failures occur, and when changes in your infrastructure cause deployment destinations that you have configured to become invalid.

To automatically deploy approved new service requests, you must:

create one or more deployment destinations

set up an approval workflow with the Automatically deploy approved requests setting enabled

These tasks are detailed below, for each managed system type.

See How Deployment Destinations Work for more details, including best practices for SCVMM managed systems.

See Creating a Deployment Destination for Fenced Networks to learn how to set up a deployment destination for vCenter fenced networks.

NotePencil-smallOnce you've configured a deployment destination or approval workflow for one of your customers or departments, select it in the list and click Copy as a shortcut for setting up additional customers or departments. Note that if you've copied a deployment destination, you cannot change the target managed system.

vCenter: Configuring destinations for automated deployment

Access through:

Configuration menu > Service Request Configuration > Provisioning Configuration tab > Automatic Deployment Placement pane

Available to:

vCommander Role of Superuser or Enterprise Administrator

Administrator and All Operator Levels of Access Rights

1.Select Configuration menu > Service Request Configuration > Provisioning Configuration tab.

2.On the Automated Deployment Placement pane, right-click a vCenter managed system and select Add, or select a destination in the tree and click Edit.

3.On the Name page, enter a name that identifies the destination (maximum 100 characters).

4.On the Assignment page:

To create a destination for automatic deployment that any user account can use, select Default Destination.

To assign the destination to specific organizations, users and groups, select Assign this destination to these specific users/groups. On the Organizations tab, select an organization from the drop-down menu. On the Users/Groups tab, enter the login or email address for one or more users or groups. You can assign a single destination to both organizations and users/groups.

NotePencil-smallIf multiple destinations are available to a user, the destination with the most capacity is chosen.

5.On the Folder page, select the appropriate folder in the tree.

7.On the Target page, select a target host or cluster. If you have chosen a cluster that has its automation level for VMware DRS (load balancing) set to Manual, you can select a host within that cluster. Otherwise, this selection is unavailable.

8.Choose to deploy based on Peak Capacity or Average Capacity by selecting from the drop-down menu. For more information, see Managing Host and Cluster Capacity.

9.On the Networks page, you define the network(s) to which VMs will attach once deployed.

Enable the option Connect to the same network as the source service if you want to match the source template's settings.

NotePencil-smallBecause we recommend the use of network zones, this option is deprecated.

Otherwise, select one or more networks from the list of available networks and click the down arrow (or double-click) to move them to the Configured Networks list.

NotePencil-smallIf no suitable configured network is available for the requested network zone, VM deployment will fail.

See Configuring Networks to learn how to assign networks to zones.

The $NETWORK deployment parameter specified by a request approver or in a script overrides the network zone specified on the request form.

10.On the IP Pools page, if an IP pool is linked to a target network:

To have vCommander automatically assign a static IP address to each NIC, select Assign each NIC a static IP address from pool. For this option, a customization specification must have been configured for the source service. For more information, see Adding a vCenter Service to the Catalog.

To allow IP addresses to be assigned manually during deployment, select Do not assign any IP addresses.

11.On the Isolated (fenced) Networks page, if you want to allow fenced deployments to be placed on this destination, check Enable fenced networks. See Creating a Deployment Destination for Fenced Networks for details on these settings.

11.On the Storage page, select a datastore or datastore cluster from the Available Storage list and click the down arrow icon (or double-click the datastore) to move it to the Configured Storage list.

Adding a datastore cluster means that all datastores in that cluster at deployment time are automatically available for deployment. There's no need to update the deployment destination when datastores are added to or removed from a datastore cluster. Note that if you add a clustered datastore as well as the datastore cluster itself, the clustered datastore is removed from the Configured Storage list; a dialog pops up to inform you when this happens.

Enable Show clustered datastores to show datastores that are part of a datastore cluster.

As required, add other datastores or datastore clusters.

Making multiple datastores available:

ensures that VMs are automatically deployed to datastores with available free space

allows datastores with different storage tiers to be selected for automated deployment

ensures that VMs with disks on different storage tiers are deployed to meet service level agreements

NotePencil-smallDatastores excluded from capacity calculations are not displayed as available datastores. For more information, see Excluding a datastore from capacity calculations.
NotePencil-smallWhile HA reserved capacity affects how vCommander chooses the best deployment destination, it does not invalidate deployment destinations. For more information, see About capacity reserved for high availability failover.

12.On the Disk Format page, select the format used to store the VM's virtual disks:

Same format as source: Use the disk format of the source template or VM.

Thin: Allocate disk space on demand. Supports over-allocation of storage resources.

SEsparse: Allocate disk space as it is used by the guest OS. Supports over-allocation of storage resources. Block size is configurable and space may be reclaimed.

NotePencil-smallThe SEsparse format is supported only for vSphere version 5.1 or higher and for hardware version 9 or higher. The source VM must have one and only one snapshot.

Thick - Lazy Zeroed: Allocate disk space now. Disk blocks are zeroed out on first write.

Thick - Eager Zeroed: Allocate disk space now. All disk blocks are zeroed out during disk creation. This is required to support clustering features such as Fault Tolerance.

13.On the Summary page, review your settings and click Finish.

NotePencil-smallFor standalone hosts only, the host property appears as "Not set" on the Summary page. Any standalone host will also appear as "Not set" on the Details pane for the placement destination you created.

Now you need to set up an approval workflow to enable automated deployment.

SCVMM: Configuring destinations for automated deployment

Access through:

Configuration menu > Service Request Configuration > Provisioning Configuration tab > Automatic Deployment Placement pane

Available to:

vCommander Role of Superuser or Enterprise Administrator

Administrator and All Operator Levels of Access Rights

1.Select Configuration menu > Service Request Configuration > Provisioning Configuration tab.

2.On the Automated Deployment Placement pane, right-click an SCVMM managed system and select Add, or select a destination in the tree and click Edit.

3.On the Name page, enter a name that identifies the destination (maximum 100 characters).

4.On the Assignment page:

To create a destination for automatic deployment that any user account can use, select Default Destination.

To assign the destination to specific organizations, users and groups, select Assign this destination to these specific users/groups. On the Organizations tab, select an organization from the drop-down menu. On the Users/Groups tab, enter the login or email address for one or more users or groups. You can assign a single destination to both organizations and users/groups.

NotePencil-smallIf multiple destinations are available to a user, the destination with the most capacity is chosen.

6.On the Target page, select a target cluster. vCommander uses capacity information (from nightly performance updates) to choose a host on that cluster as the target.

7.Choose to deploy based on Peak Capacity or Average Capacity by selecting from the drop-down menu. For more information, see Managing Host and Cluster Capacity.

8.On the Networks page, you define the network to which VMs will attach once deployed.

By default, Connect to the same network as the source service is disabled. Enable this option if you want to match the source template’s settings.

Otherwise, select one or more networks from the list of available networks and click the down arrow (or double-click) to move them to the Configured Networks list.

See Configuring Networks to learn how to assign networks to zones.

NotePencil-smallThe $NETWORK deployment parameter specified by a request approver or in a script overrides the network zone specified on the request form.

9.On the Storage page, select a datastore from the list of available datastores and click the down arrow (or double-click) to move it to the Configured Datastores list.

If required, select other datastores to add to the list of configured datastores. Making multiple datastores available:

ensures that VMs can be automatically deployed to datastores that have free space available

allows datastores with different storage tiers to be selected for automated deployment

ensures that VMs with disks on different storage tiers can be deployed to meet service level agreements

NotePencil-smallDatastores that have been excluded from capacity calculations are not displayed on the list of available datastores. For more information, see Managing Host and Cluster Capacity.

10.On the Disk Format page, select the format in which to store the VM's virtual disks.

11.On the Summary page, review your settings and click Finish.

NotePencil-smallFor standalone hosts only, the host property appears as "Not set" on the Summary page. Any standalone host will also appear as "Not set" on the Details pane for the placement destination you created.

Now you need to set up an approval workflow to enable automated deployment.

AWS: Configuring destinations for automated deployment

Access through:

Configuration menu > Service Request Configuration > Provisioning Configuration tab > Automatic Deployment Placement pane

Available to:

vCommander Role of Superuser or Enterprise Administrator

Administrator and All Operator Levels of Access Rights

NotePencil-smallYou must configure distinct deployment destinations for each AWS region. EC2 VMs (instances) must be deployed in the same AWS region as their source template (AMI). In addition, all resources in a CloudFormation template must be deployed to the same region.

1.Select Configuration menu > Service Request Configuration > Provisioning Configuration tab.

2.On the Automated Deployment Placement pane, right-click an AWS managed system and select Add, or select a destination in the tree and click Edit.

3.On the Name page, enter a name that identifies the destination (maximum 100 characters).

4.On the Assignment page:

To create a destination for automatic deployment that any user account can use, select Default Destination.

To assign the destination to specific organizations, users and groups, select Assign this destination to these specific users/groups. On the Organizations tab, select an organization from the drop-down menu. On the Users/Groups tab, enter the login or email address for one or more users or groups. You can assign a single destination to both organizations and users/groups.

NotePencil-smallIf multiple destinations are available to a user, the first destination alphabetically is chosen.

6.On the Target page, select a VPC (Virtual Private Cloud) or EC2-Classic (if you are not using VPCs).

In the Destination tree, "EC2-Classic" is a container to represent the parent of instances running in EC2-Classic (as opposed to in a VPC).

NotePencil-smallAlthough CloudFormation templates require only a region as target, the Add Automated Deployment Placement wizard requires that you specify a VPC or EC2-Classic, as well as additional information in subsequent wizard pages. Only the target region is used when deploying CloudFormation templates, unless you are using any of the #{destination.*} variables to populate parameter values.

7.On the Resources and Security page:

If you chose EC2-Classic on the Target page, choose an Availability Zone from the drop-down menu, or keep the default setting, Let the system decide, to let AWS choose the availability zone.

Optionally, specify a Key Pair Name to assign to the deployed VM. Only key pairs available in the target region are available for selection. Specifying a key pair for a deployment destination allows you to configure per-user key pairs without having to include the Key Pair element on the request form. If you also include the Key Pair element on the request form, the requester's selection takes precedence. If you do not specify a key pair here and none is specified on the request form, no key pair is assigned to the deployed VM.

Optionally, specify one or more Security Group Names. Only security groups assigned to the target VPC are shown (or, if your target is EC2-Classic, those not assigned to a VPC). If you do not specify a security group, AWS assigns the deployed VM to the default security group.

Optionally, enter the name of an IAM Role to assign to the deployed VM. The maximum number of characters is 255. Configuring the role in the deployment destination rather than in the catalog blueprint makes sense if you deploy the same template (AMI) to multiple deployment destinations, or if you have a large number of catalog entries. If an IAM role is also configured in the catalog blueprint, the blueprint takes precedence. Administrators can override the IAM role during manual deployment. To learn more, see Managing Amazon Web Services with Embotics® vCommander®. Important: vCommander does not validate IAM role names, so ensure that role names entered in vCommander match those in AWS. IAM role names are not case-sensitive.

8.If you selected a VPC on the Target page, the Subnets page appears, enabling you to configure networking information.

Select one or more subnets from the Available Subnets list, and click the down arrow to move them to the Configured Subnets list.

See Configuring Networks to learn how to assign subnets to zones.

9.On the Summary page, review your settings and click Finish.

Now you need to set up an approval workflow to enable automated deployment.

Azure: Configuring destinations for automated deployment

Access through:

Configuration menu > Service Request Configuration > Provisioning Configuration tab > Automatic Deployment Placement pane

Available to:

vCommander Role of Superuser or Enterprise Administrator

Administrator and All Operator Levels of Access Rights

Each Azure deployment destination must target an existing resource group, because all Azure Resource Manager resources must be deployed into a resource group. However, when vCommander deploys an ARM template into a new resource group, vCommander chooses the best deployment destination for the service, and then creates the new resource group in the primary region of the resource group targeted by that destination. Subnet and storage options set in the deployment destination are ignored for ARM template deployments.

1.Select Configuration menu > Service Request Configuration > Provisioning Configuration tab.

2.On the Automated Deployment Placement pane, right-click an Azure managed system and select Add, or select a destination in the tree and click Edit.

3.On the Name page, enter a name that identifies the destination (maximum 100 characters).

4.On the Assignment page:

To create a destination for automatic deployment that any user account can use, select Default Destination.

To assign the destination to specific organizations, users and groups, select Assign this destination to these specific users/groups. On the Organizations tab, select an organization from the drop-down menu. On the Users/Groups tab, enter the login or email address for one or more users or groups. You can assign a single destination to both organizations and users/groups.

NotePencil-smallIf multiple destinations are valid for a user, the first destination alphabetically is chosen.

6.On the Target page, select a resource group.

NotePencil-smallWhen an ARM template is configured to be deployed into a new resource group, vCommander creates the new resource group in the primary region of the resource group you select as the target on this page.

7.On the Resources & Security page, select a network security group. All network security groups in the target region are available for selection.

8.On the Subnets page, select a network from the Network drop-down menu.

9.Next, select one or more subnets from the Available Subnets list, and click the down arrow to move them to the Configured Subnets list.

See Configuring Networks to learn how to assign networks to zones.

10.On the Storage page, if you want to make unmanaged storage available for this destination, select one or more unmanaged storage accounts from the Available Storage list, and click the down arrow to move them to the Configured Storage list.

Managed storage is not shown in the list, because it's always available for every destination.

11.On the Summary page, review your settings and click Finish.

Now you need to set up an approval workflow to enable automated deployment.

Azure Classic: Configuring destinations for automated deployment

Access through:

Configuration menu > Service Request Configuration > Provisioning Configuration tab > Automatic Deployment Placement pane

Available to:

vCommander Role of Superuser or Enterprise Administrator

Administrator and All Operator Levels of Access Rights

Microsoft Azure VMs (instances) must be deployed in the same Azure region as their source template (image). Therefore, if you are deploying to multiple Azure regions, you need to configure a service catalog entry and a deployment destination for each region.

Service Catalog entries that will be deployed as individual components are deployed into an existing cloud service, so you must configure a deployment destination for each target cloud service.

Service Catalog entries that will be deployed as a new cloud service (represented as a virtual service in vCommander) can be deployed into a region, affinity group or virtual network.

1.Select Configuration menu > Service Request Configuration > Provisioning Configuration tab.

2.On the Automated Deployment Placement pane, right-click an Azure Classic managed system and select Add, or select a destination in the tree and click Edit.

3.On the Name page, enter a name that identifies the destination (maximum 100 characters).

4.On the Assignment page:

To create a destination for automatic deployment that any user account can use, select Default Destination.

To assign the destination to specific organizations, users and groups, select Assign this destination to these specific users/groups. On the Organizations tab, select an organization from the drop-down menu. On the Users/Groups tab, enter the login or email address for one or more users or groups. You can assign a single destination to both organizations and users/groups.

NotePencil-smallIf multiple destinations are valid for a user, the first destination alphabetically is chosen.

5.On the Target page, select a region, affinity group, virtual network or existing cloud service.

6.If you chose a virtual network or a cloud service within a virtual network, the Subnets page appears.

Select a subnet from the Subnet drop-down menu.

See Configuring Networks to learn how to assign networks to zones.

7.On the Summary page, review your settings and click Finish.

Now you need to set up an approval workflow to enable automated deployment. See the following section.

Setting up an approval workflow to enable automated deployment

Access through:

Configuration menu > Service Request Configuration > Approval Workflow tab

Available to:

vCommander Role of Superuser and Enterprise Administrator

If you have already set up an approval workflow for new service requests, simply enable Automatically deploy approved requests on the Automation Options page.

Otherwise, create an approval workflow, configuring the following options:

On the Name & Type page, select when a new request is created from the Apply this workflow drop-down menu.

On the Automation Options page, enable Automatically deploy approved requests.

NotePencil-smallIf you are using this approval workflow only for automated deployment, you do not need to configure any other options (such as workflow steps). For complete information, see Creating an Approval and Pre-Provisioning Workflow.

Deleting destinations for automated deployment

Access through:

Configuration menu > Service Request Configuration > Provisioning Configuration tab > Automatic Deployment Placement pane

Available to:

vCommander Role of Superuser or Enterprise Administrator

Administrator and All Operator Levels of Access Rights

You can delete a deployment destination by managed system (in which case the destination is completely deleted), or by organizations and users (in which case you have a choice whether to delete the destination for the selected user, or all users).

If you are viewing destinations by Organizations and Users, right-click a destination and select Delete. In the Delete Destination dialog, decide whether to delete the destination for this user, or for all users.

caution

If you delete the destination for all users, the destination is completely deleted.

If you are viewing destinations by Managed Systems, right-click a destination, select Delete, and click Yes to confirm. The destination is completely deleted.