cloudstack 笔记

最新推荐文章于 2024-08-29 20:05:13 发布

转载最新推荐文章于 2024-08-29 20:05:13 发布 · 716 阅读

本文介绍了虚拟路由器提供的特性，如负载均衡、端口转发等，并详细阐述了在基本和高级网络区域中设置物理网络的过程。此外，还讲解了不同类型网络流量的概念及其配置方法。

the Virtual Router provides many cool features like LoadBalancing, PortForwarding, (s)NAT, DHCP, VPN and so on.

When a new network is created and being used, a Virtual Router is automatically launched to support these features.

Part of adding a zone is setting up the physical network. One or (in an advanced zone) more physical networks can be associated with each zone. The network corresponds to a NIC on the hypervisor host. Each physical network can carry one or more types of network traffic. The choices of traffic type for each network vary depending on whether you are creating a zone with basic networking or advanced networking.

When basic networking is used, there can be only one physical network in the zone.

When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod.

When CloudStack's internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use.

Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address.

Guest VMs have a name and group. VM names and groups are opaque to CloudStack and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user:

Instance name – a unique, immutable ID that is generated by CloudStack and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123.
Display name – the name displayed in the CloudStack web UI. Can be set by the user. Defaults to instance name.
Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name