ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-10017) Rolling Upgrade: Expose FinalizeUpgradeAction to API or force transition from UPGRADED to CURRENT for cluster_version via API request. Additional fixes
Date Tue, 10 Mar 2015 21:17:38 GMT

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

Dmitry Lysnichenko updated AMBARI-10017:
----------------------------------------
    Issue Type: Improvement  (was: Bug)

> Rolling Upgrade: Expose FinalizeUpgradeAction to API or force transition from UPGRADED
to CURRENT for cluster_version via API request. Additional fixes
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10017
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10017
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.0.0
>
>
> To simplify for the user, provide a helper call from ambari-server like so:
> {code}
> ambari-server set-current {ClusterName} {VersionDisplayName}
> Enter Ambari login: X
> Enter Ambari password: X
> {code}
> make sure to handle:
> 1) Ambari server might be http or https
> 2) Ambari server port
> 3) Ambari server might not be running
> Please refer to "sync-ldap" that is currently part of ambari-server since it does similar
prompting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message