Skip to content

VMware vSphere datastore cluster synchronisation #205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yadvr merged 4 commits into from
May 24, 2021
Merged

VMware vSphere datastore cluster synchronisation #205

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e86691b
VMware vSphere datastore cluster synchronisation
harikrishna-patnala Mar 30, 2021
5904e4b
datastore cluster casesensitve changes
harikrishna-patnala Mar 31, 2021
a029e4b
added VMFS details
harikrishna-patnala Mar 31, 2021
234ce7c
Added NFS to supported to list for VMware vSphere
harikrishna-patnala Mar 31, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions source/adminguide/storage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
11 changes: 5 additions & 6 deletions source/installguide/configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Contributor

@sureshanaparti sureshanaparti Mar 31, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any reason to not include (iSCSI or FiberChannel) for VMFS ?

Copy link
Contributor Author

@harikrishna-patnala harikrishna-patnala Mar 31, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the new vSphere advanced capabiltities, PreSetup can be of any storage type, so to keep it generic here we mentioned the storage technology names as VMFS, vSAN, vVOls

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

Expand Down Expand Up @@ -1182,19 +1181,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".
Expand Down