[AMBARI-18634] Support Offline Stack Upgrades In a Cluster

• Type: Epic
• Status: Resolved
• Priority: Critical
• Resolution: Resolved
• Affects Version/s: 2.5.0
• Fix Version/s: 2.5.0
• Component/s: ambari-agent, ambari-server
• Epic Name: Ambari: Support for Offline Stack Upgrades
• Assignee: Nate Cole
• Reporter: Jonathan Hurley
• Created: 19/Oct/16 15:25
• Updated: 29/Nov/16 22:01
• Resolved: 29/Nov/16 22:01

Description

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.

Issue Links

• is related to: AMBARI-12556 Provide ability to apply single patches on top of RU release