mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomasz Janiszewski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-6648) MesosContainerizer launch helper should take ContainerLaunchInfo.
Date Mon, 05 Mar 2018 12:55:00 GMT

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

Tomasz Janiszewski commented on MESOS-6648:
-------------------------------------------

+1 to providing backward compatibility

https://jira.mesosphere.com/browse/MARATHON-7387

> 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
>            Priority: Major
>              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
(v7.6.3#76005)

Mime
View raw message