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

Great! Looks like we have a consensus here! Tomek, you mentioned that you're interested in helping the move. Thank you so much. Can you start with moving the following wiki pages first as they are quite important: 1) https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups

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

+1 (binding) All tests pass on OS X with libev. On Tue, Jun 7, 2016 at 11:48 PM, Jörg Schad wrote: > +1 (Non-Binding) > (sudo) make check on OSX + Update Test Script from 27.2 > > Two test failures (FetcherCacheTest.LocalUncachedExtract and >

Re: [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

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

Hi Vinod, In convert.cpp we compare the major versions of the native library and the jar. This makes upgrading frameworks unnecessarily hard because you would have to deploy Mesos and frameworks in lockstep.

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

Awesome, I'll send a patch. On Wed, Jun 8, 2016 at 9:25 AM, Vinod Kone wrote: > Thanks for catching this bug. We need to fix convert.cpp to make > scheduler/executor upgrades to 1.0 easier. @Robert/@Yan: Can one of you > file a JIRA issue for this? A patch would be even

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

Thanks for catching this bug. We need to fix convert.cpp to make scheduler/executor upgrades to 1.0 easier. @Robert/@Yan: Can one of you file a JIRA issue for this? A patch would be even better :) I'm cancelling the vote for 1.0-RC1 now. We'll cut RC2 after we fix this and any other issues that

Re: WebUI authentication in 1.0.0-rc1

On Wed, Jun 8, 2016 at 4:27 PM, Alexander Rojas wrote: > I think we should also think more thoroughly about the expected behaviour > when we introduce new authorizable actions (and we most certainly will). > Since things may break particularly if users set the

Re: WebUI authentication in 1.0.0-rc1

Maybe we can just supply a default acl template file specifying these defaults acls. Then users will have more guidance when starting to use acls. I will create a sample patch to clarify how I envision such kind of template :-). On Wed, Jun 8, 2016 at 4:27 PM, Alexander Rojas

Re: WebUI authentication in 1.0.0-rc1

I think we should also think more thoroughly about the expected behaviour when we introduce new authorizable actions (and we most certainly will). Since things may break particularly if users set the `permissive` ACL field to false. Perhaps initially, if no ACL is given for the new action we

Re: Does anyone know the MESOS-4675 is back-ported to 0.25?

Done -- https://issues.apache.org/jira/browse/MESOS-5569 On Wed, Jun 8, 2016 at 2:43 PM, Vinod Kone wrote: > +1. Cab you file a jira? > > @vinodkone > >> On Jun 8, 2016, at 7:58 AM, Neil Conway wrote: >> >> It would be great to make this information

Re: Does anyone know the MESOS-4675 is back-ported to 0.25?

+1. Cab you file a jira? @vinodkone > On Jun 8, 2016, at 7:58 AM, Neil Conway wrote: > > It would be great to make this information more prominent on the > website, especially once 1.0.0 is released. For example, we could list > the supported releases on

Re: [1/2] mesos git commit: Added aufs provisioning backend.

The document is being tracked here https://issues.apache.org/jira/browse/MESOS-5549 On Wed, Jun 8, 2016 at 7:29 PM, Neil Conway wrote: > Can you update the documentation for this change, please? > > Thanks, > Neil > > On Tue, Jun 7, 2016 at 6:14 PM,

Re: Does anyone know the MESOS-4675 is back-ported to 0.25?

It would be great to make this information more prominent on the website, especially once 1.0.0 is released. For example, we could list the supported releases on https://mesos.apache.org/downloads/, along with a link to the versioning document. Neil On Tue, Jun 7, 2016 at 6:58 PM, Vinod Kone

Re: [1/2] mesos git commit: Added aufs provisioning backend.

Can you update the documentation for this change, please? Thanks, Neil On Tue, Jun 7, 2016 at 6:14 PM, wrote: > Repository: mesos > Updated Branches: > refs/heads/master 90871a48f -> e5358ed1c > > > Added aufs provisioning backend. > > Review:

Re: how to debug HTTP API

On 06/07/2016 06:29 PM, Vinod Kone wrote: > Olivier, on a side note, it's great to see that you are playing with the > new HTTP API in python! I briefly looked at your linked code and it looks > like you are mixing the business logic of your application and the Mesos > API interaction in the

Re: how to debug HTTP API

On 06/07/2016 05:46 PM, Anand Mazumdar wrote: > Olivier, > > You are missing the “task_infos” key in your “ACCEPT” call. The master treats > “Accept” operations with no launch tasks as declining offers implicitly. I > would file a followup JIRA to ensure this is logged on the master (if not

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

Re: [Compilation Error][aufs] Getting erros compiling latest code on OSX

+1 2016-06-08 9:41 GMT+08:00 Shuai Lin : > Oops, I forgot to put the aufs tests in the block guarded by the __liunx__ > macro, sorry for that. > > I've posted a fix here: https://reviews.apache.org/r/48388/ > > @jieyu please take a look. > > On Wed, Jun 8, 2016 at 9:13