You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/03/08 16:35:40 UTC

[jira] [Commented] (KNOX-66) Support Ambari REST API access via the Gateway

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

ASF subversion and git services commented on KNOX-66:
-----------------------------------------------------

Commit c2635885dddf6cfb4db85cfe16dbe5dfd476cbb5 in knox's branch refs/heads/master from [~sumit.gupta]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=c263588 ]

KNOX-66 Ambari REST API support


> Support Ambari REST API access via the Gateway
> ----------------------------------------------
>
>                 Key: KNOX-66
>                 URL: https://issues.apache.org/jira/browse/KNOX-66
>             Project: Apache Knox
>          Issue Type: New Feature
>    Affects Versions: 0.2.0
>            Reporter: Kevin Minder
>            Assignee: Sumit Gupta
>             Fix For: Future
>
>
> Ambari provides a rich REST API feature set.  Those APIs should be accessible via the gateway.  A few important considerations.  Ambari has a different authentication model from the Hadoop cluster do this will need to be dealt with.  In addition Ambari isn't part of the Hadoop cluster so the gateway URLs for Ambari should probably peers to the cluster.  For example
> https://gw-host:gw-port/gateway/clusterA
> https://gw-host:gw-port/gateway/ambari
> So implementation wise the gateway will likely treat Ambari like a cluster with only the ambari service in it.
> Special consideration needs to be taken to understand how authentication for Ambari REST API works and how that can be made secure and performant.



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