From fa6dbd08a147026530d75c601a7674d899425377 Mon Sep 17 00:00:00 2001 From: staleycyn <45440075+staleycyn@users.noreply.github.com> Date: Wed, 20 Dec 2023 07:48:41 -0800 Subject: [PATCH] Update LAB_08-Manage_Virtual_Machines.md --- .../Lab/LAB_08-Manage_Virtual_Machines.md | 133 +----------------- 1 file changed, 5 insertions(+), 128 deletions(-) diff --git a/New Instructions/Lab/LAB_08-Manage_Virtual_Machines.md b/New Instructions/Lab/LAB_08-Manage_Virtual_Machines.md index 9fbd9531..5e7b8957 100644 --- a/New Instructions/Lab/LAB_08-Manage_Virtual_Machines.md +++ b/New Instructions/Lab/LAB_08-Manage_Virtual_Machines.md @@ -29,132 +29,9 @@ There are interactive lab simulations that you might find useful for this topic. + Task 1: Deploy zone-resilient Azure virtual machine scale sets by using the Azure portal + Task 2: Scale compute and storage for Azure virtual machine scale sets - -## Task 1: Deploy zone-resilient Azure virtual machines by using the Azure portal - -In this task, you will deploy two Azure virtual machines into different availability zones by using the Azure portal. Availability zones offer the highest level of uptime SLA for virtual machines at 99.99%. To achieve this SLA, you must deploy at least two virtual machines across different availabiliy zones. - -1. Sign in to the **Azure portal** - `http://portal.azure.com`. - -1. In the Azure portal, search for and select `Virtual machines` and, on the **Virtual machines** blade, click **+ Create**, click **+ Azure virtual machine**. - -1. On the **Basics** tab of the **Create a virtual machine** blade, in the **Availability zone** drop down menu, place a checkmark next to **Zone 2**. This should select both **Zone 1** and **Zone 2**. - - >**Note**: This will deploy two virtual machines in the selected region, one in each zone. You achieve the 99.99% uptime SLA because you have at least two VMs distributed across at least two zones. In the scenario where you might only need one VM, it is a best practice to still deploy the VM to a zone to ensure that the disk and corresponding resources are colocated in the same zone. - -1. On the Basics tab, use the following settings to complete the fields (leave others with their default values): - - | Setting | Value | - | --- | --- | - | Subscription | the name of your Azure subscription | - | Resource group | **az104-rg1** (If necessary, click **Create new**) | - | Virtual machine names | `az104-vm1` and `az104-vm2` (After selecting both availability zones, select **Edit names** under the VM name field.) | - | Region | **East US** (or a region that is near you) | - | Availability options | **Availability zone** | - | Availability zone | **Zone 1** and **Zone 2** | - | Security type | **Standard** | - | Image | **Windows Server 2019 Datacenter - x64 Gen2** | - | Azure Spot instance | **No** | - | Size | **Standard D2s v3** | - | Username | `localadmin` | - | Password | **Provide a secure password** | - | Public inbound ports | **None** | - | Would you like to use an existing Windows Server license? | **Unchecked** | - - ![image](./media/az104-lab08-create-vm.png) - -1. Click **Next: Disks >** and, on the **Disks** tab of the **Create a virtual machine** blade, specify the following settings (leave others with their default values): - - | Setting | Value | - | --- | --- | - | OS disk type | **Premium SSD** | - | Enable Ultra Disk compatibility | **Unchecked** | - -1. Click **Next: Networking >** and, on the **Networking** tab of the **Create a virtual machine** blade, click **Create new** below the **Virtual network** textbox. - -1. On the **Create virtual network** blade, specify the following settings (leave others with their default values): - - | Setting | Value | - | --- | --- | - | Name | `az104-vnet01` | - | Address range | `10.80.0.0/20` | - | Subnet name | `subnet0` | - | Subnet range | `10.80.0.0/24` | - -1. Click **OK** and, back on the **Networking** tab of the **Create a virtual machine** blade, specify the following settings (leave others with their default values): - - | Setting | Value | - | --- | --- | - | Subnet | **subnet0** | - | Public IP | Leave the default settings | - | NIC network security group | **basic** | - | Public inbound Ports | **None** | - | Accelerated networking | **Off** - | Load balancing options | **None** | - -1. Click **Next: Management >** and, on the **Management** tab of the **Create a virtual machine** blade, specify the following settings (leave others with their default values): - - | Setting | Value | - | --- | --- | - | Patch orchestration options | **Manual updates** | - -1. Click **Next: Monitoring >** and, on the **Monitoring** tab of the **Create a virtual machine** blade, specify the following settings (leave others with their default values): - - | Setting | Value | - | --- | --- | - | Boot diagnostics | **Disable** | - - 1. Click **Next: Advanced >**, on the **Advanced** tab of the **Create a virtual machine** blade, review the available settings without modifying any of them, and click **Review + Create**. - -1. On the **Review + Create** blade, click **Create**. - - - -## Task 2: Manage compute and storage scaling for virtual machines - -In this task, you will scale the compute for a virtual machine by adjusting its size to a different SKU. Azure provides flexability in VM size selection so that you can adjust a VM for periods of time if it needs more (or less) compute and memory allocated. This concept is extended to disks, where you can modify the performance of the disk, or increase the allocated capacity. - -1. In the Azure portal, search for and select `Virtual machines` and, on the **Virtual machines** blade, click **az104-vm1**. - -1. On the **az104-vm1** virtual machine blade, click **Size** and set the virtual machine size to **DS1_v2** and click **Resize** - - >**Note**: Choose another size if **Standard DS1_v2** is not available. - - ![image](./media/az104-lab08-resize-vm.png) - -1. On the **az104-vm1** virtual machine blade, click **Disks**, Under **Data disks** click **+ Create and attach a new disk**. - -1. Create a managed disk with the following settings (leave others with their default values): - - | Setting | Value | - | --- | --- | - | Disk name | `vm1-disk1` | - | Storage type | **Standard HDD** | - | Size (GiB) | `32` | - -1. Click **Apply**. - -1. After the disk has been created, click **Detach**, and then click **Apply**. - - >**Note**: You might need to scroll right to see the *detach* icon. - -1. From the Azure portal, search for and select `Disks`. - -1. From the list of disks, select the **vm1-disk1** object. - -1. From vm1-disk1, select **Size + performance**. - -1. From Size + performance, set the storage type to **Standard SSD**, and then click **Save**. - - >**Note**: You cannot change the storage type of the disk while it is attached or while the VM is running. - -1. Navigate back to the **az104-vm1** virtual machine, and select **Disks**. - -1. Under data disks, select **Attach existing disks**. - -1. Select **vm1-disk1** and then select **Apply**. - -## Task 3: Deploy zone-resilient Azure virtual machine scale sets by using the Azure portal ++ Task 3: Configure Azure virtual machine diagnostic settings + +## Task 1: Deploy zone-resilient Azure virtual machine scale sets by using the Azure portal In this task, you will deploy an Azure virtual machine scale set across availability zones. With individual VMs, you would need other automation to deploy and configure additional VMs if your application needs additional compute. VM Scale Sets reduce the administrative overhead of automation by enabling you to configure metrics or conditions that allow the scale set to automatically scale up or down the number of VMs in the set. @@ -259,7 +136,7 @@ In this task, you will deploy an Azure virtual machine scale set across availabi >**Note**: Wait for the virtual machine scale set deployment to complete. This should take appoximately 5 minutes. -## Task 4: Scale compute and storage for Azure virtual machine scale sets +## Task 2: Scale compute and storage for Azure virtual machine scale sets In this task, you will change the size of virtual machine scale set, and then upgrade the instances of the scale set to force them to the new size. You will also manage the configuration of the scale set to enable overprovisioning. This allows the service to spin up additional instances until the number of desired instances are achieved, and delete any extras, speeding up the overall deployment time. @@ -286,7 +163,7 @@ In this task, you will change the size of virtual machine scale set, and then up 1. Select **Apply**. -## Task 5: Configure Azure virtual machine diagnostic settings +## Task 3: Configure Azure virtual machine diagnostic settings In this task, you will configure Azure virtual machine diagnostic settings. Diagnostic settings allow you to capture more logging and monitoring data, and send that data to a location to store. This could be a storage account if you are using a third-party logging solution, or as in this task, a Log Analytics workspace that will centralize the log data.