[jira] [Commented] (MESOS-6648) MesosContainerizer launch helper should take ContainerLaunchInfo.

["Stephan Erb (JIRA)" <ji...@apache.org>]

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

Stephan Erb commented on MESOS-6648:
------------------------------------

I fear the sudden interface change makes upgrading difficult. Would it be possible to provide a backwards compatible shim so that users can migrate to the new command line API seamlessly?

Context:
* https://issues.apache.org/jira/browse/AURORA-1882
* https://reviews.apache.org/r/55951/

> MesosContainerizer launch helper should take ContainerLaunchInfo.
> -----------------------------------------------------------------
>
>                 Key: MESOS-6648
>                 URL: https://issues.apache.org/jira/browse/MESOS-6648
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Jie Yu
>            Assignee: Jie Yu
>              Labels: mesosphere
>             Fix For: 1.2.0
>
>
> Currently, the launch helper takes various flags from MesosContainerizer to launch the container. This makes it very hard to add more parameters to the launch helper. To simplify that, MesosContainerizer can pass 'ContainerLaunchInfo' to the launch helper instead. 'ContainerLaunchInfo' is also the protobuf message returned by isolators during 'prepare()'. This makes it very easy to merge them and send it to the launch helper. More importantly, this makes it very easy to add more parameters to the launch helper in the future.



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