Mesos/Marathon support for Docker extension

[Khanduja, Vaibhav]

Recently docker pulled in code for supporting docker volume extensions.
The docker now (1.9 & above) through CLI can be specified volume plugin
name, which docker daemon connects get the actual storage. The plugin has
today reasonable hooks for maintaining and cleaning the storage. I was
wondering if there is any analysis done on the support of this in the
code? What I understand the slave code which calls in docker cli would
need this additional parameter to be passed into.

Thx

Re: Mesos/Marathon support for Docker extension

[Khanduja, Vaibhav]

Hi Shuai

>From the link below, I pulled out changes needed while invoking docker cli or 
>docker api. This documentation is quite comprehensive and should tell what 
>changes are needed.

https://github.com/docker/docker/pull/13161

……..

$ docker run -ti -v volumename:/data --volume-driver=flocker busy box sh

There is similar api change needed ..

..

Adding this plugin into Mesos would give all necessary storage extensions 
needed for Mesos/Marathon. Can we discuss to support this out?

Thanks


On 6/6/15, 7:51 PM, "Shuai Lin" 
mailto:linshuai2...@gmail.com>> wrote:

Hi Khanduja,

What I understand the slave code which calls in docker cli would need this
additional parameter to be passed into.


I don't think mesos slave invokes docker cli directly. It calls the docker
api instead.

Also Is there any official documentation/introduction to docker plugin or
volume extensions? I found the following two pages when googling, but non
of them has an official introduction to volume extension.

https://clusterhq.com/2014/12/08/docker-extensions/
https://github.com/docker/docker/pull/13161

Best Regards,
Shuai


On Sat, Jun 6, 2015 at 12:56 AM, Khanduja, Vaibhav 
mailto:vaibhav.khand...@emc.com>
wrote:

Recently docker pulled in code for supporting docker volume extensions.
The docker now (1.9 & above) through CLI can be specified volume plugin
name, which docker daemon connects get the actual storage. The plugin has
today reasonable hooks for maintaining and cleaning the storage. I was
wondering if there is any analysis done on the support of this in the
code? What I understand the slave code which calls in docker cli would
need this additional parameter to be passed into.

Thx

Re: Mesos/Marathon support for Docker extension

[Khanduja, Vaibhav]

Hi Tim

Are you referring to following pull request

https://github.com/mesosphere/marathon/pull/798

Thanks


On 6/6/15, 8:21 PM, "Timothy Chen"  wrote:

>Hi Khadijah/Shuai,
>
>Mesos slave actually does invoke the docker cli directly for its
>integration.
>
>To support various options that docker will be adding we allowed
>arbitrary flags to be passed when launching a docker task (Params field I
>believe).
>
>Therefore if you know you have latest docker installed you can pass the
>Extra volume option and it should work.
>
>Tim
>
>> On Jun 6, 2015, at 7:51 PM, Shuai Lin  wrote:
>> 
>> Hi Khanduja,
>> 
>> What I understand the slave code which calls in docker cli would need
>>this
>>> additional parameter to be passed into.
>> 
>> 
>> I don't think mesos slave invokes docker cli directly. It calls the
>>docker
>> api instead.
>> 
>> Also Is there any official documentation/introduction to docker plugin
>>or
>> volume extensions? I found the following two pages when googling, but
>>non
>> of them has an official introduction to volume extension.
>> 
>> https://clusterhq.com/2014/12/08/docker-extensions/
>> https://github.com/docker/docker/pull/13161
>> 
>> Best Regards,
>> Shuai
>> 
>> 
>> On Sat, Jun 6, 2015 at 12:56 AM, Khanduja, Vaibhav
>>>> wrote:
>> 
>>> Recently docker pulled in code for supporting docker volume extensions.
>>> The docker now (1.9 & above) through CLI can be specified volume plugin
>>> name, which docker daemon connects get the actual storage. The plugin
>>>has
>>> today reasonable hooks for maintaining and cleaning the storage. I was
>>> wondering if there is any analysis done on the support of this in the
>>> code? What I understand the slave code which calls in docker cli would
>>> need this additional parameter to be passed into.
>>> 
>>> Thx
>>> 
>>> 

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

[Khanduja, Vaibhav]

+ 1

Sent from my iPhone. Please excuse the typos and brevity of this message.

> On Jul 3, 2015, at 6:42 PM, Marco Massenzio  wrote:
> 
> +1
> 
> *Marco Massenzio*
> *Distributed Systems Engineer*
> 
>> On Fri, Jul 3, 2015 at 12:25 PM, Adam Bordelon  wrote:
>> 
>> Hello Mesos community,
>> 
>> Please vote on releasing the following candidate as Apache Mesos 0.23.0.
>> 
>> 0.23.0 includes the following:
>> 
>> 
>> - Per-container network isolation
>> - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
>> - Dockerized slaves will properly recover Docker containers upon failover.
>> 
>> as well as experimental support for:
>> - Fetcher Caching
>> - Revocable Resources
>> - SSL encryption
>> - Persistent Volumes
>> - Dynamic Reservations
>> 
>> The CHANGELOG for the release is available at:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.23.0-rc1
>> 
>> 
>> 
>> The candidate for Mesos 0.23.0 release is available at:
>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz
>> 
>> The tag to be voted on is 0.23.0-rc1:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc1
>> 
>> The MD5 checksum of the tarball can be found at:
>> 
>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz.md5
>> 
>> The signature of the tarball can be found at:
>> 
>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc1/mesos-0.23.0.tar.gz.asc
>> 
>> The PGP key used to sign the release is here:
>> https://dist.apache.org/repos/dist/release/mesos/KEYS
>> 
>> The JAR is up in Maven in a staging repository here:
>> https://repository.apache.org/content/repositories/orgapachemesos-1056
>> 
>> Please vote on releasing this package as Apache Mesos 0.23.0!
>> 
>> The vote is open until Fri July 10th, 12:00 PDT 2015 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Mesos 0.23.0
>> [ ] -1 Do not release this package because ...
>> 
>> Thanks,
>> -Adam-
>> 

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

[Khanduja, Vaibhav]

+1

On 7/8/15, 2:01 PM, "Adam Bordelon"  wrote:

>Hello Mesos community,
>
>Please vote on releasing the following candidate as Apache Mesos 0.23.0.
>
>0.23.0 includes the following:
>--
>--
>- Per-container network isolation
>- Dockerized slaves will properly recover Docker containers upon failover.
>- Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
>
>as well as experimental support for:
>- Fetcher Caching
>- Revocable Resources
>- SSL encryption
>- Persistent Volumes
>- Dynamic Reservations
>
>The CHANGELOG for the release is available at:
>https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGEL
>OG;hb=0.23.0-rc2
>--
>--
>
>The candidate for Mesos 0.23.0 release is available at:
>https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc2/mesos-0.23.0.tar.g
>z
>
>The tag to be voted on is 0.23.0-rc2:
>https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc2
>
>The MD5 checksum of the tarball can be found at:
>https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc2/mesos-0.23.0.tar.g
>z.md5
>
>The signature of the tarball can be found at:
>https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc2/mesos-0.23.0.tar.g
>z.asc
>
>The PGP key used to sign the release is here:
>https://dist.apache.org/repos/dist/release/mesos/KEYS
>
>The JAR is up in Maven in a staging repository here:
>https://repository.apache.org/content/repositories/orgapachemesos-1058
>
>Please vote on releasing this package as Apache Mesos 0.23.0!
>
>The vote is open until Wed July 15th, 14:00 PDT 2015 and passes if a
>majority of at least 3 +1 PMC votes are cast.
>
>[ ] +1 Release this package as Apache Mesos 0.23.0
>[ ] -1 Do not release this package because ...
>
>Thanks,
>-Adam-

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

[Khanduja, Vaibhav]

+1

Sent from my iPhone. Please excuse the typos and brevity of this message.

> On Jul 9, 2015, at 6:07 PM, Adam Bordelon  wrote:
> 
> Hello Mesos community,
> 
> Please vote on releasing the following candidate as Apache Mesos 0.23.0.
> 
> 0.23.0 includes the following:
> 
> - Per-container network isolation
> - Dockerized slaves will properly recover Docker containers upon failover.
> - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
> 
> as well as experimental support for:
> - Fetcher Caching
> - Revocable Resources
> - SSL encryption
> - Persistent Volumes
> - Dynamic Reservations
> 
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.23.0-rc3
> 
> 
> The candidate for Mesos 0.23.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc3/mesos-0.23.0.tar.gz
> 
> The tag to be voted on is 0.23.0-rc3:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc3
> 
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc3/mesos-0.23.0.tar.gz.md5
> 
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc3/mesos-0.23.0.tar.gz.asc
> 
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
> 
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1060
> 
> Please vote on releasing this package as Apache Mesos 0.23.0!
> 
> The vote is open until Thurs July 16th, 18:00 PDT 2015 and passes if a
> majority of at least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Mesos 0.23.0
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> -Adam-

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

[Khanduja, Vaibhav]

+1

Sent from my iPhone. Please excuse the typos and brevity of this message.

> On Jul 17, 2015, at 4:43 PM, Adam Bordelon  wrote:
> 
> Hello Mesos community,
> 
> Please vote on releasing the following candidate as Apache Mesos 0.23.0.
> 
> 0.23.0 includes the following:
> 
> - Per-container network isolation
> - Dockerized slaves will properly recover Docker containers upon failover.
> - Upgraded minimum required compilers to GCC 4.8+ or clang 3.5+.
> 
> as well as experimental support for:
> - Fetcher Caching
> - Revocable Resources
> - SSL encryption
> - Persistent Volumes
> - Dynamic Reservations
> 
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.23.0-rc4
> 
> 
> The candidate for Mesos 0.23.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc4/mesos-0.23.0.tar.gz
> 
> The tag to be voted on is 0.23.0-rc4:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc4
> 
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc4/mesos-0.23.0.tar.gz.md5
> 
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc4/mesos-0.23.0.tar.gz.asc
> 
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
> 
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1062
> 
> Please vote on releasing this package as Apache Mesos 0.23.0!
> 
> The vote is open until Wed July 22nd, 17:00 PDT 2015 and passes if a
> majority of at least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Mesos 0.23.0 (I've tested it!)
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> -Adam-

Docker socket path for slave

[Khanduja, Vaibhav]

Hi

I have a use-case where docker deamon does not run on original socket path 
which is /var/run/docker.sock but to a path as given by user.  I start my 
docker daemon with –H option,

docker –d –H unix:///var/run/mydocker.sock

all my docker calls now use this –H for e.g. to print images:

docker –H unix:///var/run/mydocker.sock images

I am using Marathon and have started my slave with Docker as container option.

I cannot see an option in slave, where I can specify the socket port for the it 
talk with Docker daemon. docker_socket option is used for specifying docker 
port mapping in the container slave.

Does this require code change in slave?

Thx

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hi 

jfyi,

I have tried parameter option in marathon json file Š

Š..
"parameters": {
"key": "H", "value": "unix:///var/run/mydocker.sock"
    }
Š.




On 7/30/15, 12:29 PM, "Khanduja, Vaibhav"  wrote:

>Hi
>
>I have a use-case where docker deamon does not run on original socket
>path which is /var/run/docker.sock but to a path as given by user.  I
>start my docker daemon with ­H option,
>
>docker ­d ­H unix:///var/run/mydocker.sock
>
>all my docker calls now use this ­H for e.g. to print images:
>
>docker ­H unix:///var/run/mydocker.sock images
>
>I am using Marathon and have started my slave with Docker as container
>option.
>
>I cannot see an option in slave, where I can specify the socket port for
>the it talk with Docker daemon. docker_socket option is used for
>specifying docker port mapping in the container slave.
>
>Does this require code change in slave?
>
>Thx

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hi

Having not received any answer, I support there is no solution for this.

The mesos slave process, along with accepting other docker arguments
should somehow manage to take these extra arguments too. I have logged
this as an enhancement, and wondering if somebody can look at this:

https://issues.apache.org/jira/browse/MESOS-3187

I am available to provide the fix, if somebody can be a help as sheperd.

Thx

On 7/30/15, 12:58 PM, "Khanduja, Vaibhav"  wrote:

>Hi 
>
>jfyi,
>
>I have tried parameter option in marathon json file Š
>
>Š..
>"parameters": {
>"key": "H", "value": "unix:///var/run/mydocker.sock"
>}
>Š.
>
>
>
>
>On 7/30/15, 12:29 PM, "Khanduja, Vaibhav" 
>wrote:
>
>>Hi
>>
>>I have a use-case where docker deamon does not run on original socket
>>path which is /var/run/docker.sock but to a path as given by user.  I
>>start my docker daemon with ­H option,
>>
>>docker ­d ­H unix:///var/run/mydocker.sock
>>
>>all my docker calls now use this ­H for e.g. to print images:
>>
>>docker ­H unix:///var/run/mydocker.sock images
>>
>>I am using Marathon and have started my slave with Docker as container
>>option.
>>
>>I cannot see an option in slave, where I can specify the socket port for
>>the it talk with Docker daemon. docker_socket option is used for
>>specifying docker port mapping in the container slave.
>>
>>Does this require code change in slave?
>>
>>Thx
>

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hi Peter,

Thanks for  your reply.

The change for docker daemon options is probably has to be in slave code
and not int the framework. Other than marathon, there could be other
framework requiring such support.

The slave during bootup checks for connection, by querying the version of
docker daemon. 

I have opened an issue, and plan to work on it:
https://issues.apache.org/jira/browse/MESOS-3187

I am not part of contributors list, so cannot assign to myself. Can
somebody do this for me? I made few changes to code to get this working.
The changes are now in a pull request:

https://github.com/apache/mesos/pull/53

I am aware of contribution requirements:
http://mesos.apache.org/documentation/latest/, and would work in creating
patch if I get the bug assigned.

— VK, 

Technologist, 
EMC OCTO

Thx

On 8/3/15, 6:39 AM, "Peter Kolloch"  wrote:

>Hi Vaibhav,
>
>the "parameters" option works for parameters of the docker run command:
>
>https://mesosphere.github.io/marathon/docs/native-docker.html#privileged-m
>ode-and-arbitrary-docker-options
>
>You tried to use it with a command line argument for the docker _daemon_.
>Starting the docker daemon with the right command line arguments is out of
>scope for Marathon.
>
>If you find a parameter of the "docker run" command that works for you,
>you
>need to specify the long name for this option (the none-one-letter option)
>in the "parameters" option.
>
>If you find the Marathon documentation lacking, we would love to get a PR
>for a documentation improvement from you!
>
>See
>
>https://mesosphere.github.io/marathon/docs/contributing.html
>
>for details.
>
>Best regards,
>Peter
>
>[BTW: The Marathon mailing list might be better suited for this kind of
>question.]
>
>On Sat, Aug 1, 2015 at 1:57 AM, Khanduja, Vaibhav
>
>wrote:
>
>> Hi
>>
>> Having not received any answer, I support there is no solution for this.
>>
>> The mesos slave process, along with accepting other docker arguments
>> should somehow manage to take these extra arguments too. I have logged
>> this as an enhancement, and wondering if somebody can look at this:
>>
>> https://issues.apache.org/jira/browse/MESOS-3187
>>
>> I am available to provide the fix, if somebody can be a help as sheperd.
>>
>> Thx
>>
>> On 7/30/15, 12:58 PM, "Khanduja, Vaibhav" 
>> wrote:
>>
>> >Hi
>> >
>> >jfyi,
>> >
>> >I have tried parameter option in marathon json file Š
>> >
>> >Š..
>> >"parameters": {
>> >"key": "H", "value": "unix:///var/run/mydocker.sock"
>> >}
>> >Š.
>> >
>> >
>> >
>> >
>> >On 7/30/15, 12:29 PM, "Khanduja, Vaibhav" 
>> >wrote:
>> >
>> >>Hi
>> >>
>> >>I have a use-case where docker deamon does not run on original socket
>> >>path which is /var/run/docker.sock but to a path as given by user.  I
>> >>start my docker daemon with ­H option,
>> >>
>> >>docker ­d ­H unix:///var/run/mydocker.sock
>> >>
>> >>all my docker calls now use this ­H for e.g. to print images:
>> >>
>> >>docker ­H unix:///var/run/mydocker.sock images
>> >>
>> >>I am using Marathon and have started my slave with Docker as container
>> >>option.
>> >>
>> >>I cannot see an option in slave, where I can specify the socket port
>>for
>> >>the it talk with Docker daemon. docker_socket option is used for
>> >>specifying docker port mapping in the container slave.
>> >>
>> >>Does this require code change in slave?
>> >>
>> >>Thx
>> >
>>
>>

Review board: diff update

[Khanduja, Vaibhav]

Hi

I am updating a diff on review board on an existing. I understand, the existing 
commits should be adjusted before executing post_review.py. I am having few 
issues here with adjusting the commits, and wondering if somebody could guide 
me with commands which should be used to adjust the commit?

Thanks

Re: Review board: diff update

[Khanduja, Vaibhav]

Thanks .. 

On 8/7/15, 10:26 AM, "haosdent"  wrote:

>Cool!
>
>I also have two git alias to change exist commit.
>
>append = "!f() { git reset --soft HEAD~1; git commit -am \"$(git
>log --format=%B --reverse HEAD..HEAD@{1})\"; }; f"
>
>could append you local change to last exist commit in current patch.
>
>So the work flow to update exist review board could be:
>
># write some code to exist branch.
>git append
>git fetch origin master:master && git rebase master
>post_review
>
>And this alias is squal several commits to one more convenient, sometimes
>I
>use it and git amend to change the branch history.
>
>
>rb = "!f() { git reset --soft HEAD~$1; git commit -m \"$(git log
>--format=%B --reverse HEAD..HEAD@{2})\"; }; f"
>
>
>On Sat, Aug 8, 2015 at 1:19 AM, Joris Van Remoortere 
>wrote:
>
>> This is the worflow I usually share with people:
>>
>> Updating a review after comments:
>> `git checkout master`
>> `git fetch apache`
>> `git rebase apache/master`
>> 'git checkout `
>> `git rebase master`
>> 
>> `git rebase -i HEAD^` (number of `^` based on how far back you want
>>to
>> pick
>> 
>> 
>> >got
>> applied>
>> 
>> `git add `
>> 'git rebase --continue`
>> > state>
>> 
>>
>> where:
>> apache https://git-wip-us.apache.org/repos/asf/mesos.git
>>
>>
>> On Fri, Aug 7, 2015 at 10:09 AM, Khanduja, Vaibhav <
>> vaibhav.khand...@emc.com
>> > wrote:
>>
>> > Hi
>> >
>> > I am updating a diff on review board on an existing. I understand, the
>> > existing commits should be adjusted before executing post_review.py.
>>I am
>> > having few issues here with adjusting the commits, and wondering if
>> > somebody could guide me with commands which should be used to adjust
>>the
>> > commit?
>> >
>> > Thanks
>> >
>>
>
>
>
>-- 
>Best Regards,
>Haosdent Huang

Re: Mesos Developer Community Design Discussions

[Khanduja, Vaibhav]

+1

Thx

On 8/10/15, 4:41 PM, "Timothy Anderegg"  wrote:

>Live stream for folks who won't be there would be great, thanks!
>
>Tim
>
>On Mon, Aug 10, 2015 at 7:09 PM, Benjamin Hindman 
>wrote:
>
>> The spreadsheet has been updated, sorry about that!
>>
>> Dave: we didn't want to pull people away from the hackathon and all the
>> other times were taken, so we figured we'd do the best we can! Enough
>> people have chatted with me about talking about future features that it
>> made sense to put something together for anyone in the community to
>>join.
>> We'll try and get live streaming set up for folks that aren't flying in
>> until Wednesday (or at all).
>>
>> On Mon, Aug 10, 2015 at 3:01 PM Dave Lester  wrote:
>>
>> > Hi Ben,
>> >
>> > It looks like the spreadsheet/google form isn't public outside your
>> > organization, you may need to revise the permissions.
>> >
>> > I'm curious, why this particular day? It's a bit unfortunate that
>>only 8
>> > day notice is being given, since I imagine most people have their
>> > flights for MesosCon already booked and will not likely be in
>> > attendance.
>> >
>> > Best,
>> > Dave
>> >
>> > On Mon, Aug 10, 2015, at 02:52 PM, Benjamin Hindman wrote:
>> > > We've had great developer community meetings over Google Hangouts,
>>but
>> > > MesosCon is right around the corner and we'd like to do it in
>>person!
>> > >
>> > > I'd like to invite everyone to attend an in person developer
>>community
>> > > meeting on Tuesday, August 18th in Seattle. The focus will be for
>>Mesos
>> > > committers and contributors to get together to discuss "big ticket"
>> > > features to work on during the next 6 to 12 months. I will be
>>joining
>> > > many
>> > > other committers at this event and we all look forward to discussing
>> new
>> > > features with everyone!
>> > >
>> > > There is a limited amount of space so please submit your RSVP here:
>> > > http://bit.ly/mesosdesignsummit
>> > >
>> > > We look forward to seeing you in Seattle! And don't forget to
>>register
>> > > for
>> > > MesosCon
>> > > 
>>if
>> > > you haven't already!
>> >
>>

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hi

I have raised review for the code changes:

https://issues.apache.org/jira/browse/MESOS-3187


https://reviews.apache.org/r/37114/ -  A second version updated based on
the feedback. 

As per contribution documentation, the review has to be marked as “ship
it” before it can be committed.

I was wondering, if somebody could help me (Shepherd) here?

Thanks

On 8/3/15, 10:25 AM, "Vinod Kone"  wrote:

>Added you to the contributors.
>
>On Mon, Aug 3, 2015 at 9:47 AM, Khanduja, Vaibhav
>
>wrote:
>
>> Hi Peter,
>>
>> Thanks for  your reply.
>>
>> The change for docker daemon options is probably has to be in slave code
>> and not int the framework. Other than marathon, there could be other
>> framework requiring such support.
>>
>> The slave during bootup checks for connection, by querying the version
>>of
>> docker daemon.
>>
>> I have opened an issue, and plan to work on it:
>> https://issues.apache.org/jira/browse/MESOS-3187
>>
>> I am not part of contributors list, so cannot assign to myself. Can
>> somebody do this for me? I made few changes to code to get this working.
>> The changes are now in a pull request:
>>
>> https://github.com/apache/mesos/pull/53
>>
>> I am aware of contribution requirements:
>> http://mesos.apache.org/documentation/latest/, and would work in
>>creating
>> patch if I get the bug assigned.
>>
>> — VK,
>>
>> Technologist,
>> EMC OCTO
>>
>> Thx
>>
>> On 8/3/15, 6:39 AM, "Peter Kolloch"  wrote:
>>
>> >Hi Vaibhav,
>> >
>> >the "parameters" option works for parameters of the docker run command:
>> >
>> >
>> 
>>https://mesosphere.github.io/marathon/docs/native-docker.html#privileged-
>>m
>> >ode-and-arbitrary-docker-options
>> >
>> >You tried to use it with a command line argument for the docker
>>_daemon_.
>> >Starting the docker daemon with the right command line arguments is
>>out of
>> >scope for Marathon.
>> >
>> >If you find a parameter of the "docker run" command that works for you,
>> >you
>> >need to specify the long name for this option (the none-one-letter
>>option)
>> >in the "parameters" option.
>> >
>> >If you find the Marathon documentation lacking, we would love to get a
>>PR
>> >for a documentation improvement from you!
>> >
>> >See
>> >
>> >https://mesosphere.github.io/marathon/docs/contributing.html
>> >
>> >for details.
>> >
>> >Best regards,
>> >Peter
>> >
>> >[BTW: The Marathon mailing list might be better suited for this kind of
>> >question.]
>> >
>> >On Sat, Aug 1, 2015 at 1:57 AM, Khanduja, Vaibhav
>> >
>> >wrote:
>> >
>> >> Hi
>> >>
>> >> Having not received any answer, I support there is no solution for
>>this.
>> >>
>> >> The mesos slave process, along with accepting other docker arguments
>> >> should somehow manage to take these extra arguments too. I have
>>logged
>> >> this as an enhancement, and wondering if somebody can look at this:
>> >>
>> >> https://issues.apache.org/jira/browse/MESOS-3187
>> >>
>> >> I am available to provide the fix, if somebody can be a help as
>>sheperd.
>> >>
>> >> Thx
>> >>
>> >> On 7/30/15, 12:58 PM, "Khanduja, Vaibhav" 
>> >> wrote:
>> >>
>> >> >Hi
>> >> >
>> >> >jfyi,
>> >> >
>> >> >I have tried parameter option in marathon json file Š
>> >> >
>> >> >Š..
>> >> >"parameters": {
>> >> >"key": "H", "value": "unix:///var/run/mydocker.sock"
>> >> >}
>> >> >Š.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >On 7/30/15, 12:29 PM, "Khanduja, Vaibhav" 
>> >> >wrote:
>> >> >
>> >> >>Hi
>> >> >>
>> >> >>I have a use-case where docker deamon does not run on original
>>socket
>> >> >>path which is /var/run/docker.sock but to a path as given by user.
>> I
>> >> >>start my docker daemon with ­H option,
>> >> >>
>> >> >>docker ­d ­H unix:///var/run/mydocker.sock
>> >> >>
>> >> >>all my docker calls now use this ­H for e.g. to print images:
>> >> >>
>> >> >>docker ­H unix:///var/run/mydocker.sock images
>> >> >>
>> >> >>I am using Marathon and have started my slave with Docker as
>>container
>> >> >>option.
>> >> >>
>> >> >>I cannot see an option in slave, where I can specify the socket
>>port
>> >>for
>> >> >>the it talk with Docker daemon. docker_socket option is used for
>> >> >>specifying docker port mapping in the container slave.
>> >> >>
>> >> >>Does this require code change in slave?
>> >> >>
>> >> >>Thx
>> >> >
>> >>
>> >>
>>
>>

Re: Docker socket path for slave

[Khanduja, Vaibhav]

@ 

I have updated the review as suggested in feedback. I would appreciate if
review can be marked as ship-it if no more changes are needed.

Thanks

On 8/12/15, 9:31 AM, "Khanduja, Vaibhav"  wrote:

>Hi
>
>I have raised review for the code changes:
>
>https://issues.apache.org/jira/browse/MESOS-3187
>
>
>https://reviews.apache.org/r/37114/ -  A second version updated based on
>the feedback. 
>
>As per contribution documentation, the review has to be marked as “ship
>it” before it can be committed.
>
>I was wondering, if somebody could help me (Shepherd) here?
>
>Thanks
>
>On 8/3/15, 10:25 AM, "Vinod Kone"  wrote:
>
>>Added you to the contributors.
>>
>>On Mon, Aug 3, 2015 at 9:47 AM, Khanduja, Vaibhav
>>
>>wrote:
>>
>>> Hi Peter,
>>>
>>> Thanks for  your reply.
>>>
>>> The change for docker daemon options is probably has to be in slave
>>>code
>>> and not int the framework. Other than marathon, there could be other
>>> framework requiring such support.
>>>
>>> The slave during bootup checks for connection, by querying the version
>>>of
>>> docker daemon.
>>>
>>> I have opened an issue, and plan to work on it:
>>> https://issues.apache.org/jira/browse/MESOS-3187
>>>
>>> I am not part of contributors list, so cannot assign to myself. Can
>>> somebody do this for me? I made few changes to code to get this
>>>working.
>>> The changes are now in a pull request:
>>>
>>> https://github.com/apache/mesos/pull/53
>>>
>>> I am aware of contribution requirements:
>>> http://mesos.apache.org/documentation/latest/, and would work in
>>>creating
>>> patch if I get the bug assigned.
>>>
>>> — VK,
>>>
>>> Technologist,
>>> EMC OCTO
>>>
>>> Thx
>>>
>>> On 8/3/15, 6:39 AM, "Peter Kolloch"  wrote:
>>>
>>> >Hi Vaibhav,
>>> >
>>> >the "parameters" option works for parameters of the docker run
>>>command:
>>> >
>>> >
>>> 
>>>https://mesosphere.github.io/marathon/docs/native-docker.html#privileged
>>>-
>>>m
>>> >ode-and-arbitrary-docker-options
>>> >
>>> >You tried to use it with a command line argument for the docker
>>>_daemon_.
>>> >Starting the docker daemon with the right command line arguments is
>>>out of
>>> >scope for Marathon.
>>> >
>>> >If you find a parameter of the "docker run" command that works for
>>>you,
>>> >you
>>> >need to specify the long name for this option (the none-one-letter
>>>option)
>>> >in the "parameters" option.
>>> >
>>> >If you find the Marathon documentation lacking, we would love to get a
>>>PR
>>> >for a documentation improvement from you!
>>> >
>>> >See
>>> >
>>> >https://mesosphere.github.io/marathon/docs/contributing.html
>>> >
>>> >for details.
>>> >
>>> >Best regards,
>>> >Peter
>>> >
>>> >[BTW: The Marathon mailing list might be better suited for this kind
>>>of
>>> >question.]
>>> >
>>> >On Sat, Aug 1, 2015 at 1:57 AM, Khanduja, Vaibhav
>>> >
>>> >wrote:
>>> >
>>> >> Hi
>>> >>
>>> >> Having not received any answer, I support there is no solution for
>>>this.
>>> >>
>>> >> The mesos slave process, along with accepting other docker arguments
>>> >> should somehow manage to take these extra arguments too. I have
>>>logged
>>> >> this as an enhancement, and wondering if somebody can look at this:
>>> >>
>>> >> https://issues.apache.org/jira/browse/MESOS-3187
>>> >>
>>> >> I am available to provide the fix, if somebody can be a help as
>>>sheperd.
>>> >>
>>> >> Thx
>>> >>
>>> >> On 7/30/15, 12:58 PM, "Khanduja, Vaibhav" 
>>> >> wrote:
>>> >>
>>> >> >Hi
>>> >> >
>>> >> >jfyi,
>>> >> >
>>> >> >I have tried parameter option in marathon json file Š
>>> >> >
>>> >> >Š..
>>> >> >"parameters": {
>>> >> >"key": "H", "value": "unix:///var/run/mydocker.sock"
>>> >> >}
>>> >> >Š.
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >On 7/30/15, 12:29 PM, "Khanduja, Vaibhav"
>>>
>>> >> >wrote:
>>> >> >
>>> >> >>Hi
>>> >> >>
>>> >> >>I have a use-case where docker deamon does not run on original
>>>socket
>>> >> >>path which is /var/run/docker.sock but to a path as given by user.
>>> I
>>> >> >>start my docker daemon with ­H option,
>>> >> >>
>>> >> >>docker ­d ­H unix:///var/run/mydocker.sock
>>> >> >>
>>> >> >>all my docker calls now use this ­H for e.g. to print images:
>>> >> >>
>>> >> >>docker ­H unix:///var/run/mydocker.sock images
>>> >> >>
>>> >> >>I am using Marathon and have started my slave with Docker as
>>>container
>>> >> >>option.
>>> >> >>
>>> >> >>I cannot see an option in slave, where I can specify the socket
>>>port
>>> >>for
>>> >> >>the it talk with Docker daemon. docker_socket option is used for
>>> >> >>specifying docker port mapping in the container slave.
>>> >> >>
>>> >> >>Does this require code change in slave?
>>> >> >>
>>> >> >>Thx
>>> >> >
>>> >>
>>> >>
>>>
>>>
>

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hi,

Thanks for the feedback I received on review board yesterday. I have updated 
review with new code changes. Appreciate if this can be marked completed.

Thanks

> On Aug 25, 2015, at 9:58 AM, Khanduja, Vaibhav  
> wrote:
> 
> @ 
> 
> I have updated the review as suggested in feedback. I would appreciate if
> review can be marked as ship-it if no more changes are needed.
> 
> Thanks
> 
>> On 8/12/15, 9:31 AM, "Khanduja, Vaibhav"  wrote:
>> 
>> Hi
>> 
>> I have raised review for the code changes:
>> 
>> https://issues.apache.org/jira/browse/MESOS-3187
>> 
>> 
>> https://reviews.apache.org/r/37114/ -  A second version updated based on
>> the feedback. 
>> 
>> As per contribution documentation, the review has to be marked as “ship
>> it” before it can be committed.
>> 
>> I was wondering, if somebody could help me (Shepherd) here?
>> 
>> Thanks
>> 
>>> On 8/3/15, 10:25 AM, "Vinod Kone"  wrote:
>>> 
>>> Added you to the contributors.
>>> 
>>> On Mon, Aug 3, 2015 at 9:47 AM, Khanduja, Vaibhav
>>> 
>>> wrote:
>>> 
>>>> Hi Peter,
>>>> 
>>>> Thanks for  your reply.
>>>> 
>>>> The change for docker daemon options is probably has to be in slave
>>>> code
>>>> and not int the framework. Other than marathon, there could be other
>>>> framework requiring such support.
>>>> 
>>>> The slave during bootup checks for connection, by querying the version
>>>> of
>>>> docker daemon.
>>>> 
>>>> I have opened an issue, and plan to work on it:
>>>> https://issues.apache.org/jira/browse/MESOS-3187
>>>> 
>>>> I am not part of contributors list, so cannot assign to myself. Can
>>>> somebody do this for me? I made few changes to code to get this
>>>> working.
>>>> The changes are now in a pull request:
>>>> 
>>>> https://github.com/apache/mesos/pull/53
>>>> 
>>>> I am aware of contribution requirements:
>>>> http://mesos.apache.org/documentation/latest/, and would work in
>>>> creating
>>>> patch if I get the bug assigned.
>>>> 
>>>> — VK,
>>>> 
>>>> Technologist,
>>>> EMC OCTO
>>>> 
>>>> Thx
>>>> 
>>>>> On 8/3/15, 6:39 AM, "Peter Kolloch"  wrote:
>>>>> 
>>>>> Hi Vaibhav,
>>>>> 
>>>>> the "parameters" option works for parameters of the docker run
>>>> command:
>>>> 
>>>> https://mesosphere.github.io/marathon/docs/native-docker.html#privileged
>>>> -
>>>> m
>>>>> ode-and-arbitrary-docker-options
>>>>> 
>>>>> You tried to use it with a command line argument for the docker
>>>> _daemon_.
>>>>> Starting the docker daemon with the right command line arguments is
>>>> out of
>>>>> scope for Marathon.
>>>>> 
>>>>> If you find a parameter of the "docker run" command that works for
>>>> you,
>>>>> you
>>>>> need to specify the long name for this option (the none-one-letter
>>>> option)
>>>>> in the "parameters" option.
>>>>> 
>>>>> If you find the Marathon documentation lacking, we would love to get a
>>>> PR
>>>>> for a documentation improvement from you!
>>>>> 
>>>>> See
>>>>> 
>>>>> https://mesosphere.github.io/marathon/docs/contributing.html
>>>>> 
>>>>> for details.
>>>>> 
>>>>> Best regards,
>>>>> Peter
>>>>> 
>>>>> [BTW: The Marathon mailing list might be better suited for this kind
>>>> of
>>>>> question.]
>>>>> 
>>>>> On Sat, Aug 1, 2015 at 1:57 AM, Khanduja, Vaibhav
>>>>> 
>>>>> wrote:
>>>>> 
>>>>>> Hi
>>>>>> 
>>>>>> Having not received any answer, I support there is no solution for
>>>> this.
>>>>>> 
>>>>>> The mesos slave process, along with accepting other docker arguments
>>>>>> should somehow manage to take these extra arguments too. I have
>>>> logged
>

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

[Khanduja, Vaibhav]

+1

> On Aug 26, 2015, at 4:43 PM, Vinod Kone  wrote:
> 
> Pinging the thread for more (binding) votes. Hopefully people have caught
> up with emails after Mesos madness.
> 
>> On Wed, Aug 19, 2015 at 1:28 AM, haosdent  wrote:
>> 
>> +1
>> 
>> OS: Ubutnu 14.04
>> Verify command: sudo make -j8 check
>> Compiler: Both gcc4.8 and clang3.5
>> Configuration: default configuration
>> Result: all tests(828 tests) pass
>> 
>> MESOS-3053  is because
>> need update add iptable first.
>> 
>>> On Wed, Aug 19, 2015 at 2:39 PM, haosdent  wrote:
>>> 
>>> Could not
>>> pass DockerContainerizerTest.ROOT_DOCKER_Launch_Executor_Bridged in Ubuntu
>>> 14.04. Already have a issue for this
>>> https://issues.apache.org/jira/browse/MESOS-3053, it is acceptable?
>>> 
>>> On Wed, Aug 19, 2015 at 12:55 PM, Marco Massenzio 
>>> wrote:
>>> 
 +1 (non-binding)
 
 All tests (including ROOT) pass on:
 Ubuntu 14.04 (physical box)
 
 All non-ROOT tests pass on:
 CentOS 7 (VirtualBox VM)
 
 Known issue (MESOS-3050) for ROOT tests on CentOS 7, non-blocker.
 
 Thanks,
 
 *Marco Massenzio*
 
 *Distributed Systems Engineerhttp://codetrips.com *
 
 On Tue, Aug 18, 2015 at 3:26 PM, Vinod Kone 
 wrote:
 
> 0.24.0 includes the following:
> 
> 
> 
> 
> Experimental support for v1 scheduler HTTP API!
> 
> This release also wraps up support for fetcher.
> 
> 
> The CHANGELOG for the release is available at:
> 
> 
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.24.0-rc1
> 
> 
> 
> 
> 
> The candidate for Mesos 0.24.0 release is available at:
> 
> 
> https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc1/mesos-0.24.0.tar.gz
> 
> 
> The tag to be voted on is 0.24.0-rc1:
> 
> 
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.0-rc1
> 
> 
> The MD5 checksum of the tarball can be found at:
> 
> 
> https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc1/mesos-0.24.0.tar.gz.md5
> 
> 
> The signature of the tarball can be found at:
> 
> 
> https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc1/mesos-0.24.0.tar.gz.asc
> 
> 
> The PGP key used to sign the release is here:
> 
> https://dist.apache.org/repos/dist/release/mesos/KEYS
> 
> 
> The JAR is up in Maven in a staging repository here:
> 
> https://repository.apache.org/content/repositories/orgapachemesos-1064
> 
> 
> Please vote on releasing this package as Apache Mesos 0.24.0!
> 
> 
> The vote is open until Fri Aug 21 15:24:05 PDT 2015 and passes if a
> majority of at least 3 +1 PMC votes are cast.
> 
> 
> [ ] +1 Release this package as Apache Mesos 0.24.0
> 
> [ ] -1 Do not release this package because ...
> 
> 
> Thanks,
> 
> Vinod
>>> 
>>> 
>>> --
>>> Best Regards,
>>> Haosdent Huang
>> 
>> 
>> 
>> --
>> Best Regards,
>> Haosdent Huang
>> 

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hello All, 

I apologies for my repeated requests here.
 
This is my first contribution to source code and I am bit unaware of next
steps. I have updated code with feedback received and was wondering if the
code is good for it make into source repository. From what I read, there
has to be a “Ship It” on the code review before it can make to main source
line. I understand community is pre-occupied with other important patches
and bugs, so perfectly fine with a wait here, but would appreciate any
info on next steps.


Thanks


On 8/25/15, 9:58 AM, "Khanduja, Vaibhav"  wrote:

>@ 
>
>I have updated the review as suggested in feedback. I would appreciate if
>review can be marked as ship-it if no more changes are needed.
>
>Thanks
>
>On 8/12/15, 9:31 AM, "Khanduja, Vaibhav"  wrote:
>
>>Hi
>>
>>I have raised review for the code changes:
>>
>>https://issues.apache.org/jira/browse/MESOS-3187
>>
>>
>>https://reviews.apache.org/r/37114/ -  A second version updated based on
>>the feedback. 
>>
>>As per contribution documentation, the review has to be marked as “ship
>>it” before it can be committed.
>>
>>I was wondering, if somebody could help me (Shepherd) here?
>>
>>Thanks
>>
>>On 8/3/15, 10:25 AM, "Vinod Kone"  wrote:
>>
>>>Added you to the contributors.
>>>
>>>On Mon, Aug 3, 2015 at 9:47 AM, Khanduja, Vaibhav
>>>
>>>wrote:
>>>
>>>> Hi Peter,
>>>>
>>>> Thanks for  your reply.
>>>>
>>>> The change for docker daemon options is probably has to be in slave
>>>>code
>>>> and not int the framework. Other than marathon, there could be other
>>>> framework requiring such support.
>>>>
>>>> The slave during bootup checks for connection, by querying the version
>>>>of
>>>> docker daemon.
>>>>
>>>> I have opened an issue, and plan to work on it:
>>>> https://issues.apache.org/jira/browse/MESOS-3187
>>>>
>>>> I am not part of contributors list, so cannot assign to myself. Can
>>>> somebody do this for me? I made few changes to code to get this
>>>>working.
>>>> The changes are now in a pull request:
>>>>
>>>> https://github.com/apache/mesos/pull/53
>>>>
>>>> I am aware of contribution requirements:
>>>> http://mesos.apache.org/documentation/latest/, and would work in
>>>>creating
>>>> patch if I get the bug assigned.
>>>>
>>>> — VK,
>>>>
>>>> Technologist,
>>>> EMC OCTO
>>>>
>>>> Thx
>>>>
>>>> On 8/3/15, 6:39 AM, "Peter Kolloch"  wrote:
>>>>
>>>> >Hi Vaibhav,
>>>> >
>>>> >the "parameters" option works for parameters of the docker run
>>>>command:
>>>> >
>>>> >
>>>> 
>>>>https://mesosphere.github.io/marathon/docs/native-docker.html#privilege
>>>>d
>>>>-
>>>>m
>>>> >ode-and-arbitrary-docker-options
>>>> >
>>>> >You tried to use it with a command line argument for the docker
>>>>_daemon_.
>>>> >Starting the docker daemon with the right command line arguments is
>>>>out of
>>>> >scope for Marathon.
>>>> >
>>>> >If you find a parameter of the "docker run" command that works for
>>>>you,
>>>> >you
>>>> >need to specify the long name for this option (the none-one-letter
>>>>option)
>>>> >in the "parameters" option.
>>>> >
>>>> >If you find the Marathon documentation lacking, we would love to get
>>>>a
>>>>PR
>>>> >for a documentation improvement from you!
>>>> >
>>>> >See
>>>> >
>>>> >https://mesosphere.github.io/marathon/docs/contributing.html
>>>> >
>>>> >for details.
>>>> >
>>>> >Best regards,
>>>> >Peter
>>>> >
>>>> >[BTW: The Marathon mailing list might be better suited for this kind
>>>>of
>>>> >question.]
>>>> >
>>>> >On Sat, Aug 1, 2015 at 1:57 AM, Khanduja, Vaibhav
>>>> >
>>>> >wrote:
>>>> >
>>>> >> Hi
>>>> >>
>>>

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hi Tim

Thanks you very much for your time.

I have incorporated your feedback in the latest review.

Regards,

On 8/28/15, 3:52 PM, "Timothy Chen"  wrote:

>Hi Vaibhav,
>
>Thanks for the ping, sorry as you said there are other work that is
>going on that causes some delays on your review.
>
>But yes you're right you need a ship it from a committer, and
>afterwards you need a committer to merge your patch too.
>
>I'll take a look at your patch and we can go from there.
>
>Tim
>
>
>
>On Fri, Aug 28, 2015 at 3:09 PM, Khanduja, Vaibhav
> wrote:
>> Hello All,
>>
>> I apologies for my repeated requests here.
>>
>> This is my first contribution to source code and I am bit unaware of
>>next
>> steps. I have updated code with feedback received and was wondering if
>>the
>> code is good for it make into source repository. From what I read, there
>> has to be a “Ship It” on the code review before it can make to main
>>source
>> line. I understand community is pre-occupied with other important
>>patches
>> and bugs, so perfectly fine with a wait here, but would appreciate any
>> info on next steps.
>>
>>
>> Thanks
>>
>>
>> On 8/25/15, 9:58 AM, "Khanduja, Vaibhav" 
>>wrote:
>>
>>>@
>>>
>>>I have updated the review as suggested in feedback. I would appreciate
>>>if
>>>review can be marked as ship-it if no more changes are needed.
>>>
>>>Thanks
>>>
>>>On 8/12/15, 9:31 AM, "Khanduja, Vaibhav" 
>>>wrote:
>>>
>>>>Hi
>>>>
>>>>I have raised review for the code changes:
>>>>
>>>>https://issues.apache.org/jira/browse/MESOS-3187
>>>>
>>>>
>>>>https://reviews.apache.org/r/37114/ -  A second version updated based
>>>>on
>>>>the feedback.
>>>>
>>>>As per contribution documentation, the review has to be marked as “ship
>>>>it” before it can be committed.
>>>>
>>>>I was wondering, if somebody could help me (Shepherd) here?
>>>>
>>>>Thanks
>>>>
>>>>On 8/3/15, 10:25 AM, "Vinod Kone"  wrote:
>>>>
>>>>>Added you to the contributors.
>>>>>
>>>>>On Mon, Aug 3, 2015 at 9:47 AM, Khanduja, Vaibhav
>>>>>
>>>>>wrote:
>>>>>
>>>>>> Hi Peter,
>>>>>>
>>>>>> Thanks for  your reply.
>>>>>>
>>>>>> The change for docker daemon options is probably has to be in slave
>>>>>>code
>>>>>> and not int the framework. Other than marathon, there could be other
>>>>>> framework requiring such support.
>>>>>>
>>>>>> The slave during bootup checks for connection, by querying the
>>>>>>version
>>>>>>of
>>>>>> docker daemon.
>>>>>>
>>>>>> I have opened an issue, and plan to work on it:
>>>>>> https://issues.apache.org/jira/browse/MESOS-3187
>>>>>>
>>>>>> I am not part of contributors list, so cannot assign to myself. Can
>>>>>> somebody do this for me? I made few changes to code to get this
>>>>>>working.
>>>>>> The changes are now in a pull request:
>>>>>>
>>>>>> https://github.com/apache/mesos/pull/53
>>>>>>
>>>>>> I am aware of contribution requirements:
>>>>>> http://mesos.apache.org/documentation/latest/, and would work in
>>>>>>creating
>>>>>> patch if I get the bug assigned.
>>>>>>
>>>>>> — VK,
>>>>>>
>>>>>> Technologist,
>>>>>> EMC OCTO
>>>>>>
>>>>>> Thx
>>>>>>
>>>>>> On 8/3/15, 6:39 AM, "Peter Kolloch"  wrote:
>>>>>>
>>>>>> >Hi Vaibhav,
>>>>>> >
>>>>>> >the "parameters" option works for parameters of the docker run
>>>>>>command:
>>>>>> >
>>>>>> >
>>>>>>
>>>>>>https://mesosphere.github.io/marathon/docs/native-docker.html#privile
>>>>>>ge
>>>>>>d
>>>>>>-
>>>>>>m
>>>>

Re: Docker socket path for slave

[Khanduja, Vaibhav]

Hi Tim,

I have uploaded new patch, synching with master. Can you please let me know if 
the patch can make to main trunk?

Thanks

> On Aug 28, 2015, at 3:53 PM, Timothy Chen  wrote:
> 
> Hi Vaibhav,
> 
> Thanks for the ping, sorry as you said there are other work that is
> going on that causes some delays on your review.
> 
> But yes you're right you need a ship it from a committer, and
> afterwards you need a committer to merge your patch too.
> 
> I'll take a look at your patch and we can go from there.
> 
> Tim
> 
> 
> 
> On Fri, Aug 28, 2015 at 3:09 PM, Khanduja, Vaibhav
>  wrote:
>> Hello All,
>> 
>> I apologies for my repeated requests here.
>> 
>> This is my first contribution to source code and I am bit unaware of next
>> steps. I have updated code with feedback received and was wondering if the
>> code is good for it make into source repository. From what I read, there
>> has to be a “Ship It” on the code review before it can make to main source
>> line. I understand community is pre-occupied with other important patches
>> and bugs, so perfectly fine with a wait here, but would appreciate any
>> info on next steps.
>> 
>> 
>> Thanks
>> 
>> 
>>> On 8/25/15, 9:58 AM, "Khanduja, Vaibhav"  wrote:
>>> 
>>> @
>>> 
>>> I have updated the review as suggested in feedback. I would appreciate if
>>> review can be marked as ship-it if no more changes are needed.
>>> 
>>> Thanks
>>> 
>>>> On 8/12/15, 9:31 AM, "Khanduja, Vaibhav"  wrote:
>>>> 
>>>> Hi
>>>> 
>>>> I have raised review for the code changes:
>>>> 
>>>> https://issues.apache.org/jira/browse/MESOS-3187
>>>> 
>>>> 
>>>> https://reviews.apache.org/r/37114/ -  A second version updated based on
>>>> the feedback.
>>>> 
>>>> As per contribution documentation, the review has to be marked as “ship
>>>> it” before it can be committed.
>>>> 
>>>> I was wondering, if somebody could help me (Shepherd) here?
>>>> 
>>>> Thanks
>>>> 
>>>>> On 8/3/15, 10:25 AM, "Vinod Kone"  wrote:
>>>>> 
>>>>> Added you to the contributors.
>>>>> 
>>>>> On Mon, Aug 3, 2015 at 9:47 AM, Khanduja, Vaibhav
>>>>> 
>>>>> wrote:
>>>>> 
>>>>>> Hi Peter,
>>>>>> 
>>>>>> Thanks for  your reply.
>>>>>> 
>>>>>> The change for docker daemon options is probably has to be in slave
>>>>>> code
>>>>>> and not int the framework. Other than marathon, there could be other
>>>>>> framework requiring such support.
>>>>>> 
>>>>>> The slave during bootup checks for connection, by querying the version
>>>>>> of
>>>>>> docker daemon.
>>>>>> 
>>>>>> I have opened an issue, and plan to work on it:
>>>>>> https://issues.apache.org/jira/browse/MESOS-3187
>>>>>> 
>>>>>> I am not part of contributors list, so cannot assign to myself. Can
>>>>>> somebody do this for me? I made few changes to code to get this
>>>>>> working.
>>>>>> The changes are now in a pull request:
>>>>>> 
>>>>>> https://github.com/apache/mesos/pull/53
>>>>>> 
>>>>>> I am aware of contribution requirements:
>>>>>> http://mesos.apache.org/documentation/latest/, and would work in
>>>>>> creating
>>>>>> patch if I get the bug assigned.
>>>>>> 
>>>>>> — VK,
>>>>>> 
>>>>>> Technologist,
>>>>>> EMC OCTO
>>>>>> 
>>>>>> Thx
>>>>>> 
>>>>>>> On 8/3/15, 6:39 AM, "Peter Kolloch"  wrote:
>>>>>>> 
>>>>>>> Hi Vaibhav,
>>>>>>> 
>>>>>>> the "parameters" option works for parameters of the docker run
>>>>>> command:
>>>>>> 
>>>>>> https://mesosphere.github.io/marathon/docs/native-docker.html#privilege
>>>>>> d
>>>>>> -
>>>>>> m
>>>>>>> ode-and-arbitrary-docker-options
>>>

Re: Mesos/Marathon support for Docker extension

[Khanduja, Vaibhav]

Hi, 

I managed to get this working for a plugin, though with a bit of an issue.
The Docker cli now accepts volume name without a ³/³, this is done as the
name is not absolute path but a name to be used by plugin. The plugin
would then return the mount point, to the Docker daemon. The slave Docker
code not like and throws an error. The condition check in docker.cpp,

ŠŠŠ.
string volumeConfig = volume.container_path();
if (volume.has_host_path()) {
  if (!strings::startsWith(volume.host_path(), "/")) {
// Support mapping relative paths from the sandbox.
volumeConfig =
  path::join(sandboxDirectory, volume.host_path()) + ":" +
volumeConfig;
  } else {
ŠŠŠ..


requires a modification. The workaround for now is to use pass volume
name, as key value pair, but I suppose this won¹t fit well with persistent
volumes implementation.

Any suggestions? I can work on this if a ³Shepherd² can spend time with me.

Thanks

On 6/6/15, 8:44 PM, "Timothy Chen"  wrote:

>Yes.
>
>Tim
>
>Sent from my iPhone
>
>> On Jun 6, 2015, at 8:38 PM, Khanduja, Vaibhav
>> wrote:
>> 
>> Hi Tim
>> 
>> Are you referring to following pull request
>> 
>> https://github.com/mesosphere/marathon/pull/798
>> 
>> Thanks
>> 
>> 
>>> On 6/6/15, 8:21 PM, "Timothy Chen"  wrote:
>>> 
>>> Hi Khadijah/Shuai,
>>> 
>>> Mesos slave actually does invoke the docker cli directly for its
>>> integration.
>>> 
>>> To support various options that docker will be adding we allowed
>>> arbitrary flags to be passed when launching a docker task (Params
>>>field I
>>> believe).
>>> 
>>> Therefore if you know you have latest docker installed you can pass the
>>> Extra volume option and it should work.
>>> 
>>> Tim
>>> 
>>>> On Jun 6, 2015, at 7:51 PM, Shuai Lin  wrote:
>>>> 
>>>> Hi Khanduja,
>>>> 
>>>> What I understand the slave code which calls in docker cli would need
>>>> this
>>>>> additional parameter to be passed into.
>>>> 
>>>> 
>>>> I don't think mesos slave invokes docker cli directly. It calls the
>>>> docker
>>>> api instead.
>>>> 
>>>> Also Is there any official documentation/introduction to docker plugin
>>>> or
>>>> volume extensions? I found the following two pages when googling, but
>>>> non
>>>> of them has an official introduction to volume extension.
>>>> 
>>>> https://clusterhq.com/2014/12/08/docker-extensions/
>>>> https://github.com/docker/docker/pull/13161
>>>> 
>>>> Best Regards,
>>>> Shuai
>>>> 
>>>> 
>>>> On Sat, Jun 6, 2015 at 12:56 AM, Khanduja, Vaibhav
>>>> >>>> wrote:
>>>> 
>>>>> Recently docker pulled in code for supporting docker volume
>>>>>extensions.
>>>>> The docker now (1.9 & above) through CLI can be specified volume
>>>>>plugin
>>>>> name, which docker daemon connects get the actual storage. The plugin
>>>>> has
>>>>> today reasonable hooks for maintaining and cleaning the storage. I
>>>>>was
>>>>> wondering if there is any analysis done on the support of this in the
>>>>> code? What I understand the slave code which calls in docker cli
>>>>>would
>>>>> need this additional parameter to be passed into.
>>>>> 
>>>>> Thx
>> 

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

[Khanduja, Vaibhav]

fyi

I ran tests on VMs over ESX server, both with 4CPU and 4096MB of RAM

Thank

On 9/2/15, 12:18 AM, "Marco Massenzio"  wrote:

>+1 (non-binding)
>
>All tests (including ROOT) pass on Ubuntu 14.04
>All tests pass on CentOS 7.1; ROOT tests cause 1 failure:
>
>[  FAILED  ] 1 test, listed below:
>[  FAILED  ] CgroupsAnyHierarchyMemoryPressureTest.ROOT_IncreaseRSS
>
>$ cat /etc/centos-release
>CentOS Linux release 7.1.1503 (Core)
>
>This seems to be new[0], but possibly related to some limitation/setting
>of
>my test machine (VirtualBox VM, running 2 CPUs on Ubuntu host).
>Interestingly enough, I don't see the 4 failures as Vaibhav, but in my log
>it shows *YOU HAVE 11 DISABLED TESTS* (he has 12).
>
>[0] https://issues.apache.org/jira/issues/?filter=12333150
>
>*Marco Massenzio*
>
>*Distributed Systems Engineerhttp://codetrips.com *
>
>On Tue, Sep 1, 2015 at 5:45 PM, Vinod Kone  wrote:
>
>> Hi all,
>>
>>
>> Please vote on releasing the following candidate as Apache Mesos 0.24.0.
>>
>>
>> 0.24.0 includes the following:
>>
>>
>> 
>>-
>>---
>>
>> Experimental support for v1 scheduler HTTP API!
>>
>> This release also wraps up support for fetcher.
>>
>> The CHANGELOG for the release is available at:
>>
>>
>> 
>>https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGE
>>LOG;hb=0.24.0-rc2
>>
>>
>> 
>>-
>>---
>>
>>
>> The candidate for Mesos 0.24.0 release is available at:
>>
>> 
>>https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc2/mesos-0.24.0.tar.
>>gz
>>
>>
>> The tag to be voted on is 0.24.0-rc2:
>>
>> 
>>https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.0-rc2
>>
>>
>> The MD5 checksum of the tarball can be found at:
>>
>>
>> 
>>https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc2/mesos-0.24.0.tar.
>>gz.md5
>>
>>
>> The signature of the tarball can be found at:
>>
>>
>> 
>>https://dist.apache.org/repos/dist/dev/mesos/0.24.0-rc2/mesos-0.24.0.tar.
>>gz.asc
>>
>>
>> The PGP key used to sign the release is here:
>>
>> https://dist.apache.org/repos/dist/release/mesos/KEYS
>>
>>
>> The JAR is up in Maven in a staging repository here:
>>
>> https://repository.apache.org/content/repositories/orgapachemesos-1066
>>
>>
>> Please vote on releasing this package as Apache Mesos 0.24.0!
>>
>>
>> The vote is open until Fri Sep  4 17:33:05 PDT 2015 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>>
>> [ ] +1 Release this package as Apache Mesos 0.24.0
>>
>> [ ] -1 Do not release this package because ...
>>
>>
>> Thanks,
>>
>> Vinod
>>

Newbie question on checkpointing resource

[Khanduja, Vaibhav]

@

I apologies for flooding mail boxes but was wondering if I could get more info 
on “CheckPoint Resource”.  I see slave code and find following code:

"

void Slave::checkpointResources(const vector& _checkpointedResources)

"
Does CheckPoint resource mean the state of the resource can be 
preserved/CheckPointed?  I got reached to this code while understanding 
persistent volume implementation in 0.24.

Thanks