mirror of
https://github.com/apache/cloudstack.git
synced 2025-12-19 03:54:03 +01:00
32 lines
4.7 KiB
HTML
32 lines
4.7 KiB
HTML
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.1. About Zones</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Admin_Guide-4.0.0-incubating-en-US-1-" /><link rel="home" href="index.html" title="CloudStack Administrator's Guide" /><link rel="up" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="prev" href="cloud-infrastructure-concepts.html" title="Chapter 2. Cloud Infrastructure Concepts" /><link rel="next" href="about-pods.html" title="2.2. About Pods" /></head><body><p id="title"><a class="left" href="http://cloudstack.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.cloudstack.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="cloud-infrastructure-concepts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="about-pods.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="about-zones" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="about-zones">2.1. About Zones</h2></div></div></div><div class="para">
|
||
A zone is the largest organizational unit within a CloudStack deployment. A zone typically corresponds to a single datacenter, although it is permissible to have multiple zones in a datacenter. The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required).
|
||
</div><div class="para">
|
||
A zone consists of:
|
||
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
|
||
One or more pods. Each pod contains one or more clusters of hosts and one or more primary storage servers.
|
||
</div></li><li class="listitem"><div class="para">
|
||
Secondary storage, which is shared by all the pods in the zone.
|
||
</div></li></ul></div><div class="mediaobject"><img src="./images/zone-overview.png" width="444" alt="zone-overview.png: Nested structure of a simple zone" /></div><div class="para">
|
||
Zones are visible to the end user. When a user starts a guest VM, the user must select a zone for their guest. Users might also be required to copy their private templates to additional zones to enable creation of guest VMs using their templates in those zones.
|
||
</div><div class="para">
|
||
Zones can be public or private. Public zones are visible to all users. This means that any user may create a guest in that zone. Private zones are reserved for a specific domain. Only users in that domain or its subdomains may create guests in that zone.
|
||
</div><div class="para">
|
||
Hosts in the same zone are directly accessible to each other without having to go through a firewall. Hosts in different zones can access each other through statically configured VPN tunnels.
|
||
</div><div class="para">
|
||
For each zone, the administrator must decide the following.
|
||
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
|
||
How many pods to place in a zone.
|
||
</div></li><li class="listitem"><div class="para">
|
||
How many clusters to place in each pod.
|
||
</div></li><li class="listitem"><div class="para">
|
||
How many hosts to place in each cluster.
|
||
</div></li><li class="listitem"><div class="para">
|
||
How many primary storage servers to place in each cluster and total capacity for the storage servers.
|
||
</div></li><li class="listitem"><div class="para">
|
||
How much secondary storage to deploy in a zone.
|
||
</div></li></ul></div><div class="para">
|
||
When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage.
|
||
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="cloud-infrastructure-concepts.html"><strong>Prev</strong>Chapter 2. Cloud Infrastructure Concepts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="about-pods.html"><strong>Next</strong>2.2. About Pods</a></li></ul></body></html>
|