[
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671234#comment-13671234
]
ASF subversion and git services commented on CLOUDSTACK-1963:
-------------------------------------------------------------
Commit 069174bac7f5ca17a2b95fe39d4fe98500f37b82 in branch
refs/heads/vmware-datamodel from Sateesh Chodapuneedi <sate...@apache.org>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=069174b ]
CLOUDSTACK-1963 New mapping model for CloudStack zone and Vmware datacenter
Upgrade handling.
Detect legacy zones during db upgrade and perform data migration.
If legacy zone is detected the table 'cloud'.'legacy_zones' is populated.
If an existing zone which has resources that belong to single VMware datacenter
then such zone would not be marked as legacy zone. Such zone would be
automatically associated with the specific Vmware datacenter of the clusters
inside the zone.
Signed-off-by: Sateesh Chodapuneedi <sate...@apache.org>
> New mapping model for CloudStack zone and Vmware datacenter
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here,
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel
--
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
