A zone is the largest organizational unit in CloudStack, and it typically corresponds to a single datacenter. Zones provide physical isolation and redundancy. A zone consists of one or more pods (each of which contains hosts and primary storage servers) and a secondary storage server which is shared by all pods in the zone.
- Physical Network
- Public traffic
- Pod
- Guest Traffic
- Storage Traffic
When adding an advanced zone, you need to set up one or more physical networks. Each network corresponds to a NIC on the management server. Each physical network can carry one or more types of traffic, with certain restrictions on how they may be combined.
Drag and drop one or more traffic types onto each physical network.
Add physical network
-
Management
Set up the network for traffic between end-user VMs.
-
Public
Set up the network for traffic between end-user VMs.
-
Guest
Set up the network for traffic between end-user VMs.
-
Storage
Set up the network for traffic between end-user VMs.
- Netscaler
- Public traffic
- Pod
- Guest Traffic
- Storage Traffic
Please specify Netscaler info
- Netscaler
- Public traffic
- Pod
- Guest Traffic
- Storage Traffic
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 their public network.
Provide at lease one range of IP addresses for internet traffic.
- Netscaler
- Public traffic
- Pod
- Guest Traffic
- Storage Traffic
Each zone must contain in one or more pods, and we will add the first pod now. A pod contains hosts and primary storage servers, which you will add in a later step. First, configure a range of reserved IP addresses for CloudStack's internal management traffic. The reserved IP range must be unique for each zone in the cloud.
- Netscaler
- Public traffic
- Pod
- Guest Traffic
- Storage Traffic
Guest network traffic is communication between end-user virtual machines.
- Netscaler
- Public traffic
- Pod
- Guest Traffic
- Storage Traffic
Traffic between CloudStack's internal resources, including any components that communicate with the Management Server, such as hosts and CloudStack system VMs. Please configure storage traffic here.
- Cluster
- Host
- Primary Storage
- Secondary Storage
Each pod must contain one or more clusters, and we will add the first cluster now. A cluster provides a way to group hosts. The hosts in a cluster all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared storage. Each cluster consists of one or more hosts and one or more primary storage servers.
- Cluster
- Host
- Primary Storage
- Secondary Storage
Each cluster must contain at lease one host (computer) for guest VMs to run on, and we will add the first host now. For a host to function in CloudStack, you must install hypervisor software on the host, assign an IP address to the host, and ensure the host is connected to the CloudStack management server.
Give the host's DNS or IP address, the user name (usually root) and password, and any labels you use to categorize hosts.
- Cluster
- Host
- Primary Storage
- Secondary Storage
Each cluster must contain one or more primary storage servers, and we will add the first one now. Primary storage contains the disk volumes for all the VMs running on hosts in the cluster. Use any standards-compliant protocol that is supported by the underlying hypervisor.
- Cluster
- Host
- Primary Storage
- Secondary Storage
Each zone must have at lease one NFS or secondary storage server, and we will add the first one now. Secondary storage stores VM templates, ISO images, and VM disk volume snapshots. This server must be available to all hosts in the zone.
Provide the IP address and exported path.
Launch zone
Please wait while your zone is being created; this may take a while...