For hands-on/testing purposes, the Bicep framework repository
enables option for deploying all required resources, Everpure Cloud Dedicated Managed App and a test
Virtual Machine (VM) of Windows Server 2019 with pre-installed SQL server (combines all
Modules #1-#3 described above) in the single deployment script
deploy-e2e-demo.sh.
This deployment script deploys the latest version of Everpure Cloud Dedicated
automatically with a test license for 45 days (Deploy using Azure Bicep).
To start with E2E Demo deployment:
- Rename the parameter file
e2e-demo-params.sh.example to
e2e-demo-params.sh
$ mv e2e-demo-params.sh.example e2e-demo-params.sh
- Replace the placeholders in the parameter file
with actual values for the required minimum parameters, which include location, subscription ID, resource group name,
availability zone for Everpure Cloud Dedicated, test VM size (SKU), test VM
credentials and others. For automatic configuration is essential link to
custom extension script file present in
extensionFileUrl and
extensionCustomizeUXFileUrl. By default, these variables refer
to files stored in GitHub repository. In case you want to change these extension
files, please keep in mind these files needs to be accessible from the internet
(e.g. hosted from GitHub or an Azure Blob Storage). For more details about
custom extension files, see Microsoft Docs.
- Execute the deployment script with (takes up to ~60mins, depends on Azure's current load):
- When the deployment finishes, as output of the script you can find parameters for deployed VM instance, including VM public IP address. By default, there is a Network Security Group for this VM in place restricting access to RDP just for your current public IP address. When the script runs in the Windows Subsystem for Linux or in macOS, it will try to open an RDP connection automatically as the last step of the deployment script.
- At this moment, the deployment is completed and you can proceed to test VM (Deploy using Azure Bicep).