Azure Stack HCI: VM Deployment

Azure Stack HCI VM Deployment

Welcome back to the Chronicloud Series! If you’ve been following along, you should have successfully set up your Azure Stack HCI DemoLab and optimized it with Day 2 Operations. In the previous articles, Azure Stack HCI DemoLab and Azure Stack HCI: Day2 Operations, we walked you through the initial setup and essential post-deployment configurations. Now, it’s time to take the next step: deploying virtual machines (VMs) on your Azure Stack HCI environment.

This article will guide you through the Azure Stack HCI VM Deployment process using the Azure Arc Resource Bridge. We’ll cover the deployment steps, management capabilities from both cluster and VM perspectives, and highlight the advantages of using Azure Stack HCI-integrated Arc VMs. Additionally, we’ll discuss manual deployment methods and introduce a custom script from the AzSHCI repository to streamline VM access.

Prerequisites

Before diving into VM deployment, ensure that you have completed the following:

1. Azure Stack HCI DemoLab setup.
2. Azure Stack HCI Day 2 Operations configured.

These foundational steps are crucial for a smooth VM deployment experience.

Deploying VMs over Azure Arc Resource Bridge

The Azure Arc Resource Bridge plays a pivotal role in deploying and managing VMs on Azure Stack HCI. Here’s a step-by-step overview of the deployment process:

1. Initiate VM Deployment from Azure

You can start deploying a VM using various methods such as the Azure Portal, Azure CLI, ARM templates, Bicep, or Terraform. Since we’ve already managed VM images in the Day 2 Operations, we’ll now focus on creating Arc VMs using those images.

Steps to create an Arc VM via Azure Portal:

1. Sign In and Navigate: Log in to the Azure Portal and navigate to your Azure Stack HCI cluster resource.

2. Access Virtual Machines: In your cluster resource, go to Virtual machines and click on + Create VM.
3. Fill in Project Details:
   • Subscription: Choose the subscription you wish to use.
   • Resource Group: Select an existing resource group or create a new one.
4. Configure Instance Details:
   • Virtual Machine Name: Enter a name following Azure’s naming conventions (lowercase letters, numbers, and hyphens).
   • Custom Location: Select the custom location associated with your Azure Stack HCI cluster.
   • Security Type: Choose between Standard or Trusted Launch VMs.
   • Storage Path: Select a storage path for your VM’s files. You can let Azure choose automatically or specify manually.
   • Image: Select the VM image you’ve previously downloaded, such as Windows Server 2022 Datacenter: Azure Edition.
   • Administrator Account: Provide a username and password for the VM’s local administrator account.
   • Virtual Processor Count: Specify the number of vCPUs.
   • Memory: Allocate the desired amount of memory in MB.
   • Memory Type: Choose between static or dynamic memory.This cannot be changed after deployment.
5. Enable Guest Management:
   • In the VM extensions section, enable Guest Management to allow for extensions and Arc integration.
6. Domain Join (Optional):
   • If you wish to domain join the VM, enable Domain Join and provide the necessary Active Directory credentials.
7. Add Disks (Optional):
   • Add additional disks if required, specifying their size, provisioning type, and storage path.
8. Configure Networking:
   • Add at least one network interface. If you’ve enabled guest management, this step is mandatory.
   • Configure the network settings, including IP allocation methods and static IPs if needed.
9. Review and Create:
   • Review all the configurations and click Create to initiate the deployment.

2. Azure Arc Resource Bridge Handles Deployment

Once you’ve initiated the deployment, the Azure Arc Resource Bridge takes over:

• Parameter Transmission: All deployment parameters are sent to the Arc Resource Bridge.
• VM Creation: The Arc Resource Bridge communicates with your Azure Stack HCI cluster to create the VM based on the provided specifications.

3. Post-Deployment Processes

After the VM is created, several processes are automatically initiated:

a. Azure Arc Registration

If Guest Management is enabled, the VM is registered with Azure Arc upon its first boot. This registration is facilitated through the Arc Resource Bridge, ensuring seamless integration without direct registration as with conventional Arc VMs.

b. Domain Join

If you’ve opted for Domain Join during deployment, the VM will automatically join the specified domain using VM scripts and the Arc Agent, streamlining the process and ensuring compliance with your organization’s policies.

Managing Deployed VMs

Once your VMs are up and running, you have comprehensive management capabilities from both the Cluster and VM perspectives.

Cluster Perspective

From the cluster’s viewpoint, you can manage the following aspects of all VMs deployed via Azure:

• CPU and RAM Allocation: Adjust CPU cores and memory allocations within predefined limits. Note that changing any of these parameters will result in a restart of the VM without warning.

• Storage Management: Add additional storage disks to VMs. However, you cannot modify the DiskPath where the VM or its disks reside within the cluster.

• Network Configuration: Add new network interfaces to VMs. Existing network interfaces cannot be altered, and configurations cannot be mixed or modified directly from Azure.

Note: The Arc VMs provisioned on Azure Stack HCI offer more options than traditional Arc VMs, specifically related to cluster resource management like Disk, Size, and Networking. This enhanced functionality allows for better integration and management of resources directly from the Azure Portal.

VM Perspective

From the VM’s perspective, management is akin to managing any VM in Azure Arc:

• Extensions: Install and manage extensions to enhance VM functionality.

• Policies: Apply and enforce policies to ensure compliance and security.

• Azure Update Manager: Manage and automate updates to keep VMs secure and up-to-date.

• Machine Configuration: Define configurations and enforce compliance settings on your VM to ensure it meets specific criteria and standards.

• Automanage: Simplify VM management by automatically applying best practices for configuration, security, and compliance.

• Run Command (Preview): Execute PowerShell scripts or commands directly on the VM from the Azure Portal without needing a direct connection.

• Inventory: Collect and view inventory data about software installed on the VM, aiding in asset management and compliance.

• Change Tracking: Monitor and track changes to the VM’s infrastructure, including files, registry keys, services, and software.

• Monitoring Capabilities: Leverage Azure Monitor to gain insights into the VM’s performance, health, and availability, allowing for proactive management.

Advantages of Azure Stack HCI-Integrated Arc VMs

Deploying VMs through Azure Stack HCI-integrated Azure Arc offers significant benefits over conventional Arc VMs:

• Cost Efficiency: Integrated Arc VMs on Azure Stack HCI do not incur additional costs for services like Policies, Azure Update Manager, or Extended Security Updates. This ensures predictable and lower operational costs.

• Seamless Integration: Enhanced integration with Azure services, providing a unified management experience without the overhead of managing separate billing for additional services.

Manual VM Deployment Methods

While deploying VMs via Azure Arc Resource Bridge offers numerous advantages, there are alternative methods for manual deployment:

• PowerShell: Deploy VMs using PowerShell scripts.
• Windows Admin Center (WAC): Utilize the WAC interface for VM deployment.
• Failover Cluster Manager: Deploy directly through the Cluster Manager.

However, manually deployed VMs have limitations:

• Azure Portal Visibility: These VMs do not appear in the Azure Portal as they are not registered with Azure Arc. This hampers uniform management across all VMs.

• Management Challenges: Lack of integration with Azure Arc features like Policies and Update Manager can lead to inconsistent management practices.

Microsoft is actively working on solutions to “rehydrate” these manually deployed VMs, ensuring they can be integrated into Azure Arc for unified management. Currently, a workaround is available, detailed in Kenny Lowe’s blog, which we’ll explore in a future article on VM migration to Azure Stack HCI.

Enhancing VM Access with Custom Scripts

To streamline VM access without exposing firewall ports, I’ve configured a custom script in the AzSHCI repository. This script sets up the OpenSSH extension on Windows servers and establishes an RDP connection using SSH tunneling.

Key Points:

• Script Location: The script is available in my AzSHCI GitHub repository.

• Functionality: It configures the OpenSSH server on your VMs and allows secure RDP access without opening additional firewall ports.

• Based On: The script is inspired by Alexander Ortha’s article, but I’ve modified it to rely more on PowerShell and less on the Azure CLI for a streamlined process.

By using this script, you can securely manage your VMs without big changes on your network security, making remote administration more convenient.

Conclusion

Deploying VMs on Azure Stack HCI using the Azure Arc Resource Bridge streamlines the integration between your on-premises infrastructure and Azure services. By following the steps outlined in this article, you can efficiently deploy, manage, and optimize your VMs while maintaining cost-effectiveness and operational excellence.

From initiating deployments through the Azure Portal or infrastructure-as-code tools to managing resources from both cluster and VM perspectives, Azure Stack HCI provides a robust and flexible environment for your virtual workloads. The advantages of integrated Arc VMs, combined with the ability to enhance access through custom scripts, make Azure Stack HCI a compelling choice for modern hybrid cloud deployments.

Stay tuned for upcoming articles where we’ll delve into:

• Setting up and managing Azure Virtual Desktop (AVD) on Azure Stack HCI
• Deploying and managing AKS (Azure Kubernetes Service) on Azure Stack HCI

Thank you for following along, and I look forward to hearing about your Azure Stack HCI deployment experiences!