Return-Path: X-Original-To: apmail-cloudstack-commits-archive@www.apache.org Delivered-To: apmail-cloudstack-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 373F1101B4 for ; Mon, 26 Aug 2013 19:53:50 +0000 (UTC) Received: (qmail 1850 invoked by uid 500); 26 Aug 2013 19:53:49 -0000 Delivered-To: apmail-cloudstack-commits-archive@cloudstack.apache.org Received: (qmail 1821 invoked by uid 500); 26 Aug 2013 19:53:49 -0000 Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 1814 invoked by uid 99); 26 Aug 2013 19:53:48 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Aug 2013 19:53:48 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 4F4458C5BC2; Mon, 26 Aug 2013 19:53:48 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: jtomechak@apache.org To: commits@cloudstack.apache.org Message-Id: X-Mailer: ASF-Git Admin Mailer Subject: git commit: updated refs/heads/master to 91e82c8 Date: Mon, 26 Aug 2013 19:53:48 +0000 (UTC) Updated Branches: refs/heads/master 49dd7289c -> 91e82c8c2 DOC. Move misplaced paragraph from Secondary Storage section to Primary Storage section. Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/91e82c8c Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/91e82c8c Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/91e82c8c Branch: refs/heads/master Commit: 91e82c8c28a8202ce0d7ee8b06ab2ff1a64ab212 Parents: 49dd728 Author: Jessica Authored: Mon Aug 26 12:48:36 2013 -0700 Committer: Jessica Committed: Mon Aug 26 12:51:20 2013 -0700 ---------------------------------------------------------------------- docs/en-US/about-primary-storage.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/91e82c8c/docs/en-US/about-primary-storage.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/about-primary-storage.xml b/docs/en-US/about-primary-storage.xml index ebc61e8..9af9f2d 100644 --- a/docs/en-US/about-primary-storage.xml +++ b/docs/en-US/about-primary-storage.xml @@ -24,7 +24,7 @@
About Primary Storage - Primary storage is associated with a cluster and/or a zone. It stores the disk volumes for all of the VMs running on hosts in that cluster. You can add multiple primary storage servers to a cluster or a zone (at least one is required at the cluster level). Primary storage is typically located close to the hosts for increased performance. + Primary storage is associated with a cluster and/or a zone. It stores the disk volumes for all of the VMs running on hosts in that cluster. You can add multiple primary storage servers to a cluster or a zone (at least one is required at the cluster level). Primary storage is typically located close to the hosts for increased performance. &PRODUCT; manages the allocation of guest virtual disks to particular primary storage devices. Primary storage uses the concept of a storage tag. A storage tag is a label that is used to identify the primary storage. Each primary storage can be associated with zero, one, or more storage tags. When a VM is spun up or a data disk attached to a VM for the first time, these tags, if supplied, are used to determine which primary storage can support the VM or data disk (ex. say you need to guarantee a certain number of IOPS to a particular volume). Primary storage can be either static or dynamic. Static primary storage is what CloudStack has traditionally supported. In this model, the administrator must present CloudStack with a certain amount of preallocated storage (ex. a volume from a SAN) and CloudStack can place many of its volumes on this storage. In the newer, dynamic model, the administrator can present CloudStack with a storage system itself (ex. a SAN). CloudStack, working in concert with a plug-in developed for that storage system, can dynamically create volumes on the storage system. A valuable use for this ability is Quality of Service (QoS). If a volume created in CloudStack can be backed by a dedicated volume on a SAN (i.e. a one-to-one mapping between a SAN volume and a CloudStack volume) and the SAN provides QoS, then CloudStack can provide QoS. &PRODUCT; is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor, including, for example: