[jira] [Commented] (AMBARI-5749) Store cluster installed state as part of the Cluster resource

["Jonathan Hurley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998806#comment-13998806 ] 

Jonathan Hurley commented on AMBARI-5749:
-----------------------------------------

After discussing this more, it seems like the "clusterState" should remain a field that can/will be used for a calculation of the state of the cluster. We will therefore add a new field on the cluster known as "provisioningState". This field will be separate and independent of the "clusterState", which is currently unused.
provisioningState will follow the same rules as other state fields WRT the state transition model. It will not be allowed to transition from INSTALLED back to INIT. There will only be 2 states that are supported; INIT, INSTALLED.
At cluster creation time, the cluster's provisioningState will default to INIT. The web client will need to explicitly transition the state from INIT to INSTALLED. There will be no calculation of this state. The field will be returned by default (along with id, name, etc) in a request where no field properties are named in a filter.

> Store cluster installed state as part of the Cluster resource
> -------------------------------------------------------------
>
>                 Key: AMBARI-5749
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5749
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 1.6.1
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 1.6.1
>
>
> FE currently stores whether the cluster has finished installing or not in the unstructured key-value store. We need to store such information in a more structured, robust manner.
> Also, whenever someone installs a cluster via API calls, there's a "persist" call that has to be made and this looks a bit like a hack.



--
This message was sent by Atlassian JIRA
(v6.2#6252)