网络架构

  • Networking Option 1: Provider networks,the simplest way possible with primarily layer-2 (bridging/switching) services and VLAN segmentation of networks. Essentially, it bridges virtual networks to physical networks and relies on physical network infrastructure for layer-3 (routing) services. Additionally, a DHCP service provides IP address information to instances.
  • This option lacks support for self-service (private) networks, layer-3 (routing) services, and advanced services such as LBaaS and FWaaS. Consider the self-service networks option below if you desire these features.

a bit different from my example! just note it here.

  • All nodes require Internet access for administrative purposes such as package installation, security updates, DNS, and NTP. In most cases, nodes should obtain Internet access through the management network interface.
  • To highlight the importance of network separation, the example architectures use private address for the management network and assume that the physical network infrastructure provides Internet access via NAT or other methods.

  • In the provider networks architecture, all instances attach directly to the provider network.
  • In the self-service (private) networks architecture, instances can attach to a self-service or provider network. Self-service networks can reside entirely within OpenStack or provide some level of external network access using NAT through the provider network.
  • virtualization/openstack/networking.txt
  • 最后更改: 2019/04/16 18:31
  • (外部编辑)