[ 
https://issues.apache.org/jira/browse/YARN-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Billie Rinaldi updated YARN-5505:
---------------------------------
    Attachment: YARN-5505-yarn-native-services.001.patch

Attaching a first draft of the docker provider. Unit tests are passing with 
this patch, but there are some Slider IT failures I am still looking into. To 
specify the docker provider when launching an app, use the following:
{noformat}
slider create appName --provider docker --template appConfig.json --resources 
resources.json
{noformat}

The docker image and start command are specified in the appConfig as follows:
{noformat}
"docker.image": "imageName",
"docker.startCommand": "startCommand",
{noformat}

Metainfo is no longer required, as this is only needed by the Slider agent. For 
the docker provider, metainfo information is placed in the appConfig. Metainfo 
items already handled in this patch are config files and packages/tarballs to 
be localized by the AM.

Config files generated by the AM are specified in new appConfig properties 
prefixed by "conf.", while the k/v config properties to appear in the config 
files are specified under "site." (as they have been for agent apps):
{noformat}
"am.config.generation": "true",

"conf.myapp-site.type": "properties",
"conf.myapp-site.name": "/tmp/conf.properties",

"site.myapp-site.prop1": "val1",
"site.myapp-site.prop2": "val2",
{noformat}

Tarballs and other resources to be localized are specified with the prefix 
"pkg.":
{noformat}
"pkg.myapp.type": "archive",
"pkg.myapp.name": "myapp-bin.tar.gz",
{noformat}

> Create an agent-less docker provider
> ------------------------------------
>
>                 Key: YARN-5505
>                 URL: https://issues.apache.org/jira/browse/YARN-5505
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>         Attachments: YARN-5505-yarn-native-services.001.patch
>
>
> The Slider AM has a pluggable portion called a provider. Currently the only 
> provider implementation is the agent provider which contains the bulk of the 
> agent-related Java code. We can implement a docker provider that does not use 
> the agent and gets information it needs directly from the NM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to