mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <>
Subject [jira] [Updated] (MESOS-5350) Add asynchronous hook for validating docker containerizer tasks
Date Sat, 28 May 2016 00:22:12 GMT


Jie Yu updated MESOS-5350:
    Story Points: 5  (was: 2)

> Add asynchronous hook for validating docker containerizer tasks
> ---------------------------------------------------------------
>                 Key: MESOS-5350
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: docker, modules
>            Reporter: Joseph Wu
>            Assignee: Joseph Wu
>            Priority: Minor
>              Labels: containerizer, hooks, mesosphere
>             Fix For: 0.29.0
> It is possible to plug in custom validation logic for the MesosContainerizer via an {{Isolator}}
module, but the same is not true of the DockerContainerizer.
> Basic logic can be plugged into the DockerContainerizer via {{Hooks}}, but this has some
notable differences compared to isolators:
> * Hooks are synchronous.
> * Modifications to tasks via Hooks have lower priority compared to the task itself. 
i.e. If both the {{TaskInfo}} and {{slaveExecutorEnvironmentDecorator}} define the same environment
variable, the {{TaskInfo}} wins.
> * Hooks have no effect if they fail (short of segfaulting)
> i.e. The {{slavePreLaunchDockerHook}} has a return type of {{Try<Nothing>}}:
> But the effect of returning an {{Error}} is a log message:
> We should add a hook to the DockerContainerizer to narrow this gap.  This new hook would:
> * Be called at roughly the same place as {{slavePreLaunchDockerHook}}
> * Return a {{Future}} and require splitting up {{DockerContainerizer::launch}}.
> * Prevent a task from launching if it returns a {{Failure}}.

This message was sent by Atlassian JIRA

View raw message