ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Balázs Bence Sári (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
Date Tue, 26 Sep 2017 12:26:01 GMT

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

Balázs Bence Sári edited comment on AMBARI-21325 at 9/26/17 12:25 PM:
----------------------------------------------------------------------

Hey Chandana, 

Thanks. I am also testing with HDP 2.6, however I had to change a few things to make it work:
1. Change Knox path for OOZIE to _gateway/default/oozie/_
2. Change Knox path for HBASE to _gateway/default/hbase/webui_
3. Change Knox path for YARN to _gateway/default/yarn_
4. Change Knox parh for SPARK2 to to _/gateway/default/sparkhistory_


Re your solution for Spark: The <version>2.1.0</version> declaration for sparkhistory
is there in the topology.xml for the original path. I could as well remove it so spark would
work with the 1.4.0 version in place. In that case the quick link would work, however, clicking
on any further link on the Spark UI would be broken. That's why I thought the 1.4.0 may be
obsolete and 2.1.0 would be working fine. Do you know if 2.1.0 Knox service definitions for
sparkhistory are any different than 1.4.0?


was (Author: bsari):
Hey Chandana, 

Thanks. I am also testing with HDP 2.6, however I had to change a few things to make it work:
1. Change Knox path for OOZIE to _gateway/default/oozie/_
2. Change Knox path for HBASE to _gateway/default/hbase/webui_
3. Change Knox path for YARN to _gateway/default/yarn_
4. Change Knox parh for SPARK2 to to _/gateway/default/sparkhistory_


Re your solution for Spark: The _ <version>2.1.0</version>_ declaration for sparkhistory
is there in the topology.xml for the original path. I could as well remove it spark would
work with the 1.4.0 version in place. In that case the quick link would work, however, clicking
on any further link on the Spark UI would be broken. That's why I thought the 1.4.0 may be
obsolete and 2.1.0 would be working fine. Do you know if 2.1.0 Knox service definitions for
sparkhistory are any different than 1.4.0?

> Ability to switch Quick Links to use Service URL through Knox or given proxy
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-21325
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21325
>             Project: Ambari
>          Issue Type: Improvement
>    Affects Versions: trunk, 2.5.2, 2.5.3
>            Reporter: Jeffrey E  Rodriguez
>            Assignee: Chandana Mirashi
>         Attachments: 21325_test_results.zip, AMBARI-21325.patch, AMBARI-21325-rebased.patch
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Knox has the ability to proxy Hadoop user interfaces URL. Having the ability to setup
Quicklinks  through Knox so instead of for example going to "Hbase Master UI" directly we
can proxy through Knox for example: http://hdpjeff1.fyre.ibm.com:16010/master-status
> can be instead go through: https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status
> Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL.
> This will bring authentication to the UI access and would secure the UI access.
> Ideally this behavior can be set as secure going through proxy by default or it can be
turn off to go directly by Ambari Admin.
> Changes added:
> 1. Add new json properties knox_url, knox_path, supports_knox 
>    a. knox_url: template to be used for urls that are proxied through Knox
>    b. knox_path: Knox gateway path that will be added to the proxy url.
>    c. supports_knox: whether link will be redirected through Knox
> 2. Add above json properties to quicklinks.json 
> 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, SPARKUI
services to Knox topology template.
> 4. Automate protocol and port added to Knox topology file. Based on whether SSL is enabled
for the services  listed above, the port and protocol in params_linux.py will be updated.
> 5. Update quick_view_link_view.js so that when Knox is installed and support_knox is
true, quicklink url follows knox url template specified in the quicklinks.json for the service/component.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message