Re: [Containerization WG] Sync tomorrow

2018-01-24 Thread Jie Yu
Instruction on how to join the sync can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit# - Jie On Wed, Jan 24, 2018 at 3:09 PM, Jie Yu wrote: > Hi folks, > > In tomorrow's sync, we'll be discussing the plan for the next

[Containerization WG] Sync tomorrow

2018-01-24 Thread Jie Yu
Hi folks, In tomorrow's sync, we'll be discussing the plan for the next Mesos release in the containerization area. We'll be reviewing this planning spreadsheet and update it accordingly: https://docs.google.com/spreadsheets/d/1_e-YRvRDoX766ZdzoE1TtXx3eJUx7fBoZkBx_1TwPjY/edit Please join us if

Re: Questions about Pods and the Mesos Containerizer

2018-01-24 Thread Zhitao Li
Glad someone is also looking this. On Wed, Jan 24, 2018 at 2:43 PM, Jie Yu wrote: > I can help answer some of them: > > Is it possible to do healthchecks per task in a pod? > > I believe so given healthcheck is at the TaskInfo level, but AlexR can > confirm. > > Is it

Re: Questions about Pods and the Mesos Containerizer

2018-01-24 Thread Jie Yu
I can help answer some of them: Is it possible to do healthchecks per task in a pod? I believe so given healthcheck is at the TaskInfo level, but AlexR can confirm. Is it possible to allocate a separate IP address per container in a pod? Not right now, but possible. We need to change the CNI

Questions about Pods and the Mesos Containerizer

2018-01-24 Thread David Morrison
Hi Mesos community! We’re in the process of designing a Mesos framework to launch multiple containers together on the same host and are considering a couple of approaches. The first is to use pods (with the TASK_GROUP primitive), and the second is write a custom executor that launches nested

Re: [VOTE] Release Apache Mesos 1.5.0 (rc1)

2018-01-24 Thread James Peach
+1 Verified on CentOS 6 and Fedora 27 > On Jan 22, 2018, at 7:15 PM, Gilbert Song wrote: > > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.5.0. > > 1.5.0 includes the following: >