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


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


Guide for Interworking Between HUAWEI CloudFabric Solution and Redhat OpenStack

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).
Agile Controller-DCN Service Model

Agile Controller-DCN Service Model

Figure 1-7 shows the Agile Controller-DCN service model objects, including tenants, Virtual Private Clouds (VPCs), external networks, logical routers, logical switches, logical load balancers, logical firewalls, subnets, and logical points.

Figure 1-7 Agile Controller-DCN service model
  • A tenant defines a group of available network resources, such as the number of available logical routers, number of external networks, and number of logical firewalls. In the OpenStack private cloud scenario, a tenant corresponds to an OpenStack project.
  • A VPC is a logical NE abstracted from the physical network. One VPC can contain different logical objects, such as logical routers, logical switches, and logical firewalls. Different VPCs are isolated logically and share hardware resources physically.
  • An external gateway defines the physical egress (border leaf), links to PEs, available public IP addresses, and routes advertised to PEs. In the OpenStack private cloud scenario, an external gateway corresponds to an OpenStack external network.
  • A logical router defines a virtual Layer 3 router, that is, VFR on a device. A logical router is connected to logical load balancers and logical firewalls. In the OpenStack private cloud scenario, a logical router corresponds to an OpenStack router. An open-source router in the OpenStack provides the FWaaS and VPNaaS service functions and corresponds to a logical firewall of the Agile Controller-DCN.
  • A logical load balancer (for example, F5 LB) is connected to a logical router logically. In the OpenStack private cloud scenario, a logical load balancer carries the load balancing services provisioned by the LBaaS.
  • A logical firewall is implemented by the vSYS (Huawei firewall) and provides security protection for north-south and east-west traffic. In the OpenStack private cloud scenario, a logical firewall carries the services provisioned by the FWaaS.
  • A logical switch defines an independent L2 broadcast domain, which is implemented by the VXLAN bridge domain. In the OpenStack private cloud scenario, a logical switch corresponds to a OpenStack Neutron network.
  • A subnet defines an IP address segment and a gateway IP address. A logical port defines an access port on a logical switch and defines the access VLAN and bridge domain.
Updated: 2019-03-25

Document ID: EDOC1100072313

Views: 3356

Downloads: 22

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