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/11/03 15:35:58 UTC
[jira] [Updated] (AMBARI-18680) Add orchestration for HOST_ORDERED
upgrades
[ https://issues.apache.org/jira/browse/AMBARI-18680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate Cole updated AMBARI-18680:
-------------------------------
Attachment: AMBARI-18680.patch
> Add orchestration for HOST_ORDERED upgrades
> -------------------------------------------
>
> Key: AMBARI-18680
> URL: https://issues.apache.org/jira/browse/AMBARI-18680
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18680.patch
>
>
> Orchestration via UpgradeHelper need to orchestrate via HOSTS instead of the UpgradePack services. This will entail:
> * Refactor UpgradeHelper to choose orchestration model
> * Upgrade Pack changes are minimal, StageWrapper and Manual tasks are generated in-code.
> * Determine service check changes (if any)
> * HostGrouping should use the following stages per-host:
> *# Stop command for each component
> *# Manual message to ask to proceed
> *# {{install_packages}} task - ONE per host. The purpose is to make sure all the symlink logic already in place is called correctly
> *# START commands for daemons, INSTALL commands for clients, just as a new cluster would do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)