Before you start the PoP deployment, follow the section ‘Setup the Prerequisites’ and setup the prerequisites to deploy PoP.
You will be able to deploy the PoP following the below instructions
- Download the PoP Deployment Package
- Deploy the required Infrastructure through the Azure ARM template
After successful PoP deployment, the PoP details and its health status is reported under PoP Management.
Step 1 : Download the PoP Deployment Package
Follow the below steps to download the PoP deployment package.
To download the PoP Deployment Package:
- Log in to MVISION Cloud.
- Go to Service Management > Microsoft Azure, and choose a registered Azure Account.
- In the Overview section, Deploy New PoP.
- Click Download Deployment package and download the package.
The downloaded PoP Deployment package contains the installation files to deploy the PoP and the required artifacts for the PoP to communicate with the MVision Cloud. The Package is valid for 7 days after it is downloaded from MVision Cloud .
Step 2: Deploy the required Infrastructure through the Azure ARM template
The ‘Infrastructure.tar,’ that is part of the PoP Deployment Package (PopDeployment.tar), contains the ARM template (‘Azure_NewInfra.json’) to create infrastructure in the azure and deploy the PoP.
To deploy the Azure ARM template:
- Navigate to the Templates in Azure Console.
- Navigate to Templates > Add > Provide Name and Description > Copy and paste the Azure_NewInfra.json contents > Add.
- Once the template is created choose Deploy.
- Provide the required input parameters in the template:
o Subscription: Azure Subscription account name
o Resource Group: Select Resource group name which is created before deployment.
o Location: Auto-Populated according to resource group.
o Pop Name: Specify the unique name for the PoP that you need to create in the Pop Name field.
o Zone: An availability zone is a logical data center in a region available for use by any Azure customer. Select the number of Availability zones that needs to be configured from dropdown.
o Virtual Machine size: Specify the required virtual machine size. Minimum and recommended size is Standard_D2s_v3.
o Admin Username: Enter desired username for virtual machine
o Admin Password Or Key: Navigate to the SSH key created in pre-requisite step, copy the Public key value and provide as input here.
o Actions: List of roles assigned to PoP Virtual Machines to Allow actions on Azure Resources. Recommended list is
o Not actions: List of roles assigned to PoP Virtual Machines to Deny action on Azure Resources. Recommended list is ["Microsoft.Authorization/*/Delete","Microsoft.Authorization/elevateAccess/Action","Microsoft.Blueprint/blueprintAssignments/write","Microsoft.Blueprint/blueprintAssignments/delete","Microsoft.Compute/galleries/share/action"]
o Role Name: Provide a unique name for the role definition.
o Role Description: Provide detailed description of the role definition.
o Desired Secondary Node Capacity: Enter the desired capacity of nodes I.e., number of secondary machines/Virtual machine scale sets. [Min=1, Max=10]
o Cwpp Package Url: Provide PoPDeployment.tar URL path stored in Azure Storage as mentioned in pre-requisite step within single quotes like 'https://URL'
o Cwpp Deployment Script: Provide AzureDeploymentScript.sh URL path stored in Azure Storage as mentioned in pre-requisite step without single quotes like https://URL
After launching Cloud Formation, it takes about 20 minutes to deploy the PoP. You can check the deployment status in the cloud formation stack console in AWS. After the PoP Deployment, the PoP deployed in your account will update the status in MVISION Cloud. You can check the PoP details in the PoP Management page.