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

Earlier this year, Microsoft introduced the first technical preview of Microsoft Azure Stack: Microsoft Azure Stack Technical Preview 1 (x64) -designed to enable organizations from all industries to run Azure services in their own data centers. This is Microsoft's third attempt to launch an Azure private cloud experience.

Azure Stack TP1 Technical Preview Architecture:

The first time was in 2010, when Microsoft launched an Azure Appliance program to deploy applications in hosted environments with select partners. But the market was lukewarm and the project was quickly aborted.

The second time, in 2013, Microsoft announced Azure Pack, which was described as "Windows Azure Pack enables you to run Windows Azure technologies in your own data center, enabling you to build rich, self-serving, multi-tenant services while maintaining consistency with Windows Azure." "

For an introduction to Azure Pack deployment, see the previous article series,"System Center 2012 R2 Instance 2: Building Azure Pack Cloud"(Portal: http://yaojiwei.blog.51cto.com/762134/1412399).

Here's a comment from a Microsoft employee explaining some of the ideas for moving from Azure Pack to Azure Stack:

First, it is important to understand that Azure Pack and Azure Stack are two different architectures. The former is based on Windows Server and System Center, with an additional technology layer to efficiently mimic the Azure experience, setting up various core components such as VMs, DBs, websites, and more in a self-service manner. Azure Stack is a carefully designed product (not something deployed on top of Windows Server and System Center) that allows you to build and deliver Azure services to end users in your own data center (or a partner's data center). For example, in Azure Stack, the APIs used to interact with virtual machine services are consistent with those used by Azure services. So you're essentially running Azure services in your own data center. As you might imagine, in-place upgrades of systems for different underlying architectures are often not feasible, and the same is true for this product. Based on our conversations with customers, most of them plan to keep the Azure Pack deployment environment, wait until Azure Stack is released, build a new environment, and then gradually migrate the former to the latter.

Azure Stack Technology Preview is an early release of a product that is not currently suitable for deployment in production environments: there is no traditional deployment installation package, only deployment on a host without any high availability options, and the entire system is not stable enough...

Because it's still a POC environment right now. POC stands for Proof of Concept, proof of concept environment. When the general product is released, Azure Stack changes to reflect Microsoft Azure changes to maintain the design philosophy of "consistent with Azure."

Here's a look at the hardware requirements for Azure Stack Technology Preview:

Components Minimum Recommended Disk: OS 1 OS Disk (SSD or HDD) Minimum 200 GB (SSD or HDD) Disk: Data 4 OS Disks (SSD or HDD) Minimum 140GB (SSD or HDD)4 OS Disks (SSD or HDD) Minimum 250GB (SSD or HDD)CPU Dual slots 12 physical cores Dual slots 16 physical cores Memory 96 GB RAM128 GB RAMBIOS Enable Hyper-V Virtualization Support Enable Hyper-V Virtualization Support Single NIC Single NIC

1. All data disks need to be configured with the same type (e.g. SAS.SATA, etc.) and capacity. If SAS disks are used, a single path needs to be set up (MPIO, or multipath I/O, is not supported)

2. HBA is the host bus can be configured as a single HBA, if RAID HBA needs to be configured as a pass-through mode, but disk or RAID0

3. Supports bus and media type combinations: SATA HDD, SAS HDD, RAID HDD, RAID SSD, SATA SSD+SATA HDD, SAS SSD+SAS HDD, RAID pass-through

Additional considerations:

1. You can use Windows Server 2016Datacenter.vhdx in the download file to quickly install the host system. If you are using your own environment, you need to install all required upgrade patches.

2. Host systems cannot join domain environments

3. Microsoft Azure account is required for installation (International and 21Vianet editions are available)

4. Installation requires Internet connection and open port 443

5. Machine name cannot be AzureStack, which conflicts with netbios name in AzureStack.local domain

6. Installation requires logging in using the Local Administrator account

7. If the NIC is connected to a physical switch VLAN, the port needs to be in Access or Trunk mode

Let's take a look at the deployment and testing of this preview product.

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.