ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18634) Support Offline Stack Upgrades In a Cluster
Date Wed, 16 Nov 2016 16:45:58 GMT

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

Hudson commented on AMBARI-18634:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #339 (See [https://builds.apache.org/job/Ambari-branch-2.5/339/])
Merge branch 'branch-feature-AMBARI-18634' into trunk (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6e3e3cb226b8fd015ddaa441e24b058390eb5bda])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/HostOrderGrouping.java
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/host-upgrade-2.5.xml
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.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)

Mime
View raw message