diff --git a/docs/en-US/primary-storage-add.xml b/docs/en-US/primary-storage-add.xml index 588d491a07a..5581e9e79b1 100644 --- a/docs/en-US/primary-storage-add.xml +++ b/docs/en-US/primary-storage-add.xml @@ -23,6 +23,52 @@ -->
- Adding Primary Storage - TODO + Add Primary Storage +
+ System Requirements for Primary Storage + Hardware requirements: + + Any standards-compliant iSCSI or NFS server that is supported by the underlying hypervisor. + The storage server should be a machine with a large number of disks. The disks should ideally be managed by a hardware RAID controller. + Minimum required capacity depends on your needs. + + When setting up primary storage, follow these restrictions: + + Primary storage cannot be added until a host has been added to the cluster. + If you do not provision shared primary storage, you must set the global configuration parameter system.vm.local.storage.required to true, or else you will not be able to start VMs. + +
+
+ Adding Primary Stroage + When you create a new zone, the first primary storage is added as part of that procedure. You can add primary storage servers at any time, such as when adding a new cluster or adding more servers to an existing cluster. + Be sure there is nothing stored on the server. Adding the server to &PRODUCT; will destroy any existing data. + + Log in to the &PRODUCT; UI (see ). + In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the primary storage. + Click the Compute tab. + In the Primary Storage node of the diagram, click View All. + Click Add Primary Storage. + + Provide the following information in the dialog. The information required varies depending on your choice in Protocol. + + Pod. The pod for the storage device. + Cluster. The cluster for the storage device. + Name. The name of the storage device. + Protocol. For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. + Server (for NFS, iSCSI, or PreSetup). The IP address or DNS name of the storage device. + Server (for VMFS). The IP address or DNS name of the vCenter server. + Path (for NFS). In NFS this is the exported path from the server. + Path (for VMFS). In vSphere this is a combination of the datacenter name and the datastore name. The format is "/" datacenter name "/" datastore name. For example, "/cloud.dc.VM/cluster1datastore". + Path (for SharedMountPoint). With KVM this is the path on each host that is where this primary storage is mounted. For example, "/mnt/primary". + SR Name-Label (for PreSetup). Enter the name-label of the SR that has been set up outside &PRODUCT;. + Target IQN (for iSCSI). In iSCSI this is the IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984. + Lun # (for iSCSI). In iSCSI this is the LUN number. For example, 3. + Tags (optional). The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.. + + The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2. + + Click OK. + + +
diff --git a/docs/en-US/secondary-storage-add.xml b/docs/en-US/secondary-storage-add.xml index 15e8c742657..e1f45cdec66 100644 --- a/docs/en-US/secondary-storage-add.xml +++ b/docs/en-US/secondary-storage-add.xml @@ -23,6 +23,26 @@ -->
+ Add Secondary Storage +
+ System Requirements for Secondary Storage + + NFS storage appliance or Linux NFS server + (Optional) OpenStack Object Storage (Swift) (see http://swift.openstack.org) + 100GB minimum capacity + A secondary storage device must be located in the same zone as the guest VMs it serves. + Each Secondary Storage server must be available to all hosts in the zone. + +
+
Adding Secondary Storage - TODO + When you create a new zone, the first secondary storage is added as part of that procedure. You can add secondary storage servers at any time to add more servers to an existing zone. + Be sure there is nothing stored on the server. Adding the server to &PRODUCT; will destroy any existing data. + + If you are going to use Swift for cloud-wide secondary storage, you must add the Swift storage to &PRODUCT; before you add the local zone secondary storage servers. See . + To prepare for local zone secondary storage, you should have created and mounted an NFS share during Management Server installation. See .See Preparing NFS Shares in the Installation Guide. + Make sure you prepared the system VM template during Management Server installation. See .See Prepare the System VM Template in the Installation Guide. + Now that the secondary storage server for per-zone storage is prepared, add it to &PRODUCT;. Secondary storage is added as part of the procedure for adding a new zone. See . + +
diff --git a/docs/publican-all.cfg b/docs/publican-all.cfg index d338738f296..897f92b4caa 100644 --- a/docs/publican-all.cfg +++ b/docs/publican-all.cfg @@ -25,3 +25,4 @@ docname: cloudstack brand: cloudstack chunk_first: 1 chunk_section_depth: 1 +condition: install diff --git a/docs/publican-install.cfg b/docs/publican-install.cfg index 708200d460f..64eeed995bb 100644 --- a/docs/publican-install.cfg +++ b/docs/publican-install.cfg @@ -24,6 +24,4 @@ docname: cloudstack_installation brand: cloudstack chunk_first: 1 chunk_section_depth: 1 - - - +condition: install