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

FusionCloud 6.3.0 Solution Description 05

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).
Differences of Region Type I, Region Type II, and Region Type III Scenarios

Differences of Region Type I, Region Type II, and Region Type III Scenarios

To meet service requirements of users in various industries, FusionCloud supports three deployment scenarios: Region Type I, Region Type II, and Region Type III. Table 3-3 describes the differences among the three deployment scenarios.

Table 3-3 Comparison of three deployment scenarios

Comparison Item

Region Type I

Region Type II

Region Type III

Infrastructure - network node requirements

Two servers (used to deploy network nodes)

  • Three servers (used to deploy Agile Controller-DCN)
  • Network devices matching Agile Controller-DCN:
    • Core switch/aggregation switch (CloudEngine 12800)
    • Access switch (CloudEngine 6800)
    • Firewall (USG9500 series and Eduemon 8000E-X series)

No physical network node needs to be added.

Resource pool - FusionSphere OpenStack

Cascading architecture of FusionSphere OpenStack

  • Cascading FusionSphere OpenStack
  • Cascaded FusionSphere OpenStack

Non-cascading architecture of FusionSphere OpenStack

Non-cascading architecture of FusionSphere OpenStack

Resource pool - computing resource pool

The cascaded FusionSphere OpenStack can access multiple computing resource pools at one time.

  • KVM (provided by cascaded FusionSphere OpenStack)
  • FusionCompute (non-typical deployment scenario)
  • Bare metal server
  • Inventory management of VMware resource pools

FusionSphere OpenStack can access multiple computing resource pools at one time.

  • KVM (provided by FusionSphere OpenStack)
  • FusionCompute (non-typical deployment scenario)
  • Bare metal server
  • Inventory management of VMware resource pools

FusionSphere OpenStack can access multiple computing resource pools at one time.

  • KVM (provided by FusionSphere OpenStack)
  • FusionCompute (non-typical deployment scenario)
  • Bare metal server
  • Inventory management of VMware resource pools

Resource pool - network resource pool

software SDN

Components such as vRouter, L3NAT, L3_service, and VPN are deployed on network nodes of cascading FusionSphere OpenStack to provide VXLAN networks for cloud services.

hardware SDN

Agile Controller-DCN, an SDN controller oriented to DC networks, provides application-specific network automation functions and VXLAN networks for cloud services.

non-SDN

The Neutron component of FusionSphere OpenStack provides basic network capabilities and VLAN networks for cloud services.

Cloud services, common components, and the management domain

For details about cloud services supported in the three scenarios, see Table 1-2 in Cloud Services and Common Components.

Translation
Download
Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 160974

Downloads: 263

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