Re: Newbie to Mesos contributors

Hi. Chen Qiang. You can do it by yourself. Please click the subscribe button on http://mesos.apache.org/community/ But I think you have already subscribed successfully because you could send emails to the dev mailing list. On May 19, 2016 6:51 AM, "Qiang Chen" wrote: Hi

Re: MESOS-3777: Looking for a shepherd

Hi Jose, I'm shepherding this epic. Given the complexity of MESOS-3777, I think it is best to move it to Phase 2. On Wed, May 18, 2016 at 8:00 PM, José Guilherme Vanz < guilherme@gmail.com> wrote: > Hi guys > > I'm looking for shepherd in the issue that is in the roadmap: > MESOS-3777:

Delete the /observe HTTP endpoint

Hi Folks, We are going to delete the master "/observe" HTTP endpoint in the JIRA ticket MESOS-5408 since this endpoint was introduced a long time ago for supporting functionality that was never implemented. Please let us know if you have any comments or concerns, thanks! Thanks, Qian Zhang

Re: volume / mount point error with Unified Containerizer

@Olivier, In mesos 0.28.1, you are supposed to be able bind mount a volume from the host into the mesos container. Did you specify a docker image (we determine the mount point differently depending whether the container has a rootfs)? How do you specify your 'container_path' (the mount point in

[GitHub] mesos pull request: MESOS-3932 Suppressed boost auto_ptr compile w...

GitHub user frankscholten opened a pull request: https://github.com/apache/mesos/pull/104 MESOS-3932 Suppressed boost auto_ptr compile warnings. You can merge this pull request into a Git repository by running: $ git pull https://github.com/frankscholten/mesos MESOS-3932

Fwd: Notification: Community Meeting @ Thu May 19, 2016 3pm - 4pm (Apache Mesos)

-- Forwarded message -- From: Google Calendar Date: 18 May 2016 at 15:00 Subject: Notification: Community Meeting @ Thu May 19, 2016 3pm - 4pm (Apache Mesos) To: Michael Park more details »

Newbie to Mesos contributors

Hi yujie, Please Add me to the mesos dev maillist , thanks very much! -- Best Regards, Chen, Qiang

Re: volume / mount point error with Unified Containerizer

Hi Olivier, I touched on this issue as part of https://issues.apache.org/jira/browse/MESOS-5229. It would be nice if Mesos automatically created container mount points if they don't already exist. In the meantime, as a workaround for this, I've updated my filesystem images to include the path

Re: CMake and CLion

Ok, thx. I pinged Alex on Twitter and I will ask him how I can help. On Wed, May 18, 2016 at 2:40 PM, Jan Schlicht wrote: > Alex Clemmer is probably the right person to talk to regarding tasks for > improving the CMake build. Most (probably all?) devs still use >

Re: CMake and CLion

Alex Clemmer is probably the right person to talk to regarding tasks for improving the CMake build. Most (probably all?) devs still use autoconf/automake for their every day work while MESOS-898 is still in progress. That would also explain why certain things don't work yet. The things that do

Re: volume / mount point error with Unified Containerizer

It's pretty simple for you from scratch with source code https://github.com/apache/mesos/blob/master/docs/getting-started.md#building-mesos ;-) Thanks, Guangya On Wed, May 18, 2016 at 8:30 PM, Olivier Sallou wrote: > > > On 05/18/2016 02:31 PM, Guangya Liu wrote: > >

Re: volume / mount point error with Unified Containerizer

On 05/18/2016 02:31 PM, Guangya Liu wrote: > Just saw that you are working with 0.28.1, the "docker volume driver" code > was not in 0.28.1, can you please have a try with mesos master branch if > you are only doing some test? this is indeed test only for the moment. But I will have to

Re: volume / mount point error with Unified Containerizer

Just saw that you are working with 0.28.1, the "docker volume driver" code was not in 0.28.1, can you please have a try with mesos master branch if you are only doing some test? Thanks, Guangya On Wed, May 18, 2016 at 8:28 PM, Guangya Liu wrote: > Hi Olivier, > > I think

Re: volume / mount point error with Unified Containerizer

Hi Olivier, I think that you need to enable "docker volume isolator" if you want use external storage with unified container I was writing a document here https://reviews.apache.org/r/47511/, perhaps you can have a try according to the document and post some comments there if you find any issues.

Re: CMake and CLion

How can I build the agent? I can't find an add_executable definition in the CMakeLists.txt I added this to src/CMakeLists.txt {code} # Agent executable ## add_executable(${AGENT_TARGET} ${AGENT_SRC}) {code} however it fails to build when I run

Re: volume / mount point error with Unified Containerizer

Answering (partially) to myself. I seems issue is container_path does not exists inside container. On Docker, path is created and mounted. With pure mesos, container_path must exists. mesos.proto says: "If the path is an absolute path, that path must already exist." This is an issue however,

Re: mesos git commit: Updated quota endpoint help.

Thanks Neil. Pushed 54339eb0e934e120e5cb5e693681679dea24b2d2. It also includes an update induced by slave->agent rename. I think we eventually should do what Benjamin suggests. It's hard for a human to remember, when a certain script should be run (even though having a script is a huge

volume / mount point error with Unified Containerizer

Hi, I am trying unified containerizer on a single server (master/slave) on mesos 0.28.1, to switch from docker containerizer to mesos+docker image container. I have setup slave config as suggested in documentation: containerizers=docker,mesos image_providers=docker \

Re: Mesos Calico CNI

>It's not yet clear to me what exactly I have to put in the directories pointed by --network_cni_config_dir and --network_cni_plugins_dir in order to create a network? According to my understanding from code, Mesos try to parse any files under --network_cni_config_dir except directories.

Re: mesos git commit: Updated quota endpoint help.

Hi, the way one currently has to manually regenerate markdown outputs which should then be checked in together (and ideally: atomically) with the corresponding source changes seems to be a reoccurring source of friction. I understand that being able to e.g., reference the generated markdown

Re: CMake and CLion

I think you could refer to Bplotka's repo: https://github.com/Bplotka/docker-mesos-clion Juan have a patch to show how build Mesos via CMake as well. https://reviews.apache.org/r/45668/ Noted that so far CMake only could build the Mesos Agent(Slave) component, don't include Mesos Master. On

Re: Mesos admin REST API

>kill tasks via the scheduler REST API Cool, a quick workaround. On Wed, May 18, 2016 at 5:12 PM, Erik Weathers < eweath...@groupon.com.invalid> wrote: > Maybe I'm misunderstanding the question, but I've used this mechanism to > kill tasks via the scheduler REST API, so from my perspective that

Re: Mesos admin REST API

Maybe I'm misunderstanding the question, but I've used this mechanism to kill tasks via the scheduler REST API, so from my perspective that *does* exist already: https://mesos.apache.org/documentation/latest/scheduler-http-api/ We don't do any authentication stuff in our Mesos system though. -

Re: mesos git commit: Updated quota endpoint help.

When modifying the endpoint help text, we should remember to update the generated help files (via support/generate-endpoint-help.py) -- the changes to both the input text and generated output files should be included as part of the same commit. Neil On Wed, May 18, 2016 at 10:58 AM,

CMake and CLion

Hi all, How can I help out with the CMake build of Mesos? This seems to be the epic related to it https://issues.apache.org/jira/browse/MESOS-898 Are there specific issues I can look at? I run Ubuntu 16.04 Cheers, Frank

Re: Mesos admin REST API

No, but there are some discussion and JIRA tracing this https://issues.apache.org/jira/browse/MESOS-3220 On Wed, May 18, 2016 at 4:08 PM, Olivier Sallou wrote: > Hi, > Is there any operator/admin admin to kill a task, via an admin API ? > > I faced issue where

Re: Mesos Calico CNI

Is there a separate cli for testing of checking the the network isolation config and plugin files without starting up an entire cluster? On Wed, May 18, 2016 at 10:40 AM, Frank Scholten wrote: > Hi Avinash, > > Thanks for your response. I am following the steps at >

Re: Mesos Calico CNI

Hi Daniel, Cool. I will have a look at your repository. If you can add a PR to my repo to demonstrate how it works I would really appreciate it. On Tue, May 17, 2016 at 5:57 PM, Daniel Osborne wrote: > Frank, > > I’ve done some work to get Calico-CNI working in Mesos. The work

Re: Mesos Calico CNI

Hi Avinash, Thanks for your response. I am following the steps at https://github.com/asridharan/mesos/blob/MESOS-4771/docs/cni.md and when I run the mesos-execute command on the cluster I started at https://github.com/ContainerSolutions/mesos-calico-cni-sandbox I get a message saying the network

Mesos admin REST API

Hi, Is there any operator/admin admin to kill a task, via an admin API ? I faced issue where mesos does not send any offer to my framework after a task failure (remains in staging, or can't contact an old framework. The result is my framework cannot send new kills etc.. I'd like, as a mesos