cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter
Date Sun, 19 May 2013 12:07:16 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661539#comment-13661539
] 

ASF subversion and git services commented on CLOUDSTACK-1963:
-------------------------------------------------------------

Commit 438505756d00258f211a1c3d986fe37d57290554 in branch refs/heads/vmware-datamodel from
Sateesh Chodapuneedi <sateesh@apache.org>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4385057 ]

CLOUDSTACK-1963 New mapping model for CloudStack zone and Vmware datacenter Upgrade changes
with legacy zone support

DC-Zone mapping constraints should allow multiple hypervisors per zone.
Such zones would just be ignored.
Looking for only VMware clusters in the zone while associating a VMware DC with a zone.
Fixed upgrade path for zones with 1 cluster from 1 DC/vCenter. Auto-associating in this case.

                
> 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

Mime
View raw message