Skip to content

Conversation

@harikrishna-patnala
Copy link
Contributor

These documentation changes are related to the improvement PR apache/cloudstack#4871
In VMware vSphere, primary storage datastore cluster can be now synchronised with CloudStack upon any changes on the datastore cluster at vCenter. If any new child datastore is added to datastore cluster or if any existing child datastore is removed from the datastore cluster at vCenter then these changes can be synchronised with datastore cluster in CloudStack primary storage.

the storage as is done with NFS. The CloudStack requires that the
administrator insure that the storage is available

VMware vSphere supports VMFS5, VMFS6, vSAN, vVols, datastorecluster storage types.
Copy link
Contributor

Choose a reason for hiding this comment

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

datastorecluster => DatastoreCluster

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated the name in all occurrences.

Copy link
Contributor

Choose a reason for hiding this comment

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


- **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

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

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

@harikrishna-patnala harikrishna-patnala force-pushed the vSphereDatastoreClusterSynchronisation branch from 0d5900e to 5904e4b Compare March 31, 2021 05:57
Copy link
Contributor

@sureshanaparti sureshanaparti left a comment

Choose a reason for hiding this comment

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

doc LGTM

@yadvr yadvr added this to the 4.15 milestone May 24, 2021
@yadvr yadvr merged commit a618875 into 4.15 May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants