Re: [VOTE] Release Apache Mesos 0.27.3 (rc1)

+1 (Non-Binding) (sudo) make check on OSX + Update Test Script from 27.2 Two test failures (FetcherCacheTest.LocalUncachedExtract and FetcherCacheHttpTest.HttpMixed) which are both known and fixed in later versions. On Tue, Jun 7, 2016 at 9:52 PM, Vinod Kone wrote: > +1 (binding) > > Tested on

Fwd: [VOTE] Release Apache Mesos 1.0.0 (rc1)

What do you think about this Vinod? I think we can remove this major version checking altogether. Backwards-incompatible changes would warrant a major version bump but not vise versa. Plus it's more standard to express and check dependency versions outside of the code but through package metadata.

Re: Mesos 0.24.1 on Raspberry Pi 3

@ Spyker I found these $40/each arm64v8 board, with 2 G of ram each. It would be keen if we many folks interested in mesos on arm64v8, could agree at least on a low cost dev board to work on for mesos development, imho. I'd really like embedded arm64v8 boards with 4 gig of ram. https://archlin

Re: Mesos 0.24.1 on Raspberry Pi 3

That systemd is required for mesos 0.25+ would be news to me, since we've run at least 0.24 through 0.28.1 on Ubuntu 14.04, which is Upstart-based. On Tue, Jun 7, 2016 at 9:18 AM, Joris Van Remoortere wrote: > All versions of mesos *should* work without systemd. The intent was to add > *support*

Re: Mesos 0.24.1 on Raspberry Pi 3

FYI ... We were not able to compile latest master or 0.28.1. What we saw was that the linking step ran out of memory - well beyond the 1G of physical and 1G of swap. We considered some linking options to trade off memory, but haven't tried them. On Tue, Jun 7, 2016 at 12:18 PM, Joris Van Remoort

Re: [VOTE] Release Apache Mesos 0.27.3 (rc1)

+1 (binding) Tested on ASF CI (NOTE: The failing build for ubuntu + gcc is a red herring) *Revision*: 68dd1f6a12c321a21a7e6e257d5a23b41d127273 - refs/tags/0.27.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl [image: Success]

Re: [VOTE] Release Apache Mesos 1.0.0 (rc1)

Here is a link to the rpm/deb packages for Mesos 1.0.0-rc1: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc1 Please note that from this release (>=1.0.0-rc1) onwards, we are configuring Mesos with SSL support. We have also added `--enable-install-module-dependencies` configur

Re: 0.28.2 has been released

Hi All, The 0.28.2 rpm/deb packages can be found here: http://open.mesosphere.com/downloads/mesos/#apache-mesos-0.28.2 Best, Kapil On Mon, Jun 6, 2016 at 5:21 PM, Kapil Arya wrote: > Hi Craig, > > I should be sending out a link to the RPM packages in a couple of days. > (Our packaging scri

Re: [VOTE] Release Apache Mesos 0.27.3 (rc1)

+1 (binding) Ran CI builds for various distros. The deb/rpm packages can be found here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-0.27.3-rc1 Kapil On Tue, Jun 7, 2016 at 1:42 PM, Jie Yu wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos

[VOTE] Release Apache Mesos 0.27.3 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.27.3. NOTE: I fat fingered and accidentally released the 0.27.3 jar to maven repo and I have no permission to remove it (apologies!). If this vote passes, nothing needs to be done. If not, I'll see how I can update it. Sor

Re: Set LIBPROCESS_IP for frameworks launched with marathon

Tom, We’ve discussed the ‘plucking’ earlier. It would be desired to move away from having to set a file on the agent. Think - DC/OS. As a user, you may have no chance to access the filesystem. I get that the order might be not what the user would expect. Hence I’d be more towards the latter optio

Re: Mesos 0.24.1 on Raspberry Pi 3

All versions of mesos *should* work without systemd. The intent was to add *support* for systemd, not make it a requirement. If specific version of mesos *don't* work without systemd then that is a bug, and it would be awesome if you could share specific issues (we can make JIRAs). The purpose of

Re: Rack awareness support for Mesos

On Tuesday, June 7, 2016, Du, Fan wrote: > > > On 2016/6/6 23:48, Jörg Schad wrote: > >> Hi, >> thanks for your idea and design doc! >> Just a few thoughts: >> a) The scheduling part would be implemented in a framework scheduler and >> not the Mesos Core, or? >> > > I'm not sure which level of sc

Re: Mesos 0.24.1 on Raspberry Pi 3

Just the opposite, I'm mostly interested in mesos without systemd on bard metal, minimized linux systems. So with that temporal requirement, what is the latest version of mesos that one can run without systemd? James On 06/07/2016 10:35 AM, Joris Van Remoortere wrote: It should be straightfo

Re: Rack awareness support for Mesos

+dev. @Fan, I responded on the JIRA with some next steps. Thanks for bringing this up! — *Joris Van Remoortere* Mesosphere On Tue, Jun 7, 2016 at 12:58 PM, james wrote: > On 06/07/2016 09:57 AM, Du, Fan wrote: > >> >> >> On 2016/6/6 21:27, james wrote: >> >>> Hello, >>> >>> >>> @Stephen::I gue

Re: Rack awareness support for Mesos

On 06/07/2016 09:57 AM, Du, Fan wrote: On 2016/6/6 21:27, james wrote: Hello, @Stephen::I guess Stephen is bringing up the 'security' aspect of who get's access to the information, particularly cluster/cloud devops, customers or interlopers? ACLs should play in this part to address sec

RE: Rack awareness support for Mesos

Would this perhaps make sense as a mesos module which can automatically assigns labels to the agents, rather than something in the core itself? -- Aaron Carey Production Engineer - Cloud Pipeline Industrial Light & Magic London 020 3751 9150 From: Du, Fa

Re: Mesos 0.24.1 on Raspberry Pi 3

It should be straightforward to apply the patch that adds the `systemd_enable_support` flag to older releases. Let me know if you need help! — *Joris Van Remoortere* Mesosphere On Tue, Jun 7, 2016 at 11:28 AM, haosdent wrote: > No, it is mandatory in 0.25. `systemd_enable_support` is added sinc

Re: Mesos 0.24.1 on Raspberry Pi 3

Oh, my bad about `systemd_enable_support`. That's to explicitly disable systemd support, when running with systemd. Before that, systemd related features were enabled when systemd was available. But Mesos still runs fine in systems without systemd, so I wouldn't call it mandatory. On Tue, Jun 7, 2

Re: Mesos 0.24.1 on Raspberry Pi 3

No, it is mandatory in 0.25. `systemd_enable_support` is added since 0.27 https://issues.apache.org/jira/browse/MESOS-4675 On Tue, Jun 7, 2016 at 11:21 PM, Jan Schlicht wrote: > It's not mandatory. There's the `systemd_enable_support` flag to enable > some systemd related features on an agent bu

Re: Mesos 0.24.1 on Raspberry Pi 3

It's not mandatory. There's the `systemd_enable_support` flag to enable some systemd related features on an agent but it can be disabled. Cheers, Jan On Tue, Jun 7, 2016 at 3:55 PM, james wrote: > > I thought systemd was not mandatory in version 0.25 and later? > > James > > > On 06/07/2016 07:

Re: Set LIBPROCESS_IP for frameworks launched with marathon

Actually not only LIBPROCESS_IP, some SSL related environment didn't pass as well. @Cody @Tim, is it OK that pass flags.executor_environment_variables to the Docker container? [1]: https://issues.apache.org/jira/browse/MESOS-3740 On Tue, Jun 7, 2016 at 9:25 AM, Radoslaw Gruchalski wrote: > Yes,

Re: Rack awareness support for Mesos

On 2016/6/6 23:48, Jörg Schad wrote: Hi, thanks for your idea and design doc! Just a few thoughts: a) The scheduling part would be implemented in a framework scheduler and not the Mesos Core, or? I'm not sure which level of scheduling part do you indicate, For the "Future" section of proposal

Re: Re: make check crashes

Hi Alexander, this is a really good point! My locale is a mix between the US and DE locale: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US LC_CTYPE="en_US.UTF-8" LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY=de_DE.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=de_DE.UTF-8 LC

Re: Set LIBPROCESS_IP for frameworks launched with marathon

>>> Maybe it would be a good idea if Mesos was setting env variables named >>> AGENT_IP_0, AGENT_IP_1 and so on for every IP interface on the agent, maybe >>> AGENT_BIND_IP if bind IP is different than 0.0.0.0 That said, it’d be tricky to always be sure that IP_0 was the one you wanted. If the

Re: Rack awareness support for Mesos

On 2016/6/6 21:27, james wrote: Hello, @Stephen::I guess Stephen is bringing up the 'security' aspect of who get's access to the information, particularly cluster/cloud devops, customers or interlopers? ACLs should play in this part to address security concern. @Fan:: As a consultant

Re: Set LIBPROCESS_IP for frameworks launched with marathon

Currently I have it configured to use host networking Thanks Eli > On 7 Jun 2016, at 11:25, Radoslaw Gruchalski wrote: > > Yes, because that runs in host network. This leads to a question: your docker > task, is it bridge or host network. > > -- > Best regards, > Rad > > > > > On Tue, Ju

Re: Mesos 0.24.1 on Raspberry Pi 3

I thought systemd was not mandatory in version 0.25 and later? James On 06/07/2016 07:42 AM, tommy xiao wrote: only 0.24 can work on it. 0.25 use systemd and can't ignore it. 2016-06-07 7:50 GMT+08:00 Benjamin Mahler mailto:bmah...@apache.org>>: Cool stuff Andrew, thanks for sharing!

Re: Mesos 0.24.1 on Raspberry Pi 3

only 0.24 can work on it. 0.25 use systemd and can't ignore it. 2016-06-07 7:50 GMT+08:00 Benjamin Mahler : > Cool stuff Andrew, thanks for sharing! > > On Thu, Jun 2, 2016 at 11:50 AM, Andrew Spyker > > wrote: > > > FYI, based on the work others have done in the past, Netflix was able to > > ge

Re: Proposal: move content in Wiki to docs in code repo

+1, good point. 2016-06-07 3:18 GMT+08:00 Vinod Kone : > Works for me. Some things we might miss from wiki would be comments and > ability to watch for updates; but I don't think many people use them. > > On Mon, Jun 6, 2016 at 3:15 PM, Gilbert Song > wrote: > >> +1. >> >> At least I personally

Re: [VOTE] Release Apache Mesos 1.0.0 (rc1)

Hi, the authorization documentation in the RC seems to be messing some changes introduced by https://issues.apache.org/jira/browse/MESOS-5405. We already added and committed fixes as part this ticket (see https://issues.apache.org/jira/browse/MESOS-5405?focusedCommentId=15318058&page=com.atlassian.