[jira] [Assigned] (AMBARI-16030) Ambari operation history: Add ambari_operation_history table for record keeping history of ambari versions and operations

[Sumit Mohanty (Jira)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty reassigned AMBARI-16030:
--

Assignee: (was: Sumit Mohanty)

> Ambari operation history: Add ambari_operation_history table for record 
> keeping history of ambari versions and operations
> -
>
> Key: AMBARI-16030
> URL: https://issues.apache.org/jira/browse/AMBARI-16030
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Priority: Major
> Fix For: 3.0.0
>
>
> When investigating upgrade issues, information about history about Ambari 
> versions is missing. Also information about when the Ambari upgrades actually 
> happened in the past is completely missing. 
> Instead of relying on this information to be provided, Ambari should record 
> Ambari upgrade history in Ambari DB. 
> {noformat}
> ambari_version_history
> VersionDateNotes
> 2.2.2.0-102/09/2015 01:00:00Clean Install
> 2.2.3.0-203/10/2015 01:00:00Upgraded 2.2.2.0-1 -> 
> 2.2.3.0-2
> 2.4.0.0-306/09/2015 01:00:00Upgraded 2.2.3.0-2 -> 
> 2.4.0.0-3
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Assigned] (AMBARI-17069) Recovery Manager: Refactor desired state transitions into a state table

[Sumit Mohanty (Jira)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty reassigned AMBARI-17069:
--

Assignee: (was: Sumit Mohanty)

> Recovery Manager: Refactor desired state transitions into a state table
> ---
>
> Key: AMBARI-17069
> URL: https://issues.apache.org/jira/browse/AMBARI-17069
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Priority: Major
> Fix For: 3.0.0
>
>
> The desired state transitions for various auto start types are computed using 
> a big if-else block which is difficult to maintain as we keep adding newer 
> features. Move the state transition to a state machine for easy lookup.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org