[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Travis Graham reassigned CLOUDSTACK-4609:
-----------------------------------------

    Assignee: Travis Graham

> [doc] Review Comments on Dedicated Resources: POD, CLUSTER
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-4609
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4609
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc
>            Reporter: Radhika Nair
>            Assignee: Travis Graham
>         Attachments: update-about-pods-clusters.patch
>
>
> 2.3. About Pods
> A pod often represents a single rack. Hosts in the same pod are in the same 
> subnet. A pod is the second-largest organizational unit within a CloudStack 
> deployment. Pods are contained within zones.
> Each zone can contain one or more pods. A pod consists of one or more 
> clusters of hosts and one or more primary storage servers. Pods are not 
> visible to the end user.
> [Pod is "third-largest" rather than "second-largest" now, after region and 
> zone]
> 2.4. About Clusters
> ...
> A cluster is the third-largest organizational unit within a CloudStack 
> deployment. Clusters are contained within pods, and pods are contained within 
> zones. Size of the cluster is limited by the underlying hypervisor, although 
> the CloudStack recommends less in most cases; see Best Practices.
> [cluster is the "fourth-largest" now]
> 2.7
> CloudStack provides plugins that enable both OpenStack Object Storage (Swift, 
> swift.openstack.org1
> )
> and Amazon Simple Storage Service (S3) object storage. When using one of 
> these storage plugins, you configure Swift or S3 storage for the entire 
> CloudStack, then set up the NFS Secondary Staging Store for each zone. The 
> NFS storage in each zone acts as a staging area through which all templates 
> and other secondary storage data pass before being forwarded to Swoft or S3. 
> The backing object storage acts as a cloud-wide resource, making templates 
> and other data available to any zone in the cloud.
> "Swift" not "Swoft"



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to