Merge pull request #16250 from alkohli/6-azlreb

Deployment screens, typo in storage path article

Author: Stacyrch140

azure-stack/hci/concepts/system-requirements-small-23h2.md

@@ -0,0 +1,153 @@
+---
+title: System requirements for small deployments of Azure Local, version 23H2 (preview)
+description: How to choose machines, storage, and networking components for small deployments of Azure Local, version 23H2 (preview).
+author: alkohli
+ms.author: alkohli
+ms.topic: how-to
+ms.service: azure-stack-hci
+ms.custom: references_regions
+ms.date: 11/07/2024
+---
+
+# System requirements for Small Form Factor deployment of Azure Local, version 23H2 (preview)
+
+[!INCLUDE [applies-to](../../hci/includes/hci-applies-to-23h2.md)]
+
+This article describes the requirements for machines, storage, and networking for building solutions of Azure Local that use the Small Form Factor hardware. If you purchase class *small* hardware from the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog), ensure that these requirements are met before you deploy the Azure Local solutions.
+
+[!INCLUDE [important](../../hci/includes/hci-preview.md)]
+
+## About the small hardware class
+
+Azure Local supports a new class of devices with reduced hardware requirements. This new, low-cost hardware class referenced as *small* is suited for various edge scenarios across the industry horizontals. To ensure compatibility, interoperability, security, and reliability, this class of hardware must meet the Windows Server certification requirements as well as relaxed requirements from Software Defined Data Center (SDDC) and Windows Server Software-Defined (WSSD) program.
+
+The certified devices are listed in the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog) as *small form factor* hardware.
+
+## Device requirements
+
+The device must be listed in the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog) which indicates that the device has passed the Windows Server certification and the extra qualifications from the SDDC and WSSD program.
+
+The following table lists the requirements for the small hardware:
+
+| Component | Description |
+|-----------|-------|
+| Number of machines | 1 to 3 machines are supported. Each machine must be the same model, manufacturer, have the same network adapters, and have the same number and type of storage drives. |
+| CPU | An Intel Xeon or AMD EPYC or later compatible processor with second-level address translation (SLAT). <br> Up to 16 physical cores |
+| Memory | A minimum of 32 GB per machine with EEC. |
+| Host network adapters | Two network adapters listed in the [Windows Server Catalog](https://www.windowsservercatalog.com/).<br> RDMA isn't required for storage intent.<br> Minimum link speed must be 1 Gbit/s. |
+| BIOS | Intel VT or AMD-V must be turned on.|
+| Boot drive | A minimum size of 200 GB.|
+| Data drives | A minimum single disk of capacity 1 TB. <br> The drives must be all flash single drive type, either Nonvolatile Memory Express (NVME) or Solid-State Drive (SSD). <br> All the drives must be of the same type. <br> No caching. |
+| Trusted Platform Module (TPM) | TPM version 2.0 hardware must be present and enabled. |
+| Secure boot | Secure Boot must be present and turned on. |
+| Storage Controller | Pass-through. <br> RAID controller cards or SAN (Fibre Channel, iSCSI, FCoE) aren't supported. |
+| GPU | Optional |
+
+## Storage requirements
+
+The storage subsystem for an Azure Local running Azure Stack HCI OS is layered on top of Storage Space Direct. When building a solution using class *small* hardware:
+
+- A minimum of one data drive is required to create a storage pool. 
+- All drives in the pool must be of the same type, either NVMe or SSD.
+- Remember that mixing drive types for caching (NVMe and SSD, or SSD and HDD) isn't supported.
+
+The supported volume configuration for the system is:
+
+- A single, 250 GB, fixed infrastructure volume.
+
+### Supported sample storage configurations
+
+| Node count | Disk count | Disk type | Volume resiliency level | Sustain faults |
+|------------|------------|-----------|-------------------------|----------------|
+| 1 | 1 | NVMe or SSD | Simple | None |
+| 2 | 1 | NVMe or SSD | Two way mirror | Single fault (drive or node) |
+| 3 | 1 | NVMe or SSD | Two way mirror | Single fault (drive or node) |
+| 1 | 2 | NVMe or SSD | Two way mirror | Single fault (drive) |
+| 2 | 2 | NVMe or SSD | Two way mirror | Two faults (drive and node) |
+| 3 | 2 | NVMe or SSD | Three way mirror | Two faults |
+
+## Networking requirements
+
+Network adapters must meet the Windows Server certification requirements. This requirement ensures compatibility and reliability with Hyper-V and also controls how the adapter properties are exposed by the driver (VLAN ID, RSS, VMQ).
+
+The reduced networking requirements are as follows:
+
+- Storage intent doesn't require RDMA.
+- Single link is needed.
+- Minimum link speed of 1 Gbit/s is required.
+- A Layer 2 switch with VLAN support is required.
+
+Removal of RDMA allows the use of a layer 2 network switch with VLAN support. This further simplifies the configuration management and reduces the overall solution cost.
+
+### Supported sample network configurations
+
+| Link count | Intent | Switch type | Sustain faults |
+|------------|--------|-------------|----------------|
+| 2 | Single intent | Switch | Single fault |
+| 2 | Two intents | Switch | None |
+| 4 | Two intents | Switch | Single fault |
+| 3 | Three intents | Switch | None |
+| 2 | Two intents | No switch for storage | None |
+| 4 | Two intents | No switch for storage | Single fault |
+| 6 | Three intents | No switch for storage | Single fault |
+
+## Considerations
+
+Following are some workload considerations for building a solution using the small hardware class:
+
+- Baseline workload IOP requirements for sizing storage configuration to see if small hardware class is the right fit.
+- vCPU requirements and target ratio due to lower total physical cores when using small hardware class.
+- Total memory requirement with three servers using small hardware class. Keep capacity work one node free for update runs and failure scenarios.
+- Network bandwidth requirements.
+- The VM creation time is critical as it's influenced by network bandwidth.
+
+### Availability
+
+- Spare part logistics to remediate failures timely.
+- Part replacement and identification for non-hot swap components.
+
+
+<!--## Azure requirements
+
+Here are the Azure requirements for your Azure Local instance:
+
+- **Azure subscription**: If you don't already have an Azure account, [create one](https://azure.microsoft.com/). You can use an existing subscription of any type:
+
+   - Free account with Azure credits [for students](https://azure.microsoft.com/free/students/) or [Visual Studio subscribers](https://azure.microsoft.com/pricing/member-offers/credit-for-visual-studio-subscribers/).
+   - [Pay-as-you-go](https://azure.microsoft.com/pricing/purchase-options/pay-as-you-go/) subscription with credit card.
+   - Subscription obtained through an Enterprise Agreement (EA).
+   - Subscription obtained through the Cloud Solution Provider (CSP) program.
+
+- **Azure permissions**: Make sure that you're assigned the required roles and permissions for registration and deployment. For information on how to assign permissions, see [Assign Azure permissions for registration](../deploy/deployment-arc-register-server-permissions.md#assign-required-permissions-for-deployment).
+
+- **Azure regions**: Azure Local is supported for the following regions:
+
+   - East US
+   - West Europe
+   - Australia East
+   - Southeast Asia
+   - India Central
+   - Canada Central
+   - Japan East
+   - South Central US
+
+
+    > [!NOTE]
+    > Host-bus adapter (HBA) cards must implement simple pass-through mode for any storage devices used for Storage Spaces Direct.
+
+For more feature-specific requirements for Hyper-V, see [System requirements for Hyper-V on Windows Server](/windows-server/virtualization/hyper-v/system-requirements-for-hyper-v-on-windows).
+
+## Networking requirements
+
+An Azure Local instance requires a reliable high-bandwidth, low-latency network connection between each machine.
+
+Verify that physical switches in your network are configured to allow traffic on any VLANs you use. For more information, see [Physical network requirements for Azure Local](../concepts/physical-network-requirements.md). -->
+
+
+## Next steps
+
+Review firewall, physical network, and host network requirements:
+
+- [Firewall requirements](./firewall-requirements.md).
+- [Physical network requirements](./physical-network-requirements.md).
+- [Host network requirements](./host-network-requirements.md).

azure-stack/hci/deploy/deploy-via-portal.md

@@ -3,7 +3,7 @@ title: Deploy an Azure Local instance using the Azure portal
 description: Learn how to deploy an Azure Local instance from the Azure portal
 author: alkohli
 ms.topic: how-to
-ms.date: 10/17/2024
+ms.date: 11/07/2024
 ms.author: alkohli
 ms.service: azure-stack-hci
 #CustomerIntent: As an IT Pro, I want to deploy an Azure Local instance of 1-16 machines via the Azure portal so that I can host VM and container-based workloads on it.
@@ -22,7 +22,7 @@ This article helps you deploy an Azure Local instance, version 23H2 using the Az
 
 ## Start the wizard and fill out the basics
 
-1. Open a web browser, navigate to [**Azure portal**](https://portal.azure.com). Search for **Azure Arc**. Select **Azure Arc** and then go to **Infrastructure | Azure Local**. On the **Get started** tab, select **Deploy cluster**.
+1. Open a web browser, navigate to [**Azure portal**](https://portal.azure.com). Search for **Azure Arc**. Select **Azure Arc** and then go to **Infrastructure | Azure Local**. On the **Get started** tab, select **Create instance**.
 2. Select the **Subscription** and **Resource group** in which to store this system's resources.
 
    All resources in the Azure subscription are billed together.
@@ -197,7 +197,7 @@ Choose whether to create a new configuration for this system or to load deployme
 
 1. Review the settings that will be used for deployment and then select **Review + create** to deploy the system.
 
-    :::image type="content" source="./media/deploy-via-portal/review-create-tab-1.png" alt-text="Screenshot of the Review + Create tab in deployment via Azure portal." lightbox="./media/deploy-via-portal/review-create-tab-1.png":::
+    <!--:::image type="content" source="./media/deploy-via-portal/review-create-tab-1.png" alt-text="Screenshot of the Review + Create tab in deployment via Azure portal." lightbox="./media/deploy-via-portal/review-create-tab-1.png":::-->
 
 The **Deployments** page then appears, which you can use to monitor the deployment progress.
 
@@ -267,7 +267,7 @@ You may need to connect to the system via RDP to deploy workloads. Follow these
     Disable-ASRemoteDesktop
     ```
 
-### Lock Arc Resource bridge
+### Lock Arc Resource Bridge
 
 The Arc Resource Bridge enables the Azure Arc services to manage your Azure Local instance. To prevent the accidental deletion, we recommend that you lock the Arc Resource Bridge resource.
 Follow these steps to configure the resource locks:

azure-stack/hci/deploy/download-23h2-software.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-stack-hci
-ms.date: 10/14/2024
+ms.date: 11/06/2024
 ---
 
 # Download version 23H2 operating system for Azure Local deployment
@@ -42,11 +42,11 @@ Follow these steps to download the software:
 
     After you select **Azure Local**, you're directed to the Azure Local **Get started** page, with the **Get started** tab selected by default.
 
-1. On the **Get started** tab, under the **Download software** tile, select **Download operating system**. Skip this step if your Azure Local instance came installed with the OS.
+1. On the **Get started** tab, under the **Prepare machines** tile, select **Download software**. Skip this step if your Azure Local instance came installed with the OS.
 
     :::image type="content" source="media/download-23h2-software/get-started-page-with-download-button.png" alt-text="Screenshot of the Get started page with the option to download the Azure Stack HCI OS." lightbox="media/download-23h2-software/get-started-page-with-download-button.png":::
 
-1. On the **Download Azure Stack HCI Operating System** page on the right, do the following:
+1. On the **Download Azure Local software** page on the right, do the following:
 
     :::image type="content" source="media/download-23h2-software/download-23h2-software-2.png" alt-text="Screenshot of the Download Azure Stack HCI OS version 23H2 page with the various ISO options." lightbox="media/download-23h2-software/download-23h2-software-2.png":::
 
@@ -62,7 +62,7 @@ Follow these steps to download the software:
         > The ISO that you download is OS version 25398.469. This ISO is then patched to the latest OS version during the installation process.
     1. Review service terms and privacy notice.
     1. Select the license terms and privacy notice checkbox.
-    1. Select **Download Azure Stack HCI OS**. This action begins the download. Use the downloaded ISO file to install the software on each machine that you want to cluster.
+    1. Select **Download software**. This action begins the download. Use the downloaded ISO file to install the software on each machine that you want to cluster.
 
         :::image type="content" source="media/download-23h2-software/download-23h2-software-1.png" alt-text="Screenshot of the Download Azure Stack HCI version 23H2 page." lightbox="media/download-23h2-software/download-23h2-software-1.png":::