cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chandan Purushothama (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-4220) 3.0.6 to ASF 4.2 Upgrade: "Add VMWare DataCenter" button should not be provided for Legacy Zones
Date Mon, 12 Aug 2013 23:57:48 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chandan Purushothama reopened CLOUDSTACK-4220:
----------------------------------------------


Attached the 3.0.6 Setup's MySQL Dump.Reopening the bug. The feature was worked on by Sateesh.
You may check with him to confirm the intended observations.

Thank you,
Chandan.
                
> 3.0.6 to ASF 4.2 Upgrade: "Add VMWare DataCenter" button should not be provided for Legacy
Zones
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4220
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4220
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>            Assignee: Jessica Wang
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> After Upgrade, DB Observations:
> mysql> select * from vmware_data_center;
> Empty set (0.03 sec)
> mysql> select * from vmware_data_center_zone_map;
> Empty set (0.02 sec)
> mysql> select * from legacy_zones;
> +----+---------+
> | id | zone_id |
> +----+---------+
> |  1 |       1 |
> +----+---------+
> 1 row in set (0.00 sec)
> mysql> select * from clusters;
> ERROR 1146 (42S02): Table 'cloud.clusters' doesn't exist
> mysql> select * from cluster;
> +----+--------------------------------+--------------------------------------+--------------------------------------+--------+----------------+-----------------+-----------------+------------------+---------------+---------+-------+---------+-------------+--------------+
> | id | name                           | uuid                                 | guid 
                               | pod_id | data_center_id | hypervisor_type | cluster_type
   | allocation_state | managed_state | removed | owner | created | lastUpdated | engine_state
|
> +----+--------------------------------+--------------------------------------+--------------------------------------+--------+----------------+-----------------+-----------------+------------------+---------------+---------+-------+---------+-------------+--------------+
> |  1 | 10.223.52.61/VMDC/clus1        | 2bc52adc-0345-426d-b4dc-b10bb26b475c | c4ca4238-a0b9-3382-8dcc-509a6f75849b
|      1 |              1 | VMware          | ExternalManaged | Enabled          | Managed
      | NULL    | NULL  | NULL    | NULL        | Disabled     |
> |  2 | 10.223.52.61/OTHERVMDC/clus2   | e80bff91-598e-4d4e-8951-205311a979d4 | c81e728d-9d4c-3f63-af06-7f89cc14862c
|      2 |              1 | VMware          | ExternalManaged | Enabled          | Managed
      | NULL    | NULL  | NULL    | NULL        | Disabled     |
> |  3 | 10.223.52.61/ANOTHERVMDC/clus3 | 159b911e-864d-41ef-b24e-de7be25a0ffb | eccbc87e-4b5c-32fe-a830-8fd9f2a7baf3
|      1 |              1 | VMware          | ExternalManaged | Enabled          | Managed
      | NULL    | NULL  | NULL    | NULL        | Disabled     |
> +----+--------------------------------+--------------------------------------+--------------------------------------+--------+----------------+-----------------+-----------------+------------------+---------------+---------+-------+---------+-------------+--------------+
> 3 rows in set (0.00 sec)
> mysql>
> Reference: the Mapping Model at https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Considering a model where a CloudStack deployment will have some zones with multiple
DCs and some zones with single DC. This comes from the fact that existing CloudStack deployment
has zones with multiple DCs. But after upgrade to the newest version, customer would like
to have existing zones to operate as-is. But all new CloudStack zones would be having single
DC. In this model, the existing zone with multiple DCs is termed as Legacy zone and it will
not support the zone wide features are requires a zone to have only 1 DC. Also operations
on legacy zone should be seamless (like adding a cluster etc.) as they were before upgrade.
This means the code base doesn't apply any new logic, that affects the functionality, over
legacy zone. For example, constraint checks that happen while adding a cluster to new zone
should not be done if the zone is legacy zone.

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