You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Donald Hansen (JIRA)" <ji...@apache.org> on 2015/04/01 00:43:52 UTC

[jira] [Commented] (AMBARI-1423) Taking over a supported Ambari Stack cluster via API's/Scripts to be able to manage and monitor.

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

Donald Hansen commented on AMBARI-1423:
---------------------------------------

This issue is pretty old. Any traction or work around? I've been searching the web and haven't found anything yet. Thanks.

> Taking over a supported Ambari Stack cluster via API's/Scripts to be able to manage and monitor.
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-1423
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1423
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>         Attachments: Taking Over Cluster Via Ambari.docx, mitchwyle@ebaysf.com-suggestions-2013-02-20-1030-Taking Over Cluster Via Ambari.docx
>
>
> Taking over a supported Ambari Stack cluster via API's/Scripts to be able to manage and monitor. This to be able to take over clustets deployed manually or via some other means to be managed/monitored via Ambari. This idea also alludes to a cluster blueprint which explains the state of the cluster which Ambari can then use to manage/monitor.



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