Re: Can health-checks be run by Mesos for docker tasks?

I am using my own framework, and the full task info I'm using is posted earlier in this thread. Do you happen to know if Marathon uses Mesos's health checks for its health check system? > On Oct 6, 2015, at 9:01 PM, haosdent wrote: > > Yes, launch the health task

Re: Broken images in documentation on web

Hi, @Brian. Joseph have a patch for this MESOS-3183 , but the website still not update. Before the document in website update, you could read these documents in github mirror https://github.com/apache/mesos/tree/master/docs first. Thank you for

Re: Can health-checks be run by Mesos for docker tasks?

I'm happy to try this, however wouldn't there be output in the logs with the string "health" or "Health" if the health-check were active? None of my master or slave logs contain the string.. > On Oct 6, 2015, at 7:45 PM, haosdent wrote: > > Could you use "exit 1"

Re: Can health-checks be run by Mesos for docker tasks?

When health check launch, it would have a log like this in your executor stdout ``` Health check process launched at pid xxx ``` On Wed, Oct 7, 2015 at 11:37 AM, Jay Taylor wrote: > I'm happy to try this, however wouldn't there be output in the logs with > the string

Re: Can health-checks be run by Mesos for docker tasks?

Precisely, and there are none of those statements. Are you or others confident health-checks are part of the code path when defined via task info for docker container tasks? Going through the code, I wasn't able to find the linkage for anything other than health-checks triggered through a

Re: Can health-checks be run by Mesos for docker tasks?

Yes, launch the health task through its definition in taskinfo. Do you launch your task through Marathon? I could test it in my side. On Wed, Oct 7, 2015 at 11:56 AM, Jay Taylor wrote: > Precisely, and there are none of those statements. Are you or others > confident

Re: MesosCon EU Hackathon hot list?

Joyent has just announced additional details of their sponsorship, including prizes: http://www.joyent.com/blog/getting-ready-for-mesoscon-hackathon • Joyent is offering every participant a $10,000 credit for Triton Elastic Container services • Each member of the winning teams in the

mesos framework authentication: authentication failure

Hi, I am trying to setup mesos framework authentication. I created the necessary config files and now mesos starts up with the --authenticate="true" flag : I1006 20:11:52.940199 7866 master.cpp:380] Flags at startup: --allocation_interval="1secs" --allocator="HierarchicalDRF"

[VOTE] Release Apache Mesos 0.25.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.25.0. 0.25.0 includes the following: * [MESOS-1474] - Experimental support for maintenance primitives. * [MESOS-2600] - Added master

Re: Scheduling tasks based on dependancy

Hi Sharma, Awesome!. This is what I was looking for. Thanks for the reply. I will have a look for more info in wiki. Regards, Pradeep On 5 October 2015 at 18:28, Sharma Podila wrote: > Pradeep, > > We recently open sourced Fenzo (wiki >

Can health-checks be run by Mesos for docker tasks?

Does Mesos support health checks for docker image tasks? Mesos seems to be ignoring the TaskInfo.HealthCheck field for me. Example TaskInfo JSON received back from Mesos: { > > "name":"hello-app.web.v3", > > "task_id":{ > > "value":"hello-app_web-v3.fc05a1a5-1e06-4e61-9879-be0d97cd3eec"

Re: Can health-checks be run by Mesos for docker tasks?

Hi Jay, We just added health check support for docker tasks that's in master but not yet released. It will run docker exec with the command you provided as health checks. It should be in the next release. Thanks! Tim > On Oct 6, 2015, at 6:49 PM, Jay Taylor wrote: >

Re: Can health-checks be run by Mesos for docker tasks?

Great, thanks for the quick reply Tim! Do you know if there is a branch I can checkout to test it out? On Tue, Oct 6, 2015 at 6:54 PM, Timothy Chen wrote: > Hi Jay, > > We just added health check support for docker tasks that's in master but > not yet released. It will run

Re: Can health-checks be run by Mesos for docker tasks?

Oops- Now I see you already said it's in master. I'll look there :) Thanks again! On Tue, Oct 6, 2015 at 6:59 PM, Jay Taylor wrote: > Great, thanks for the quick reply Tim! > > Do you know if there is a branch I can checkout to test it out? > > On Tue, Oct 6, 2015 at 6:54

Re: Can health-checks be run by Mesos for docker tasks?

I remember 0.23.1 and 0.24.1 contains this backport, let me double check. On Wed, Oct 7, 2015 at 10:01 AM, Jay Taylor wrote: > Oops- Now I see you already said it's in master. I'll look there :) > > Thanks again! > > On Tue, Oct 6, 2015 at 6:59 PM, Jay Taylor

Re: Can health-checks be run by Mesos for docker tasks?

yes, adam also help commit it to 0.23.1 and 0.24.1 https://github.com/apache/mesos/commit/8c0ed92de3925d4312429bfba01b9b1ccbcbbef0 https://github.com/apache/mesos/commit/09e367cd69aa39c156c9326d44f4a7b829ba3db7 Are you use one of this version? On Wed, Oct 7, 2015 at 10:26 AM, haosdent

Re: Can health-checks be run by Mesos for docker tasks?

Could you use "exit 1" instead of "sleep 5" to see whether could see unhealthy status in your task stdout/stderr. On Wed, Oct 7, 2015 at 10:38 AM, Jay Taylor wrote: > My current version is 0.24.1. > > On Tue, Oct 6, 2015 at 7:30 PM, haosdent wrote: > >>

Old docker version deployed

Hello all, I'm new to this list, so please let me know if there is a better/more appropriate forum for this question. We are currently experimenting with marathon and mesos for deploying a simple webapp. We ship the app as a docker container. Sporadically (ie 1 out of 100) we find an

RE: Old docker version deployed

No different tags. From: Rad Gruchalski [mailto:ra...@gruchalski.com] Sent: Tuesday, October 06, 2015 11:39 AM To: user@mesos.apache.org Subject: Re: Old docker version deployed Paul, Are you using the same tag every time? Kind regards,
 Radek Gruchalski 


RE: Old docker version deployed

I do see the stdout in the webgui, which is how I can confirm the old version is deployed. What I need is some information about what version/tag of the image mesos is using. From: haosdent [mailto:haosd...@gmail.com] Sent: Tuesday, October 06, 2015 11:37 AM To: user@mesos.apache.org Subject:

RE: Old docker version deployed

My marathon deploy json: { "type": "DOCKER", "volumes": [ { "containerPath": "/home/myapp /log", "hostPath": "/home", "mode": "RW" } ], "docker": { "image": "docker-registry:8080/myapp:86", "network": "BRIDGE", "portMappings": [ {

Re: Old docker version deployed

You could see the stdout/stderr of your container from mesos webui. On Tue, Oct 6, 2015 at 5:30 PM, Paul Wolfe wrote: > Hello all, > > > > I'm new to this list, so please let me know if there is a better/more > appropriate forum for this question. > > > > We are currently

Re: Old docker version deployed

Paul, Are you using the same tag every time? Kind regards,
 Radek Gruchalski 
ra...@gruchalski.com (mailto:ra...@gruchalski.com)
 (mailto:ra...@gruchalski.com) de.linkedin.com/in/radgruchalski/ (http://de.linkedin.com/in/radgruchalski/) Confidentiality: This communication is intended

Re: Old docker version deployed

I don't think mesos log "version/tag of the image". When mesos start a docker container, always use your image name "docker-registry:8080/myapp:86" as pull and run parameters. I think maybe some machines have problems to connect your image registry. On Tue, Oct 6, 2015 at 5:40 PM, Paul Wolfe

RE: Old docker version deployed

Fair enough, although if that was the case would expect it to fail hard, not randomly run an old image. One thing I did notice was that on the master box, docker images misses the version that should have been deployed (ie has version 77 and 79, but no 78) From: haosdent

Re: Old docker version deployed

Randomly run an old image looks strange, is it because your image registry have problems in some cases? On Tue, Oct 6, 2015 at 5:53 PM, Paul Wolfe wrote: > Fair enough, although if that was the case would expect it to fail hard, > not randomly run an old image. > > > > One

Re: Scheduling tasks based on dependancy

Hi Sharma, Is this how you collect the network info from the VMs? First you get the resource offers from the Mesos and then you collect the network bandwidth info and then you use that for assigning for your tasks? Or The mesos-slave collects the resource information? But I don't see any code to

RE: Old docker version deployed

Turns out it was a “bug” in docker. We found that running by hand the same tag (78) would randomly run version 18. Wouldn’t pull, even though the images wasn’t in the cache. Upgrading from docker 1.7.1 to 1.8.2 seems to solve it, dangerous problem though… From: Rad Gruchalski

command executor stdout with status update

Hello, Is there a way we can add the default command executor output to the status update lifecycle method of Scheduler. Can you please guide to achieve this somehow Thanks, -Bijoy

Re: Scheduling tasks based on dependancy

Hi Guangya, One doubt about the --attributes=rackid:r1;groupid:g1 option. How does the master provisions the resources? How will be the resource offer? Is it like (Rack 1 , G1, System)? how does this way of doing resource offer will help? Can you please give me more information? -Pradeep

Re: command executor stdout with status update

I not suggest you add the stdout/stderr to status update. And you could get stdout/stderr from mesos http endpoint. https://github.com/apache/mesos/blob/master/src/cli/mesos-tail is a example to show how get stdout/stderr through /files/read endpoint. If you want to get status through you command

Broken images in documentation on web

It seems several documentation pages now have broken images, for example: http://mesos.apache.org/documentation/latest/external-containerizer/ (under " Container Lifecycle Sequence Diagrams") http://mesos.apache.org/documentation/latest/oversubscription/ (under "How does it work?") However,

Re: Securing executors

Hi Paul, I can refer you to the talk given by Adam Bordelon at MesosCon https://www.youtube.com/watch?v=G3sn1OLYDOE If you want to the short answer, the solution is to put a firewall around your cluster. On a closer look on the port, it is the

Re: Securing executors

Thanks, Alexander; I will check out the vid. I kind of assumed that this port was used for exactly the purpose you mention. Is TLS a possibility here? -Paul On Tue, Oct 6, 2015 at 8:15 AM, Alexander Rojas wrote: > Hi Paul, > > I can refer you to the talk given by

Re: Scheduling tasks based on dependancy

Hi Pradeep, >From here https://github.com/apache/mesos/blob/master/src/master/master.cpp#L4913 you can see that the offer does include resource attributes, so you can get the filter the offers based on those attribute. Thanks, Guangya On Tue, Oct 6, 2015 at 7:03 PM, Pradeep Kiruvale

Re: ARM64 version Mesos

out of curiosity, which ARM64 server(s) are you guys using? On Tue, Oct 6, 2015 at 12:22 PM, haosdent wrote: > I think this issue maybe helpful for you. > https://issues.apache.org/jira/browse/MESOS-2786 The patches maybe out of > date. > > On Wed, Oct 7, 2015 at 12:13 AM,

Re: Scheduling tasks based on dependancy

Hi Pradeep, We augment the mesos-slave command line on each agent to report the available network bandwidth in Mbps. For example, the agents that have 1Gbps bandwidth have this additional custom resources (--resources command line option) set: "network:1024". This shows up in the offers as a

Re: Scheduling tasks based on dependancy

Pradeep, attributes show up as name value pairs in the offers. Custom attributes can also be used in Fenzo for assignment optimizations. For example, we set custom attributes for AWS EC2 ZONE names and ASG names. We use the ZONE name custom attribute to balance tasks of a job across zones via the

Re: ARM64 version Mesos

I think this issue maybe helpful for you. https://issues.apache.org/jira/browse/MESOS-2786 The patches maybe out of date. On Wed, Oct 7, 2015 at 12:13 AM, Pradeep Kiruvale wrote: > Hi All, > > Is there a Mesos that runs on ARM64? I just tried compiling, its not >

Re: Securing executors

Paul, yes encryption is a possibility since Mesos 0.23. See http://mesos.apache.org/documentation/latest/mesos-ssl/ I believe you can also select which listener port you want to use by specifying LIBPROCESS_PORT in the executor's environment. On Tue, Oct 6, 2015 at 6:59 AM, Paul Bell

ARM64 version Mesos

Hi All, Is there a Mesos that runs on ARM64? I just tried compiling, its not working, has some issues. Please let me know if some one already tried on ARM64. I am trying mesos on a physical box, ubuntu running on it. Regards, Pradeep

Re: ARM64 version Mesos

As of now I am using Applied Micro box. We also have AMD (Seatle) box, Cavium Thunder X and our own home grown ARM boxes. -Pradeep On 6 October 2015 at 18:24, Michael Schenck wrote: > out of curiosity, which ARM64 server(s) are you guys using? > > On Tue, Oct 6, 2015 at