[
https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668601#comment-13668601
]
ASF subversion and git services commented on CLOUDSTACK-2029:
-------------------------------------------------------------
Commit db8030baa9ebc809d893d6829202b6bc9f9f4dc4 in branch
refs/heads/zone-primarystorage-vmware from Sateesh Chodapuneedi
<sate...@apache.org>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=db8030b ]
CLOUDSTACK-2029 zone wide primary storage support for cloudstack over vmware
deployments
Added hypervisor type to CreateStoragePoolCmd & Storage pool responses.
DatastoreLifeCycle would consider hypervisor type while attaching datastore to
zone.
ZoneWideStoragePoolAllocator would filter zone wide primary storage pools by
hypervisor type along with tags in disk profile.
hypervisor type is mandatory parameter if scope is specified as ZONE while
creating primary storage pool.
As of now KVM, VMware are allowed to use ZoneWideStoragePoolAllocator.
> zone wide primary storage support for cloudstack over vmware deployments
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2029
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller, VMware
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Support for primary storage that span across clusters in CloudStack zone.
> Similar to Amazon's EBS.
> This is to facilitate virtual disk availability across clusters.
> Functional Specification:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target
>
> A dedicated section is being added to the above FS with specifics around
> VMware resource support.
> Code for this feature can be found in branch
> refs/heads/zone-primarystorage-vmware
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
