Shulou(Shulou.com)06/02 Report--

Following the release of Azure Stack TP1, Microsoft released TP2 in late September, which is prohibitive to the installation conditions of Azure Stack. Let's take a look at the deployment conditions of the TP2 version:

Hardware

Component

Minimum

Recommended

Disk drives: Operating System

1 OS disk with minimum of 200 GB available for system partition (SSD or HDD)

1 OS disk with minimum of 200 GB available for system partition (SSD or HDD)

Disk drives: General Azure Stack POC Data

4 disks. Each disk provides a minimum of 140GB of capacity (SSD or HDD). All available disks will be used.

4 disks. Each disk provides a minimum of 250GB of capacity (SSD or HDD). All available disks will be used.

Compute: CPU

Dual-Socket: 12 Physical Cores (total)

Dual-Socket: 16 Physical Cores (total)

Compute: Memory

96 GB RAM

128 GB RAM

Compute: BIOS

Hyper-V Enabled (with SLAT support)

Hyper-V Enabled (with SLAT support)

Network: NIC

Windows Server 2012 R2 Certification required for NIC; no specialized features required

Windows Server 2012 R2 Certification required for NIC; no specialized features required

HW logo certification

Certified for Windows Server 2012 R2

Certified for Windows Server 2012 R2

This is a headache for those who want to experience Azure Stack but do not have so many hardware resources. In fact, we can modify the check conditions of the deployment script so that we can experience Azure Stack with low hardware resources. Of course, the reason for Microsoft to do this is to enable people to get a better experience, but it also affects some people who do not have such good hardware resources to some extent.

Open C:\ CloudDeployment\ Configuration\ Roles\ Infrastructure\ BareMetal\ OneNodeRole.xml

Modify the above parameters to meet the existing hardware conditions.

If you are deploying Azure Stack in a virtual machine using nested virtualization, you will encounter a check error. Because this version of Azure Stack checks the type of server, if it is a virtual machine, it will return a failure and stop running the script.

This can be done by modifying the following parameters:

C:\ CloudDeployment\ Roles\ PhysicalMachines\ Tests\ BareMetal.Tests.ps1

Change false to true

The CPU audit check statement is as follows:

If you want to skip the check, log out of this paragraph.

Finally, if conditions permit, it is recommended to deploy according to the hardware configuration recommended by Microsoft.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.