[
https://issues.apache.org/jira/browse/YARN-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791048#comment-16791048
]
Jonathan Eagles commented on YARN-7129:
---------------------------------------
bq. Multiple options are available to deactivate Docker image build
If a build feature is disabled a majority of the time, the default should be
off.
bq. Using profile to generate different artifact is strongly discouraged
practice by Maven best practice guide line
I generally agree with this, which is I would argue creating a docker image
should be a separate process, possibly even project.
>From a process perspective, does the docker image evolve at the same rate as
>the project? Is there a 1-to-1 relationship between build artifacts (i.e.
>would multiple docker images be viable for a single hadoop release.
>conversely, would a single docker image be viable for multiple hadoop
>release).
>From a community perspective, does feature restrict who can be a release
>manager? Does this work out of the box for per build instructions? Do we
>compromise the security of developers by enabling this feature?
>From a process perspective, this jira isn't following best practices. An
>umbrella jira shouldn't be closed before its subtasks. With a 1MB+ patch, I
>wonder if we are combining multiple features into a single jira.
[~eyang], I do have a few question for you so that we can avoid revert work in
the future. Did you feel there was community consensus or contention before
this went in? Did the right people look at the jira before commit. Personally,
the title and description were not enough for me to know what a large change it
was. But specifically, I wonder what you thought could help.
> Application Catalog for YARN applications
> -----------------------------------------
>
> Key: YARN-7129
> URL: https://issues.apache.org/jira/browse/YARN-7129
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: applications
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN Appstore.pdf, YARN-7129.001.patch,
> YARN-7129.002.patch, YARN-7129.003.patch, YARN-7129.004.patch,
> YARN-7129.005.patch, YARN-7129.006.patch, YARN-7129.007.patch,
> YARN-7129.008.patch, YARN-7129.009.patch, YARN-7129.010.patch,
> YARN-7129.011.patch, YARN-7129.012.patch, YARN-7129.013.patch,
> YARN-7129.014.patch, YARN-7129.015.patch, YARN-7129.016.patch,
> YARN-7129.017.patch, YARN-7129.018.patch, YARN-7129.019.patch,
> YARN-7129.020.patch, YARN-7129.021.patch, YARN-7129.022.patch,
> YARN-7129.023.patch, YARN-7129.024.patch, YARN-7129.025.patch,
> YARN-7129.026.patch, YARN-7129.027.patch, YARN-7129.028.patch
>
>
> YARN native services provides web services API to improve usability of
> application deployment on Hadoop using collection of docker images. It would
> be nice to have an application catalog system which provides an editorial and
> search interface for YARN applications. This improves usability of YARN for
> manage the life cycle of applications.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
