+1 (non-binding)
Built and installed on Ubuntu 10.04 + 14.04
Configured with --disable-java --enable-python --disable-bundled-pip
--disable-python-dependency-install
On 04.11.2016 14:15, Till Toenshoff wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.1.0.
process and stout that they were never set.
> Good point about trusty not including gcc 4.9. Do you think it would be
> acceptable to instruct people to take it from the toolchain PPA?
> https://wiki.ubuntu.com/ToolChain#PPA_packages
>
> Thanks,
> Aaron
>
> On 10/10/16, 2:18 P
Hi,
I think this would break the build on ubuntu trusty, the latest natively
available version there is 4.8.2
Also, glancing at your review, I feel like `-Wall -Werror` is somewhat
of an anti-pattern, it just seems to guarantee that the build will break
whenever the compiler writers decide to add
ilable
> for dual stack Mesos (possibly --ip and --ip6 both would be allowed), and
> more importantly what would be the interaction between Mesos v6 masters,
> with Mesos v4 clients or vice versa, would be really helpful.
>
> On Fri, Sep 23, 2016 at 7:41 AM, Evers Benno wrote:
&
Hi,
some of you may faintly remember my announcement that we're planning to
add IPv6 support for Mesos roughly half a year ago.
While the idea was met favorably, and there seems to be a general
consensus that it is a good feature to have, there was also a feeling
that a more detailed design docum
ra/browse/MESOS-4548
> https://issues.apache.org/jira/browse/MESOS-5322
>
> Neil
>
>
> On Wed, Jul 13, 2016 at 3:27 PM, Evers Benno wrote:
>> Let me try to clarify:
>>
>> The problem is that I don't get to decide manually if the framwork
>> shoul
more intuitive)
On 13.07.2016 14:50, Neil Conway wrote:
> On Wed, Jul 13, 2016 at 2:44 PM, Evers Benno wrote:
>> imagine the following situation: I am a framework with failover timeout
>> of 1 hour, and 59 minutes and 55 seconds after shutting down I want to
>> register with t
Hi all,
imagine the following situation: I am a framework with failover timeout
of 1 hour, and 59 minutes and 55 seconds after shutting down I want to
register with the master again.
If my registration attempt arrives at the master within the time limit
everything will be fine and I even get back
Sure,
it looks like this, not very imaginative. There is currently no
authorization on the agents.
{
"permissive": false,
[...] // Here is the previous ACL with actions "run_tasks" and
"register_frameworks"
"get_endpoints": [
{
"principals
t; MPark
>
> On 3 June 2016 at 12:36, Evers Benno wrote:
>
>>
>> I just tried building and running the 1.0.0-rc1, and it seems that the
>> web UI is broken due to /metrics/snapshot returning a 403. (There's a
>> popup continously displaying "Failed to conn
I just tried building and running the 1.0.0-rc1, and it seems that the
web UI is broken due to /metrics/snapshot returning a 403. (There's a
popup continously displaying "Failed to connect to
mesos-master.example.org:5050!"
I'm running mesos-master with options `--no-authenticate_http
--acls={"pe
A random guess, but gdb tends to load shared libraries only after you do
"run" for the first time, maybe that's what's missing?
Apart from this, after installation mesos is just a normal c++ binary,
so you could bypass libtool by installing in some custom prefix (not
sure how to do this on mac) an
ll
status updates on executor shutdown.
It would be great if someone would like to shepherd this.
Best regards,
Benno
On 03.05.2016 14:49, Evers Benno wrote:
> Hi,
>
> I was wondering about the semantics of the Executor::sendStatusUpdate()
> method. It is described as
>
&g
; Benno—
>
> you may be seeing MESOS-4111
> <https://issues.apache.org/jira/browse/MESOS-4111>. Also, have a
> look at this comment:
> https://github.com/apache/mesos/blob/9f472b1eff904d0d96063d3bed535a8e81263d69/src/launcher/executor.cpp#L611-L617
>
>
>
On Tu
Hi,
I was wondering about the semantics of the Executor::sendStatusUpdate()
method. It is described as
// Sends a status update to the framework scheduler, retrying as
// necessary until an acknowledgement has been received or the
// executor is terminated (in which case, a TASK_LOST
Hi all,
sorry in advance for the wall of text below :)
I went ahead and implemented a proof-of-concept, and things seem to work
quite well so far: I have a mesos-master and a mesos-slave on different
machines in an IPv6-only network, and I'm able run RENDLER jobs on them.
The one unexpected issu
Hi,
can you please add me as a contributor in JIRA? My username is "bennoe".
Thanks,
Benno
I just wanted to note that there are some existing packages doing this
already.
For example the thunderbird-dev package on ubuntu (>= trusty) has
several private library headers in e.g. /usr/include/thunderbird/gmock
or /usr/include/thunderbird/google/protobuf
On 27.01.2016 16:28, Kapil Arya wrot
e un-assigned and removed the shepherd on this, no work has taken place
>> for some time.
>>
>> Glad to see you're using Mesos! There is currently no shepherd for IPv6
>> support, but it would be great if you could publish a design document for
>> feedback after
Hi all,
after looking through the mesos source code for a while, here are
some of my initial thoughts.
There seem to be at least two issues that can be tackled separately:
- Communication between mesos daemons over the network
- Communication in and out of containers when using network isolatio
Hello all,
We are currently planning to deploy a mesos cluster for internal use in
Yandex.Maps.
Since the ability to work on IPv6-only hosts is necessary for us, we are
planning to start working on the necessary patches in the coming weeks,
and to contribute our progress.
Work towards full IPv6
21 matches
Mail list logo
