Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 31 Oct 2013 04:52:25 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12672122.1380800140809.9507.1383195145692@arcas>
In-Reply-To: <JIRA.12672122.1380800140809@arcas>
References: <JIRA.12672122.1380800140809@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-4793) Improve VR Upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Animesh Chaturvedi updated CLOUDSTACK-4793:
-------------------------------------------


There is no update on these items and are in open state, if they are not ready for 4.3.0 please move them out to "Future". Remember the feature freeze date for 4.3.0 is 11/08 and the last day for merge request with 72 hour feedback peiod is 11/05.

> Improve VR Upgrade
> ------------------
>
>                 Key: CLOUDSTACK-4793
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4793
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Kishan Kavala
>            Assignee: Kishan Kavala
>             Fix For: 4.3.0
>
>
> Give admin control to sequence the upgrade of the cloud by:
>   Infrastructure hierarchy: by Cluster, Pod, and Zone etc.
>   Administrative hierarchy: by Tenant or Domain 
> Minimize service interruption to users
> Improve the speed of the upgrade time by making as many upgrade operations in parallel as possible


--
This message was sent by Atlassian JIRA
(v6.1#6144)