[
https://issues.apache.org/jira/browse/SLIDER-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347930#comment-14347930
]
Steve Loughran commented on SLIDER-804:
---------------------------------------
Draft proposal
# Have a dir under each cluster, something like {{artifacts/}}
# have subdirs for each component, like {{artifacts/slideram}}
{{artifacts/regionserver}}
# recursively copy down each artifact from the subdir into the component.
Fun comes when you think about localisation. Do we want to be able to have the
artifacts copied late, **after any tar files in the app package are expanded**,
or early, in which case the NM can do the localisation. Early is easiest,
latest is better for app-relative deployment, though even there the need to
know the version numbers of paths add complexity. The slideram artifacts MUST
be early
> Add way in automatically add arbitrary artifacts to the container of
> components
> -------------------------------------------------------------------------------
>
> Key: SLIDER-804
> URL: https://issues.apache.org/jira/browse/SLIDER-804
> Project: Slider
> Issue Type: Improvement
> Affects Versions: Slider 0.70
> Reporter: Steve Loughran
>
> We want to add things like multiple .war files on top of an expanded tomcat
> installation, do something similar for node.js, etc.
> This could be done app-package by app-package, but it would be nicer to have
> a standard way across packages to do this
> # somewhere to keep text, data & binary artifacts in HDFS for each component
> type in an application instance.
> # an easy way to add artifacts at create time on the CLI (or at least after
> the build operation)
> # a way to list/update/review artifacts
> Having some structured layout in HDFS for artifacts would make this stuff
> possible & let us use the HDFS CLI & web view for initial interaction
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
