This is an automated email from the ASF dual-hosted git repository.
rohit pushed a commit to branch 4.15
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/4.15 by this push:
new a618875 VMware vSphere datastore cluster synchronisation (#205)
a618875 is described below
commit a618875051348c600b8949218ce4c5b96c1617f9
Author: Harikrishna <[email protected]>
AuthorDate: Mon May 24 16:05:22 2021 +0530
VMware vSphere datastore cluster synchronisation (#205)
* VMware vSphere datastore cluster synchronisation
* datastore cluster casesensitve changes
* added VMFS details
* Added NFS to supported to list for VMware vSphere
---
source/adminguide/storage.rst | 8 ++++++++
source/installguide/configuration.rst | 11 +++++------
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/source/adminguide/storage.rst b/source/adminguide/storage.rst
index 6feb481..5d082dc 100644
--- a/source/adminguide/storage.rst
+++ b/source/adminguide/storage.rst
@@ -121,6 +121,14 @@ OCFS2. In this case the CloudStack does not attempt to
mount or unmount
the storage as is done with NFS. The CloudStack requires that the
administrator insure that the storage is available
+VMware vSphere supports NFS, VMFS5, VMFS6, vSAN, vVols, DatastoreCluster
storage types.
+For DatastoreCluster storage type, any changes to the datastore cluster
+at vCenter can be synchronised with CloudStack, like any addition of new
+child datastore to the DatastoreCluster or removal or existing child datastore
+from the DatastoreCluster. Synchronisation of DatastoreCluster happens during
+host connect or storage pool maintenance operations or by calling the API
+syncStoragePool.
+
With NFS storage, CloudStack manages the overprovisioning. In this case
the global configuration parameter storage.overprovisioning.factor
controls the degree of overprovisioning. This is independent of
diff --git a/source/installguide/configuration.rst
b/source/installguide/configuration.rst
index 1146ff2..067c284 100644
--- a/source/installguide/configuration.rst
+++ b/source/installguide/configuration.rst
@@ -678,9 +678,8 @@ Advanced Zone Configuration
- **Protocol.** For XenServer, choose either NFS, iSCSI, or
PreSetup. For KVM, choose NFS, SharedMountPoint, CLVM, and RBD.
- For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The
- remaining fields in the screen vary depending on what you choose
- here.
+ For vSphere, choose either NFS, PreSetup (VMFS - iSCSI/FiberChannel,
vSAN, vVols) or DatastoreCluster.
+ The remaining fields in the screen vary depending on what you choose
here.
.. cssclass:: table-striped table-bordered table-hover
@@ -1125,19 +1124,19 @@ cluster.
- **Protocol.** For XenServer, choose either NFS, iSCSI, or
PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere
- choose either NFS, PreSetup (VMFS, vSAN, vVols) or datastorecluster. For
Hyper-V,
+ choose either NFS, PreSetup (VMFS - iSCSI/FiberChannel, vSAN, vVols) or
DatastoreCluster. For Hyper-V,
choose SMB.
- **Server (for NFS, iSCSI, or PreSetup).** The IP address or DNS
name of the storage device.
- - **Server (for PreSetup or datastorecluster).** The IP address or DNS
name of the vCenter
+ - **Server (for PreSetup or DatastoreCluster).** 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 PreSetup or datastorecluster).** In vSphere this is a
combination of the
+ - **Path (for PreSetup or DatastoreCluster).** In vSphere this is a
combination of the
datacenter name and the datastore or datastore cluster name. The format
is "/"
datacenter name "/" datastore or datastore cluster name. For example,
"/cloud.dc.VM/cluster1datastore".
