Apache Mesos / Containerization Working Group

Agenda: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

Agenda and notes:
https://docs.google.com/a/mesosphere.io/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=drive_web

Agenda and notes:
https://docs.google.com/a/mesosphere.io/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=drive_web

Notes for the working group: https://docs.google.com/a/mesosphere.io/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=drive_web

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

Agenda and Notes:
https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit

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

Agenda and Notes:
https://docs.google.com/a/mesosphere.io/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=drive_web

Agenda and Notes:
https://docs.google.com/a/mesosphere.io/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=drive_web

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

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

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

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

No description provided.

Agenda and Notes: https://docs.google.com/a/mesosphere.io/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=drive_web
Chat with the working group: https://mesos.slack.com/ #containerizer

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

Agenda/Notes:
Volume ownership/permission (Ilya)
[Jie] different types of volumes in Mesos
Sandbox
Host volume
Docker volume (external, dvdi based)
Persistent volume (local, or CSI based in the future)
[jpeach] We need to call out the semantics we want in the doc.
[jpeach] alternative: require that all containers that want to access the same volume are under the same user
[jie] setgid bits? Do we really need that?
[jpeach] should the ownership of the volume be allowed to be changed
[yanx] similar to jpeach’s comment, we can allow framework to specify the ownership of the persistent volume and the access control is up to the operator.
Action items:
Jie will schedule a meeting to discuss the semantics we want to support with relevant stakeholders

Status update
Planning spreadsheet

No description provided.

No description provided.