- Getting Started
- Deployment Scenarios
- Automated Architecture Assessment
Welcome to the Enterprise Scale for Azure VMware Solution (AVS) repository
To find out more about the Azure landing zones reference implementation, please refer to the documentation on our Wiki
Enterprise-scale is an architectural approach and a reference implementation that enables effective construction and operationalization of landing zones on Azure, at scale. This approach aligns with the Azure roadmap and the Cloud Adoption Framework for Azure.
Enterprise-scale for AVS represents the strategic design path and target technical state for an Azure VMware Solution (AVS) deployment. This solution provides an architectural approach and reference implementation to prepare landing zone subscriptions for a scalable Azure VMware Solution (AVS) cluster. For the architectural guidance, check out Enterprise-scale for AVS in Microsoft Docs.
The enterprise-scale for AVS only talks about with what gets deployed in the specific AVS landing zone subscription highlighted by the red box in the picture above. It is assumed that an appropriate platform foundation is already setup which may or may not be the official ESLZ platform foundation. This means that policies and governance should already be in place or should be setup after this implementation and are not a part of the scope this program. The policies applied to management groups in the hierarchy above the subscription will trickle down to the Enterprise-scale for AVS landing zone subscription.
This repository contains reference implementation scenarios based on a number of different scenarios. For each scenario, we have included both ARM and Bicep as the deployment languages
In this repository, you get access to various customer scenarios that can help accelerate the development and deployment of AVS clusters that conform with Enterprise-Scale for AVS best practices and guidelines. Each scenario aims to represent common customer experiences with the goal of accelerating the process of developing and deploying conforming AVS clusters using IaC as well as providing a step-by-step learning experience.
This deployment is best suited to those looking to provision a new AVS Private Cloud, the automation will let you choose and deploy the following:
- AVS Private Cloud: Choose New or Existing
- [Optional]: Choose New or Existing virtual network (VNet)
- [Optional]: Deploy Dashboards and Monitoring
- [Optional]: Enable Diagnostics and Logging for AVS
- [Optional]: Enable HCX and SRM
| Greenfield deployment options: | |
|---|---|
| Azure portal UI | |
| Command line (Bicep/ARM) |  |
| Terraform |  |
This deployment is a lite version of the full AVS Greenfield Deployment and will deploy the following:
- New AVS Private Cloud - Allows for a custom resource group name and Private Cloud Name
- or Choose an existing AVS Private Cloud
- [Optional]: Deploy AVS Monitoring
- [Optional]: Deploy HCX and SRM
| Greenfield Lite deployment: | |
|---|---|
| Azure portal UI |
We've created a number of additional Terraform modules for AVS related deployment activities. Details on these modules can be found in the Terraform readme.
If an AVS SDDC was deployed using assests provided in this repository or it pre-existed, in both scenarios, it is possible to assess the architectural quality of the deployment. Refer to following links for additional guidance.
Azure deployment templates are being developed in Bicep. Thus, a script file Build-ARM.ps1 is used to compile the .bicep files to .json so templates can be executed as ARM templates instead of Bicep. This is necessary in any deployment mechanism that communicates with Azure Resource Manager REST API directly.
Once you execute Build-ARM.ps1 in its current location, it will recursively perform 'az bicep build' to all .bicep files to .json files (ARM templates).
Next steps, head to Getting Started to review prerequisites and deployment options
