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: Isolator network/port_mapping in mesos 1.7

Marc, this is because it depends on a specific version of libnl3 which is not by default, available on some supported Linux distro. - Jie On Tue, Jul 30, 2019 at 7:28 AM Marc Roos wrote: > > Any specific reason why this is not compiled in? > > > -Original Message- > From: Marc Roos >

Re: Is chained cni networks supported in mesos 1.7

No, not yet On Wed, Jul 24, 2019 at 12:27 PM Marc Roos wrote: > > > > > > This error message of course > E0724 21:19:17.852210 1160 cni.cpp:330] Failed to parse CNI network > configuration file '/etc/mesos-cni/93-chain.conflist': Protobuf parse > failed: Missing required fields: typ > > >

Re: How should I pass the cni_args / ip, injecting lables #5592 not working

from scratch :) > > > > > -Original Message- > From: Jie Yu [mailto:yujie@gmail.com] > Sent: zaterdag 4 mei 2019 0:14 > To: user > Subject: Re: How should I pass the cni_args / ip, injecting lables #5592 > not working > > ah. I think one workaround I can think of is to w

Re: How should I pass the cni_args / ip, injecting lables #5592 not working

ah. I think one workaround I can think of is to write a wrapper CNI plugin that understand args."org.apache.mesos", and set "cni.ips" properly for the macvtap plugin. This is a common pattern in CNI called delegation before CNI chaining was proposed. - Jie On Fri, May 3, 2019 at 11:14 AM Marc

Re: How should I pass the cni_args / ip, injecting lables #5592 not working

"name": "test-macvtap-cniip" > } > } > }, > > > Yet the cni plugin is afaik not even looking at the > args.'org.apache.mesos'.network_info > configuration, for the cni_args it looks e.g. at args.cni.ips (or an > environment variable) > >

Re: FW: How should I pass the cni_args / ip, injecting lables #5592 not working

Marc, I think the CNI_ARGS that Mesos passed into CNI plugin is the NetworkInfo object. https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L3096 I don't know if there's a way in Marathon to inject NetworkInfo.labels from the app definition. Any marathon folks can answer this?

Re: Slack upgrade to Standard plan. Thanks Criteo

Thanks Criteo friends! On Tue, Apr 23, 2019 at 10:13 AM Vinod Kone wrote: > Hi folks, > > As you probably realized today, we got our Slack upgraded from "free" plan > to "standard" plan, which allows us to have unlimited message history and > better analytics among other things! This would be

Re: Container cannot write to volume? path created as nagios user???

nerPath": "data", > "persistent": { > "type": "root", > "size": 100 > }, > "mode": "RW" > } > ], > "docker": { > "image"

Re: Container cannot write to volume? path created as nagios user???

What user do you use to launch containers? We need more information to triage this. - Jie On Tue, Feb 12, 2019 at 11:44 AM Marc Roos wrote: > > > [@m03 foo]# ls -alrt > total 0 > drwxr-xr-x 3 root root 17 Dec 23 2017 .. > drwx-- 2 nagios root 6 Feb 12 20:32 >

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: mesos containerizer issue with v1.8.0: HTTP response Decoding failed

Olivier, are you sure you're talking to dockerhub directly? Is there a proxy in the middle? I think it's also likely that it's related to your curl version. I tested on today's master branch, using this marathon config (docker image is centos). It works for me. { "id": "/test", "instances":

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

[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: [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: 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. > > >

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

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: [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

Re: LIBPROCESS_IP

Hendrik, It looks to me that Mesos always pass LIBPROCESS_IP to executor if agent's LIBPROCESS_IP environment variable is set: https://github.com/apache/mesos/blob/1.4.x/src/slave/slave.cpp#L8106-L8115 Maybe that's the difference between your vanilla Mesos, and DC/OS Mesos config? - Jie On

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: Mesos on OS X

There's no isolation between containers on OSX. Process management is based on posix process tree (unlike cgroups on Linux), which has some limitations. If you're fine with the above, then it should work. - Jie On Wed, Mar 21, 2018 at 9:23 PM, Benjamin Mahler wrote: >

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: 2 Mesos Slaves in same machine

> utilized by accepting the same offer twice by the framework. > > 2. May I know the settings( cgroup ) required to run 2 slaves in the same > server and How does it behave? > > On Wed, Mar 7, 2018 at 10:03 PM, Jie Yu <yujie@gmail.com> wrote: > >> Running Doc

Re: 2 Mesos Slaves in same machine

omes unresponsive. Is running 2 > slaves are the main reason for this issue? > > On Wed, Mar 7, 2018 at 9:52 PM, Jie Yu <yujie@gmail.com> wrote: > >> It depends on your isolation setting (mainly cgroup, or any node level >> resources). In general, we don't recommen

Re: 2 Mesos Slaves in same machine

It depends on your isolation setting (mainly cgroup, or any node level resources). In general, we don't recommend folks use multiple agents on a node. It's possible to make it work by setting `cgroup_root` separately for MesosContainerizer. For DockerContainerizer, currently, we hard code

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: 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,

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: Questions about Pods and the Mesos Containerizer

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

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: Mesos replicated log fills disk with logging output

Stephan, I haven't seen that before. A quick Google search suggests that it might be related to leveldb. The following thread might be related. https://groups.google.com/d/msg/leveldb/lRrbv4Y0YgU/AtfRTfQXNoYJ What is the filesystem you're using? - JIe On Mon, Jan 8, 2018 at 2:28 PM, Stephan

Re: Container user '27' is not supported

em": 256, > "instances": 1, > "acceptedResourceRoles": ["*"], > "constraints": [["hostname", "CLUSTER", "m02.local"]], > "container": { > "type": "MESOS", > "

Re: Container user '27' is not supported

The 'user' specified in the image won't be honored. The current code will reject the container launch if the 'user' is specified in the image (although, i think we should print a warning if --switch_user flag is on because Mesos will always overwrite the user, similar to `docker run -u`, I'll send

Re: Cannot enable the isolator volume/host_path

What's your Mesos version? On Fri, Dec 22, 2017 at 4:09 PM, Marc Roos wrote: > > > Dec 23 01:04:33 m01 mesos-slave[10344]: E1223 01:04:33.213044 10344 > main.cpp:489] EXIT with status 1: Failed to create a containerizer: > Could not create MesosContainerizer: Failed to

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

er crash). > >> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yujie@gmail.com> wrote: >> >> 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. >

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: explain these replication logs?

Nov 8 00:12:37 host2091 aurora-scheduler[80146]: I1108 00:12:37.005336 80278 replica.cpp:710] Persisted action APPEND at position 67516183 Nov 8 00:00:32 host1162 aurora-scheduler[14638]: I1108 00:00:32.736395 14772 coordinator.cpp:348] Coordinator attempting to write APPEND action at position

Re: Dedicated ip to task

+ Avinash On Mon, Dec 11, 2017 at 2:21 PM, Marc Roos wrote: > > > In this https://youtu.be/0UMCoojACOs?t=1737 cni video of Avinash > Sridharan, he has a haproxy setup with two webservers on different > networks. But how does he know what these ip adresses will be, so

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! > >

Re: Is it possible to configure a mesos agent to use multiple work directories?

You can config multiple disks for persistent volumes. Please see this doc for more details: http://mesos.apache.org/documentation/latest/multiple-disk/ - Jie On Wed, Nov 22, 2017 at 1:57 PM, Jeff Kubina wrote: > Thanks, that is what I thought. > > Why: To spread the

Re: Directory mounted in job not visible on host

Tobias, By default, Mesos marks all mounts in a Mesos container as slave mount. Therefore, the mount propagation is from host to container, but not container to host. I am actually working on a patch chain to enable bidirectional mount propagation:

Re: Adding the limited resource to TaskStatus messages

+1 On Mon, Oct 9, 2017 at 10:56 AM, James Peach wrote: > Hi all, > > In https://reviews.apache.org/r/62644/, I am proposing to add an optional > Resources field to the TaskStatus message named `limited_resources`. > > In the case that a task is killed because it violated a

Re: Containerizers & Isolation

> > - When someone is using the Docker Containerizer what kind of isolation > can be used and how Mesos handles it? It's the default isolation that Docker engine provides. You can alter some of those using ContainerInfo.DockerInfo. - Custom isolators can be used both for Docker Containerizer

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: 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: 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

Welcome Gilbert Song as a new committer and PMC member!

Hi folks, I' happy to announce that the PMC has voted Gilbert Song as a new committer and member of PMC for the Apache Mesos project. Please join me to congratulate him! Gilbert has been working on Mesos project for 1.5 years now. His main contribution is his work on unified containerizer,

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

-1 I suggest we include this fix in 1.1.2 https://issues.apache.org/jira/browse/MESOS-7471 On Thu, May 4, 2017 at 12:07 PM, Alex Rukletsov wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.1.2. > > 1.1.2 includes the following: >

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

-1 I want to get this fix into 1.3.0 https://issues.apache.org/jira/browse/MESOS-7471 - Jie On Tue, May 9, 2017 at 1:14 AM, Yan Xu wrote: > We work around autotools and protobuf bugs and glibc is only harder for > users and developers to upgrade. :) > > I agree that we can

Re: [Req]Starting Japan User Group

Shingo, This is great! Can you send a pull request to update this doc? https://github.com/apache/mesos/blob/master/site/source/community/user-groups.html.md - Jie On Tue, May 9, 2017 at 9:50 AM, Kitayama, Shingo wrote: > > > Hi, owners of Mesos User Groups. > > > >

Re: Mesos fetcher error when running as non-root user

Graig, Thanks for reporting! I believe this might be related to MESOS-7208 , which is fixed in the 1.2.x branch. So 1.2.1 should have this issue resolved. Is there a way to test 1.2.x branch see if this problem still exists? - Jie On Wed, Apr

Re: Mesos installation problems

Zois, have you joined the Apache Mesos slack? (search Slack in the following link) http://mesos.apache.org/community/ You'll get a lot of help from there. - Jie On Mon, Apr 3, 2017 at 8:00 AM, Zois Theodoros wrote: > Hello, > > I am new to Mesos and i have many problems on

Re: Mesos (and Marathon) port mapping

Thomas, - it is the hostports which are used to multiplex traffic into container. > My understanding is that, since each container is in it's network > namespace, it has its own full range of container ports and that you use a > direct mapping (hostport n <-> same container port n), is that

Re: Mesos (and Marathon) port mapping

t; > network as per Docker (mapping of container port 80 to host port 3 for > example) > > Olivier > > > pt., 31 mar 2017 o 02:04 użytkownik Jie Yu <yujie@gmail.com> napisał: > >> are you talking about the NAT feature of docker in BRIDGE m >> >> >> Y

Re: Mesos (and Marathon) port mapping

orts in that case. You can find more details about port mapping isolator in this talk I gave in 2015 MesosCon: https://www.youtube.com/watch?v=ZA96g1M4v8Y - Jie On Thu, Mar 30, 2017 at 2:13 AM, Thomas HUMMEL <thomas.hum...@pasteur.fr> wrote: > > On 03/29/2017 07:25 PM, Jie Yu wrot

Re: mesos container cluster came across health check coredump log

+ AlexR, haosdent For posterity, the root cause of this problem is that when agent is running inside a docker container and `--docker_mesos_image` flag is specified, the pid namespace of the executor container (which initiate the health check) is different than the root pid namespace. Therefore,

Re: Mesos (and Marathon) port mapping

Thomas, I think you are confused about the port mapping for NAT purpose, and the port mapping isolator . Those two very different thing. The port mapping isolator (unfortunate naming), as described in the doc, gives you network

MesosCon Asia CFP deadline extended

Chinese version below/ 中文详情请见下文 In order to allow for more submissions, we have extended the CFP deadline for MesosCon Asia until April 5th 11:59pm PDT. http://events.linuxfoundation.org/events/mesoscon-asia/program/cfp None of the other submission dates have changed. Community voting on

Re: [Design Doc] Improve Storage Support in Mesos using Resources Provider

scendants of block devices. > > > On Sun, Mar 12, 2017 at 6:47 PM, Jie Yu <yujie@gmail.com> wrote: > > Hi, > > > > Currently, Mesos supports both local persistent volumes as well as > external > > persistent volumes. However, both of them are not ideal

Container Storage Interface (CSI)

Hi, Container Storage Interface (CSI) is a joint work between container orchestrators (Mesos, Kubernetes, Docker and Cloud Foundry) trying to standardize the interface between container orchestrator and storage platforms. The goal is to let

Re: mesos network/port_mapping + spark traffic not flowing between containers

Dominic, This might be related to this: https://issues.apache.org/jira/browse/MESOS-7130 - Jie On Sun, Mar 19, 2017 at 10:10 AM, Dominic Grégoire < dominic.grego...@gmail.com> wrote: > Hello all, > > I’m testing with mesos 1.1.0 on aws linux to see if it applies to some of > our processes and

[Design Doc] Improve Storage Support in Mesos using Resources Provider

Hi, Currently, Mesos supports both local persistent volumes as well as external persistent volumes. However, both of them are not ideal. Local persistent volumes do not support offering physical or logical block devices directly. Also, frameworks do not have choices to select filesystems for

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

-0 I wanna fix MESOS-7208 which affects all tasks that are launched as non-root using container image. But this is not a new regression because it exists in 1.1.0, thus I am a -0 - Jie On Fri, Mar 3, 2017 at 4:08 PM, Vinod Kone

Re: Welcome Neil Conway as Mesos Committer and PMC member!

Congrats! Neil! Well deserved! On Sun, Jan 22, 2017 at 6:56 PM, haosdent wrote: > Congrats Neil !! > > On Sun, Jan 22, 2017 at 3:29 AM, Gabriel Hartmann > wrote: > >> Congrats Neil. >> >> On Sat, Jan 21, 2017 at 7:08 AM Deepak Vij (A)

Re: Why task environment variables are set for executor/containerizer?

Daniel, Yes, this is a tech debt in the old command executor. The new default executor does not have this issue. - Jie On Wed, Jan 18, 2017 at 5:49 PM, Daniel Krawczyk wrote: > Hi, > > When I set an environment variable for my task it is as well applied both > to

Re: Why task environment variables are set for executor/containerizer?

Can you create a ticket for that? I personally want to fix that for command executor. - Jie On Wed, Jan 18, 2017 at 5:52 PM, Jie Yu <yujie@gmail.com> wrote: > Daniel, > > Yes, this is a tech debt in the old command executor. The new default > executor does not have thi

Re: customized IP for health check

also want the app treated as > they are deployed as the old way, which have a unique IP for each > container. > > This kind of app is not the only type that my framework support, with > BRIDGE driver supported too. > > On Wed, Jan 18, 2017 at 5:30 PM, Jie Yu <yujie@gmai

Re: customized IP for health check

so let the health check on the IP is the best option. > > > > To Jie Yu: > > by DEFAULT_DOMAIN I mean > > *static const string DEFAULT_DOMAIN = "127.0.0.1"* > > in source code src/health-check/health_checker.cpp > > On Wed, Jan 18, 2017 at 4:58 PM, Jie Yu

Re: customized IP for health check

meet my requirements as DEFAULT_DOMAIN is hard coded, now the > only option to be might be health check with COMMAND, but if TCP does > support passing IP would be great help. > > Thanks > > On Wed, Jan 18, 2017 at 4:40 PM, Jie Yu <yujie@gmail.com> wrote: > > Hi,

Re: customized IP for health check

Hi, can you elaborate a bit more on why you need to use an customized IP, rather than using localhost for health check? - Jie On Wed, Jan 18, 2017 at 9:19 AM, CmingXu wrote: > Is there any plan we support customized IP when define a health check? > If true, what's the ETA?

Re: Providing end-user feedback on Docker image download progress

Frank, Thanks for reaching out! I think this is definitely something we've thought about, just don't have the cycle to get it prioritized. https://issues.apache.org/jira/browse/MESOS-2256 The idea is around re-using STAGING state with more information about the progress of the provisioning (and

Re: Welcome Haosdent Huang as Mesos Committer and PMC member!

Congrats! Well deserved!! Always wondering why you have so much time! - Jie On Mon, Dec 19, 2016 at 5:19 PM, Jay Guo wrote: > Congratulations Haosdent!!! > > /J > > On Mon, Dec 19, 2016 at 4:40 PM, Chengwei Yang > wrote: > >

Welcome Guangya Liu as Mesos Committer and PMC member!

Hi folks, Please join me in formally welcoming Guangya Liu as Mesos Committer and PMC member. Guangya has worked on the project for more than a year now and has been a very active contributor to the project. I think one of the most important contribution he has for the community is that he

Re: Multi-agent machine

Charles, It should be possible. Here are the global 'object' that might conflict: 1) cgroup (you can use different cgroup root) 2) work_dir and runime_dir (you can set them to be different between agents) 3) network (e.g., iptables, if you use host network, should not be a problem. Otherwise, you

Re: Path vs Mount disk resources

> > The documentation states "non performance-critical applications" and > "should only be done in a testing or staging environment" about Path type > resources. Is there any particular reason for that? I think the documentation is not very precise. Path disk resource is the default disk

Re: Docker snadbox disk statistics

s some trick to turn it on. > > Thanks > Tomek > > czw., 3.11.2016 o 17:46 użytkownik Jie Yu <yujie@gmail.com> napisał: > >> posix/disk isolator is for MesosContaineizer only. If you're using docker >> containerizer, this won't work. >> >>

Re: Mesos containerizer & isolation

To add to haosdent's reply: - I have a USER directive in my Dockerfile in order for the CMD to be > executed as that user, but that does not seem to be supported (yet?) by the > Docker image provider. Is there any method (except `sudo`/`setuser`) to > achieve running as a user present in the

Re: Soft limit for docker tasks

You can try to use Mesos containerizer to launch your Docker containers https://github.com/apache/mesos/blob/master/docs/containerizer.md https://github.com/apache/mesos/blob/master/docs/container-image.md , and build a custom memory isolator to set the soft memory limit for your task. - Jie On

Unified cgroups isolator

Hi, We just merged the unified cgroups isolator. Huge shout out to @haosdent and @qianzhang to make this happen! https://issues.apache.org/jira/browse/MESOS-4697 Just to give you some context. Previously, it's a huge pain to add a new cgroups subsystem to Mesos because it requires creating a new

Re: Support for tasks groups aka pods in Mesos

Aaron, an important feature of kubernetes for us is the ability to share mount and > network namespaces between containers in the pod (so containers can share > mounts etc) yes, this will be supported in MVP. it's described in the design doc. - Jie On Thu, Aug 11, 2016 at 6:32 AM, Aaron Carey

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

iscuss the actual fix on the ticket, I feel that a short term fix shouldn't >> be more than a few lines to unblock the release. >> >>> On Jul 26, 2016, at 3:26 PM, Jie Yu <yujie@gmail.com> wrote: >>> >>> Yan, are you going to shepherd the f

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

+1 sudo make check on CentOS 6/7, Debian 8, Fedora 23, Ubuntu 12/14/15/16 - Jie On Tue, Jul 26, 2016 at 1:58 AM, haosdent wrote: > +1 > > * make check in CentOS 7.2 > * make check in Ubuntu 14.04 > * test upgrade from 0.28.2 to 1.0.0-rc4 > > > On Tue, Jul 26, 2016 at 8:33

Re: max_executors_per_agent does not take effect on mesos docker executor

Can you create a ticket on this? I think this might be a bug related to how we handle command tasks. - Jie On Thu, Jul 21, 2016 at 3:35 AM, Qi Feng wrote: > I build mesos-1.0.0-rc2 with network isolator. And try to set > max_executors_per_agent=10 > to test if docker

  1   2   >