[jira] [Comment Edited] (YARN-6626) Embed REST API service into RM

2017-10-05 Thread Jian He (JIRA) 

[ 
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192524#comment-16192524
 ] 

Jian He edited comment on YARN-6626 at 10/5/17 7:41 AM:


[~eyang], standalone API-server doesn't work now after this patch. 
I reverted this patch from yarn-native-services for now. Please help check
Thanks [~rohithsharma] for reporting


was (Author: jianhe):
[~eyang], standalone API-server cannot start now after this patch. 
I reverted this patch from yarn-native-services for now. Please help check
Thanks [~rohithsharma] for reporting

> Embed REST API service into RM
> --
>
> Key: YARN-6626
> URL: https://issues.apache.org/jira/browse/YARN-6626
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Gour Saha
>Assignee: Eric Yang
> Fix For: yarn-native-services
>
> Attachments: YARN-6626.yarn-native-services.001.patch, 
> YARN-6626.yarn-native-services.002.patch, 
> YARN-6626.yarn-native-services.003.patch, 
> YARN-6626.yarn-native-services.004.patch, 
> YARN-6626.yarn-native-services.005.patch, 
> YARN-6626.yarn-native-services.006.patch, 
> YARN-6626.yarn-native-services.007.patch, 
> YARN-6626.yarn-native-services.008.patch, 
> YARN-6626.yarn-native-services.009.patch, 
> YARN-6626.yarn-native-services.010.patch, 
> YARN-6626.yarn-native-services.011.patch
>
>
> As of now the deployment model of the Native Services REST API service is 
> standalone. There are several cross-cutting solutions that can be inherited 
> for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API 
> service if it is embedded into the RM process. In fact we can expose the REST 
> API via the same port as RM UI (8088 default). The URI path 
> /services/v1/applications will distinguish the REST API calls from other RM 
> APIs.



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

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Comment Edited] (YARN-6626) Embed REST API service into RM

2017-09-26 Thread Eric Yang (JIRA) 

[ 
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180966#comment-16180966
 ] 

Eric Yang edited comment on YARN-6626 at 9/26/17 3:43 PM:
--

Remove .clone from getResource.  The probability of external code modifying 
data structure injection to Service object is almost not existed.  The code can 
be better written using List instead of ResourceInformation[], which should be 
another JIRA to handle all the touch points.  This feature is default to 
disabled per Jian's request.


was (Author: eyang):
Remove .clone from getResource.  The probability of external code modifying 
data structure injection to Service object is almost not existed.  The code can 
be better written using List instead of ResourceInformation[], which should be 
another JIRA to handle all the touch points.
This feature is default to disabled per Jian's request.

> Embed REST API service into RM
> --
>
> Key: YARN-6626
> URL: https://issues.apache.org/jira/browse/YARN-6626
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Gour Saha
> Fix For: yarn-native-services
>
> Attachments: YARN-6626.yarn-native-services.001.patch, 
> YARN-6626.yarn-native-services.002.patch, 
> YARN-6626.yarn-native-services.003.patch, 
> YARN-6626.yarn-native-services.004.patch, 
> YARN-6626.yarn-native-services.005.patch, 
> YARN-6626.yarn-native-services.006.patch
>
>
> As of now the deployment model of the Native Services REST API service is 
> standalone. There are several cross-cutting solutions that can be inherited 
> for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API 
> service if it is embedded into the RM process. In fact we can expose the REST 
> API via the same port as RM UI (8088 default). The URI path 
> /services/v1/applications will distinguish the REST API calls from other RM 
> APIs.



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

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Comment Edited] (YARN-6626) Embed REST API service into RM

2017-09-24 Thread Eric Yang (JIRA) 

[ 
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178396#comment-16178396
 ] 

Eric Yang edited comment on YARN-6626 at 9/24/17 11:11 PM:
---

Fixed findbugs and javadoc issues.


was (Author: eyang):
Fixed findbugs issues.

> Embed REST API service into RM
> --
>
> Key: YARN-6626
> URL: https://issues.apache.org/jira/browse/YARN-6626
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Gour Saha
> Fix For: yarn-native-services
>
> Attachments: YARN-6626.yarn-native-services.001.patch, 
> YARN-6626.yarn-native-services.002.patch, 
> YARN-6626.yarn-native-services.003.patch, 
> YARN-6626.yarn-native-services.004.patch, 
> YARN-6626.yarn-native-services.005.patch
>
>
> As of now the deployment model of the Native Services REST API service is 
> standalone. There are several cross-cutting solutions that can be inherited 
> for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API 
> service if it is embedded into the RM process. In fact we can expose the REST 
> API via the same port as RM UI (8088 default). The URI path 
> /services/v1/applications will distinguish the REST API calls from other RM 
> APIs.



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

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Comment Edited] (YARN-6626) Embed REST API service into RM

2017-09-22 Thread Eric Yang (JIRA) 

[ 
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176621#comment-16176621
 ] 

Eric Yang edited comment on YARN-6626 at 9/22/17 3:59 PM:
--

Fixed findbugs, unit test, and checkstyle issues.


was (Author: eyang):
Fixed findbugs issue.

> Embed REST API service into RM
> --
>
> Key: YARN-6626
> URL: https://issues.apache.org/jira/browse/YARN-6626
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Gour Saha
> Fix For: yarn-native-services
>
> Attachments: YARN-6626.yarn-native-services.001.patch, 
> YARN-6626.yarn-native-services.002.patch, 
> YARN-6626.yarn-native-services.003.patch
>
>
> As of now the deployment model of the Native Services REST API service is 
> standalone. There are several cross-cutting solutions that can be inherited 
> for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API 
> service if it is embedded into the RM process. In fact we can expose the REST 
> API via the same port as RM UI (8088 default). The URI path 
> /services/v1/applications will distinguish the REST API calls from other RM 
> APIs.



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

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Comment Edited] (YARN-6626) Embed REST API service into RM

2017-09-14 Thread Eric Yang (JIRA) 

[ 
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167071#comment-16167071
 ] 

Eric Yang edited comment on YARN-6626 at 9/14/17 10:47 PM:
---

This can be done by specifying hadoop-yarn-service-api as dependency to 
hadoop-yarn-ui project, this will automatically place 
hadoop-yarn-service-api*.jar and dependencies into WEB-INF/lib of 
hadoop-yarn-ui war file.  In web.xml file, specify:

{code}

  YARN UI

  
REST_API

com.sun.jersey.spi.container.servlet.ServletContainer

  com.sun.jersey.config.property.packages
  
org.apache.hadoop.yarn.appcatalog.controller;org.apache.hadoop.yarn.service.webapp


  com.sun.jersey.api.json.POJOMappingFeature
  true

1
  

  
REST_API
/ws/v2/*
  

{code}

Note that the prefix URL is hard coded in RestApiConstants.  The better 
approach is to ensure the prefix directory is described by configuration like 
in web.xml, or in ApiServerWebApp where addJerseyResourcePackage is the prefix 
path.  Hence the URL have the same prefix between apiserver and resource 
manager.


was (Author: eyang):
This can be done by specifying hadoop-yarn-service-api as dependency to 
hadoop-yarn-ui project, this will automatically place 
hadoop-yarn-service-api*.jar and dependencies into WEB-INF/lib of 
hadoop-yarn-ui war file.  In web.xml file, specify:

{code}

  YARN UI

  
REST_API

com.sun.jersey.spi.container.servlet.ServletContainer

  com.sun.jersey.config.property.packages
  
org.apache.hadoop.yarn.appcatalog.controller;org.apache.hadoop.yarn.service.webapp


  com.sun.jersey.api.json.POJOMappingFeature
  true

1
  

  
REST_API
/ws/v2/*
  

{code}

> Embed REST API service into RM
> --
>
> Key: YARN-6626
> URL: https://issues.apache.org/jira/browse/YARN-6626
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Gour Saha
> Fix For: yarn-native-services
>
>
> As of now the deployment model of the Native Services REST API service is 
> standalone. There are several cross-cutting solutions that can be inherited 
> for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API 
> service if it is embedded into the RM process. In fact we can expose the REST 
> API via the same port as RM UI (8088 default). The URI path 
> /services/v1/applications will distinguish the REST API calls from other RM 
> APIs.



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

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org