Re: Newbie to Mesos contributors

[haosdent]

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

Please Add me to the mesos dev maillist , thanks very much!

-- 
Best Regards,
Chen, Qiang

Re: MESOS-3777: Looking for a shepherd

[Vinod Kone]

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: Replace Master/Slave Terminology Phase I - Modify public
> interfaces 
>
> Thanks
>

Delete the /observe HTTP endpoint

[Qian Zhang]

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

[Gilbert Song]

@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 the container)? If
it is an
absolute path, we require that dir to be pre-existed. If it is a relative
path, we will
mkdir for it.

@Joshua,
Thank for posting your workaround on mesos. As I mentioned above, in 0.28.1
or
older, we only mkdir for container_path which is relative path (not
starting with "/").
Because if no rootfs specified for a mesos container, the container shares
the host
root filesystem. Obviously we don't want any random files to be created
implicitly
on your host fs.
>From mesos 0.29 (release by the end of this month), we will mkdir the mount
point in the container except for the command task case that specify an
absolute
container_path without a rootfs. Because we simplify the mounting logic, and
sandbox bind mount will only be done in container mount namespace instead of
host mount namespace (what we did before). Please keep tuned.

Cheers,
Gilbert

On Wed, May 18, 2016 at 8:14 AM, Joshua Cohen  wrote:

> 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 (e.g. in Dockerfile, add `RUN mkdir -p
> /some/mount/point`). Not the best solution, but the only thing I've seen
> that works at the moment.
>
> Cheers,
>
> Joshua
>
> On Wed, May 18, 2016 at 7:36 AM, Guangya Liu  wrote:
>
> > 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:
> > > > 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
> > > recompile/install mesos  :-(  (I used packages for install).
> > >
> > > I will try when possible, but thanks for the hint.
> > > >
> > > > Thanks,
> > > >
> > > > Guangya
> > > >
> > > > On Wed, May 18, 2016 at 8:28 PM, Guangya Liu 
> > wrote:
> > > >
> > > >> 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.
> > > >>
> > > >> Also you can patch mesos-execute here
> > > https://reviews.apache.org/r/46762/ to
> > > >> have a try with mesos-execute.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Guangya
> > > >>
> > > >> On Wed, May 18, 2016 at 7:17 PM, Olivier Sallou <
> > > olivier.sal...@irisa.fr>
> > > >> wrote:
> > > >>
> > > >>> 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, using Docker images, the path I want to
> > mount
> > > >>> does not exists, and it cannot be modified "on the fly".
> > > >>>
> > > >>> Is there a workaround for this ?
> > > >>>
> > > >>>
> > > >>> On 05/18/2016 12:24 PM, Olivier Sallou wrote:
> > >  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 \
> > >  isolation=filesystem/linux,docker/runtime
> > > 
> > >  However, when I execute my task with a volume I have an error:
> > > 
> > >  
> > >  + mount -n --rbind
> > > 
> > > >>>
> > >
> >
> /tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
> > > >>>
> > >
> >
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
> > >  + mount -n 

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

[frankscholten]

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

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/104.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #104


commit 4fbe309be6b17f65cb2ad7c0dde0967ed3643b72
Author: Frank Scholten 
Date:   2016-05-18T12:21:49Z

Suppressed boost auto_ptr compile warnings.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Michael Park]

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

Community Meeting

*When*
Thu May 19, 2016 3pm – 4pm Pacific Time

*Calendar*
Apache Mesos

*Who*
•
Michael Park - creator
•
dev@mesos.apache.org
*Attachments*
Mesos Developer Community Sync


Invitation from Google Calendar 

You are receiving this email at the account mcyp...@gmail.com because you
set a notification for this event on the calendar Apache Mesos.

You can change your notifications for specific events in the event details
page in https://www.google.com/calendar/.

Forwarding this invitation could allow any recipient to modify your RSVP
response. Learn More
.

Newbie to Mesos contributors

[Qiang Chen]

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

[Joshua Cohen]

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 (e.g. in Dockerfile, add `RUN mkdir -p
/some/mount/point`). Not the best solution, but the only thing I've seen
that works at the moment.

Cheers,

Joshua

On Wed, May 18, 2016 at 7:36 AM, Guangya Liu  wrote:

> 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:
> > > 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
> > recompile/install mesos  :-(  (I used packages for install).
> >
> > I will try when possible, but thanks for the hint.
> > >
> > > Thanks,
> > >
> > > Guangya
> > >
> > > On Wed, May 18, 2016 at 8:28 PM, Guangya Liu 
> wrote:
> > >
> > >> 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.
> > >>
> > >> Also you can patch mesos-execute here
> > https://reviews.apache.org/r/46762/ to
> > >> have a try with mesos-execute.
> > >>
> > >> Thanks,
> > >>
> > >> Guangya
> > >>
> > >> On Wed, May 18, 2016 at 7:17 PM, Olivier Sallou <
> > olivier.sal...@irisa.fr>
> > >> wrote:
> > >>
> > >>> 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, using Docker images, the path I want to
> mount
> > >>> does not exists, and it cannot be modified "on the fly".
> > >>>
> > >>> Is there a workaround for this ?
> > >>>
> > >>>
> > >>> On 05/18/2016 12:24 PM, Olivier Sallou wrote:
> >  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 \
> >  isolation=filesystem/linux,docker/runtime
> > 
> >  However, when I execute my task with a volume I have an error:
> > 
> >  
> >  + mount -n --rbind
> > 
> > >>>
> >
> /tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
> > >>>
> >
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
> >  + mount -n --rbind
> > 
> > >>>
> >
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
> > >>>
> >
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
> >  mount: mount point
> > 
> > >>>
> >
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
> >  does not exist
> >  Failed to execute a preparation shell command
> > 
> >  Then, my task switches to FAILED.
> > 
> >  I define a local volume to bind mount in my "container"
> > 
> > >>>
> >
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
> >  => /mnt/god-data
> >  My directory exists on local server.
> >  In mesos UI, I can see the .rootfs directory along stdout and stderr
> >  files, and inside .rootfs, I can see /mnt/god-data (empty).
> > 
> >  Running the same using Docker containerizer instead of mesos
> >  containerizer (with a Docker image) works fine.
> > 
> >  It seems it fails to mount my local directory in the container. Any
> > idea
> >  of what is going wrong or how to debug this?
> > 
> > 
> >  Thanks
> > 
> > >>> --
> > >>> Olivier Sallou
> > >>> IRISA / 

Re: CMake and CLion

[Frank Scholten]

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
> 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 work, though, should compile just fine. Judging from the
> `CMakeLists.txt` that should be creating the `libmesos.so` library and its
> dependencies but no agent yet.
>
> On Wed, May 18, 2016 at 1:21 PM, Frank Scholten 
> wrote:
>
>> 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
>>
>> $ make mesos-agent
>>
>> Also if I first run
>>
>> $ make mesos-0.29.0
>>
>> I get a lot of undefined references errors.
>>
>>
>> On Wed, May 18, 2016 at 11:42 AM, haosdent  wrote:
>> > 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 Wed, May 18, 2016 at 4:58 PM, Frank Scholten 
>> > wrote:
>> >
>> >> 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
>> >>
>> >
>> >
>> >
>> > --
>> > Best Regards,
>> > Haosdent Huang
>>
>
>
>
> --
> *Jan Schlicht*
> Distributed Systems Engineer, Mesosphere

Re: CMake and CLion

[Jan Schlicht]

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 work, though, should compile just fine. Judging from the
`CMakeLists.txt` that should be creating the `libmesos.so` library and its
dependencies but no agent yet.

On Wed, May 18, 2016 at 1:21 PM, Frank Scholten 
wrote:

> 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
>
> $ make mesos-agent
>
> Also if I first run
>
> $ make mesos-0.29.0
>
> I get a lot of undefined references errors.
>
>
> On Wed, May 18, 2016 at 11:42 AM, haosdent  wrote:
> > 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 Wed, May 18, 2016 at 4:58 PM, Frank Scholten 
> > wrote:
> >
> >> 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
> >>
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
>



-- 
*Jan Schlicht*
Distributed Systems Engineer, Mesosphere

Re: volume / mount point error with Unified Containerizer

[Guangya Liu]

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:
> > 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
> recompile/install mesos  :-(  (I used packages for install).
>
> I will try when possible, but thanks for the hint.
> >
> > Thanks,
> >
> > Guangya
> >
> > On Wed, May 18, 2016 at 8:28 PM, Guangya Liu  wrote:
> >
> >> 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.
> >>
> >> Also you can patch mesos-execute here
> https://reviews.apache.org/r/46762/ to
> >> have a try with mesos-execute.
> >>
> >> Thanks,
> >>
> >> Guangya
> >>
> >> On Wed, May 18, 2016 at 7:17 PM, Olivier Sallou <
> olivier.sal...@irisa.fr>
> >> wrote:
> >>
> >>> 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, using Docker images, the path I want to mount
> >>> does not exists, and it cannot be modified "on the fly".
> >>>
> >>> Is there a workaround for this ?
> >>>
> >>>
> >>> On 05/18/2016 12:24 PM, Olivier Sallou wrote:
>  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 \
>  isolation=filesystem/linux,docker/runtime
> 
>  However, when I execute my task with a volume I have an error:
> 
>  
>  + mount -n --rbind
> 
> >>>
> /tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
> >>>
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
>  + mount -n --rbind
> 
> >>>
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
> >>>
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
>  mount: mount point
> 
> >>>
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
>  does not exist
>  Failed to execute a preparation shell command
> 
>  Then, my task switches to FAILED.
> 
>  I define a local volume to bind mount in my "container"
> 
> >>>
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
>  => /mnt/god-data
>  My directory exists on local server.
>  In mesos UI, I can see the .rootfs directory along stdout and stderr
>  files, and inside .rootfs, I can see /mnt/god-data (empty).
> 
>  Running the same using Docker containerizer instead of mesos
>  containerizer (with a Docker image) works fine.
> 
>  It seems it fails to mount my local directory in the container. Any
> idea
>  of what is going wrong or how to debug this?
> 
> 
>  Thanks
> 
> >>> --
> >>> Olivier Sallou
> >>> IRISA / University of Rennes 1
> >>> Campus de Beaulieu, 35000 RENNES - FRANCE
> >>> Tel: 02.99.84.71.95
> >>>
> >>> gpg key id: 4096R/326D8438  (keyring.debian.org)
> >>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
> >>>
> >>>
>
> --
> Olivier Sallou
> IRISA / University of Rennes 1
> Campus de Beaulieu, 35000 RENNES - FRANCE
> Tel: 02.99.84.71.95
>
> gpg key id: 4096R/326D8438  (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>
>

Re: volume / mount point error with Unified Containerizer

[Olivier Sallou]

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
recompile/install mesos  :-(  (I used packages for install).

I will try when possible, but thanks for the hint.
>
> Thanks,
>
> Guangya
>
> On Wed, May 18, 2016 at 8:28 PM, Guangya Liu  wrote:
>
>> 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.
>>
>> Also you can patch mesos-execute here https://reviews.apache.org/r/46762/ to
>> have a try with mesos-execute.
>>
>> Thanks,
>>
>> Guangya
>>
>> On Wed, May 18, 2016 at 7:17 PM, Olivier Sallou 
>> wrote:
>>
>>> 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, using Docker images, the path I want to mount
>>> does not exists, and it cannot be modified "on the fly".
>>>
>>> Is there a workaround for this ?
>>>
>>>
>>> On 05/18/2016 12:24 PM, Olivier Sallou wrote:
 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 \
 isolation=filesystem/linux,docker/runtime

 However, when I execute my task with a volume I have an error:

 
 + mount -n --rbind

>>> /tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
>>> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
 + mount -n --rbind

>>> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
>>> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
 mount: mount point

>>> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
 does not exist
 Failed to execute a preparation shell command

 Then, my task switches to FAILED.

 I define a local volume to bind mount in my "container"

>>> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
 => /mnt/god-data
 My directory exists on local server.
 In mesos UI, I can see the .rootfs directory along stdout and stderr
 files, and inside .rootfs, I can see /mnt/god-data (empty).

 Running the same using Docker containerizer instead of mesos
 containerizer (with a Docker image) works fine.

 It seems it fails to mount my local directory in the container. Any idea
 of what is going wrong or how to debug this?


 Thanks

>>> --
>>> Olivier Sallou
>>> IRISA / University of Rennes 1
>>> Campus de Beaulieu, 35000 RENNES - FRANCE
>>> Tel: 02.99.84.71.95
>>>
>>> gpg key id: 4096R/326D8438  (keyring.debian.org)
>>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>>>
>>>

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Re: volume / mount point error with Unified Containerizer

[Guangya Liu]

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 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.
>
> Also you can patch mesos-execute here https://reviews.apache.org/r/46762/ to
> have a try with mesos-execute.
>
> Thanks,
>
> Guangya
>
> On Wed, May 18, 2016 at 7:17 PM, Olivier Sallou 
> wrote:
>
>> 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, using Docker images, the path I want to mount
>> does not exists, and it cannot be modified "on the fly".
>>
>> Is there a workaround for this ?
>>
>>
>> On 05/18/2016 12:24 PM, Olivier Sallou wrote:
>> > 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 \
>> > isolation=filesystem/linux,docker/runtime
>> >
>> > However, when I execute my task with a volume I have an error:
>> >
>> > 
>> > + mount -n --rbind
>> >
>> /tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
>> >
>> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
>> > + mount -n --rbind
>> >
>> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
>> >
>> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
>> > mount: mount point
>> >
>> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
>> > does not exist
>> > Failed to execute a preparation shell command
>> >
>> > Then, my task switches to FAILED.
>> >
>> > I define a local volume to bind mount in my "container"
>> >
>> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
>> > => /mnt/god-data
>> > My directory exists on local server.
>> > In mesos UI, I can see the .rootfs directory along stdout and stderr
>> > files, and inside .rootfs, I can see /mnt/god-data (empty).
>> >
>> > Running the same using Docker containerizer instead of mesos
>> > containerizer (with a Docker image) works fine.
>> >
>> > It seems it fails to mount my local directory in the container. Any idea
>> > of what is going wrong or how to debug this?
>> >
>> >
>> > Thanks
>> >
>>
>> --
>> Olivier Sallou
>> IRISA / University of Rennes 1
>> Campus de Beaulieu, 35000 RENNES - FRANCE
>> Tel: 02.99.84.71.95
>>
>> gpg key id: 4096R/326D8438  (keyring.debian.org)
>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>>
>>
>

Re: volume / mount point error with Unified Containerizer

[Guangya Liu]

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.

Also you can patch mesos-execute here https://reviews.apache.org/r/46762/ to
have a try with mesos-execute.

Thanks,

Guangya

On Wed, May 18, 2016 at 7:17 PM, Olivier Sallou 
wrote:

> 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, using Docker images, the path I want to mount
> does not exists, and it cannot be modified "on the fly".
>
> Is there a workaround for this ?
>
>
> On 05/18/2016 12:24 PM, Olivier Sallou wrote:
> > 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 \
> > isolation=filesystem/linux,docker/runtime
> >
> > However, when I execute my task with a volume I have an error:
> >
> > 
> > + mount -n --rbind
> >
> /tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
> >
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
> > + mount -n --rbind
> >
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
> >
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
> > mount: mount point
> >
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
> > does not exist
> > Failed to execute a preparation shell command
> >
> > Then, my task switches to FAILED.
> >
> > I define a local volume to bind mount in my "container"
> >
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
> > => /mnt/god-data
> > My directory exists on local server.
> > In mesos UI, I can see the .rootfs directory along stdout and stderr
> > files, and inside .rootfs, I can see /mnt/god-data (empty).
> >
> > Running the same using Docker containerizer instead of mesos
> > containerizer (with a Docker image) works fine.
> >
> > It seems it fails to mount my local directory in the container. Any idea
> > of what is going wrong or how to debug this?
> >
> >
> > Thanks
> >
>
> --
> Olivier Sallou
> IRISA / University of Rennes 1
> Campus de Beaulieu, 35000 RENNES - FRANCE
> Tel: 02.99.84.71.95
>
> gpg key id: 4096R/326D8438  (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>
>

Re: CMake and CLion

[Frank Scholten]

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

$ make mesos-agent

Also if I first run

$ make mesos-0.29.0

I get a lot of undefined references errors.


On Wed, May 18, 2016 at 11:42 AM, haosdent  wrote:
> 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 Wed, May 18, 2016 at 4:58 PM, Frank Scholten 
> wrote:
>
>> 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
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang

Re: volume / mount point error with Unified Containerizer

[Olivier Sallou]

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, using Docker images, the path I want to mount
does not exists, and it cannot be modified "on the fly".

Is there a workaround for this ?


On 05/18/2016 12:24 PM, Olivier Sallou wrote:
> 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 \
> isolation=filesystem/linux,docker/runtime
>
> However, when I execute my task with a volume I have an error:
>
> 
> + mount -n --rbind
> /tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
> + mount -n --rbind
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
> mount: mount point
> /tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
> does not exist
> Failed to execute a preparation shell command
>
> Then, my task switches to FAILED.
>
> I define a local volume to bind mount in my "container"
> /home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
> => /mnt/god-data
> My directory exists on local server.
> In mesos UI, I can see the .rootfs directory along stdout and stderr
> files, and inside .rootfs, I can see /mnt/god-data (empty).
>
> Running the same using Docker containerizer instead of mesos
> containerizer (with a Docker image) works fine.
>
> It seems it fails to mount my local directory in the container. Any idea
> of what is going wrong or how to debug this?
>
>
> Thanks
>

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Re: mesos git commit: Updated quota endpoint help.

[Alex Rukletsov]

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 improvement already).

On Wed, May 18, 2016 at 11:53 AM, Benjamin Bannier <
benjamin.bann...@mesosphere.io> wrote:

> 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
> outputs is useful, but believe the fundamentally right thing to do would be
> to generate the markdown outputs as part of the build and *not check them
> into source control*. If one would need to reference the endpoint help one
> could e.g., use links to
> https://mesos.apache.org/documentation/latest/endpoints/ and children.
>
> Any reason this isn’t what we are already doing?
>
>
> Cheers,
>
> Benjamin
>
>
> > On May 18, 2016, at 11:42 AM, haosdent  wrote:
> >
> > Is it possible to show a warning in `./support/mesos-style.py` when
> commit
> > changes contains "src/master/http.cpp" or "src/slave/http.cpp" while
> > doesn't contain document changes?
> >
> > On Wed, May 18, 2016 at 5:06 PM, Neil Conway 
> wrote:
> >
> >> 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,   wrote:
> >>> Repository: mesos
> >>> Updated Branches:
> >>>  refs/heads/master a7835f889 -> 9f63d95f3
> >>>
> >>>
> >>> Updated quota endpoint help.
> >>>
> >>>
> >>> Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> >>> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/9f63d95f
> >>> Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/9f63d95f
> >>> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/9f63d95f
> >>>
> >>> Branch: refs/heads/master
> >>> Commit: 9f63d95f3cac17c94a7aff57980478263c78f6ee
> >>> Parents: a7835f8
> >>> Author: Adam B 
> >>> Authored: Wed May 18 01:56:57 2016 -0700
> >>> Committer: Adam B 
> >>> Committed: Wed May 18 01:57:52 2016 -0700
> >>>
> >>> --
> >>> src/master/http.cpp | 11 ---
> >>> 1 file changed, 8 insertions(+), 3 deletions(-)
> >>> --
> >>>
> >>>
> >>>
> >>
> http://git-wip-us.apache.org/repos/asf/mesos/blob/9f63d95f/src/master/http.cpp
> >>> --
> >>> diff --git a/src/master/http.cpp b/src/master/http.cpp
> >>> index c4ca343..5d73a1d 100644
> >>> --- a/src/master/http.cpp
> >>> +++ b/src/master/http.cpp
> >>> @@ -1286,15 +1286,20 @@ string Master::Http::QUOTA_HELP()
> >>> {
> >>>   return HELP(
> >>> TLDR(
> >>> -"Sets quota for a role."),
> >>> +"Gets or updates quota for roles."),
> >>> DESCRIPTION(
> >>> -"Returns 200 OK when the quota has been changed
> successfully.",
> >>> +"Returns 200 OK when the quota was queried or updated
> >> successfully.",
> >>> "Returns 307 TEMPORARY_REDIRECT redirect to the leading master
> >> when",
> >>> "current master is not the leader.",
> >>> "Returns 503 SERVICE_UNAVAILABLE if the leading master cannot
> >> be",
> >>> "found.",
> >>> +"GET: Returns the currently set quotas as JSON.",
> >>> +"",
> >>> "POST: Validates the request body as JSON",
> >>> -" and sets quota for a role."),
> >>> +" and sets quota for a role.",
> >>> +"",
> >>> +"DELETE: Validates the request body as JSON",
> >>> +" and removes quota for a role."),
> >>> AUTHENTICATION(true),
> >>> AUTHORIZATION(
> >>> "Using this endpoint to set a quota for a certain role requires
> >> that",
> >>>
> >>
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
>
>

volume / mount point error with Unified Containerizer

[Olivier Sallou]

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 \
isolation=filesystem/linux,docker/runtime

However, when I execute my task with a volume I have an error:


+ mount -n --rbind
/tmp/mesos/provisioner/containers/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/backends/copy/rootfses/f9f66bb2-308d-4555-ba77-49ec61cbeb4f
/tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs
+ mount -n --rbind
/home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
/tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
mount: mount point
/tmp/mesos/slaves/2a296daf-7419-4659-ade1-763c792cd522-S0/frameworks/aef1b0e3-ea2d-4770-baac-96d673ab88f9-/executors/51/runs/2d7ea311-5e8b-440f-a3ca-a40e1b946b8e/.rootfs/mnt/god-data
does not exist
Failed to execute a preparation shell command

Then, my task switches to FAILED.

I define a local volume to bind mount in my "container"
/home/osallou/Development/NOSAVE/go-docker/godshared/tasks/pairtree_root/us/er/_o/sa/ll/ou/task
=> /mnt/god-data
My directory exists on local server.
In mesos UI, I can see the .rootfs directory along stdout and stderr
files, and inside .rootfs, I can see /mnt/god-data (empty).

Running the same using Docker containerizer instead of mesos
containerizer (with a Docker image) works fine.

It seems it fails to mount my local directory in the container. Any idea
of what is going wrong or how to debug this?


Thanks

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Re: Mesos Calico CNI

[haosdent]

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

--network_cni_plugins_dir is used for find execute files. Suppose you
define your network in --network_cni_config_dir like

```
{
  "type": "foo",
  ...
  "ipam": {
"type: "bar",
  }
  ...
}
```

After Mesos finish parsing the network definition file under
--network_cni_config_dir, it would try find the execute file "foo" and
"bar" under
--network_cni_plugins_dir. Because the type of network you defined above is
"foo", and the type of "ipam" is "bar".

Just my quick reply, you could wait for Qian Zhang or Avinash's detail
reply later.


On Wed, May 18, 2016 at 4:40 PM, Frank Scholten 
wrote:

> 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 does not exist. This is ok because I have
> not created the network yet.
>
> 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?
>
>
> On Tue, May 17, 2016 at 5:16 PM, Avinash Sridharan
>  wrote:
> > Hi Frank,
> >  I am in the process of putting up the documentation for CNI support in
> > Mesos. You can find the RB patch for the documentation here:
> > https://reviews.apache.org/r/47463/
> >
> > You can find a rendering of the markdown on my github over here:
> > https://github.com/asridharan/mesos/blob/MESOS-4771/docs/cni.md
> >
> >
> > I have put up one example of using the `network/cni` isolator with a
> > "bridge" plugin. Working on adding some more examples, but given that
> > people have already started showing some interest thought would be a good
> > dry run for the documentation if someone could test out the instructions.
> >
> > Would be great if you can try following the instructions and leave any
> > feedback on the review board.
> >
> >
> > Thanks,
> > Avinash
> >
> > On Tue, May 17, 2016 at 6:51 AM, Frank Scholten 
> > wrote:
> >
> >> In the meantime I am looking at an alternative route trying to figure
> >> out how an ipAddress value on a Marathon app get propagated into Mesos
> >> CNI.
> >>
> >> Marathon reads the ipAddress value from the AppDefinition and then
> >> publishes on the eventbus. I don't see what happens to it from that
> >> point.
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Tue, May 17, 2016 at 2:58 PM, Jay JN Guo 
> wrote:
> >> > - net::links() -> stout/net.hpp
> >> > - Personally, I'm not very familiar with CLion build. Maybe somebody
> else
> >> > could answer that.
> >> > - I think this is very much related to dev mailing list, so +dev
> >> >
> >> > /J
> >> >
> >> > Frank Scholten  wrote on 05/17/2016 20:47:12:
> >> >
> >> >> From: Frank Scholten 
> >> >> To: u...@mesos.apache.org
> >> >> Cc: Qian AZ Zhang/China/IBM@IBMCN, avin...@mesosphere.io
> >> >> Date: 05/17/2016 20:48
> >> >> Subject: Re: Mesos Calico CNI
> >> >>
> >> >> Thanks. I now like to run that unit test via the debugger from the
> >> >> Mesos source try in CLion. Is there a doc on how to build Mesos in
> >> >> CLion and debug a unit test?
> >> >>
> >> >> Also, where does net::links() come from? Can't find it in the
> sources.
> >> >>
> >> >>
> >> >> On Tue, May 17, 2016 at 11:00 AM, haosdent 
> wrote:
> >> >> >>Is there some user documentation for this feature?
> >> >> > Unfortunately, the document is not ready.
> >> >> > https://issues.apache.org/jira/browse/MESOS-4771
> >> >> >
> >> >> >>but I am not sure what I have to do to create an IP for a task.
> >> >> > Qian Zhang show an example of configuration in his test cases, I
> think
> >> > you
> >> >> > may take a look first.
> >> >> > https://reviews.apache.org/r/46097/diff/7#index_header
> >> >> >
> >> >> > On Tue, May 17, 2016 at 4:20 PM, Frank Scholten
> >> > 
> >> >> > wrote:
> >> >> >>
> >> >> >> Hi all,
> >> >> >>
> >> >> >> I tried out CNI support with Calico but I am not sure what I have
> to
> >> >> >> do to create an IP for a task.
> >> >> >>
> >> >> >> See this sandbox repository on Github
> >> >> >>
> >> >> >> https://github.com/ContainerSolutions/mesos-calico-cni-sandbox
> >> >> >>
> >> >> >> In this repo I build the Mesos master branch and
> >> >> >> https://github.com/projectcalico/calico-cni, create a local
> cluster
> >> >> >> and deploy an application. I don't see anything in the logs about
> >> cni,
> >> >> >> except that it loads the cni isolator.
> >> >> >>
> 

Re: mesos git commit: Updated quota endpoint help.

[Benjamin Bannier]

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 outputs 
is useful, but believe the fundamentally right thing to do would be to generate 
the markdown outputs as part of the build and *not check them into source 
control*. If one would need to reference the endpoint help one could e.g., use 
links to https://mesos.apache.org/documentation/latest/endpoints/ and children.

Any reason this isn’t what we are already doing?


Cheers,

Benjamin


> On May 18, 2016, at 11:42 AM, haosdent  wrote:
> 
> Is it possible to show a warning in `./support/mesos-style.py` when commit
> changes contains "src/master/http.cpp" or "src/slave/http.cpp" while
> doesn't contain document changes?
> 
> On Wed, May 18, 2016 at 5:06 PM, Neil Conway  wrote:
> 
>> 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,   wrote:
>>> Repository: mesos
>>> Updated Branches:
>>>  refs/heads/master a7835f889 -> 9f63d95f3
>>> 
>>> 
>>> Updated quota endpoint help.
>>> 
>>> 
>>> Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
>>> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/9f63d95f
>>> Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/9f63d95f
>>> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/9f63d95f
>>> 
>>> Branch: refs/heads/master
>>> Commit: 9f63d95f3cac17c94a7aff57980478263c78f6ee
>>> Parents: a7835f8
>>> Author: Adam B 
>>> Authored: Wed May 18 01:56:57 2016 -0700
>>> Committer: Adam B 
>>> Committed: Wed May 18 01:57:52 2016 -0700
>>> 
>>> --
>>> src/master/http.cpp | 11 ---
>>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>> --
>>> 
>>> 
>>> 
>> http://git-wip-us.apache.org/repos/asf/mesos/blob/9f63d95f/src/master/http.cpp
>>> --
>>> diff --git a/src/master/http.cpp b/src/master/http.cpp
>>> index c4ca343..5d73a1d 100644
>>> --- a/src/master/http.cpp
>>> +++ b/src/master/http.cpp
>>> @@ -1286,15 +1286,20 @@ string Master::Http::QUOTA_HELP()
>>> {
>>>   return HELP(
>>> TLDR(
>>> -"Sets quota for a role."),
>>> +"Gets or updates quota for roles."),
>>> DESCRIPTION(
>>> -"Returns 200 OK when the quota has been changed successfully.",
>>> +"Returns 200 OK when the quota was queried or updated
>> successfully.",
>>> "Returns 307 TEMPORARY_REDIRECT redirect to the leading master
>> when",
>>> "current master is not the leader.",
>>> "Returns 503 SERVICE_UNAVAILABLE if the leading master cannot
>> be",
>>> "found.",
>>> +"GET: Returns the currently set quotas as JSON.",
>>> +"",
>>> "POST: Validates the request body as JSON",
>>> -" and sets quota for a role."),
>>> +" and sets quota for a role.",
>>> +"",
>>> +"DELETE: Validates the request body as JSON",
>>> +" and removes quota for a role."),
>>> AUTHENTICATION(true),
>>> AUTHORIZATION(
>>> "Using this endpoint to set a quota for a certain role requires
>> that",
>>> 
>> 
> 
> 
> 
> -- 
> Best Regards,
> Haosdent Huang

Re: CMake and CLion

[haosdent]

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 Wed, May 18, 2016 at 4:58 PM, Frank Scholten 
wrote:

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



-- 
Best Regards,
Haosdent Huang

Re: Mesos admin REST API

[haosdent]

>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 *does*
> exist already:
>
> https://mesos.apache.org/documentation/latest/scheduler-http-api/
>
> We don't do any authentication stuff in our Mesos system though.
>
> - Erik
>
> On Wed, May 18, 2016 at 1:47 AM, Guangya Liu  wrote:
>
> > 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 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 admin, to send a kill request (or other kind of
> > > requests), "by passing" the framework.
> > >
> > > Thanks
> > >
> > > Olivier
> > >
> > > --
> > > Olivier Sallou
> > > IRISA / University of Rennes 1
> > > Campus de Beaulieu, 35000 RENNES - FRANCE
> > > Tel: 02.99.84.71.95
> > >
> > > gpg key id: 4096R/326D8438  (keyring.debian.org)
> > > Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
> > >
> > >
> >
>



-- 
Best Regards,
Haosdent Huang

Re: Mesos admin REST API

[Erik Weathers]

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.

- Erik

On Wed, May 18, 2016 at 1:47 AM, Guangya Liu  wrote:

> 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 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 admin, to send a kill request (or other kind of
> > requests), "by passing" the framework.
> >
> > Thanks
> >
> > Olivier
> >
> > --
> > Olivier Sallou
> > IRISA / University of Rennes 1
> > Campus de Beaulieu, 35000 RENNES - FRANCE
> > Tel: 02.99.84.71.95
> >
> > gpg key id: 4096R/326D8438  (keyring.debian.org)
> > Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
> >
> >
>

Re: mesos git commit: Updated quota endpoint help.

[Neil Conway]

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,   wrote:
> Repository: mesos
> Updated Branches:
>   refs/heads/master a7835f889 -> 9f63d95f3
>
>
> Updated quota endpoint help.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/9f63d95f
> Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/9f63d95f
> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/9f63d95f
>
> Branch: refs/heads/master
> Commit: 9f63d95f3cac17c94a7aff57980478263c78f6ee
> Parents: a7835f8
> Author: Adam B 
> Authored: Wed May 18 01:56:57 2016 -0700
> Committer: Adam B 
> Committed: Wed May 18 01:57:52 2016 -0700
>
> --
>  src/master/http.cpp | 11 ---
>  1 file changed, 8 insertions(+), 3 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/mesos/blob/9f63d95f/src/master/http.cpp
> --
> diff --git a/src/master/http.cpp b/src/master/http.cpp
> index c4ca343..5d73a1d 100644
> --- a/src/master/http.cpp
> +++ b/src/master/http.cpp
> @@ -1286,15 +1286,20 @@ string Master::Http::QUOTA_HELP()
>  {
>return HELP(
>  TLDR(
> -"Sets quota for a role."),
> +"Gets or updates quota for roles."),
>  DESCRIPTION(
> -"Returns 200 OK when the quota has been changed successfully.",
> +"Returns 200 OK when the quota was queried or updated successfully.",
>  "Returns 307 TEMPORARY_REDIRECT redirect to the leading master when",
>  "current master is not the leader.",
>  "Returns 503 SERVICE_UNAVAILABLE if the leading master cannot be",
>  "found.",
> +"GET: Returns the currently set quotas as JSON.",
> +"",
>  "POST: Validates the request body as JSON",
> -" and sets quota for a role."),
> +" and sets quota for a role.",
> +"",
> +"DELETE: Validates the request body as JSON",
> +" and removes quota for a role."),
>  AUTHENTICATION(true),
>  AUTHORIZATION(
>  "Using this endpoint to set a quota for a certain role requires 
> that",
>

CMake and CLion

[Frank Scholten]

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

[Guangya Liu]

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 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 admin, to send a kill request (or other kind of
> requests), "by passing" the framework.
>
> Thanks
>
> Olivier
>
> --
> Olivier Sallou
> IRISA / University of Rennes 1
> Campus de Beaulieu, 35000 RENNES - FRANCE
> Tel: 02.99.84.71.95
>
> gpg key id: 4096R/326D8438  (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>
>

Re: Mesos Calico CNI

[Frank Scholten]

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
> 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 does not exist. This is ok because I have
> not created the network yet.
>
> 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?
>
>
> On Tue, May 17, 2016 at 5:16 PM, Avinash Sridharan
>  wrote:
>> Hi Frank,
>>  I am in the process of putting up the documentation for CNI support in
>> Mesos. You can find the RB patch for the documentation here:
>> https://reviews.apache.org/r/47463/
>>
>> You can find a rendering of the markdown on my github over here:
>> https://github.com/asridharan/mesos/blob/MESOS-4771/docs/cni.md
>>
>>
>> I have put up one example of using the `network/cni` isolator with a
>> "bridge" plugin. Working on adding some more examples, but given that
>> people have already started showing some interest thought would be a good
>> dry run for the documentation if someone could test out the instructions.
>>
>> Would be great if you can try following the instructions and leave any
>> feedback on the review board.
>>
>>
>> Thanks,
>> Avinash
>>
>> On Tue, May 17, 2016 at 6:51 AM, Frank Scholten 
>> wrote:
>>
>>> In the meantime I am looking at an alternative route trying to figure
>>> out how an ipAddress value on a Marathon app get propagated into Mesos
>>> CNI.
>>>
>>> Marathon reads the ipAddress value from the AppDefinition and then
>>> publishes on the eventbus. I don't see what happens to it from that
>>> point.
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, May 17, 2016 at 2:58 PM, Jay JN Guo  wrote:
>>> > - net::links() -> stout/net.hpp
>>> > - Personally, I'm not very familiar with CLion build. Maybe somebody else
>>> > could answer that.
>>> > - I think this is very much related to dev mailing list, so +dev
>>> >
>>> > /J
>>> >
>>> > Frank Scholten  wrote on 05/17/2016 20:47:12:
>>> >
>>> >> From: Frank Scholten 
>>> >> To: u...@mesos.apache.org
>>> >> Cc: Qian AZ Zhang/China/IBM@IBMCN, avin...@mesosphere.io
>>> >> Date: 05/17/2016 20:48
>>> >> Subject: Re: Mesos Calico CNI
>>> >>
>>> >> Thanks. I now like to run that unit test via the debugger from the
>>> >> Mesos source try in CLion. Is there a doc on how to build Mesos in
>>> >> CLion and debug a unit test?
>>> >>
>>> >> Also, where does net::links() come from? Can't find it in the sources.
>>> >>
>>> >>
>>> >> On Tue, May 17, 2016 at 11:00 AM, haosdent  wrote:
>>> >> >>Is there some user documentation for this feature?
>>> >> > Unfortunately, the document is not ready.
>>> >> > https://issues.apache.org/jira/browse/MESOS-4771
>>> >> >
>>> >> >>but I am not sure what I have to do to create an IP for a task.
>>> >> > Qian Zhang show an example of configuration in his test cases, I think
>>> > you
>>> >> > may take a look first.
>>> >> > https://reviews.apache.org/r/46097/diff/7#index_header
>>> >> >
>>> >> > On Tue, May 17, 2016 at 4:20 PM, Frank Scholten
>>> > 
>>> >> > wrote:
>>> >> >>
>>> >> >> Hi all,
>>> >> >>
>>> >> >> I tried out CNI support with Calico but I am not sure what I have to
>>> >> >> do to create an IP for a task.
>>> >> >>
>>> >> >> See this sandbox repository on Github
>>> >> >>
>>> >> >> https://github.com/ContainerSolutions/mesos-calico-cni-sandbox
>>> >> >>
>>> >> >> In this repo I build the Mesos master branch and
>>> >> >> https://github.com/projectcalico/calico-cni, create a local cluster
>>> >> >> and deploy an application. I don't see anything in the logs about
>>> cni,
>>> >> >> except that it loads the cni isolator.
>>> >> >>
>>> >> >> Is there some user documentation for this feature? If not I am happy
>>> >> >> to write documentation once I figure out how this feature works.
>>> >> >>
>>> >> >> Cheers,
>>> >> >>
>>> >> >> Frank
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Best Regards,
>>> >> > Haosdent Huang
>>> >>
>>>
>>
>>
>>
>> --
>> Avinash Sridharan, Mesosphere
>> +1 (323) 702 5245

Re: Mesos Calico CNI

[Frank Scholten]

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 is based
> on the net-modules repo (even though CNI doesn’t have much to do with
> netmdoules) only because it already had a pretty slick docker demo set up.
> Here’s the branch: https://github.com/djosborne/net-modules/tree/cni
>
> I’d be happy to assist you in getting it working on your repo.  Let me know
> if you need any assistance.
>
> We haven't published much information on this as of yet, since Mesos CNI
> support is only just rolling out now.
>
> -Dan
>
> On Tue, May 17, 2016 at 8:16 AM, Avinash Sridharan 
> wrote:
>
>> Hi Frank,
>>  I am in the process of putting up the documentation for CNI support in
>> Mesos. You can find the RB patch for the documentation here:
>> https://reviews.apache.org/r/47463/
>>
>> You can find a rendering of the markdown on my github over here:
>> https://github.com/asridharan/mesos/blob/MESOS-4771/docs/cni.md
>>
>>
>> I have put up one example of using the `network/cni` isolator with a
>> "bridge" plugin. Working on adding some more examples, but given that
>> people have already started showing some interest thought would be a good
>> dry run for the documentation if someone could test out the instructions.
>>
>> Would be great if you can try following the instructions and leave any
>> feedback on the review board.
>>
>>
>> Thanks,
>> Avinash
>>
>> On Tue, May 17, 2016 at 6:51 AM, Frank Scholten 
>> wrote:
>>
>>> In the meantime I am looking at an alternative route trying to figure
>>> out how an ipAddress value on a Marathon app get propagated into Mesos
>>> CNI.
>>>
>>> Marathon reads the ipAddress value from the AppDefinition and then
>>> publishes on the eventbus. I don't see what happens to it from that
>>> point.
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, May 17, 2016 at 2:58 PM, Jay JN Guo 
>>> wrote:
>>> > - net::links() -> stout/net.hpp
>>> > - Personally, I'm not very familiar with CLion build. Maybe somebody
>>> else
>>> > could answer that.
>>> > - I think this is very much related to dev mailing list, so +dev
>>> >
>>> > /J
>>> >
>>> > Frank Scholten  wrote on 05/17/2016 20:47:12:
>>> >
>>> >> From: Frank Scholten 
>>> >> To: u...@mesos.apache.org
>>> >> Cc: Qian AZ Zhang/China/IBM@IBMCN, avin...@mesosphere.io
>>> >> Date: 05/17/2016 20:48
>>> >> Subject: Re: Mesos Calico CNI
>>> >>
>>> >> Thanks. I now like to run that unit test via the debugger from the
>>> >> Mesos source try in CLion. Is there a doc on how to build Mesos in
>>> >> CLion and debug a unit test?
>>> >>
>>> >> Also, where does net::links() come from? Can't find it in the sources.
>>> >>
>>> >>
>>> >> On Tue, May 17, 2016 at 11:00 AM, haosdent  wrote:
>>> >> >>Is there some user documentation for this feature?
>>> >> > Unfortunately, the document is not ready.
>>> >> > https://issues.apache.org/jira/browse/MESOS-4771
>>> >> >
>>> >> >>but I am not sure what I have to do to create an IP for a task.
>>> >> > Qian Zhang show an example of configuration in his test cases, I
>>> think
>>> > you
>>> >> > may take a look first.
>>> >> > https://reviews.apache.org/r/46097/diff/7#index_header
>>> >> >
>>> >> > On Tue, May 17, 2016 at 4:20 PM, Frank Scholten
>>> > 
>>> >> > wrote:
>>> >> >>
>>> >> >> Hi all,
>>> >> >>
>>> >> >> I tried out CNI support with Calico but I am not sure what I have to
>>> >> >> do to create an IP for a task.
>>> >> >>
>>> >> >> See this sandbox repository on Github
>>> >> >>
>>> >> >> https://github.com/ContainerSolutions/mesos-calico-cni-sandbox
>>> >> >>
>>> >> >> In this repo I build the Mesos master branch and
>>> >> >> https://github.com/projectcalico/calico-cni, create a local cluster
>>> >> >> and deploy an application. I don't see anything in the logs about
>>> cni,
>>> >> >> except that it loads the cni isolator.
>>> >> >>
>>> >> >> Is there some user documentation for this feature? If not I am happy
>>> >> >> to write documentation once I figure out how this feature works.
>>> >> >>
>>> >> >> Cheers,
>>> >> >>
>>> >> >> Frank
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Best Regards,
>>> >> > Haosdent Huang
>>> >>
>>>
>>
>>
>>
>> --
>> Avinash Sridharan, Mesosphere
>> +1 (323) 702 5245
>>

Re: Mesos Calico CNI

[Frank Scholten]

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 does not exist. This is ok because I have
not created the network yet.

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?


On Tue, May 17, 2016 at 5:16 PM, Avinash Sridharan
 wrote:
> Hi Frank,
>  I am in the process of putting up the documentation for CNI support in
> Mesos. You can find the RB patch for the documentation here:
> https://reviews.apache.org/r/47463/
>
> You can find a rendering of the markdown on my github over here:
> https://github.com/asridharan/mesos/blob/MESOS-4771/docs/cni.md
>
>
> I have put up one example of using the `network/cni` isolator with a
> "bridge" plugin. Working on adding some more examples, but given that
> people have already started showing some interest thought would be a good
> dry run for the documentation if someone could test out the instructions.
>
> Would be great if you can try following the instructions and leave any
> feedback on the review board.
>
>
> Thanks,
> Avinash
>
> On Tue, May 17, 2016 at 6:51 AM, Frank Scholten 
> wrote:
>
>> In the meantime I am looking at an alternative route trying to figure
>> out how an ipAddress value on a Marathon app get propagated into Mesos
>> CNI.
>>
>> Marathon reads the ipAddress value from the AppDefinition and then
>> publishes on the eventbus. I don't see what happens to it from that
>> point.
>>
>>
>>
>>
>>
>>
>> On Tue, May 17, 2016 at 2:58 PM, Jay JN Guo  wrote:
>> > - net::links() -> stout/net.hpp
>> > - Personally, I'm not very familiar with CLion build. Maybe somebody else
>> > could answer that.
>> > - I think this is very much related to dev mailing list, so +dev
>> >
>> > /J
>> >
>> > Frank Scholten  wrote on 05/17/2016 20:47:12:
>> >
>> >> From: Frank Scholten 
>> >> To: u...@mesos.apache.org
>> >> Cc: Qian AZ Zhang/China/IBM@IBMCN, avin...@mesosphere.io
>> >> Date: 05/17/2016 20:48
>> >> Subject: Re: Mesos Calico CNI
>> >>
>> >> Thanks. I now like to run that unit test via the debugger from the
>> >> Mesos source try in CLion. Is there a doc on how to build Mesos in
>> >> CLion and debug a unit test?
>> >>
>> >> Also, where does net::links() come from? Can't find it in the sources.
>> >>
>> >>
>> >> On Tue, May 17, 2016 at 11:00 AM, haosdent  wrote:
>> >> >>Is there some user documentation for this feature?
>> >> > Unfortunately, the document is not ready.
>> >> > https://issues.apache.org/jira/browse/MESOS-4771
>> >> >
>> >> >>but I am not sure what I have to do to create an IP for a task.
>> >> > Qian Zhang show an example of configuration in his test cases, I think
>> > you
>> >> > may take a look first.
>> >> > https://reviews.apache.org/r/46097/diff/7#index_header
>> >> >
>> >> > On Tue, May 17, 2016 at 4:20 PM, Frank Scholten
>> > 
>> >> > wrote:
>> >> >>
>> >> >> Hi all,
>> >> >>
>> >> >> I tried out CNI support with Calico but I am not sure what I have to
>> >> >> do to create an IP for a task.
>> >> >>
>> >> >> See this sandbox repository on Github
>> >> >>
>> >> >> https://github.com/ContainerSolutions/mesos-calico-cni-sandbox
>> >> >>
>> >> >> In this repo I build the Mesos master branch and
>> >> >> https://github.com/projectcalico/calico-cni, create a local cluster
>> >> >> and deploy an application. I don't see anything in the logs about
>> cni,
>> >> >> except that it loads the cni isolator.
>> >> >>
>> >> >> Is there some user documentation for this feature? If not I am happy
>> >> >> to write documentation once I figure out how this feature works.
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Frank
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Best Regards,
>> >> > Haosdent Huang
>> >>
>>
>
>
>
> --
> Avinash Sridharan, Mesosphere
> +1 (323) 702 5245

Mesos admin REST API

[Olivier Sallou]

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 admin, to send a kill request (or other kind of
requests), "by passing" the framework.

Thanks

Olivier

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438