[
https://issues.apache.org/jira/browse/YARN-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated YARN-6160:
---------------------------------
Attachment: YARN-6160-yarn-native-services.001.patch
Here is a first attempt at enabling different providers based on the artifact
type of the component. One question I have is whether we should add a new
artifact type such as "simple" or "command" that does not even require a
tarball, or whether we should make that a special case of the "tarball"
artifact type (where the id specified has a particular value such as "none" or
"null"). [~jianhe] [~gsaha]
Example json:
{noformat}
{
"name": "test1",
"lifetime": "3600",
"components" :
[
{
"name": "SLEEP",
"number_of_containers": 2,
"artifact": {
"id": "<path_to_tarball_in_hdfs>",
"type": "TARBALL"
},
"launch_command": "sleep 3600",
"resource": {
"cpus": 2,
"memory": "1024"
}
},
{
"name": "SLEEP_DOCKER",
"number_of_containers": 2,
"artifact": {
"id": "<docker_image_name>",
"type": "DOCKER"
},
"launch_command": "sleep 3600",
"resource": {
"cpus": 2,
"memory": "1024"
}
}
]
}
{noformat}
> Create an agent-less docker-less provider in the native services framework
> --------------------------------------------------------------------------
>
> Key: YARN-6160
> URL: https://issues.apache.org/jira/browse/YARN-6160
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Fix For: yarn-native-services
>
> Attachments: YARN-6160-yarn-native-services.001.patch
>
>
> The goal of the agent-less docker-less provider is to be able to use the YARN
> native services framework when Docker is not installed or other methods of
> app resource installation are preferable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
