No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Guide for Interworking Between CloudEngine Switches and Azure Stack

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Introduction to Azure Stack

Introduction to Azure Stack

Overview of Azure Stack

Microsoft Azure Stack is an extension of Azure. It introduces cloud computing agility and innovations into the local environment and enables the unique hybrid cloud. By providing consistent APIs between Azure and Azure Stack, users can obtain the same experience, tools, application mode, automation capability, deployment and configuration, and O&M across public and hybrid clouds, as shown in Figure 1-1.

Azure Stack can be used to build a cloud platform in the local data center and the services provided by Azure can be used.

Figure 1-1 Architecture of Azure Stack

Microsoft Solution

Microsoft is only responsible for Azure Stack software, and needs to work with hardware vendors to form a unified solution. Involved vendors include HPE, Cisco, Arista, Lenovo, and Huawei. The integrated device is sold to customers, and the vendors sell the products to customers in the form of solutions.

  • The hardware includes servers and switches.
  • The software includes the switch version and server software (Azure Stack).

If a customer selects Huawei's solution, Huawei hardware devices + Azure Stack software is used. If another vendor is selected, corresponding vendor's hardware + Azure Stack software is used.

Currently, the commercial version supports only one cabinet that allows 4 to 16 servers. The multi-cabinet solution is being verified.

Figure 1-2 Single cabinet and multiple cabinets

Figure 1-3 shows the hardware distribution in the current solution.

  • ToR switches: 2
  • BMC switch: 1
  • Servers: 4-16
Figure 1-3 Distribution of hardware devices in a single cabinet

In the solution, the hardware switch is deployed in the underlay, and the vSwitch of Azure Stack is deployed in the overlay. Therefore, hardware switches need to be configured with fixed features, such as ACL, BGP, NTP, and QoS. Customers do not need to detect these configurations.

Download
Updated: 2019-03-25

Document ID: EDOC1100072310

Views: 180

Downloads: 3

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next