Can we use http://doodle.com/ to arrive at consensus regarding time slot?
@vinodkone
> On Jun 22, 2017, at 8:07 AM, Judith Malnick wrote:
>
> Hi everyone,
>
> Thanks for the interest! I know many of you are in Asia for MesosCon, so I'm
> just going to propose a few
The only required skill is interest in that package :).
There are many different tasks including development, testing, building
docker images, documentation
We will discuss details in during the meeting.
Joerg
On Wed, Jun 21, 2017 at 7:33 PM, wrote:
> Hi,
>
Did you see my slack message?
On Wed, Jun 21, 2017 at 9:56 PM, Stavros Kontopoulos <
st.kontopou...@gmail.com> wrote:
> Will be there as I have already started working on that.
>
> best,
> Stavros
>
> On Wed, Jun 21, 2017 at 2:33 PM, wrote:
>
>> Hi,
>>
>>
Here's the earlier email which has the feature comparison:
https://lists.apache.org/thread.html/527a29b45c52a042c122c96754804983b1447b7409ffec3d635b7143@%3Cdev.mesos.apache.org%3E
The list is still accurate, except that precompiled headers are no longer
"upcoming".
On Wed, Jun 21, 2017 at 4:42
Hi Aaron,
I'd like to expand on what Andy said:
If you want cross-platform development, then cmake is the only way to go. For
example, if you want to build on Windows, you MUST use cmake. We anticipate,
over time, that cmake will replace the autotools build (we do not want to
maintain two
Hi Aaron,
The biggest difference right now is that the Java and Python bindings are not
built whatsoever with the CMake build system. We also do not have an install
target, so the CMake output is kind of stuck in “developer mode” and it won’t
generate an installable package.
I probably would
Hi all,
I'm curious as to what the current state of came is on Linux. I noticed that
some features that are present in the autotools build are not yet in cmake.
Also, the output from a successful cmake build looks a bit different as far as
the number of libraries that are produced and the
Thank you all for the feedback.
To summarize, not killing tasks for non-Partition Aware frameworks will make
the schedulers see a higher volume of non terminal updates for tasks for which
they have already received a TASK_LOST but nothing new that they are not seeing
today. So, this shouldn’t
Thanks,
But I think Mesos right now uses Proto2, not Proto3.
If I switch entirely to a REST server with ProtocalBuffer, I think this
will be fully compatible with Mesos?
Thanks
Wenzhao
On Wed, Jun 21, 2017 at 3:53 AM, James Peach wrote:
>
> > On Jun 20, 2017, at 11:23 AM,
My bad. Fixed this now, hopefully.
On Wed, Jun 21, 2017 at 8:38 PM, wrote:
> Repository: mesos-site
> Updated Branches:
> refs/heads/asf-site 9bed07c77 -> 1a235ab5a
>
>
> Updated the website built from mesos SHA: ae76475.
>
>
> Project:
Hi,
we are actively looking for contributors (and anyone interested) for the
Flink DC/OS package, as well as the Mesos Flink framework.
We will have a first meeting to explain the current package and
outline/develop a potential roadmap in the next virtual DC/OS office hours:
Very excited and happy to join!
On Sat, Jun 17, 2017 at 1:38 AM, James Peach wrote:
>
> > On Jun 15, 2017, at 10:57 AM, Vinod Kone wrote:
> >
> > Hi folks,
> >
> > Seeing that our first official containerizer WG is off to a good start,
> we
> > want to
> On Jun 20, 2017, at 11:23 AM, Wenzhao Zhang wrote:
>
> Hello, All:
>
> I'm working on an independent server, which should be able to talk to the
> master via HTTP POST requests.
> I setup a Jersey REST server. My initial plan is to use *JSON/XML* to map
> Entities, as
13 matches
Mail list logo