You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Eron Wright (JIRA)" <ji...@apache.org> on 2015/02/23 19:54:12 UTC
[jira] [Created] (AMBARI-9754) Add programmatic identifiers to
manual steps in stack upgrade
Eron Wright created AMBARI-9754:
------------------------------------
Summary: Add programmatic identifiers to manual steps in stack upgrade
Key: AMBARI-9754
URL: https://issues.apache.org/jira/browse/AMBARI-9754
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Reporter: Eron Wright
The rolling upgrade procedure involves a combination of automated and manual steps. Manual steps typically exist due to externalities that aren't under the direct control of Ambari. For example, before upgrading a database schema, the operator is asked to backup the database (which Ambari can't do automatically in all cases).
The upgrade API allows an external system to observe upgrade progress, and observe that a manual step has been reached. Imagine that the external system is designed to automate certain manual steps. *Ambari should provide a clear way to identify a specific manual step.*
A manual step should be identifiable by:
- service instance
- component instance
- task code
As a stretch goal, this improvement should apply to all steps, not merely manual steps.
Implementation-wise, this improvement would impact the upgrade pack (to define a task code), and the upgrade API (to report the new information).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)