Re: [VOTE] Move Apache Mesos to Attic

+1 It was great working with you all. On Tue, Apr 6, 2021 at 7:13 AM Till Toenshoff wrote: > > > On 5. Apr 2021, at 19:58, Vinod Kone wrote: > > Hi folks, > > Based on the recent conversations >

Re: RFC: Improving linting in Mesos (MESOS-9630)

+1. I've used pre-commit in other projects and have been pretty successful. - Jie On Sun, Aug 18, 2019 at 5:41 PM James Peach wrote: > > > > On Aug 17, 2019, at 10:12 PM, Benjamin Bannier > wrote: > > > > Hi, > > > > I opened MESOS-9360[^1] to improve the way we do linting in Mesos some >

Re: [jira] [Created] (MESOS-9621) Mesos failed to build due to error LNK2019 on Windows using MSVC.

+ Qian, Gilbert On Fri, Mar 1, 2019 at 1:12 AM LinGao (JIRA) wrote: > LinGao created MESOS-9621: > - > > Summary: Mesos failed to build due to error LNK2019 on > Windows using MSVC. > Key: MESOS-9621 > URL:

Re: [VOTE] Release Apache Mesos 1.5.2 (rc3)

+1 make dist check on macOS Mojave On Tue, Jan 15, 2019 at 12:57 AM Gilbert Song wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.5.2. > > 1.5.2 includes the following: > >

Re: [VOTE] Release Apache Mesos 1.5.2 (rc2)

What's the progress on this? On Wed, Nov 28, 2018 at 10:31 PM Gilbert Song wrote: > Thanks, Chun! > > I will cut rc3 sometime early next week. > > On Tue, Nov 27, 2018 at 11:13 AM Chun-Hung Hsiao > wrote: > >> -1 for https://issues.apache.org/jira/browse/MESOS-8623 >> >> I'm working on a fix.

Re: Propose to create a Kubernetes framework for Mesos

roduction.As Jie mentioned,with this proposal,I mainly want to solve the > static partition issue.I agree to explore the ideas in a WG. > > > Cameron > > Jie Yu 于2018年12月6日周四 上午9:48写道： > > > I'd like to get some feedback on what Mesos users want. I can potentially > >

Re: Propose to create a Kubernetes framework for Mesos

. VK talks >> to >> > providers in-process and is highly-opinionated about the fact a provider >> > has no lifecycle (there's no _start_ or _stop_, as there would be for a >> > framework). There are talks about having Provide API over gRPC but it's >> not >&

Re: Propose to create a Kubernetes framework for Mesos

+ user list as well to hear more feedback from Mesos users. I am +1 on this proposal to create a Mesos framework that exposes k8s API, and provide nodeless experience to users. Creating Mesos framework that

Re: [VOTE] Release Apache Mesos 1.5.2 (rc2)

+1 > On Oct 31, 2018, at 4:26 PM, Gilbert Song wrote: > > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.5.2. > > 1.5.2 includes the following: > > *Announce major bug fixes

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

Gilbert, can we fix this and call another vote? Thanks, - Jie On Wed, Oct 24, 2018 at 12:45 PM Greg Mann wrote: > Hmm I wonder if this is an issue on 1.5.1, or perhaps introduced by this > commit? https://github.com/apache/mesos/commit/902aa34b79 > > On Wed, Oct 24, 2018 at 12:30 PM Vinod Kone

Re: Mesos container on windows

+ Andy On Fri, Oct 5, 2018 at 2:04 PM Vaibhav Khanduja wrote: > I plan to use mesos container's for windows. Does any body has any > production experience? Thx > > *Sent with Shift > < >

[Containerization] Mesos CNI support

Hi, If you are not using Mesos CNI integration, please ignore this email. Recently, we discovered a few bugs related to our CNI integration when there are lots of containers (200+) on a single agent box. Please see the following tickets for details. MESOS-9125

Re: Getting write access to our GitHub repo

avoid > conflicts (that need to be manually resolved) when people commit to both > repos independently and there is slowness in synchronization. > > 3) Our RB server currently points to yet another mirror " > git.apache.org/mesos" which has occasionally given us issues when po

Re: [VOTE] Move the project repos to gitbox

+1 On Tue, Jul 17, 2018 at 9:38 AM, Andrew Schwartzmeyer < and...@schwartzmeyer.com> wrote: > +1 > > > > On 07/17/2018 8:54 am, Zhitao Li wrote: > > +1 > > On Tue, Jul 17, 2018 at 8:10 AM James Peach wrote: > >> >> >> > On Jul 17, 2018, at 7:58 AM, Vinod Kone wrote: >> > >> > Hi, >> > >> > As

Re: Backport Policy

Greg, I like your idea of adding a prescriptive "policy" when evaluating whether a bug fix should be backported, and leave the decision to committer (because they have the most context, and avoid a bottleneck in the process). - Jie On Mon, Jul 16, 2018 at 11:24 AM, Greg Mann wrote: > My

Re: Getting write access to our GitHub repo

Vinod, can you start a VOTE thread per our discussion during the committer's meeting. On Sun, Jul 15, 2018 at 1:34 AM, Gastón Kleiman wrote: > On Wed, Jun 20, 2018 at 7:59 PM Vinod Kone wrote: > > > Hi folks, > > > > Looks like ASF now supports giving write > >

Re: Backport Policy

I typically backport all bug fixes that cleanly apply and the risk is low. It's a judgement call, but many of the time, you can easily tell the risk is low. I think my argument on why we want to do this is "why not". I want our software to have less bugs! Letting release manager decides which

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

+1 Passed on our internal CI that has the following matrix. I looked into the only failed test, looks to be a flaky test due to a race in the test. On Tue, Jun 26, 2018 at 7:02 PM, Greg Mann wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.6.1. > > >

CNI isolator bug in 1.6.0

Hi, We recently discovered one critical bug (kudos to Stéphane Cottin and Qian Zhang!) in CNI isolator that might cause your container to be killed when agent restarts. See more details in MESOS-9025 . The bug has been fixed both in 1.7.0 and

Re: Getting write access to our GitHub repo

+1 Does this means we can add CI webhooks to the git repo? On Thu, Jun 21, 2018 at 3:45 PM, James Peach wrote: > > > > On Jun 20, 2018, at 7:58 PM, Vinod Kone wrote: > > > > Hi folks, > > > > Looks like ASF now supports giving write > > access to committers for

Re: Proposing change to the allocatable check in the allocator

I would suggest we also consider the possibility of adding per framework control on `min_allocatable_resources`. If we want to consider supporting per-framework setting, we should probably model this as a protobuf, rather than a free form JSON. The same protobuf can be reused for both master

[Design Proposal] Non-resource Volume Support using CSI

Hi {{FIRST_NAME}}, I am working on the design doc for supporting non-resource volumes in Mesos through CSI. Please see the background and design in the following doc. Would love to get some feedback on this! Feel free to comment in the doc. JIRA: MESOS-8984

setsid(2) dependency

Hi, Currently, if you're using Mesos container (aka UCR), we put each container into a separate process session (i.e., calling setsid(2) after fork the initial

Re: Mesos replicated log dual writes

I am not aware any ticket related to this, so creating a ticket for tracking the issue would be great. - Jie On Tue, Jun 5, 2018 at 9:30 AM, Meghdoot bhattacharya < meghdoo...@yahoo.com.invalid> wrote: > Thx Joseph. Writing back the entire blob is costly instead of writing back > only the 2

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

+1 On Tue, May 15, 2018 at 2:56 PM, Greg Mann wrote: > +1 (binding) > > I did `sudo make check` and verified that only expected flaky tests failed. > > > Cheers, > Greg > > On Fri, May 11, 2018 at 12:35 PM, Gilbert Song wrote: > >> Hi all, >> >> Please

Container logger module interface change

Hi, I committed a patch that changed the container logger interface. The `prepare()` interface in the ContainerLogger now takes a ContainerCofig. This change is necessary for us to support per container control on logger behavior. Previously, it was only

Re: Update the *Minimum Linux Kernel version* supported on Mesos

> > User namespaces require >= 3.12 (November 2013). Can we make that the > minimum? No, we need to support CentOS7 which uses 3.10 (some variant) - Jie On Thu, Apr 5, 2018 at 8:56 AM, James Peach wrote: > > > > On Apr 5, 2018, at 5:00 AM, Andrei Budnik

Re: Release policy and 1.6 release schedule

r 23, 2018 at 9:21 PM, Jie Yu <yujie@gmail.com> wrote: > It's a burden for supporting multiple releases. > > 1.2 was released March, 2017 (1 year ago), and I know that some users are > still on that version > 1.3 was released June, 2017 (9 months ago), and we're still m

Re: Release policy and 1.6 release schedule

features that community members want to land in a > particular release. > > > Jie, I'm curious why you suggest a *minimal* interval between releases. > Could you elaborate a bit on your motivations there? > > Cheers, > Greg > > > On Fri, Mar 16, 2018 at 2:01 PM, Ji

Re: [Containerization WG] Call for Agenda, March 22nd, 2018

Looks like we don't have any agenda item for tomorrow. So I *cancelled* the meeting. See you guys in two weeks, and if you want to discuss anything, please add the agenda item to the notes. Thanks! - Jie On Wed, Mar 21, 2018 at 10:30 AM, Gilbert Song wrote: > Folks, > > We

Re: Release policy and 1.6 release schedule

Thanks Greg for starting this thread! > My primary motivation here is to bring our documented policy in line with > our practice, whatever that may be +100 Do people think that we should attempt to bring our release cadence more in > line with our current stated policy, or should the policy

Re: API Review: Resize (persistent) volume support

> > That said, I'm not sure if this is a valid concern since we don't have such > CSI functions yet. So input from folks would be very welcome! FYI, I just opened an issue in the CSI community: https://github.com/container-storage-interface/spec/issues/212 - Jie On Fri, Mar 16, 2018 at 11:40

Re: Welcome Zhitao Li as Mesos Committer and PMC Member

Congrats Zhitao! On Mon, Mar 12, 2018 at 2:02 PM, Gilbert Song wrote: > Hi, > > I am excited to announce that the PMC has voted Zhitao Li as a new > committer and member of PMC for the Apache Mesos project. Please join me to > congratulate Zhitao! > > Zhitao has been an

Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

Hi, I am happy to announce that the PMC has voted Chun-Hung Hsiao as a new committer and member of PMC for the Apache Mesos project. Please join me to congratulate him! Chun has been an active contributor for the past year. His main contributions to the project include: * Designed and

Re: Reconsidering `allocatable` check in the allocator

ide {cpu, mem, disk} is present) return true > else return true iff at least one of {cpu, mem, disk} has >= {MIN_CPU, > MIN_MEM, MIN_DISK} > } > > Otherwise, 1 GPU would be offered but 1GPU + 0.001 CPU would not? > > On Fri, Mar 2, 2018 at 9:27 AM, Jie Yu <yujie@gmail

Re: Looking for a shepherd for MESOS-4965

etty high priority to our org (some recent > accounting shows that it's potentially a lot of saving on hardware). > > On Mon, Mar 5, 2018 at 11:09 AM, Jie Yu <yujie@gmail.com> wrote: > > > Zhitao, I can provide some feedback because it most likely overlap with > the

Re: Looking for a shepherd for MESOS-4965

Zhitao, I can provide some feedback because it most likely overlap with the Resource Provider/CSI work. - Jie On Fri, Mar 2, 2018 at 9:08 PM, Zhitao Li wrote: > Hi, > > As our workload using persistent volume increases, the support for resizing > volumes

Reconsidering `allocatable` check in the allocator

Hi, The allocatable check in the allocator (shown below) was originally introduced to help alleviate the situation where a framework receives some resources, but no cpu/memory, thus cannot launch

Re: Thoughts on initial implementation to use libarchive?

Jeff, I looked a brief look, this looks great! 1. Is the API reasonable, more or less? Yeah, it looks reasonable to me. 2. Is the name of the API reasonable? Andy suggested namespace archive, > so you could do something like "archive::extract", but unfortunately > libarchive uses that with

Re: Anyone using a custom Sorter?

if your intention is to kill sorter interface, i am +100 On Wed, Feb 28, 2018 at 2:12 PM, Michael Park wrote: > I'm not even sure if anyone's using a custom Allocator, but > is anyone using a custom Sorter? It doesn't seem like there's > even a module for it so it wouldn't be

Re: Usage of Apache Jenkins Resources

I deleted Mesos-Buildbot-Custom. It was created for testing, and looks like we forgot to delete it after that. - Jie On Sat, Feb 17, 2018 at 1:49 PM, Karl Heinz Marbaise wrote: > Hi, > > mesos devs > > I would like to ask you why are you starting so many build jobs on a

Re: Docker image for fast e2e test with Mesos

goal I want to achieve is to test unreleased Mesos versions. - Jie On Sun, Feb 11, 2018 at 4:21 PM, Craig Wickesser <codecr...@gmail.com> wrote: > Might be worth checking out mini-mesos as well https://www.minimesos.org > > On Sun, Feb 11, 2018 at 7:05 PM Jie Yu <yujie@gmail.c

Docker image for fast e2e test with Mesos

Hi, When we were developing a framework with Mesos, we realized that it'll be great to have a Docker image that allows framework developers to quickly test with Mesos APIs (preferably new APIs that haven't been released yet). The docker container will have both Mesos master and agent running,

[Containerization WG] Sync tomorrow

Hi folks, During the sync tomorrow, we'll be doing a grooming for all the containerization related bugs and issues in Mesos JIRA: Bugs: https://issues.apache.org/jira/issues/?filter=12343087 All issues: https://issues.apache.org/jira/issues/?filter=12343086 Please join us if you're interested.

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

+1 Verified in our internal CI that `sudo make check` passed in CentOS 6, CentOS7, Debian 8, Ubuntu 14.04, Ubuntu 16.04 (both w/ or w/o SSL enabled). On Thu, Feb 1, 2018 at 5:36 PM, Gilbert Song wrote: > Hi all, > > Please vote on releasing the following candidate as

Re: [Containerization WG] Sync tomorrow

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 <yujie@gmail.com> wrote: > Hi folks, > > In tomorrow's sync, we'll be discussing the pl

[Containerization WG] Sync tomorrow

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: [VOTE] Release Apache Mesos 1.5.0 (rc1)

+1 Verified in our internal CI that `sudo make check` passed in CentOS 6, CentOS7, Debian 8, Ubuntu 14.04, Ubuntu 16.04 (both w/ or w/o SSL enabled). - Jie On Mon, Jan 22, 2018 at 9:17 PM, Sam wrote: > +1 > > > Regards, > > [image: Watch the Video] >

Re: [Containerization WG] Sync tomorrow

For those of you who cannot attend the meeting, the recording can be found here: https://zoom.us/recording/play/aSXMraCSUcOqx-L5yrM_Qf2vdeVTyffv4eAfkA2wqgtWPYq9s6KW1ksE8r85muwm - Jie On Wed, Jan 10, 2018 at 6:48 PM, Jie Yu <yujie@gmail.com> wrote: > Hi, > > I'll be talkin

[Containerization WG] Sync tomorrow

Hi, I'll be talking about the CSI support we introduced in 1.5, and probably should some demo! The notes and agenda (and how to join) can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit# See u all tomorrow! - Jie

Re: Mesos 1.5.0 Release

Branched! https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=shortlog;h=refs/heads/1.5.x - JIe On Fri, Dec 22, 2017 at 3:12 PM, Jie Yu <yujie@gmail.com> wrote: > Hey folks, > > I did a cleanup on tickets that target for 1.5.0. Here are the remaining >

Re: Mesos 1.5.0 Release

! Thanks, - Jie On Fri, Dec 22, 2017 at 3:14 AM, Alex Rukletsov <a...@mesosphere.com> wrote: > https://issues.apache.org/jira/browse/MESOS-8297 has just landed. Let's > include it in 1.5.0 as well. > > On Fri, Dec 22, 2017 at 4:35 AM, Jie Yu <yujie@gmail.com> wrot

Re: Mesos 1.5.0 Release

Hi, We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs to go into 1.5.0 that hasn't landed, please let me or Gilbert know asap. Thanks! - Jie On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song wrote: > Folks, > > It is time for Mesos 1.5.0 release. I am the

Re: [3/3] mesos git commit: Fixed the volume profile related build breakage.

Chun is working on a cleanup, see my comments in this review: https://reviews.apache.org/r/64659/ - Jie On Tue, Dec 19, 2017 at 11:16 AM, Benjamin Mahler wrote: > +joseph > > Chun and I wrote a fix for this last night to unbreak the build, please > take a look and adjust if

[Containerization WG] Cancelling the WG meeting tomorrow

Looks like everyone is busy with Mesos 1.5 release and we don't have an agenda. I am cancelling the sync. See you guys next year! - Jie

Re: Container launch metrics on agent

+ Joseph Gilbert Yeah, we need to follow up with some cleanups. This also applies to nested container. - Jie On Tue, Dec 12, 2017 at 10:09 AM, Zhitao Li wrote: > > > On Mon, Dec 11, 2017 at 7:34 PM, Benjamin Mahler > wrote: > >> 1) My guess is that

Re: mesos git commit: Added a performance working group December 2017 blog post.

This is AWESOME! - Jie On Mon, Dec 11, 2017 at 11:54 AM, wrote: > Repository: mesos > Updated Branches: > refs/heads/master 83f81b7b2 -> e7244ae1e > > > Added a performance working group December 2017 blog post. > > This blog post discusses the master failover performance

Re: Agent reconfiguration without losing tasks

Thanks Benno! This is exciting! On Wed, Dec 6, 2017 at 11:53 AM, Zhitao Li wrote: > Thank you for the amazing work! This addresses one of the biggest > operational pains we had in our cluster. > > > > On Wed, Dec 6, 2017 at 11:13 AM, Vinod Kone

Re: Mesos LXC container Support

Antonis, Please follow http://mesos.apache.org/documentation/latest/advanced-contribution/#before-coding-starts for this non-trivial feature. I feel that for this work, adding a new Containerizer might be the

[Containerization WG] Sync tomorrow

Hi, We'll be discussing "limiting rootfs size for containers" tomorrow (zhitao): https://docs.google.com/document/d/1KCNWUnyBpeDqzZz-URkunEp8RrgO0Gb2Twbgq_RKBRY/edit The notes and agenda (and how to join) can be found here:

Re: Welcome Andrew Schwartzmeyer as a new committer and PMC member!

Congrats, Andy! - Jie On Mon, Nov 27, 2017 at 3:00 PM, Joseph Wu wrote: > Hi devs & users, > > I'm happy to announce that Andrew Schwartzmeyer has become a new committer > and member of the PMC for the Apache Mesos project. Please join me in > congratulating him! > >

[Containerization WG] Sync tomorrow

Hi, Here are the tentative agenda for tomorrow's WG meeting: - [gilbert, zhitao] Image GC demo and gc policy discussion - [james] User namespace implementation plan If we have more time, we'll go through the roadmap doc to make it up-to-date. Instruction on how to join the meeting can be

[Containerization WG] Meeting tomorrow

Hi, For the regular WG sync tomorrow, James Peach will lead a discussion on the user namespace research he did recently. Here is the doc: https://docs.google.com/document/d/1IQ-Br4koPCKb1sh8xfdwJriphwzFN4AX_oMhPF3Nml4 We'll be delaying our VM support discussion by 2 weeks given that the research

Re: [Containerization WG] Meeting tomorrow

< janardhan.pulivar...@gmail.com> wrote: > Hi Jie, > > can you please provide the date & time both, because we're in different > timezones. > > Thanks, > Janardhan > > On Thu, Oct 5, 2017 at 5:14 AM, Jie Yu <yujie@gmail.com> wrote: > > > Hi > > &

[Containerization WG] Meeting tomorrow

Hi We'll have our regular sync tomorrow morning at 9am PST. Zhitao and Gilbert will be chatting about the docker image gc support they've been working on. There is the full agenda and notes. Feel free to add more!

Re: Operator HTTP API

+ Vinod On Tue, Oct 3, 2017 at 9:42 AM, David Morrison wrote: > Hello, > > My name is David Morrison, and I'm one of the engineers at Yelp working > with some of our large Mesos clusters. I was wondering if you could tell > me about the stability of the new operator HTTP

[Containerization WG] Meeting recording today

Hi folks, Thanks for the meeting today! The recording of today's meeting can be found here: https://drive.google.com/file/d/0B78XyMjTpvTmcENUWWs3M05pRms/view?usp=sharing The notes can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=sharing

Re: Mesos at Metamarkets

> > With regards to metrics and measuring of containers, having the Mesos > agents register with all cgroups that they can expose through > /monitor/statistics just for executor tracking purposes would be an awesome > feature to implement. Mesos now supports all available cgroup subsystems. I

[Containerization WG] Meeting agenda tomorrow

Hi folks, We'll be holding our regular WG sync tomorrow morning PST (9am-10am). Here is the tentative agenda. Please join us if you are interested! Look at this doc for the instruction how to join the sync:

[Containerization WG] Meeting recording 09/07/2017

Hi, Thanks everyone for joining the sync today! And thanks James for presenting the PAM support design. Good discussion! The recording of the meeting can be found here: https://drive.google.com/file/d/0B78XyMjTpvTmU0x2eW9kYzRTTGc/view?usp=sharing - Jie

[Containerization WG] Meeting tomorrow

Hi, James will lead the discussion on the design proposal for PAM support: https://docs.google.com/document/d/1nlWC7ArgQRr5f_ uH5wJ0AGV8BHMhoKgYf__RTmu7TKk/edit# The Agenda can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugt c2nHR89skFXSpU/edit?usp=sharing

Re: Welcome James Peach as a new committer and PMC memeber!

Congrats James! Well deserved! On Wed, Sep 6, 2017 at 2:08 PM, Yan Xu wrote: > Hi Mesos devs and users, > > Please welcome James Peach as a new Apache Mesos committer and PMC member. > > James has been an active contributor to Mesos for over two years now. He > has made many

Re: Questions about the mesos protocol

Sorry, the comment above applies to MesosContainerizer. For DockerContainerizer, all mounts will be private (docker default). We don't have immediate plan to support slave/shared mount for DockerContainerizer. You can use MesosContainerizer to launch Docker containers, see doc here:

Re: Questions about the mesos protocol

By default, all host volumes are slave mounts. We're planning to add support for allowing a host volume to be a shared mount. - Jie On Thu, Aug 31, 2017 at 12:11 AM, yawei@xtaotech.com < yawei@xtaotech.com> wrote: > Hi all > In current mesos protocol(defined in mesos.proto), the

Re: Offer operation reconciliation discussion notes

> What are the next steps for moving this forward, Jie James, the next step is to create a design doc for this. Looks like we're aligned on the high level approach. On Wed, Aug 30, 2017 at 11:40 AM, Jie Yu <yujie@gmail.com> wrote: > + Gaston and Greg > > Wh

Re: Offer operation reconciliation discussion notes

an Xu <xuj...@apple.com> wrote: >> >>> Yeah a reason for failed operations is probably useful for all resource >>> operations. It looks like the task-style status update is still the best >>> approach. >>> >>> --- >>> @xujyan <https

[Containerization WG] Meeting recording 08/24/2017

Hi folks, Thanks for the meeting and discussion today! Thanks Joseph and James for presenting! The recording for the meeting can be found here: https://drive.google.com/file/d/0B78XyMjTpvTmVW9MeS1NYlBxVWM/view?usp=sharing - Jie

Re: [Containerization WG] Meeting tomorrow

Information about how to join the meeting can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=sharing - Jie On Wed, Aug 23, 2017 at 3:16 PM, Jie Yu <yujie@gmail.com> wrote: > Hi, > > We'll hold the regular WG meeting t

[Containerization WG] Meeting tomorrow

Hi, We'll hold the regular WG meeting tomorrow morning (9am PDT). Here is the tentative agenda for the sync: [Joseph] Standalone container design review https://docs.google.com/document/d/1DZVfZAOLtqd8kbiWHD4j29LzaYcNC h1k6QQnbggyTio/edit#heading=h.djaqtpndp41e [James] Network ports isolator

Re: Offer operation reconciliation discussion notes

API can address this. Maybe we can add both if we feel both are useful? Thoughts? - Jie On Wed, Aug 23, 2017 at 11:26 AM, Jie Yu <yujie@gmail.com> wrote: > Hi, > > We had a discussion on some very early proposal (see the attached slides) > on providing feedback for off

Offer operation reconciliation discussion notes

Hi, We had a discussion on some very early proposal (see the attached slides) on providing feedback for offer operations (e.g., CREATE/DESTORY, RESERVE/UNRESERVE, etc.) with a bunch of folks from the community. Here are the notes I captured in the meeting: - One alternative approach

[Containerization WG] Meeting notes 08/10/2017

Hi, We had a very good session today. Thanks everyone for joining! The notes are captured here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit# The recording of the meeting can be found here:

Re: Deprecating `--disable-zlib` in libprocess

+1 on removing this flag. On Tue, Aug 8, 2017 at 11:32 AM, Benjamin Mahler wrote: > Sorry, I think this was me, feel free to remove it from libprocess now that > it's required. > > On Tue, Aug 8, 2017 at 10:57 AM, Chun-Hung Hsiao > wrote: > > > Hi

Re: [Containerization WG] Meeting notes 07/27/2017

For the follow up discussions on the volume ownership and access control, I created a slack channel (#volume-access-control) in Apache Mesos slack. If you're interested or want to provide feedback, please join that channel. Thanks! - Jie On Thu, Jul 27, 2017 at 1:41 PM, Jie Yu <yu

[Containerization WG] Meeting notes 07/27/2017

Hi folks, Thanks for those attend the meeting today. We had a good discussion on volume ownership and access control . Notes are captured here:

[Containerization WG] Meeting tomorrow

Hi folks, We'll have our regular containerization working group tomorrow. We'll going to continue discuss the volume ownership and access control design. I also invited Microsoft folks to join the meeting so that they can provide perspective from Windows's perspective. See you tomorrow!

Re: Mesos execute behind proxy - Failed to connect to registry-1.docker.io...

Looks like some issue with the proxy setting. Can you print your agent environment variables? (HTTP_PROXY and HTTPS_PROXY) - Jie On Thu, Jul 20, 2017 at 1:16 PM, William Markito Oliveira < mark...@apache.org> wrote: > I'm reading MESOS-6010 [1] which seems very similar to the problem I'm >

[Containerization WG] Meeting notes 07/13/2017

Hi folks, The notes and recording for today's meeting can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=sharing https://drive.google.com/file/d/0B78XyMjTpvTmenBWdG1aR3h5dDQ/view?usp=sharing - Jie

[Containerization WG] Meeting tomorrow

Hi folks, For the meeting tomorrow, we'll be discussing the following: 1) isolator via container [Jie] 2) OCI Image Store and unified artifacts support [Gilbert] Please join us if you're interested. The agenda and how to join is captured in this note:

CHANGELOG entry for 1.x.0 releases

Hi folks, I was told that for 1.x.0 releases, we should not add WIP CHANGELOG entries until a release candidate is cut. However, I'd argue that we should keep adding WIP entries (mainly 'new feature' and 'deprecation') to the CHANGELOG for 1.x.0 releases. For the ticket list, we should use the

Re: how to wait for nested container launch in tests

One way is to define a health check? - Jie On Fri, Jun 30, 2017 at 3:36 AM, James Peach wrote: > Hi all, > > I'm trying to write a nested container test for an isolator. It turns out > that the default executor sends TASK_RUNNING immediately after receiving > the

[Containerization WG] Meeting notes 06/29/2017

Hi folks, We had a great meeting today. The notes of the meeting can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=sharing The recording of the meeting can be found here:

[Containerization WG] Regular meeting tomorrow

Hi folks, Here is tomorrow's tentative agenda [YanX, Jason, Gilbert] pre/post hook discussion [Jpeach] Linux capabilities enhancement, MESOS-7671 More details can be found here: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit# Please join us if you're

Re: [Proposal] Multiple Containers in Single Mesos Task

Thanks for the proposal! Sorry about the late reply on this. My take on this is: we should avoid introducing APIs that allow folks to do the same thing using different ways. Looks like the proposal here would allow frameworks to launch pod like workload in different ways (via TaskGroup or via

[Containerization WG] Notes 06/15/2017

Hi folks, Today, we discussed the volume ownership problem, lead by Ilya. https://docs.google.com/document/d/1eMaSTS3-DTsWJYyeXUnotIquSpf3nsukrHEt9GS2ONE/edit# Please find today's notes in the following doc.

Re: Easing the Pain of Code Formatting in Mesos

+1 Also, agreed with AlexR. Some of our style rules are very subjective. Tooling and enforceable rules are much more important. - Jie On Thu, Jun 15, 2017 at 8:13 AM, Zhitao Li wrote: > strongly +1 to this. > > On Thu, Jun 15, 2017 at 7:20 AM, Alex Rukletsov

[Containerization WG] Meeting tomorrow

Hi folks, Mesos Containerization WG is scheduled for tomorrow (9AM PST). Ilya will lead the discussion on volume ownership/permission cleanup. Please join us if you're interested in this topic.

Re: Welcome Greg Mann as a new committer and PMC member!

Congrats Greg! On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone wrote: > Hi folks, > > Please welcome Greg Mann as the newest committer and PMC member of the > Apache Mesos project. > > Greg has been an active contributor to the Mesos project for close to 2 > years now and has

[Containerization WG] Notes 06/01/2017

Hi Today, we went over the design proposal (CPU pinning in Mesos) from Dmitry. Please find today's notes in the following doc. https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugt c2nHR89skFXSpU/edit?usp=sharing The recording can be found here:

Mesos Containerization WG meeting tomorrow

Hi folks, Mesos Containerization WG is scheduled for tomorrow (9AM PST). Dmitry will present the design proposal for "CPU pinning in Mesos ". Please join us if you're interested! The full agenda

  1   2   3   4   5   6   7   8   9   10   >