Create Azure VNET Site

• Select Manage from the configuration menu in the system namespace. Select Site Management -> Azure VNET Site from the options. Click Add Azure VNET Site.
• Set a name for your VNET in the metadata section.

Go to Site Type Selection section` and perform the following:

Step 2.1: Set region and configure VNET.

• Enter your Azure resource group in the Resource Group field.
• Select a region in the Azure Region drop-down field.
• Select an option for the Select existing Vnet or create new Vnet field and configure as per the following guidelines:
  • For the New Vnet Parameters option, enter the name in the Azure Vnet Name field and enter the CIDR in the IPv4 CIDR block field.
  • For the Existing Vnet option, enter an existing resource group name and VNET name in the Vnet Resource Group and Vnet Name fields respectively.

Step 2.2: Set the node configuration.

Select an option for the Select Ingress Gateway or Ingress/Egress Gateway field and perform one of the following steps accordingly.

Step 2.2.1: Configure ingress gateway site.

For the Ingress Gateway (One Interface) option, perform configuration as per the following guidelines:

• Select an option for the Azure AZ name field that matches the configured Azure Region.
• Select Name of Existing Subnet or New Subnet for the Select Existing Subnet or Create New field. Enter a subnet address in the IPv4 Subnet or Subnet Name and Subnet Resource Group options accordingly.

Note: The Azure Certified Hardware is set to azure-byol-voltmesh by default. You can add more than one node using the Add item option.

Step 2.2.2: Configure ingress/egress gateway site.

For the Ingress/Egress Gateway (Two Interface) option, click Edit to open the two-interface node configuration wizard and enter the configuration as per the following guidelines.

• Select an option for the Azure AZ name field that matches the configured Azure Region.
• Select Name of Existing Subnet or New Subnet for the Select Existing Subnet or Create New field in the Subnet for Inside Interface section. Enter a subnet address in the IPv4 Subnet or Subnet Name and Subnet Resource Group options accordingly.
• Select Name of Existing Subnet or New Subnet for the Select Existing Subnet or Create New field in the Subnet for Outside Interface section. Enter a subnet address in the IPv4 Subnet or Subnet Name and Subnet Resource Group options accordingly.

• In the Site Network Firewall section, optionally select Active Network Policies in the Manage Network Policy field. Select an existing network policy or click Create new network policy to create and apply a network policy. After creating the policy, click Continue to apply.
• Optionally select Active Forward Proxy Policies in the Manage Forward Proxy Policy field. Select an existing forward proxy policy or click Create new forward proxy policy to create and apply a forward proxy policy. After creating the policy, click Continue to apply.

• In the advanced configuration section, enable the Show Advanced Fields option. Select Manage Static Routes for the Manage Static Routes for Inside Network field and click Add item for the Static route list field. Perform one of the following steps:

  • Select Simple Static Route and enter a static route in the Simple Static Route field.
  • Select Custom Static Route and click Configure under the Custom Static Route option and perform the following steps:
    • In the Subnets section, select IPv4 or IPv6 option for the Version field. Enter a prefix and prefix length for your subnet. You can use the Add item option to set more subnets.
    • In the Nexthop section, select a next-hop type for the Type field. Select IPv4 or IPv6 for the Version field in the Address section and enter an IP address accordingly. Click Select interface object in case you choose next-hop type as network interface. Select a network interface or click Add new network interface to create and apply a new network interface. Click Select interface object to apply the interface.
    • In the Attributes section, select supported attributes in the Attributes field. You can select more than one from this list.
    • Click Apply to add the custom route.

• Select Manage Static Routes for the Manage Static Routes for Outside Network field and click Add item for the Static route list field. Follow the same procedure as that of managing the static routes for inside network.

• Click Apply.

Note: The Azure Certified Hardware is set to azure-byol-multi-nic-voltmesh by default. You can add more than one node using the Add item option.

Step 2.3: Set the deployment type.

Select an option for the Select Automatic or Assisted Deployment field and perform further actions as per the following guidelines.

• For the Automatic Deployment option, select an existing Azure credentials object or click Create new azure cred option to load new credential creation wizard. Create the new credentials as per the following guidelines:
  • Enter a name in the metadata section. Optionally set labels and enter a description.
  • Select Azure Client Secret for Service Principal in the Select Cloud Credential Type field. Enter your Azure account client ID, subscription ID, and tenant ID in the Client ID, Subscription ID, and Tenant ID fields.
  • Click Configure under the Client Secret field.
  • Select an option for the Secret Info. If you select Blindfold Secret, enter the secret in the Location field. If you select Clear Secret, enter the secret in the Clear Secret field in either ASCII or base64(binary) formats. To encrypt your secret using Blindfold, see Blindfold your App Secrets. Click Apply.
  • Click Continue to add the new credentials.

• For the Assisted Deployment option, obtain the terraform parameters after this VNET object is created in VoltConsole and perform the site deployment as per the instructions for assisted deployment mentioned in the Deploy Site chapter.

Note: In the Assisted Deployment mode, the deployment options from VoltConsole are not available.

Go to the Site Node Parameters section and enable the Show Advanced Fields option. Perform the following:

• Set the Azure machine type by selecting an option for the Azure Machine Type for Node field.
• Set a scaling limit for the worker nodes by configuring a value for the Auto Scale Limit field. This is optional.
• Enter your SSH key in the Public SSH key field.

Click Continue to complete creating the Azure VNET site.

Note: The Status field for the VNET object shows Generated. You can navigate to the created Azure VNET object using the Manage -> Site Management -> Azure VNET Site option.

• Navigate to the created Azure VNET object using the Manage -> Site Management -> Azure VNET Site option.

• Find your Azure VNET object and click ... -> Plan (Optional) for your Azure VNET to start the action of terraform plan. This creates the execution plan for terraform.

• Navigate to the created Azure VNET object using the Manage -> Site Management -> Azure VNET Site option.

• Find your VNET object and click ... -> Terraform Parameters for it.

• Click Download Params to download the terraform parameters.

Perform this procedure in case you created the VNET object with automatic deployment option.

• Navigate to the created Azure VNET object using the Manage -> Site Management -> Azure VNET Site option. Find your Azure VNET object and click Apply under the Actions column. The Status field for your Azure VNET object changes to Applying.

• Wait for the apply to complete and the status to change to Applied.

• Navigate to Sites -> Sites List. Find your site from the displayed list and verify that the status is ONLINE.

Note: It takes a few minutes for the site to be deployed and status to become ONLINE.

Perform this procedure in case you created the VNET object with assisted deployment option.

• Download Volterra quickstart utility.

          docker pull volterraio/volt-terraform

        

• Run the terraform container.

          docker run --entrypoint tail --name terraform-cli -d -it \
-w /terraform/templates \
-v \${HOME}/.ssh:/root/.ssh \
volterraio/volt-terraform:latest \
-f /dev/null

        

• Copy the downloaded terraform variables file to the container. The following example copies to the /var/tmp folder on the container.

          
docker cp /Users/ted/Downloads/system-azure-vnet-a.json terraform-cli:/var/tmp
        

• Enter the terraform container.

          
docker exec -it terraform-cli sh
        

• Login to Azure using your Active Domain(AD) credentials. Enter the following command and follow the instructions displayed on the screen.

          az login

        

• Check the default subscription and resource group.

          az account list --output table

        

• Set a default subscription by name or uuid.

          SUBSCRIPTION_ID=<subscription_id>
az account set -s \$SUBSCRIPTION_ID

        

• Verify that the correct subscription is set.

           az account list --output table --query '[].{Name:name, IsDefault:isDefault}'

        

• Create a service principal account that has permissions to manage resources in the selected subscription. Save the output.

          az ad sp create-for-rbac -n <deployment-name> --role="Contributor" --scopes="/subscriptions/\$SUBSCRIPTION_ID"

        

The following is a sample output of the service principal account creation.

           {
        "appId": "00000000-0000-0000-0000-000000000000",
        "displayName": "azure-cli-2017-06-05-10-41-15",
        "name": "http://azure-cli-2017-06-05-10-41-15",
        "password": "0000-0000-0000-0000-000000000000",
        "tenant": "00000000-0000-0000-0000-000000000000"
 }

        

Note: The following list shows the fields in the output of above command. These are required for preparing the input variables in the next step for deployment:

• The field appId is the client_id variable.
• The field password is the client_secret variable.
• The field tenant is the tenant_idvariable.

• Edit the copied terraform parameters file and add the parameters obtained from service principal account creation.

• Change to the VNET template directory and set the environment variable for API credentials password.

          cd /terraform/templates/views/assisted/azure-volt-node
export VES_P12_PASSWORD=<api_cred_password>

        

Note: See the Generate API Certificate for information on API credentials.

• Deploy the nodes by executing the terraform commands.

          terraform init
terraform apply -var-file=/var/tmp/system-azure-vnet-a.json

        

Note: The terraform init command brings up the Azure cloud resources. When the terraform apply command is executed, it prompts for user input to proceed. Enter yes to begin deploying the node(s) and wait for the deployment to complete.

• Navigate to Sites -> Sites List. Find your site from the displayed list and verify that the status is ONLINE.

Note: It takes a few minutes for the site to be deployed and status to become ONLINE.