Re: Attendance for Mesos Developer Community Meeting (Nov 17)

+0.9 Is there an agenda in case there are enough attendees? On Wed, Nov 16, 2016 at 3:15 PM, James Peach wrote: > > > On Nov 16, 2016, at 3:06 PM, Michael Park wrote: > > > > If you're planning to attend this meeting, please reply to this before > Nov > >

Re: Attendance for Mesos Developer Community Meeting (Nov 17)

> On Nov 16, 2016, at 3:06 PM, Michael Park wrote: > > If you're planning to attend this meeting, please reply to this before Nov > 17 8am PST. If there are less than 5 people planning to attend (including > me), we'll skip it. +1 > > On Wed, Nov 16, 2016 at 11:02 AM,

Re: Attendance for Mesos Developer Community Meeting (Nov 17)

If you're planning to attend this meeting, please reply to this before Nov 17 8am PST. If there are less than 5 people planning to attend (including me), we'll skip it. On Wed, Nov 16, 2016 at 11:02 AM, Haripriya Ayyalasomayajula < aharipriy...@gmail.com> wrote: > +1. > > On Wed, Nov 16, 2016 at

Re: Mesos V1 Operator HTTP API - Java Proto Classes

Added. Welcome to the contributors list :) On Wed, Nov 16, 2016 at 9:49 AM, Vijay Srinivasaraghavan < vijikar...@yahoo.com> wrote: > I have created a JIRA and will submit a patch. Could someone please add me > to the contributor list as I am not able to assign the JIRA to myself? > >

Re: Attendance for Mesos Developer Community Meeting (Nov 17)

+1. On Wed, Nov 16, 2016 at 10:58 AM, Michael Park wrote: > Many people will be in China for MesosCon, so I'd like to get a quick count > for how many people are planning to join the developer community meeting > tomorrow. > > Please reply with a +1 if you're planning to

Attendance for Mesos Developer Community Meeting (Nov 17)

Many people will be in China for MesosCon, so I'd like to get a quick count for how many people are planning to join the developer community meeting tomorrow. Please reply with a +1 if you're planning to attend.

Re: Mesos V1 Operator HTTP API - Java Proto Classes

I have created a JIRA and will submit a patch. Could someone please add me to the contributor list as I am not able to assign the JIRA to myself? https://issues.apache.org/jira/browse/MESOS-6597 On Wednesday, November 16, 2016 9:00 AM, Anand Mazumdar wrote: We

[GitHub] mesos issue #182: Add TFMesos in frameworks.md

Github user haosdent commented on the issue: https://github.com/apache/mesos/pull/182 @klueska may interest at this. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

Re: Build failed in Jenkins: Mesos » autotools,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2) #2933

Has there been any response from the ASF Infra folks on addressing the VM/hardware issues? Seems like it will be difficult to get good signal from the ASF CI in the absence of some improvements on the infrastructure side. Neil On Wed, Nov 16, 2016 at 10:45 AM, Alex R wrote: >

Re: Mesos V1 Operator HTTP API - Java Proto Classes

We wanted to move the project away from officially supporting anything other than C++ and discuss more on if we should be responsible for publishing to the various language specific channels. However, for the time being, we had decided to include the v1 protobufs in the mesos JAR itself. (it

Re: Mesos V1 Operator HTTP API - Java Proto Classes

I think this is a bug, I feel the jar should include all v1 protobuf files. Vijay, I encourage you to file a ticket. On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan < vijikar...@yahoo.com.invalid> wrote: > I believe the HTTP API will use the same underlying message format (proto > def)

Re: Build failed in Jenkins: Mesos » autotools,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2) #2933

Looks like VM lag again: http://pastebin.com/GZhG4fuN What do folks think about removing future timeouts in tests altogether? Instead, we can time the whole suite differently on different CIs? On 16 November 2016 at 15:30, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

[GitHub] mesos pull request #183: Add PyMesos in api-client-libraries.md

GitHub user windreamer opened a pull request: https://github.com/apache/mesos/pull/183 Add PyMesos in api-client-libraries.md You can merge this pull request into a Git repository by running: $ git pull https://github.com/windreamer/mesos-1 windreamer-patch-3 Alternatively

[GitHub] mesos pull request #182: Add TFMesos in frameworks.md

GitHub user windreamer opened a pull request: https://github.com/apache/mesos/pull/182 Add TFMesos in frameworks.md You can merge this pull request into a Git repository by running: $ git pull https://github.com/windreamer/mesos-1 windreamer-patch-1 Alternatively you can

[GitHub] mesos pull request #181: Add elastic-job -cloud description into frameworks....

GitHub user terrymanu opened a pull request: https://github.com/apache/mesos/pull/181 Add elastic-job -cloud description into frameworks.md You can merge this pull request into a Git repository by running: $ git pull https://github.com/terrymanu/mesos master Alternatively