Re: Proposal: move content in Wiki to docs in code repo

+1. At least I personally rarely touch the wiki. Gilbert On Mon, Jun 6, 2016 at 11:51 AM, Zhou Z Xing wrote: > +1 > > It's good idea to collect and gather every thing in one single repo, would > be easier for users to find out. > > Thanks & Best Wishes, > > Tom Xing(邢舟) >

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

Hi Kevin, Please remove the the patch below from the list: Implemented runtime isolator default cmd test (still under review). https://reviews.apache.org/r/44469/ Because the bug was fixed by patch #44468, the test should not be considered as a block. I am updating MESOS-4888 and move the test

Executors no longer inherit environment variables from the agent

Hi, TL;DR Executors will no longer inherit environment variables from the agent by default in 0.30. Currently, executors are inheriting environment variables form the agent in mesos containerizer by default. This is an unfortunate legacy behavior and is insecure. If you do have environment

Re: Executors no longer inherit environment variables from the agent

ROCESS_IP going to be an exception to this? Some executors are > using this variable as an alternative of implementing their own IP > detection logic AFAIK so this behavior would break them. > > On Tue, Mar 8, 2016 at 11:33 AM, Gilbert Song <gilb...@mesosphere.io> > wrote:

Re: Mesos Web UI

Julian, since the fix was after 0.28, could you try it again by applying the patch @haosdent provided, or try with mesos master head? On Fri, Apr 29, 2016 at 8:52 AM, Julian Gonzalez Llorente < jgonza...@medallia.com> wrote: > Hello list, > > I found one little error on the web UI of mesos. > In

Re: FW: failure notice

Hi Aishwarya, It would be helpful to find out the root cause if the agent log and sandbox log can be attached:) Gilbert On Tue, Apr 26, 2016 at 5:17 AM, haosdent wrote: > Could you provide Mesos Agent log and stdout/stderr log? > > On Tue, Apr 26, 2016 at 7:53 PM,

Re: Potential serious issue when upgrading OpenJDK8 to >= 8u77 with Debian / Ubuntu packaging

Hi Steven, Thanks for reporting this serious issue. And yes, this is the right place to notify mesos users, which may potentially save many people a bunch of time while collecting more review comments on your PR. Also, It would be helpful to expose the risk of upgrading OpenJDK to mesos users.

Re: How could Mesos work with docker?

Yu, Mesos supports docker images without using the docker daemon. This feature is called Unified Containerizer, which was introduced since Mesos 0.28. Please follow this document to launch your containers: http://mesos.apache.org/documentation/latest/container-image/ Feel free to join our slack

The External Containerizer is Removed

Hello All, FYI, as we discussed on the mailing list in Oct 2015 (link ) and Apr 2016 (link

Re: Jenkins CI Plugin

Seems like Master::exited() is called for your jenkins frameworkId or PID. Which Mesos version are you using? It may possibly caused by network partition. Are you consistently getting this error? Gilbert On Fri, Sep 2, 2016 at 12:01 PM, June Taylor wrote: > Greetings, > > We're

Re: Unified cgroups isolator

Awesome! Kudos to @haosdent and @qianzhang! On Tue, Sep 13, 2016 at 11:22 AM, haosdent wrote: > Really appreciate @qian and @jie's great helps on this! It makes us easier > to add cgroups isolation for rest subsystem. > > Additionally, if you find any changes about unified

Docker Private Registry Credential per Container

Hi all, Recently, we started working on support for docker private registry credential per container in Mesos (MESOS-7088 ). This feature aims to allow users to specify a registry credential for an image at the first class API. Here is the link

Re: [mesos-mail] Re: Welcome Greg Mann as a new committer and PMC member!

Congrats, Greg! On Wed, Jun 14, 2017 at 11:46 AM, Sam wrote: > Congrats, well deserved > > > Regards, > Sam Chen | APJ Country Director | DC/OS Evangelist > > [image: Watch the Video] > >

Re: Quarterly Doc-a-thon Scheduling

This is great! Thank you for scheduling the docathon, Judith! BTW, do you mean January 2nd Tuesday or January 4th Thursday (asking since I might be on a flight on the 2nd January)? Cheers, Gilbert On Mon, Nov 20, 2017 at 11:00 AM, Vinod Kone wrote: > SGTM! > > On Mon,

Re: Quarterly Doc-a-thon Scheduling

t; > Cheers, > Judith > > -- > Get the Boomerang Email App <http://boomerangapp.com/mobile> on your phone > > > ------ > On Mon, Nov 20, 2017 at 6:17 PM, Gilbert Song <gilb...@apache.org> wrote: >

Mesos 1.5.0 Release

Folks, It is time for Mesos 1.5.0 release. I am the release manager. We plan to cut the rc1 in next couple weeks. Please start to wrap up patches if you are contributing or shepherding any issue. If you expect any particular JIRA for this new release, please set *Target Version* as " *1.5.0"*

[VOTE] Release Apache Mesos 1.5.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.5.1. 1.5.1 includes the following: * [MESOS-1720] - Slave should send exited executor message when the executor is never launched. *

[RESULT][VOTE] Release Apache Mesos 1.5.1 (rc1)

Hi all, The vote for Mesos 1.5.1 (rc1) has passed with the following votes. +1 (Binding) -- *** Greg Mann *** Jie Yu *** Ben Mahler There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.5.1 It is recommended to

Re: Questions about Pods and the Mesos Containerizer

> > >- > >Is it possible to allocate a separate IP address per container in a >pod? > > Right now nested containers share the network from their parent container (pod). Do we have a specific use case that we need containers inside of a taskgroup have different IP addresses? - Gilbert

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

owse/MESOS-8481 > On Wed, Jan 24, 2018 at 10:34 AM James Peach <jor...@gmail.com> wrote: > > > +1 > > > > Verified on CentOS 6 and Fedora 27 > > > > > On Jan 22, 2018, at 7:15 PM, Gilbert Song <gilb...@apache.org> wrote: > > > > > >

Re: This Month in Mesos - January 2018

Awesome, Greg! On Tue, Jan 30, 2018 at 10:34 AM, Vinod Kone wrote: > Thanks Greg for the update! > > > *Medium Posts* >> Going forward, we'll be cross-posting Apache Mesos blog posts on Medium to >> increase exposure, get feedback on engagement, and make it easier to >>

[VOTE] Release Apache Mesos 1.5.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.5.0. 1.5.0 includes the following: * Support Container Storage Interface (CSI). * Agent reconfiguration policy. * Auto GC docker

[RESULT][VOTE] Release Apache Mesos 1.5.0 (rc2)

Hi all, The vote for Mesos 1.5.0 (rc2) has passed with the following votes. +1 (Binding) -- Jie Yu Vinod Kone James Peach Andrew Schwartzmeyer +1 (Non-binding) -- Zhitao Li Chun-Hung Hsiao There were no 0 or -1 votes. Please find the

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

8 at 8:18 AM, Gilbert Song <gilb...@apache.org> wrote: > Hi all, > > The vote for Mesos 1.5.0 (rc2) has passed with the > following votes. > > +1 (Binding) > -- > Jie Yu > Vinod Kone > James Peach

Re: Backport Policy

Thanks for clarifying the backporting policy, BenM! I totally agree with the changes proposed for the backporting policy, but I realize two more scenarios that are more clear to me yet: - There are some bugs that are not fixable (due to legacy technical decisions), and we end up with

New Image Distribution Protocol and HDFS Image Fetching Design

Hi folks, Here is the design doc for HDFS Image Fetching . It includes a custom protocol (Mesos Image Distribution Protocol

[VOTE] Release Apache Mesos 1.5.0 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.5.0. 1.5.0 includes the following: * Support Container Storage Interface (CSI). * Agent reconfiguration policy. * Auto GC docker

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

Congrats, Chun! It is great to have you in the community! - Gilbert On Sun, Mar 11, 2018 at 4:40 PM, Andrew Schwartzmeyer < and...@schwartzmeyer.com> wrote: > Congratulations Chun! > > I apologize for not also giving you a +1, as I certainly would have, but > just discovered my mailing list

Welcome Zhitao Li as Mesos Committer and PMC Member

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 active contributor to Mesos for one and a half years. His main contributions include: - Designed and

[Containerization WG] Sync Agenda for April 5th, 2018

Hi folks, Tomorrow's WG meeting starts at 9 am PST. The agenda: - Volume Ownership use case update. - Mesos 1.6.0 will be cut around the end of April, let’s review our goals for 1.6 and update the spreadsheet. - Update the *Minimum Linux Kernel version* supported on Mesos to 2.6.28

Re: [mesos-mail] Re: Update the *Minimum Linux Kernel version* supported on Mesos

Hi all, FYI we landed this patch to avoid nested freezer cgroup support check for old kernel versions. Please reply to this thread if you had concerns about this update. - Gilbert On Sun, Apr 8, 2018 at 12:18 AM, Alex Rukletsov wrote:

Re: Questions about secret handling in Mesos

IIUC, your assumptions are all correct. @Kapil, could you please confirm? Maybe we could improve the document at the next Docathon. Gilbert On Thu, Apr 19, 2018 at 10:57 AM, Zhitao Li wrote: > Hello, > > We at Uber plan to use volume/secret isolator to send secrets from

Mesos 1.5.1 Release

Folks, I will be the release manager for Mesos 1.5.1 Release. Here is the JIRA filter created for this release: https://issues.apache.org/jira/issues/?filter=12343539 Please add the *JIRA target version as *1.5.1** and *mark it as *blocker** if you have any issue that you need in 1.5.1, and

Re: This Month in Mesos - March 2018

Thanks for the awesome update, Greg! - Gilbert On Fri, Mar 30, 2018 at 6:20 PM, Vinod Kone wrote: > Thanks for the update Greg! > > Sent from my phone > > > On Mar 30, 2018, at 3:08 PM, Greg Mann wrote: > > > > Oh hai there Apache Mesos Community! > >

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

Folks, We are planning for a WG meeting tomorrow at 9 am PST. Please add any agenda item or topic that you like to discuss with the Containerization WG to the following list: https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit#heading=h.j7quoqe53vwr Thanks,

Re: Communicate with a container while using Mesos unified container runtime

Hi Karan, Before figuring out some ways to achieve this with Mesos, I would like to better understand your use cases. Do you mean you rely on `docker attach/exec` to send commands to an existing running container? Is there any reason that keeps you from launching a container for each batch job?

Re: Communicate with a container while using Mesos unified container runtime

.11/monitoring/debugging/task-exec/> to do that given you have the taskId. Gilbert On Wed, Mar 21, 2018 at 12:08 PM, Karan Pradhan <karanprad...@gmail.com> wrote: > > > On 2018/03/21 18:06:48, Gilbert Song <gilb...@apache.org> wrote: > > Hi Karan, > > >

Re: Communicate with a container while using Mesos unified container runtime

> > On 2018/03/22 23:16:06, Gilbert Song <gilb...@apache.org> wrote: > > Hi Karan, > > > > It does not seem to me that launching more mesos containers would add > more > > overheads. > > > > If you want to achieve *docker exec* for debugging p

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

Seems like there is no agenda item for tomorrow's WG meeting. We will cancel it at this time. On Wed, Mar 21, 2018 at 10:30 AM, Gilbert Song <gilb...@apache.org> wrote: > Folks, > > We are planning for a WG meeting tomorrow at 9 am PST. > > Please add any agenda item o

Re: Tasks may be explicitly dropped by agent in Mesos 1.5

Meng, Could you double check if this is really an issue in Mesos 1.5.0 release? MESOS-1720 was resolved after the 1.5 release (rc-2) and it seems like it is only at the master branch and 1.5.x branch (not 1.5.0). Did I miss anything? - Gilbert

Re: Propose to update the minimal supported Docker version in Mesos to Docker 1.8.0

We are considering to backport this fix to Mesos 1.6.x, 1.5.x and 1.4.x, which means starting from 1.4.x your minimum docker version will be bumped to Docker 1.8.0 (an old docker daemon version). Please reply on this thread if this is a breaking change for you. Thank you! - Gilbert On Fri, Sep

[VOTE] Release Apache Mesos 1.5.2 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.5.2. 1.5.2 includes the following: * [MESOS-3790] - ZooKeeper connection should retry on `EAI_NONAME`. * [MESOS-8128] - Make os::pipe

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

^~~ >>> ../../src/slave/http.cpp:3196:10: note: in instantiation of function >>> template specialization >>> 'process::Future::Future>> process::Future > >' requested here >>> return slave->containerizer->attach(containerId) >>

Re: Welcome Meng Zhu as PMC member and committer!

Well deserved, Meng! On Wed, Oct 31, 2018 at 2:36 PM Benjamin Mahler wrote: > Please join me in welcoming Meng Zhu as a PMC member and committer! > > Meng has been active in the project for almost a year and has been very > productive and collaborative. He is now one of the few people of >

[VOTE] Release Apache Mesos 1.5.2 (rc2)

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 here* * [MESOS-3790] - ZooKeeper connection should retry on

Re: mesos containerizer issue with v1.8.0: HTTP response Decoding failed

Hi Olivier and Adam, This issue is already fixed by https://issues.apache.org/jira/browse/MESOS-8907 which was merged and backported 17 days ago. Please try it out and let me know. More background contexts: 1. http-parse does not support http/2:

Re: Propose to run debug container as the same user of its parent container by default

@James Peach agree, for debug containers, the default user should inherit from parent, while CLI toolings (e.g., task exec) should provide an option `--root` (by setting the commandinfo user as root). @Qian Zhang @Benjamin Mahler , if we step back, it seems to me we should extend the user

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

+1 (binding). All tests passed except 5 failures (known flakiness) from our internal CI: FLAG=CMake,label=mesos-ec2-centos-7 mesos-ec2-centos-7-CMake.Mesos.CgroupsIsolatorTest.ROOT_CGROUPS_CFS_EnableCfs FLAG=SSL,label=mesos-ec2-centos-7 mesos-ec2-centos-7-SSL.MESOS_TESTS_ABORTED.xml.[empty]

[VOTE] Release Apache Mesos 1.5.2 (rc3)

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 here* https://jira.apache.org/jira/issues/?filter=12345443 The

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

ubuntu-us1)&&(!ubuntu-eu2)/ > > > > cmake > > [image: Success] > > < > https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/58/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(

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

gt; make check on Ubuntu 18.04 > > > > On Wed, Oct 31, 2018 at 4:26 PM Gilbert Song > > wrote: > > > > > Hi all, > > > > > > Please vote on releasing the fo

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

+1 (binding). On Thu, Feb 21, 2019 at 2:18 PM Gastón Kleiman wrote: > +1 > > Ran it through Mesosphere's internal CI. Only 7 test failures were > observed, all known flakes. > > On Fri, Feb 15, 2019 at 11:49 AM Vinod Kone wrote: > >> +1 (binding) >> >> Tested on ASF CI. Red builds are known

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

+1 (binding). On Wed, Feb 20, 2019 at 5:42 PM Meng Zhu wrote: > +1 -- ran on centos 7.4 with only known flaky tests > > -Meng > > On Wed, Feb 20, 2019 at 4:57 PM Gastón Kleiman > wrote: > >> +1 (binding) — ran the build through Mesosphere's internal CI and only >> two known flaky tests failed.

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

+1 (binding). On Fri, Feb 22, 2019 at 9:43 AM Meng Zhu wrote: > +1, ran through out internal CI, only flaky failures > > On Thu, Feb 21, 2019 at 11:41 AM Greg Mann wrote: > > > +1 > > > > Built on CentOS 7.4 and ran all tests as root. Only 3 test failures were > > observed, all known flakes. >

[RESULT][VOTE] Release Apache Mesos 1.5.3 (rc1)

Hi all, The vote for Mesos 1.5.3 (rc1) has passed with the following votes. +1 (Binding) -- Vinod Kone Greg Mann Gilbert Song Chun-Hung Hsiao +1 (Non-binding) -- Meng Zhu There were no 0 or -1 votes. Please find the release at: https

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

-1 Sorry, given the fact that this is very likely to be the last point release for Mesos 1.4, there are some security improvement patches that are very useful for users but not included in this RC. I would down vote it for another cut, which could include more improvements from 1.4.x branch.

[RESULT][VOTE] Release Apache Mesos 1.5.2 (rc3)

Hi all, The vote for Mesos 1.5.2 (rc3) has passed with the following votes. +1 (Binding) -- Jie Yu Vinod Kone Chun-Hung Hsiao Gilbert Song There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.5.2

Re: Subject: [VOTE] Release Apache Mesos 1.8.0 (rc1)

-1 for rc1. I would like to have MESOS-9704 (backported to 1.8.x branch) in for 1.8.0, otherwise it could be a regression for some conner cases. -Gilbert On Tue, Apr 16, 2019 at 8:40 AM Benno Evers wrote: > You're right, I forgot to make a

Re: Provisioning containers with configuration file via sandbox mount or copy via entrypoint.sh

It depends on how do you want to manage the configuration files for your containers - dynamic or static. - Dynamic - Fetch via URI - you probably do not need your application entrypoint to fetch. Instead Mesos and marathon supports fetching URIs to your container sandbox.

Re: Is chained cni networks supported in mesos 1.7

Are you interested in implementing the CNI chain support? -Gilbert On Wed, Jul 24, 2019 at 12:52 PM Marc Roos wrote: > > Hmm, I guess I should not get my hopes up this will be there soon? > [0] > https://issues.apache.org/jira/browse/MESOS-7178 > > > > -Original Message- > From: Jie Yu

Re: [mesos-mail] Cant get sandbox_path to work

Are you using Marathon? The Mesos SANDBOX_PATH volume was supported by Marathon as the pod's ephemeral volume. Please note that Mesos framework API is different from Marathon API and refer to Marathon documentation if necessary. -Gilbert On Sat, Jul 20, 2019 at 5:25 PM Marc Roos wrote: > >

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

+1 (binding). Tested on our internal CI. Green on most of the platforms: Configuration Matrix Plain SSL CMake Clang BUILD_ISOLATORS mac [image: Not run] [image: Success] [image: Not run] [image: