youtube image
From YouTube: Mesos Containerization WG 06 29 2017

Description

https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=sharing

Agenda/Notes:
[YanX, Jason, Gilbert] pre/post hook discussion
[YanX] preliminary doc about the problem and the thoughts
[Jie] sounds good. The key is to figure out the “context” where those commands will be executed. For instance, what namespaces (agent/container) the commands can assume? What cgroup those commands will be put into? What filesystem (agent/container) the command will assume?
[Jie] hooks within the container context can be done via a nested container by the executor?
[Jie] What’s the relationship between isolator container work? Will isolator container be sufficient for the use case?
[Jpeach] Linux capabilities enhancement, MESOS-7671
[Jpeach] Demo on the new linux capability improvement using mesos-execute
[Greg] Authorization on what capabilities a framework can grant a container?
[Jpeach] Host port isolation, MESOS-7675
[Jie] ephemeral port? Libprocess based executors are binding to a port that is not allocated by Mesos. Work around: only scan advertised ports (i.e., ‘port’ resources).
Status update
Planning spreadsheet