Re: How to record time elapsed of a set of async functions operation?

[haosdent]

Maybe we could integrated Mesos with Zipkin
https://github.com/openzipkin/zipkin , so that it would display the latency
more obviously.

On Sat, Apr 23, 2016 at 7:42 AM, Joris Van Remoortere 
wrote:

> To be clear, BenM's example will result in the total wall-clock time for
> the chain to complete, rather than the sum of time actually spent in those
> functions.
>
>
> —
> *Joris Van Remoortere*
> Mesosphere
>
> On Fri, Apr 22, 2016 at 4:26 PM, Benjamin Mahler 
> wrote:
>
> > Here's an example of using Stopwatch for this:
> >
> > Future f = Nothing();
> > Stopwatch s;
> >
> > s.start();
> > f.then(a)
> >  .then(b)
> >  .then(c)
> >  .onAny([s](){ cout << "a->b->c took: " << s.elapsed() << endl; });
> >
> > On Fri, Apr 22, 2016 at 3:16 AM, Jian Qiu 
> wrote:
> >
> > > Hi folks,
> > >
> > > We are trying to do some performance tests for Mesos, and intend to add
> > log
> > > to output the time duration for different kinds of operation. There is
> a
> > > Stopwatch class that can calculate the time elapsed for a blocking
> call.
> > > However, I am wondering if there is some utility to record the time
> > elapsed
> > > for a async call chain. For instance, Mesos always have a chain like
> > >  future.then(xxx).onAny.  Is there anyway to calculate the whole
> time
> > > elapsed of this kind of chain instead of printing out the time stamp?
> > >
> > > Thanks.
> > >
> > > Regards
> > > Qiu Jian
> > >
> >
>



-- 
Best Regards,
Haosdent Huang

Re: Running Mesos agent on ARM (Raspberry Pi)?

[tommy xiao]

the alternative way, use Docker on rpi to containerised the mesos master
and slave, it also cool things.

2016-04-23 1:38 GMT+08:00 Dario Rexin :

> Hi Sharma,
>
> I played around with Mesos on RPi a while back and have been able to
> compile and run it with 2 little patches.
>
> 1) Depending on the ZK version, it may be necessary to patch a function
> that uses inline ASM to use the resp. compiler intrinsics (I don’t remember
> where exactly in zk it was, but the compile error should tell you)
>
> 2) There is string formatting code somewhere that compiles, but is not
> architecture independent, i.e. behaves different on 32 and 64 bit. IIRC the
> fix was to change %lu to %llu or something close to that. The stack trace
> when Mesos crashes should tell you. If you’re lucky enough to have an RPi3,
> this may not be necessary.
>
> Also, if you compile on the RPi make sure to create a swap file of
> >=512MB. The build process will use lots of memory. I have not been able to
> compile on multiple cores, because the memory usage was just too high.
>
> I hope this helps.
>
> On Apr 22, 2016, at 10:23 AM, Tomek Janiszewski  wrote:
>
> As @haosdent mentioned with Kevin we tried to run it on ARM. AFAIR there
> was a problem only with master, agents runs smoothly (or pretend to). To
> run it on RPi you need to compile it for ARM. Easy but long solution is to
> compile it on rpi. Quick but a little bit harder  cross compile it on
> "normal" machine and upload to device.
>
>
> http://likemagicappears.com/projects/raspberry-pi-cluster/mesos-on-raspbian/
>
> pt., 22 kwi 2016, 19:02 użytkownik haosdent  napisał:
>
>> Tomek have a gsoc proposal to make Mesos build on ARM
>> https://docs.google.com/document/d/1zbms2jQfExuIm6g-adqaXjFpPif6OsqJ84KAgMrOjHQ/edit
>> I think you could take a look at this code in github
>> https://github.com/lyda/mesos-on-arm
>>
>> On Sat, Apr 23, 2016 at 12:53 AM, Sharma Podila 
>> wrote:
>>
>>> We are working on a hack to run Mesos agents on Raspberry Pi and are
>>> wondering if anyone here has done that before. From the Google search
>>> results we looked at so far, it seems like it has been compiled, but we
>>> haven't seen an indication that anyone has run it and launched tasks on
>>> them. And does it sound right that it might take 4 hours or so to compile?
>>>
>>> We are looking to run just the agents. The master will be on a regular
>>> Ubuntu laptop or a server.
>>>
>>> Appreciate any pointers.
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>


-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Shepherd for MESOS-4279 (Graceful restart of docker task)

[Benjamin Mahler]

If any bugs were discovered in
https://issues.apache.org/jira/browse/MESOS-4279, could we file new tickets
for them? It would be nice to distinguish the investigation/triaging of
user reports from the bugs that we end up finding in mesos. If I were to
see the following ticket (e.g. in the CHANGELOG):

MESOS-4279 - Graceful restart of docker task

It reads like the introduction of a feature, and if I open it I realize
it's a bug report but I can't easily find the underlying issue(s).

On Fri, Jan 8, 2016 at 11:22 PM, Qian Zhang  wrote:

> Sure, I have added you as the shepherd, thanks Tim!
>
> 2016-01-09 1:44 GMT+08:00 Timothy Chen :
>
> > I'll shepherd this, can you add me to the jira?
> >
> > Thanks,
> >
> > Tim
> >
> > > On Jan 8, 2016, at 7:04 AM, Qian Zhang  wrote:
> > >
> > > Hi,
> > >
> > > Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-4279?
> I
> > > have posted some findings there, we can do further discussion in the
> > ticket.
> > >
> > >
> > > Thanks,
> > > Qian Zhang
> >
>

Re: How to record time elapsed of a set of async functions operation?

[Joris Van Remoortere]

To be clear, BenM's example will result in the total wall-clock time for
the chain to complete, rather than the sum of time actually spent in those
functions.


—
*Joris Van Remoortere*
Mesosphere

On Fri, Apr 22, 2016 at 4:26 PM, Benjamin Mahler  wrote:

> Here's an example of using Stopwatch for this:
>
> Future f = Nothing();
> Stopwatch s;
>
> s.start();
> f.then(a)
>  .then(b)
>  .then(c)
>  .onAny([s](){ cout << "a->b->c took: " << s.elapsed() << endl; });
>
> On Fri, Apr 22, 2016 at 3:16 AM, Jian Qiu  wrote:
>
> > Hi folks,
> >
> > We are trying to do some performance tests for Mesos, and intend to add
> log
> > to output the time duration for different kinds of operation. There is a
> > Stopwatch class that can calculate the time elapsed for a blocking call.
> > However, I am wondering if there is some utility to record the time
> elapsed
> > for a async call chain. For instance, Mesos always have a chain like
> >  future.then(xxx).onAny.  Is there anyway to calculate the whole time
> > elapsed of this kind of chain instead of printing out the time stamp?
> >
> > Thanks.
> >
> > Regards
> > Qiu Jian
> >
>

Re: How to record time elapsed of a set of async functions operation?

[Benjamin Mahler]

Here's an example of using Stopwatch for this:

Future f = Nothing();
Stopwatch s;

s.start();
f.then(a)
 .then(b)
 .then(c)
 .onAny([s](){ cout << "a->b->c took: " << s.elapsed() << endl; });

On Fri, Apr 22, 2016 at 3:16 AM, Jian Qiu  wrote:

> Hi folks,
>
> We are trying to do some performance tests for Mesos, and intend to add log
> to output the time duration for different kinds of operation. There is a
> Stopwatch class that can calculate the time elapsed for a blocking call.
> However, I am wondering if there is some utility to record the time elapsed
> for a async call chain. For instance, Mesos always have a chain like
>  future.then(xxx).onAny.  Is there anyway to calculate the whole time
> elapsed of this kind of chain instead of printing out the time stamp?
>
> Thanks.
>
> Regards
> Qiu Jian
>

Re: Outdated mesos staging repositories in Nexus

[Vinod Kone]

Thanks Stian for bringing this up.

Looks like the release managers for the releases are not properly dropping
the RC repos :(

The release managers use a script (./support/release.sh) that automates
some of the steps but it doesn't automate the maven/nexus parts
unfortunately. It just spits out a log line "please release the staging
repo", but that could be easily missed by the release managers.

Would be great if you or someone can send a PR that can automate the maven
parts in vote.sh script.

I'll drop the stale staging repos for now.

Thanks for the PR for the website, btw. We will get that fixed.

On Fri, Apr 22, 2016 at 7:49 AM, Stian Soiland-Reyes 
wrote:

> Hi,
>
> I noticed in https://repository.apache.org/#stagingRepositories
>
> there are multiple outdated Mesos staging repositories, e.g.
>
> https://repository.apache.org/content/repositories/orgapachemesos-1122/
> (0.24.2)
> https://repository.apache.org/content/repositories/orgapachemesos-1128/
> (0.26.1)
>
> To me this seems to indicate an ongoing release vote.
>
> However the latest published release in
>
> https://repository.apache.org/content/repositories/releases/org/apache/mesos/mesos/
>
> is 0.28.1 - and 0.24.2 and 0.26.1 are also published.
>
>
> Would it be in order to Drop these repositories?
>
>
> BTW - I also noticed you published release candidate versions like
> http://central.maven.org/maven2/org/apache/mesos/mesos/0.26.1-rc3/
>
> to Maven Central - which is a bit confusing to me - as I can't see the
> "-rc" versions on
> http://mesos.apache.org/downloads/
>
> Are these official releases?
>
> See http://www.apache.org/dev/release.html#host-rc
>
>
>
>
> BTW:
>
> 0.28.1 is not listed on http://mesos.apache.org/downloads/
>
>
> And the download links for 0.28.0 there does not work:
>
> http://www.apache.org/dyn/mirrors/mirrors.cgi/mesos/0.28.0/
>
> just sends me to the top of the mirror, e.g.
> http://apache.mirror.anlx.net/
>
> I believe the link should be like this:
>
> http://www.apache.org/dyn/closer.cgi/mesos/0.28.1/mesos-0.28.1.tar.gz
>
>
> I suggested both fixes in https://github.com/apache/mesos/pull/97
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/-0001-9842-9718
>

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Dario Rexin]

Hi Sharma,

I played around with Mesos on RPi a while back and have been able to compile 
and run it with 2 little patches.

1) Depending on the ZK version, it may be necessary to patch a function that 
uses inline ASM to use the resp. compiler intrinsics (I don’t remember where 
exactly in zk it was, but the compile error should tell you)

2) There is string formatting code somewhere that compiles, but is not 
architecture independent, i.e. behaves different on 32 and 64 bit. IIRC the fix 
was to change %lu to %llu or something close to that. The stack trace when 
Mesos crashes should tell you. If you’re lucky enough to have an RPi3, this may 
not be necessary.

Also, if you compile on the RPi make sure to create a swap file of >=512MB. The 
build process will use lots of memory. I have not been able to compile on 
multiple cores, because the memory usage was just too high.

I hope this helps.

> On Apr 22, 2016, at 10:23 AM, Tomek Janiszewski  wrote:
> 
> As @haosdent mentioned with Kevin we tried to run it on ARM. AFAIR there was 
> a problem only with master, agents runs smoothly (or pretend to). To run it 
> on RPi you need to compile it for ARM. Easy but long solution is to compile 
> it on rpi. Quick but a little bit harder  cross compile it on "normal" 
> machine and upload to device.
> 
> http://likemagicappears.com/projects/raspberry-pi-cluster/mesos-on-raspbian/ 
> 
> pt., 22 kwi 2016, 19:02 użytkownik haosdent  > napisał:
> Tomek have a gsoc proposal to make Mesos build on ARM 
> https://docs.google.com/document/d/1zbms2jQfExuIm6g-adqaXjFpPif6OsqJ84KAgMrOjHQ/edit
>  
> 
>  I think you could take a look at this code in github 
> https://github.com/lyda/mesos-on-arm 
> 
> On Sat, Apr 23, 2016 at 12:53 AM, Sharma Podila  > wrote:
> We are working on a hack to run Mesos agents on Raspberry Pi and are 
> wondering if anyone here has done that before. From the Google search results 
> we looked at so far, it seems like it has been compiled, but we haven't seen 
> an indication that anyone has run it and launched tasks on them. And does it 
> sound right that it might take 4 hours or so to compile?
> 
> We are looking to run just the agents. The master will be on a regular Ubuntu 
> laptop or a server. 
> 
> Appreciate any pointers.
>  
> 
> 
> 
> 
> -- 
> Best Regards,
> Haosdent Huang

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Tomek Janiszewski]

As @haosdent mentioned with Kevin we tried to run it on ARM. AFAIR there
was a problem only with master, agents runs smoothly (or pretend to). To
run it on RPi you need to compile it for ARM. Easy but long solution is to
compile it on rpi. Quick but a little bit harder  cross compile it on
"normal" machine and upload to device.

http://likemagicappears.com/projects/raspberry-pi-cluster/mesos-on-raspbian/

pt., 22 kwi 2016, 19:02 użytkownik haosdent  napisał:

> Tomek have a gsoc proposal to make Mesos build on ARM
> https://docs.google.com/document/d/1zbms2jQfExuIm6g-adqaXjFpPif6OsqJ84KAgMrOjHQ/edit
> I think you could take a look at this code in github
> https://github.com/lyda/mesos-on-arm
>
> On Sat, Apr 23, 2016 at 12:53 AM, Sharma Podila 
> wrote:
>
>> We are working on a hack to run Mesos agents on Raspberry Pi and are
>> wondering if anyone here has done that before. From the Google search
>> results we looked at so far, it seems like it has been compiled, but we
>> haven't seen an indication that anyone has run it and launched tasks on
>> them. And does it sound right that it might take 4 hours or so to compile?
>>
>> We are looking to run just the agents. The master will be on a regular
>> Ubuntu laptop or a server.
>>
>> Appreciate any pointers.
>>
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: [Performance Isolation] Meeting on Thursday April 21 2016 5pm PST

[Ian Downes]

Likewise, I tried calling but no one was hosting the meeting.

On Fri, Apr 22, 2016 at 10:04 AM, Kevin Klues  wrote:

> I tried calling into this last night, but no one was there.  Was it
> post-poned again?
>
> On Mon, Apr 18, 2016 at 12:03 PM, Niklas Nielsen  wrote:
> > Hi everyone,
> >
> > Per our conversation about Intel CAT enablement in Mesos, we are
> scheduling
> > a Performance Isolation Working Group meeting at Thursday April 21 2016
> > 5pm-6pm PST.
> >
> > Feel free to suggest agenda topics here:
> >
> https://docs.google.com/document/d/11mlGPZSABItP47J6VX-zB0fAK6Qr1mCIOI7nhlATMqk/edit#
> >
> > Also, let's use this hangout to meet:
> >
> https://hangouts.google.com/hangouts/_/intel.com/mesos-performance-isolation?hl=en=1
> >
> > Cheers,
> > Niklas
>
>
>
> --
> ~Kevin
>

Re: [Performance Isolation] Meeting on Thursday April 21 2016 5pm PST

[Kevin Klues]

I tried calling into this last night, but no one was there.  Was it
post-poned again?

On Mon, Apr 18, 2016 at 12:03 PM, Niklas Nielsen  wrote:
> Hi everyone,
>
> Per our conversation about Intel CAT enablement in Mesos, we are scheduling
> a Performance Isolation Working Group meeting at Thursday April 21 2016
> 5pm-6pm PST.
>
> Feel free to suggest agenda topics here:
> https://docs.google.com/document/d/11mlGPZSABItP47J6VX-zB0fAK6Qr1mCIOI7nhlATMqk/edit#
>
> Also, let's use this hangout to meet:
> https://hangouts.google.com/hangouts/_/intel.com/mesos-performance-isolation?hl=en=1
>
> Cheers,
> Niklas



-- 
~Kevin

Re: Running Mesos agent on ARM (Raspberry Pi)?

[haosdent]

Tomek have a gsoc proposal to make Mesos build on ARM
https://docs.google.com/document/d/1zbms2jQfExuIm6g-adqaXjFpPif6OsqJ84KAgMrOjHQ/edit
I think you could take a look at this code in github
https://github.com/lyda/mesos-on-arm

On Sat, Apr 23, 2016 at 12:53 AM, Sharma Podila  wrote:

> We are working on a hack to run Mesos agents on Raspberry Pi and are
> wondering if anyone here has done that before. From the Google search
> results we looked at so far, it seems like it has been compiled, but we
> haven't seen an indication that anyone has run it and launched tasks on
> them. And does it sound right that it might take 4 hours or so to compile?
>
> We are looking to run just the agents. The master will be on a regular
> Ubuntu laptop or a server.
>
> Appreciate any pointers.
>
>
>


-- 
Best Regards,
Haosdent Huang

Re: mesos git commit: Add /containers endpoint.

[haosdent]

Sorry for didn't see Jay's patch before, I have rebased mine.

On Sat, Apr 23, 2016 at 12:24 AM, Jie Yu  wrote:

> Haosdent, since your patch depends on some other changes. I'll commit Jay's
> patch first.
>
> On Fri, Apr 22, 2016 at 8:17 AM, Jay JN Guo  wrote:
>
> > Hi,
> >
> > The script was run and submitted here:
> https://reviews.apache.org/r/46075/
> >
> > It was not committed along with the patch though. I've sent a notice to
> > @Jie.
> >
> > Since the change is included in the patch as @haosdent mentioned, I guess
> > we could drop the one I created.
> >
> > Thanks for reminding!
> >
> > Cheers,
> > /J
> >
> > haosdent  wrote on 04/22/2016 22:57:53:
> >
> > > From: haosdent 
> > > To: dev 
> > > Date: 04/22/2016 22:59
> > > Subject: Re: mesos git commit: Add /containers endpoint.
> > >
> > > I notice this new endpoint today. I think it have already included in
> > > https://reviews.apache.org/r/46472/
> > >
> > > On Fri, Apr 22, 2016 at 10:54 PM, Neil Conway 
> > wrote:
> > >
> > > > Folks,
> > > >
> > > > When adding a new endpoint or modifying the help text of an existing
> > > > endpoint, we should rerun the `support/generate-endpoint-help.py`
> > > > script.
> > > >
> > > > Neil
> > > >
> > > >
> > > > On Thu, Apr 21, 2016 at 8:49 PM,   wrote:
> > > > > Repository: mesos
> > > > > Updated Branches:
> > > > >   refs/heads/master fa55a69a2 -> 90f7645cc
> > > > >
> > > > >
> > > > > Add /containers endpoint.
> > > > >
> > > > > It returns both resource statistics and container status.
> > > > >
> > > > > Review: https://reviews.apache.org/r/45014/
> > > > >
> > > > >
> > > > > Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> > > > > Commit:
> http://git-wip-us.apache.org/repos/asf/mesos/commit/90f7645c
> > > > > Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/90f7645c
> > > > > Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/90f7645c
> > > > >
> > > > > Branch: refs/heads/master
> > > > > Commit: 90f7645cc51d43b63990aec4d0c5e37423b584f0
> > > > > Parents: fa55a69
> > > > > Author: Jay Guo 
> > > > > Authored: Thu Apr 21 09:48:10 2016 -0700
> > > > > Committer: Jie Yu 
> > > > > Committed: Thu Apr 21 17:48:59 2016 -0700
> > > > >
> > > > >
> > --
> > > > >  src/slave/http.cpp  | 135
> ++
> > +++
> > > > >  src/slave/slave.cpp |   6 ++
> > > > >  src/slave/slave.hpp |   5 ++
> > > > >  src/tests/containerizer.cpp |   3 +
> > > > >  src/tests/containerizer.hpp |   4 ++
> > > > >  src/tests/slave_tests.cpp   | 139
> > > > +++
> > > > >  6 files changed, 292 insertions(+)
> > > > >
> > --
> > > > >
> > > > >
> > > > >
> > > > http://git-wip-us.apache.org/repos/asf/mesos/blob/90f7645c/src/
> > > slave/http.cpp
> > > > >
> > --
> > > > > diff --git a/src/slave/http.cpp b/src/slave/http.cpp
> > > > > index 3908e33..f887a71 100644
> > > > > --- a/src/slave/http.cpp
> > > > > +++ b/src/slave/http.cpp
> > > > > @@ -14,9 +14,11 @@
> > > > >  // See the License for the specific language governing permissions
> > and
> > > > >  // limitations under the License.
> > > > >
> > > > > +#include 
> > > > >  #include 
> > > > >  #include 
> > > > >  #include 
> > > > > +#include 
> > > > >
> > > > >  #include 
> > > > >
> > > > > @@ -25,6 +27,7 @@
> > > > >  #include 
> > > > >  #include 
> > > > >
> > > > > +#include 
> > > > >  #include 
> > > > >  #include 
> > > > >  #include 
> > > > > @@ -74,7 +77,9 @@ using process::http::UnsupportedMediaType;
> > > > >
> > > > >  using process::metrics::internal::MetricsProcess;
> > > > >
> > > > > +using std::list;
> > > > >  using std::string;
> > > > > +using std::tuple;
> > > > >
> > > > >
> > > > >  namespace mesos {
> > > > > @@ -626,6 +631,136 @@ Future Slave::Http::statistics(
> > > > >  });
> > > > >  }
> > > > >
> > > > > +
> > > > > +string Slave::Http::CONTAINERS_HELP()
> > > > > +{
> > > > > +  return HELP(
> > > > > +  TLDR(
> > > > > +  "Retrieve container status and usage information."),
> > > > > +  DESCRIPTION(
> > > > > +  "Returns the current resource consumption data and
> status
> > > > for",
> > > > > +  "containers running under this slave.",
> > > > > +  "",
> > > > > +  "Example (**Note**: this is not exhaustive):",
> > > > > +  "",
> > > > > +  "```",
> > > > > +  "[{",
> > > > > +  "\"container_id\":\"container\",",
> > > > > +  "\"container_status\":",
> > > > > +  "{",
> > > > > +  "\"network_infos\":",
> > > > > 

Re: mesos git commit: Add /containers endpoint.

[Jie Yu]

Haosdent, since your patch depends on some other changes. I'll commit Jay's
patch first.

On Fri, Apr 22, 2016 at 8:17 AM, Jay JN Guo  wrote:

> Hi,
>
> The script was run and submitted here: https://reviews.apache.org/r/46075/
>
> It was not committed along with the patch though. I've sent a notice to
> @Jie.
>
> Since the change is included in the patch as @haosdent mentioned, I guess
> we could drop the one I created.
>
> Thanks for reminding!
>
> Cheers,
> /J
>
> haosdent  wrote on 04/22/2016 22:57:53:
>
> > From: haosdent 
> > To: dev 
> > Date: 04/22/2016 22:59
> > Subject: Re: mesos git commit: Add /containers endpoint.
> >
> > I notice this new endpoint today. I think it have already included in
> > https://reviews.apache.org/r/46472/
> >
> > On Fri, Apr 22, 2016 at 10:54 PM, Neil Conway 
> wrote:
> >
> > > Folks,
> > >
> > > When adding a new endpoint or modifying the help text of an existing
> > > endpoint, we should rerun the `support/generate-endpoint-help.py`
> > > script.
> > >
> > > Neil
> > >
> > >
> > > On Thu, Apr 21, 2016 at 8:49 PM,   wrote:
> > > > Repository: mesos
> > > > Updated Branches:
> > > >   refs/heads/master fa55a69a2 -> 90f7645cc
> > > >
> > > >
> > > > Add /containers endpoint.
> > > >
> > > > It returns both resource statistics and container status.
> > > >
> > > > Review: https://reviews.apache.org/r/45014/
> > > >
> > > >
> > > > Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> > > > Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/90f7645c
> > > > Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/90f7645c
> > > > Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/90f7645c
> > > >
> > > > Branch: refs/heads/master
> > > > Commit: 90f7645cc51d43b63990aec4d0c5e37423b584f0
> > > > Parents: fa55a69
> > > > Author: Jay Guo 
> > > > Authored: Thu Apr 21 09:48:10 2016 -0700
> > > > Committer: Jie Yu 
> > > > Committed: Thu Apr 21 17:48:59 2016 -0700
> > > >
> > > >
> --
> > > >  src/slave/http.cpp  | 135 ++
> +++
> > > >  src/slave/slave.cpp |   6 ++
> > > >  src/slave/slave.hpp |   5 ++
> > > >  src/tests/containerizer.cpp |   3 +
> > > >  src/tests/containerizer.hpp |   4 ++
> > > >  src/tests/slave_tests.cpp   | 139
> > > +++
> > > >  6 files changed, 292 insertions(+)
> > > >
> --
> > > >
> > > >
> > > >
> > > http://git-wip-us.apache.org/repos/asf/mesos/blob/90f7645c/src/
> > slave/http.cpp
> > > >
> --
> > > > diff --git a/src/slave/http.cpp b/src/slave/http.cpp
> > > > index 3908e33..f887a71 100644
> > > > --- a/src/slave/http.cpp
> > > > +++ b/src/slave/http.cpp
> > > > @@ -14,9 +14,11 @@
> > > >  // See the License for the specific language governing permissions
> and
> > > >  // limitations under the License.
> > > >
> > > > +#include 
> > > >  #include 
> > > >  #include 
> > > >  #include 
> > > > +#include 
> > > >
> > > >  #include 
> > > >
> > > > @@ -25,6 +27,7 @@
> > > >  #include 
> > > >  #include 
> > > >
> > > > +#include 
> > > >  #include 
> > > >  #include 
> > > >  #include 
> > > > @@ -74,7 +77,9 @@ using process::http::UnsupportedMediaType;
> > > >
> > > >  using process::metrics::internal::MetricsProcess;
> > > >
> > > > +using std::list;
> > > >  using std::string;
> > > > +using std::tuple;
> > > >
> > > >
> > > >  namespace mesos {
> > > > @@ -626,6 +631,136 @@ Future Slave::Http::statistics(
> > > >  });
> > > >  }
> > > >
> > > > +
> > > > +string Slave::Http::CONTAINERS_HELP()
> > > > +{
> > > > +  return HELP(
> > > > +  TLDR(
> > > > +  "Retrieve container status and usage information."),
> > > > +  DESCRIPTION(
> > > > +  "Returns the current resource consumption data and status
> > > for",
> > > > +  "containers running under this slave.",
> > > > +  "",
> > > > +  "Example (**Note**: this is not exhaustive):",
> > > > +  "",
> > > > +  "```",
> > > > +  "[{",
> > > > +  "\"container_id\":\"container\",",
> > > > +  "\"container_status\":",
> > > > +  "{",
> > > > +  "\"network_infos\":",
> > > > +  "
> > > [{\"ip_addresses\":[{\"ip_address\":\"192.168.1.1\"}]}]",
> > > > +  "}",
> > > > +  "\"executor_id\":\"executor\",",
> > > > +  "\"executor_name\":\"name\",",
> > > > +  "\"framework_id\":\"framework\",",
> > > > +  "\"source\":\"source\",",
> > > > +  "\"statistics\":",
> > > > +  "{",
> > > > +  "

Re: Can I be a contributor in JIRA?

[Artem Harutyunyan]

Done. Welcome to the community!

On Thu, Apr 21, 2016 at 11:17 AM, Li, Bing  wrote:
> Hi there,
>
> I'm enabling Mesos on System z.
>
> I just opened MESOS-5241 .
> I'll open related issues under it.
>
> Thanks,
>
>
>
> Li, Bing

Re: mesos git commit: Add /containers endpoint.

[Jay JN Guo]

Hi,

The script was run and submitted here: https://reviews.apache.org/r/46075/

It was not committed along with the patch though. I've sent a notice to
@Jie.

Since the change is included in the patch as @haosdent mentioned, I guess
we could drop the one I created.

Thanks for reminding!

Cheers,
/J

haosdent  wrote on 04/22/2016 22:57:53:

> From: haosdent 
> To: dev 
> Date: 04/22/2016 22:59
> Subject: Re: mesos git commit: Add /containers endpoint.
>
> I notice this new endpoint today. I think it have already included in
> https://reviews.apache.org/r/46472/
>
> On Fri, Apr 22, 2016 at 10:54 PM, Neil Conway 
wrote:
>
> > Folks,
> >
> > When adding a new endpoint or modifying the help text of an existing
> > endpoint, we should rerun the `support/generate-endpoint-help.py`
> > script.
> >
> > Neil
> >
> >
> > On Thu, Apr 21, 2016 at 8:49 PM,   wrote:
> > > Repository: mesos
> > > Updated Branches:
> > >   refs/heads/master fa55a69a2 -> 90f7645cc
> > >
> > >
> > > Add /containers endpoint.
> > >
> > > It returns both resource statistics and container status.
> > >
> > > Review: https://reviews.apache.org/r/45014/
> > >
> > >
> > > Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> > > Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/90f7645c
> > > Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/90f7645c
> > > Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/90f7645c
> > >
> > > Branch: refs/heads/master
> > > Commit: 90f7645cc51d43b63990aec4d0c5e37423b584f0
> > > Parents: fa55a69
> > > Author: Jay Guo 
> > > Authored: Thu Apr 21 09:48:10 2016 -0700
> > > Committer: Jie Yu 
> > > Committed: Thu Apr 21 17:48:59 2016 -0700
> > >
> > >
--
> > >  src/slave/http.cpp  | 135 ++
+++
> > >  src/slave/slave.cpp |   6 ++
> > >  src/slave/slave.hpp |   5 ++
> > >  src/tests/containerizer.cpp |   3 +
> > >  src/tests/containerizer.hpp |   4 ++
> > >  src/tests/slave_tests.cpp   | 139
> > +++
> > >  6 files changed, 292 insertions(+)
> > >
--
> > >
> > >
> > >
> > http://git-wip-us.apache.org/repos/asf/mesos/blob/90f7645c/src/
> slave/http.cpp
> > >
--
> > > diff --git a/src/slave/http.cpp b/src/slave/http.cpp
> > > index 3908e33..f887a71 100644
> > > --- a/src/slave/http.cpp
> > > +++ b/src/slave/http.cpp
> > > @@ -14,9 +14,11 @@
> > >  // See the License for the specific language governing permissions
and
> > >  // limitations under the License.
> > >
> > > +#include 
> > >  #include 
> > >  #include 
> > >  #include 
> > > +#include 
> > >
> > >  #include 
> > >
> > > @@ -25,6 +27,7 @@
> > >  #include 
> > >  #include 
> > >
> > > +#include 
> > >  #include 
> > >  #include 
> > >  #include 
> > > @@ -74,7 +77,9 @@ using process::http::UnsupportedMediaType;
> > >
> > >  using process::metrics::internal::MetricsProcess;
> > >
> > > +using std::list;
> > >  using std::string;
> > > +using std::tuple;
> > >
> > >
> > >  namespace mesos {
> > > @@ -626,6 +631,136 @@ Future Slave::Http::statistics(
> > >  });
> > >  }
> > >
> > > +
> > > +string Slave::Http::CONTAINERS_HELP()
> > > +{
> > > +  return HELP(
> > > +  TLDR(
> > > +  "Retrieve container status and usage information."),
> > > +  DESCRIPTION(
> > > +  "Returns the current resource consumption data and status
> > for",
> > > +  "containers running under this slave.",
> > > +  "",
> > > +  "Example (**Note**: this is not exhaustive):",
> > > +  "",
> > > +  "```",
> > > +  "[{",
> > > +  "\"container_id\":\"container\",",
> > > +  "\"container_status\":",
> > > +  "{",
> > > +  "\"network_infos\":",
> > > +  "
> > [{\"ip_addresses\":[{\"ip_address\":\"192.168.1.1\"}]}]",
> > > +  "}",
> > > +  "\"executor_id\":\"executor\",",
> > > +  "\"executor_name\":\"name\",",
> > > +  "\"framework_id\":\"framework\",",
> > > +  "\"source\":\"source\",",
> > > +  "\"statistics\":",
> > > +  "{",
> > > +  "\"cpus_limit\":8.25,",
> > > +  "\"cpus_nr_periods\":769021,",
> > > +  "\"cpus_nr_throttled\":1046,",
> > > +  "\"cpus_system_time_secs\":34501.45,",
> > > +  "\"cpus_throttled_time_secs\":352.597023453,",
> > > +  "\"cpus_user_time_secs\":96348.84,",
> > > +  "\"mem_anon_bytes\":4845449216,",
> > > +  "\"mem_file_bytes\":260165632,",
> > > +  "

Re: mesos git commit: Add /containers endpoint.

[haosdent]

I notice this new endpoint today. I think it have already included in
https://reviews.apache.org/r/46472/

On Fri, Apr 22, 2016 at 10:54 PM, Neil Conway  wrote:

> Folks,
>
> When adding a new endpoint or modifying the help text of an existing
> endpoint, we should rerun the `support/generate-endpoint-help.py`
> script.
>
> Neil
>
>
> On Thu, Apr 21, 2016 at 8:49 PM,   wrote:
> > Repository: mesos
> > Updated Branches:
> >   refs/heads/master fa55a69a2 -> 90f7645cc
> >
> >
> > Add /containers endpoint.
> >
> > It returns both resource statistics and container status.
> >
> > Review: https://reviews.apache.org/r/45014/
> >
> >
> > Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/90f7645c
> > Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/90f7645c
> > Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/90f7645c
> >
> > Branch: refs/heads/master
> > Commit: 90f7645cc51d43b63990aec4d0c5e37423b584f0
> > Parents: fa55a69
> > Author: Jay Guo 
> > Authored: Thu Apr 21 09:48:10 2016 -0700
> > Committer: Jie Yu 
> > Committed: Thu Apr 21 17:48:59 2016 -0700
> >
> > --
> >  src/slave/http.cpp  | 135 +
> >  src/slave/slave.cpp |   6 ++
> >  src/slave/slave.hpp |   5 ++
> >  src/tests/containerizer.cpp |   3 +
> >  src/tests/containerizer.hpp |   4 ++
> >  src/tests/slave_tests.cpp   | 139
> +++
> >  6 files changed, 292 insertions(+)
> > --
> >
> >
> >
> http://git-wip-us.apache.org/repos/asf/mesos/blob/90f7645c/src/slave/http.cpp
> > --
> > diff --git a/src/slave/http.cpp b/src/slave/http.cpp
> > index 3908e33..f887a71 100644
> > --- a/src/slave/http.cpp
> > +++ b/src/slave/http.cpp
> > @@ -14,9 +14,11 @@
> >  // See the License for the specific language governing permissions and
> >  // limitations under the License.
> >
> > +#include 
> >  #include 
> >  #include 
> >  #include 
> > +#include 
> >
> >  #include 
> >
> > @@ -25,6 +27,7 @@
> >  #include 
> >  #include 
> >
> > +#include 
> >  #include 
> >  #include 
> >  #include 
> > @@ -74,7 +77,9 @@ using process::http::UnsupportedMediaType;
> >
> >  using process::metrics::internal::MetricsProcess;
> >
> > +using std::list;
> >  using std::string;
> > +using std::tuple;
> >
> >
> >  namespace mesos {
> > @@ -626,6 +631,136 @@ Future Slave::Http::statistics(
> >  });
> >  }
> >
> > +
> > +string Slave::Http::CONTAINERS_HELP()
> > +{
> > +  return HELP(
> > +  TLDR(
> > +  "Retrieve container status and usage information."),
> > +  DESCRIPTION(
> > +  "Returns the current resource consumption data and status
> for",
> > +  "containers running under this slave.",
> > +  "",
> > +  "Example (**Note**: this is not exhaustive):",
> > +  "",
> > +  "```",
> > +  "[{",
> > +  "\"container_id\":\"container\",",
> > +  "\"container_status\":",
> > +  "{",
> > +  "\"network_infos\":",
> > +  "
> [{\"ip_addresses\":[{\"ip_address\":\"192.168.1.1\"}]}]",
> > +  "}",
> > +  "\"executor_id\":\"executor\",",
> > +  "\"executor_name\":\"name\",",
> > +  "\"framework_id\":\"framework\",",
> > +  "\"source\":\"source\",",
> > +  "\"statistics\":",
> > +  "{",
> > +  "\"cpus_limit\":8.25,",
> > +  "\"cpus_nr_periods\":769021,",
> > +  "\"cpus_nr_throttled\":1046,",
> > +  "\"cpus_system_time_secs\":34501.45,",
> > +  "\"cpus_throttled_time_secs\":352.597023453,",
> > +  "\"cpus_user_time_secs\":96348.84,",
> > +  "\"mem_anon_bytes\":4845449216,",
> > +  "\"mem_file_bytes\":260165632,",
> > +  "\"mem_limit_bytes\":7650410496,",
> > +  "\"mem_mapped_file_bytes\":7159808,",
> > +  "\"mem_rss_bytes\":5105614848,",
> > +  "\"timestamp\":1388534400.0",
> > +  "}",
> > +  "}]",
> > +  "```"));
> > +}
> > +
> > +
> > +Future Slave::Http::containers(const Request& request) const
> > +{
> > +  Owned metadata(new list());
> > +  list statusFutures;
> > +  list statsFutures;
> > +
> > +  foreachvalue (const Framework* framework, slave->frameworks) {
> > +foreachvalue (const Executor* executor, framework->executors) {
> > +  const ExecutorInfo& info = executor->info;
> > +  const ContainerID& containerId = executor->containerId;
> > +
> > +  JSON::Object entry;