[MESOS-4240] Pull provisioner from linux filesystem isolator to Mesos containerizer.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.27.0
• Labels: mesosphere unified-containerizer-mvp
• Epic Link: Unified Container
• Sprint: Mesosphere Sprint 26
• Story Points: 5
• Assignee: Gilbert Song
• Reporter: Jie Yu
• Shepherd: Jie Yu
• Created: 22/Dec/15 21:01
• Updated: 26/Nov/18 12:22
• Resolved: 26/Nov/18 12:22

Description

The rationale behind this change is that many of the image specifications (e.g., Docker/Appc) are not just for filesystems. They also specify runtime configurations (e.g., environment variables, volumes, etc) for the container.

Provisioner should return those runtime configurations to the Mesos containerizer and Mesos containerizer will delegate the isolation of those runtime configurations to the relevant isolator.

Here is what it will be look like eventually. We could do those changes in phases:
1) Provisioner will return a ProvisionInfo which includes a 'rootfs' and image specific runtime configurations (could be the Docker/Appc manifest).
2) Then, the Mesos containerizer will generate a ContainerConfig (a protobuf which includes rootfs, sandbox, docker/appc manifest, similar to OCI's host independent config.json) and pass that to each isolator in 'prepare'. Imaging in the future, a DockerRuntimeIsolator takes the docker manifest from ContainerConfig and prepare the container.
3) The isolator's prepare function will return a ContainerLaunchInfo (contains environment variables, namespaces, etc.) which will be used by Mesos containerize to launch containers. Imaging that information will be passed to the launcher in the future.

We can do the renaming (ContainerPrepareInfo -> ContainerLaunchInfo) later.

Issue Links

• blocks: MESOS-4282 Update isolator prepare function to use ContainerLaunchInfo
• is depended upon by: MESOS-4225 Exposed docker/appc image manifest to mesos containerizer.