You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2016/10/24 15:40:59 UTC
[jira] [Updated] (AMBARI-18634) Support Offline Stack Upgrades In a
Cluster
[ https://issues.apache.org/jira/browse/AMBARI-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate Cole updated AMBARI-18634:
-------------------------------
Epic Name: Ambari: Support for Offline Stack Upgrades (was: Ambari: Support for Offline Upgrades)
> 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
>
>
> 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)