Azure Stop VM

Objective

The goal of the tutorial is to stop the Virtual Machine(s). This automation includes:

• Stop the Virtual Machine using One or more Virtual Machine Id(s) / Virtual Machine Name and Resource group Name using Azure CLI.

We will walk through each of the FlexDeploy features that will be created/configured to accomplish this goal and stop the Virtual Machine in a very short amount of time.

Checklist

Configure cloud account

First, an Azure account needs to be configured under Integrations. FlexDeploy will connect to the right Azure Subscription with provided details and stops the Virtual Machine(s).

1. Select Integrations from the Menu.

2. Navigate to the Cloud tab from the left-hand pane.

3. Create a new Cloud account of the provider type “Azure” with the “+ Create” button.

It should have a Client ID, Client Key, Tenant Id, and Subscription Id configured in it. The Client ID must have relevant access to the Virtual Machine and make other associated changes(Application Setting update etc).

1. Client Key is a password field and hence needs to be kept hidden. To update the same click on the pencil icon as shown below

2. Update the Client Key value under Secret Text. This is to make sure no one else can retrieve the password

After saving the credential, click on Save on the cloud instance. Do a Test Connection. The green color ticket mark will show that the connection is successful.

Utility Workflow

Navigate to the Workflows tab and create a workflow using the “+”(Click to create new Workflow) button

Next, create one Utility workflow as shown below. The Workflow Type field defines the type of workflow.

Utility Workflow

1. Navigate to the Workflows tab

2. Select the “+” button from the left-hand pane to create a new workflow with type as Utility.

The Workflow Group and Subgroup define the folder hierarchy. Once the workflow is created, it should look like the below. No constraint on workflow or folder naming convention.

The steps of the workflow execution can be configured through the Definition section.

Below given is a sample utility workflow to stop the Virtual Machine.

The StopVM operation returns three output variables. To capture them and use them for further processing/evaluation, one can create three variables and map them against the output parameters. Return As Output drop down option should be set as Yes.

1. First, navigate to the Workflow Definition tab and click on the Variables button

2. Next use Create option to add three output variables.

Map the variables against the output of the StopVM operation to capture the responses and also update the Workflow Input values.

Now, click on save and activate the workflow.

Workflow Inputs

Topology

For detailed steps on how to configure the topology and map the workflows manually, please refer to Configure the Topology for Azure

Target Properties

Selecting the DEV environment mapped to the Target Group will display the configurable properties/Endpoint and allows to the configure the properties.

Provide the value for AzureCloudAccount, and AzureCLIPath(optional if set in classPath), Number of Iterations (optional, default value is 6), and Interval Duration (optional default value is 30sec) and map the localhost as Endpoint as shown below.

Target Properties Info

Create the Azure Stop VM Project using Blank Project

For details steps on how to configure the project and execution, please refer to Create the Azure Start/Stop/Restart VM Project

Reports

With the successful execution of the Utility workflow, a text (.txt) file is created, stored in the reports tab. Every execution will generate a new report with execution Id appended to the text file in the Reports tab.

Click on the text file generated to see the details. This file captures the details of each instance i.e., VM Resource Id, Provision State, and Power State. In the workflow, there were two Azure VM Resource Id’s are provided as input. Hence, the report contains the details of both the Azure VM's. Also, user can download the report file generated.

Congratulations! You have successfully completed the Azure Stop Virtual Machine tutorial.

Now that you have configured FlexDeploy for one Azure VM operation, it is extremely easy to replicate the same for other Azure VM operations. Simply use the Copy Project feature and a new project will be created with all of the configuration completed already. You just need to make the necessary configuration changes.