You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Abhishek Dasgupta (JIRA)" <ji...@apache.org> on 2016/02/03 20:16:39 UTC

[jira] [Commented] (MESOS-4572) docker executor should support preconfiguration and postconfiguration steps

    [ https://issues.apache.org/jira/browse/MESOS-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130925#comment-15130925 ] 

Abhishek Dasgupta commented on MESOS-4572:
------------------------------------------

How about if we pass two new fields i.e preconfig script and postconfig script through TaskInfo and the executor runs it before and after executing Docker run? 
[~jieyu] Tim Chen, Any thought about this?? 

> docker executor should support preconfiguration and postconfiguration steps
> ---------------------------------------------------------------------------
>
>                 Key: MESOS-4572
>                 URL: https://issues.apache.org/jira/browse/MESOS-4572
>             Project: Mesos
>          Issue Type: Improvement
>          Components: docker
>            Reporter: popsuper1982
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> there should be one way to execute some scripts before and after the docker is created.
> Preconfiguration: for example, check the environments (IP addresses, Hostnames, Bridges, Volume directories) of the hosts where docker will run, and form the ENV for the docker and then run the docker with those environments.
> Postconfiguration: for example, use pipework to configure the docker, get the ports allocated and reports to another docker to configure relationships between applications between dockers.
> another postconfiguration example, after docker is shutdown, cleanup some data in the volumes 



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