Azure provides instructions on how to deploy your AVS environment. These instructions can be found at this link and it should be reviewed for in-depth explanation of the various different components and requirements needed for a successful AVS Gen 2 deployment.
The steps to deploy AVS Gen 2 Private Cloud via the Azure GUI can be summarized in a few screenshots below.
To start search for Azure VMware Solution within the Azure Marketplace.
When the AVS icon appears, click on the drop-down menu and select create.
The prerequisites for AVS deployment are shown in the first screen of the wizard and are covered in the previous section of this page. Click on the Next: Prerequisites button to proceed.
The next screenshot shows the fields that need to be filled out to deploy AVS. Fields are broken out individually below the screenshot.
-
Numbers of Hosts: Select the number of AVS host you would like to deploy, the minimum number of hosts for AVS cluster is 3 hosts.
When filled out, click on the Next button on the bottom of the screen to continue with Networking configuration tab.
-
CIDR Address block: You must provide a non-overlapping CIDR block with a minimum /22 size that AVS will segregate into normal VMware services (e.g. VMware ESXi Management, vMotion, vSAN, etc.). This range must not overlap with other networks in Azure and must fall within selected VNet address range in step 8.
When filled out, click on the Next button on the bottom of the screen.
In the following window, you may optionally assign Azure tags to your deployment
When complete, click on the Next button at the bottom of the screen to go to the last tab "Review and Create".
Upon your validation and review, click on the Create button to begin the deployment. Note that a new AVS deployment will take anywhere from 3-5 hours or longer to complete.
Important: When an AVS deployment successfully builds, it is critical that Everpure Cloud Dedicated can also be deployed within the same AZ. Deployment of both products within the same AZ is an important best practice because deployment of Everpure Cloud Dedicated and AVS into the same AZ will minimize network hops between the two solutions.Deployment of Everpure Cloud Dedicated in different AZ then AVS will work but it can negatively affect storage performance.To determine what Availability Zone was AVS deployed into, first click on the AVS managed object in Azure:
From the AVS Overview screen, the Availability Zone can be found in the highlighted area:
Make sure to note down what Availability Zone AVS has been deployed into and use the same Availability Zone when deploying Everpure Cloud Dedicated.