[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479759#comment-16479759 ] Hudson commented on YARN-8293: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14224 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14224/]) YARN-8293. Removed "User Name for service" for deploying secure YARN (eyang: rev 7802af6e9a85f033e9515cc7b23c125a0e06c325) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/services/hosts.js * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/templates/components/deploy-service.hbs * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/adapters/yarn-servicedef.js * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/initializers/loader.js * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/config/default-config.js * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/components/deploy-service.js > In YARN Services UI, "User Name for service" should be completely removed in > secure clusters > > > Key: YARN-8293 > URL: https://issues.apache.org/jira/browse/YARN-8293 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > Fix For: 3.2.0, 3.1.1 > > Attachments: YARN-8293.001.patch > > > "User Name for service" should be completely removed in secure clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478844#comment-16478844 ] Rohith Sharma K S commented on YARN-8293: - thanks [~sunilg] for the patch. I tested the patch and looks fine to me. [~eyang] Would you be able to commit this patch today? > In YARN Services UI, "User Name for service" should be completely removed in > secure clusters > > > Key: YARN-8293 > URL: https://issues.apache.org/jira/browse/YARN-8293 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > Attachments: YARN-8293.001.patch > > > "User Name for service" should be completely removed in secure clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477754#comment-16477754 ] Sunil G commented on YARN-8293: --- bq.Does this imply that the user interface can only display jobs for the login user, and not all the jobs from all users for yarn admin? Yes. Only login user can see only his apps. But he is an admin, then all apps could be seen. This filtering is done in RM if a config param is turned on. Otherwise in a secure cluster, only same user apps can be seen. We can an open another Jira to do an investigation which covers all secure/non-secure scenarios. I ll do that post this patch > In YARN Services UI, "User Name for service" should be completely removed in > secure clusters > > > Key: YARN-8293 > URL: https://issues.apache.org/jira/browse/YARN-8293 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > Attachments: YARN-8293.001.patch > > > "User Name for service" should be completely removed in secure clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477594#comment-16477594 ] Eric Yang commented on YARN-8293: - [~sunilg] The changes in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/templates/components/deploy-service.hbs will hide username column from the displaying table. Does this imply that the user interface can only display jobs for the login user, and not all the jobs from all users for yarn admin? This seems to be a use ability limitation for yarn admin users. We might need follow up JIRAs to make sure that we can support the case where yarn admin look at all the jobs from all users. Other than this nitpick, I think this patch is ready. > In YARN Services UI, "User Name for service" should be completely removed in > secure clusters > > > Key: YARN-8293 > URL: https://issues.apache.org/jira/browse/YARN-8293 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > Attachments: YARN-8293.001.patch > > > "User Name for service" should be completely removed in secure clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477011#comment-16477011 ] Sunil G commented on YARN-8293: --- Hi [~eyang] We will be removing user.name only in secure cluster where its doesnt consider user.name. It always takes from the kinited user. Hence we hide this in secure cluster. In normal cluster, same will be available for the use case which u mentioned above > In YARN Services UI, "User Name for service" should be completely removed in > secure clusters > > > Key: YARN-8293 > URL: https://issues.apache.org/jira/browse/YARN-8293 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > Attachments: YARN-8293.001.patch > > > "User Name for service" should be completely removed in secure clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476034#comment-16476034 ] Eric Yang commented on YARN-8293: - YARN service can have duplicated application name between users. If user name field is removed, this will cause confusion for administrator who is looking at all jobs from all users. > In YARN Services UI, "User Name for service" should be completely removed in > secure clusters > > > Key: YARN-8293 > URL: https://issues.apache.org/jira/browse/YARN-8293 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > Attachments: YARN-8293.001.patch > > > "User Name for service" should be completely removed in secure clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[
https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475690#comment-16475690
]
genericqa commented on YARN-8293:
-
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
28s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 23m
55s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
33m 19s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
10m 27s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
23s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 45m 4s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:abb62dd |
| JIRA Issue | YARN-8293 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12923458/YARN-8293.001.patch |
| Optional Tests | asflicense shadedclient |
| uname | Linux fa7ba26833ed 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20
11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / 2bb647b |
| maven | version: Apache Maven 3.3.9 |
| Max. process+thread count | 410 (vs. ulimit of 1) |
| modules | C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui U:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/20728/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> In YARN Services UI, "User Name for service" should be completely removed in
> secure clusters
>
>
> Key: YARN-8293
> URL: https://issues.apache.org/jira/browse/YARN-8293
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-ui-v2
>Reporter: Sunil G
>Assignee: Sunil G
>Priority: Major
> Attachments: YARN-8293.001.patch
>
>
> "User Name for service" should be completely removed in secure clusters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters
[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475654#comment-16475654 ] Sunil G commented on YARN-8293: --- [~rohithsharma] pls help to review > In YARN Services UI, "User Name for service" should be completely removed in > secure clusters > > > Key: YARN-8293 > URL: https://issues.apache.org/jira/browse/YARN-8293 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sunil G >Priority: Major > Attachments: YARN-8293.001.patch > > > "User Name for service" should be completely removed in secure clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
