[
https://issues.apache.org/jira/browse/AMBARI-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654650#comment-15654650
]
Hudson commented on AMBARI-18634:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #302 (See
[https://builds.apache.org/job/Ambari-branch-2.5/302/])
Merge branch 'branch-feature-AMBARI-18634' into trunk (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ba7457b7b0680ed1db58d8acb93ce29904c69a5e])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/HostMaintenanceModeCheck.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HostMaintenanceModeCheckTest.java
> Support Offline Stack Upgrades In a Cluster
> -------------------------------------------
>
> Key: AMBARI-18634
> URL: https://issues.apache.org/jira/browse/AMBARI-18634
> Project: Ambari
> Issue Type: Epic
> Components: ambari-agent, ambari-server
> Affects Versions: 2.5.0
> Reporter: Jonathan Hurley
> Assignee: Nate Cole
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: UpgradePackforHostOrdered.pdf
>
>
> The purpose of this Epic is to track the work required for offline upgrades.
> The general workflow will be:
> * Create a host (VM) that is NOT part of a cluster that duplicates the
> hostname.
> * Install bits for an upgraded version of the software on a cluster.
> * Make Ambari aware that a new version is installed on the cluster.
> * Host-by-host, instruct Ambari to stop services for a host.
> * Once the components are stopped, stop the agent on the host.
> * After removing the host from the cluster, bring up the new host with the
> new bits pre-installed.
> * Ambari should accept the versions reported by the new host.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
