Re: Build failed in Jenkins: mesos-reviewbot #6201

On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > checking for C++ compiler version... 4.8.2 > checking for C++ compiler vendor... (cached) gnu > configure: error: GCC 4.8 or higher required (found 4.8.2) > hmm. this looks weird.

Re: Mesos Jira workflow

+jake Marco, this sounds good to me. Have you looked into see if JIRA allows us to constrain ourselves to this workflow? If yes, the next step would be to work with ASF infra to see if they are ok with us adopting a new workflow. IIRC, there are some JIRA settings that are global to all ASF projec

Re: Checking if Framework has capabilities

We currently don't show the capabilities in the UI. You could add that info to state.json though where we model the framework. Mind sending a patch for that? Also, the requestReesources() call is currently a no op. @vinodkone > On Jun 18, 2015, at 8:06 AM, Aditi Dixit wrote: > > Well current

Re: Help required in doing Reregistration

Can you send us the gist? @vinodkone > On Jun 19, 2015, at 8:49 AM, Aditi Dixit wrote: > > Hi, > Thanks for the responses haosdent and Adam. > I'm sorry if I wasn't clear enough, but yes, the patch exactly does what > Adam just mentioned. > We create 2 instances of the driver and in the second

Re: [Breaking Change 0.24, MESOS 1988] Silently ignore launchTask/acceptOffers calls when disconnected

Hi guys, I asked Anand to sent that email out, so let me chime in. First off, looks like the motivation for this change was not properly communicated to the list. I was under the impression that we had a public discussion about this when I originally introduced this behavior (back in 2013). But I

Re: Weekly Update

Thanks Aditi for the update! On Wed, Jun 24, 2015 at 12:08 PM, Aditi Dixit wrote: >- I also talked with Adam and Till regarding exposing the FrameworkInfo >as a whole in the state HTTP endpoint. They said that it wouldn't be a >problem. So, I wanted to know what you guys think before

Re: Weekly Update

, Jun 25, 2015 at 12:50 AM, Vinod Kone wrote: > > Most of the FrameworkInfo fields are already exposed. What did you mean by > > exposing it as a whole? Did you mean having a field in the JSON (say > > "info") that uses the default Protobuf to JSON converter? > > > > Yeah, that's exactly what I meant :) >

Re: [Breaking Change 0.24 & Upgrade path] ZooKeeper MasterInfo change.

Just to clarify, any frameworks that are using the Mesos provided bindings (aka libmesos.so) should not worry, as long as the version of the bindings and version of the mesos master are not separated by more than 1 version. In other words, you should be able to live upgrade a cluster from 0.23.0 to

Re: Cannot add Resolution to Resolved issues

Thanks Jake! I also bulk transitioned the erroneously reopened issues back to resolved. On Thu, Jul 2, 2015 at 11:48 AM, Jake Farrell wrote: > I updated the workflow to take care of this, should be all set now > > -Jake > > On Thu, Jul 2, 2015 at 1:54 PM, Marco Massenzio > wrote: > > > Just he

Re: [VOTE] Release Apache Mesos 0.23.0 (rc3)

Found a bug in HTTP API related code: MESOS-3055 If we don't fix this in 0.23.0, we cannot expect the 0.24.0 scheduler driver (that will send Calls) to properly subscribe with a 0.23.0 master. I could add a work around in the driver to only send C

Re: [VOTE] Release Apache Mesos 0.23.0 (rc3)

t; > Sent from Mailbox <https://www.dropbox.com/mailbox> > > > > > > On Thu, Jul 16, 2015 at 3:10 PM, Timothy Chen wrote: > > > >> As Adam mention I also think this is not a blocker, as it only affects > >> the way we test the cgroup on CentOS 7.x

Re: RFC: QuiesceOffers message

I will be happy to shepherd this. Have you looked at MESOS-3037 that was filed recently for essentially the same thing? We can add filters to that call too. Do you want this in the current API (scheduler driver) or can you wait until the HTTP API

Are any allocator modules relying on requestResources() call?

requestResources() call was added to the scheduler driver a long time ago, but was never implemented by the built-in hierarchical allocator. One of the reasons for not implementing it was that it wasn't clear how it should be used in the face of DRF. I was thinking to remove the code dealing with

Re: [VOTE] Release Apache Mesos 0.23.0 (rc4)

+1 (binding) Successfully built RPMs for CentOS5 and CentOS6 with network isolator. On Fri, Jul 17, 2015 at 4:56 PM, Khanduja, Vaibhav wrote: > +1 > > Sent from my iPhone. Please excuse the typos and brevity of this message. > > > On Jul 17, 2015, at 4:43 PM, Adam Bordelon wrote: > > > > Hell

Re: Are any allocator modules relying on requestResources() call?

of policies in our mechanism!! > > > > Regards, > Gidon > > > > > > > > From: Vinod Kone > To: dev > Date: 18/07/2015 03:03 AM > Subject:Are any allocator modules relying on requestResources() > call? > > > >

Prepping for next release

Hi folks, I will be the release manager for the upcoming release (ETA early August). To prep for the release (and make my life easy) I'm planning to remove the target versions for all *unresolved* tickets that have a target version 0.24.0. I would like folks to explicitly set the target version

Re: Prepping for next release

wrote: > Or odd number version is no stable version while the even number version is > a stable version, just like HBase. > > On Wed, Jul 22, 2015 at 2:22 AM, haosdent wrote: > > > Is it too fast to release 0.24, because 0.23 is still rc3 now. > > > > On Wed, Jul

Re: Prepping for next release

So far, we have maintained compatibility with version N and N-1. Regarding support, we typically support the latest release and the previous release. On Tue, Jul 21, 2015 at 12:52 PM, James Peach wrote: > > > On Jul 21, 2015, at 11:46 AM, Vinod Kone wrote: > > > > I

Re: Introducing a CMake-based build system for Mesos

This is exciting! Thanks for sharing the progress Alex. Mind sending us instructions on how to build/test with cmake for noobs like me? On Wed, Jul 22, 2015 at 2:19 PM, Kevin Lyda wrote: > On Wed, Jul 22, 2015 at 10:12 PM, Alex Clemmer > wrote: > > depends on (cf. MESOS-898[2]). In the near fu

Re: Introducing a CMake-based build system for Mesos

n Thu, Jul 23, 2015 at 11:27 AM, Marco Massenzio < > ma...@mesosphere.io> > >> > wrote: > >> > > >> >> This is really cool! > >> >> Eclipse CDT is becoming a bit tiresome to use, but JetLabs' CLion > only > >> >>

Re: Introducing a CMake-based build system for Mesos

be a FATAL_ERROR or a WARNING. I > recommend being at parity with autotools -- am I correct in assuming > that it errors out? > > On Thu, Jul 23, 2015 at 12:12 PM, Vinod Kone wrote: > > The one thing I found odd while testing was that some errors when running > > 'cm

Re: Where's Meses design documents

Ideally, all design docs that are finalized should go to Mesos's cwiki space . We have some there already. @all: if you've finalized (i.e., corresponding code has been committed) design docs please move them to the cwiki space. Let me know

Re: RFC: batch-only allocations

Can I ask why you want to do this change in the first place? On Mon, Jul 27, 2015 at 2:11 PM, James Peach wrote: > Hi all, > > See MESOS-3157 for more details. I'd like mesos-master to only do resource > allocation from the periodic batch callback, never from reviveOffers, > addFramework, etc. C

Re: RFC: batch-only allocations

Never mind. Just saw MESOS-3157 On Mon, Jul 27, 2015 at 2:22 PM, Vinod Kone wrote: > Can I ask why you want to do this change in the first place? > > On Mon, Jul 27, 2015 at 2:11 PM, James Peach wrote: > >> Hi all, >> >> See MESOS-3157 for more details. I&

Re: Autoscaling in an IaaS environment

Thanks for pinging again Mathieu! I think auto-scaling of a Mesos cluster is a nifty feature to have. The only question in my mind (and likely others) is whether this functionality should reside in Mesos, or a framework or an operator. As you mentioned, Netflix took the framework way but it doesn'

Re: Ask a Shepherd for MESOS-3070 (Master CHECK failure if a framework uses duplicated task id)

On Fri, Jul 31, 2015 at 2:11 AM, Klaus Ma wrote: > solution for this ticket J. > I'll be happy to shepherd.

Design doc for HTTP API versioning

Hi folks, As part of our effort to introduce a new HTTP API for Mesos, we have also started to formulate a plan for how we want to version our API. The design doc for the versioning is here

Re: Docker socket path for slave

Added you to the contributors. On Mon, Aug 3, 2015 at 9:47 AM, Khanduja, Vaibhav wrote: > Hi Peter, > > Thanks for your reply. > > The change for docker daemon options is probably has to be in slave code > and not int the framework. Other than marathon, there could be other > framework requirin

Re: Mesos Contribution Request

Welcome Tim. This doc might help you get a sense of the current state of authN and where it is going. On Wed, Aug 5, 2015 at 9:53 AM, Timothy Anderegg wrote: > Yeah, I thought it was a

Re: Prepping for next release

based release, but we might want to keep some of these targeted > so we can track the priority issues. When the actual rc1 cut date > approaches, it's pretty easy to aggressively push things out of the release > that haven't made it. Let me know what you think. > > Cheers, &g

Re: Re-opening an issue (aka - Un-Resolving it)

Ah. That's confusing. Is there no way we can fix the schema to not do this? I'm assuming you already asked INFRA? On a side note, is it possible to make the "Shepherd" field mandatory when a task transitions from Accepted --> Assigned? I think this will force users to find shepherds before they st

Re: Apache Mesos Community Sync

s issues currently facing our >>> developers. >>> >>> Please add agenda items to the same doc we've been using for previous >>> meetings' Agenda/Notes: >>> >>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lz

Re: Prepping for next release

Removed the target versions for all unresolved tickets (except for HTTP scheduler API ones) targeted for 0.24.0 <https://issues.apache.org/jira/browse/MESOS-2562> Hoping to cut an RC tomorrow. On Wed, Aug 5, 2015 at 11:31 AM, Vinod Kone wrote: > Hi, > > The tracking ticket

Re: Prepping for next release

-2841 > in 0.24.0. Currently in review. > > Any chance that can make it in? > > > On Wed, Aug 12, 2015 at 1:16 PM, Vinod Kone wrote: > > > Removed the target versions for all unresolved tickets (except for HTTP > > scheduler API ones) targeted for 0.24.0 > > <https

Re: Prepping for next release

DeFelice > > wrote: > > > > > > Hi Vinod, > > > > > > Would *really* like to see > > https://issues.apache.org/jira/browse/MESOS-2841 > > > in 0.24.0. Currently in review. > > > > > > Any chance that can make it in? > > > > >

Re: Prepping for next release

p 1] On Mon, Aug 17, 2015 at 11:23 AM, Vinod Kone wrote: > Update: > > There are 3 outstanding tickets (all related to flaky tests), that we are > trying to resolve. Any help fixing those (esp. MESOS-3050 > <https://issues.apache.org/jira/browse/MESOS-3050>) would be apprec

Re: Prepping for next release

your gpg key properly set up > with Maven? > > On Tue, Aug 18, 2015 at 1:13 PM, Vinod Kone wrote: > > > I'm getting the following error when running ./support/tag.sh. Has any of > > the recent release managers seen this one before? > > > > [ERROR] Fai

Re: Prepping for next release

On Tue, Aug 18, 2015 at 1:48 PM, Vinod Kone wrote: > > > I definitely had to create a new gpg key because my previous one > expired! I > > uploaded them id.apache and our SVN repo containing KEYS. > > > > Do I need to do anything specific for maven? > > > >

[VOTE] Release Apache Mesos 0.24.0 (rc1)

0.24.0 includes the following: Experimental support for v1 scheduler HTTP API! This release also wraps up support for fetcher. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/as

Re: Coverity Scan

+Vinson Vinson from Twitter is the one who set up the CI job* for automatic upload to Coverity. AFAICT, the job has been uploading artifacts to coverity as recently as Aug 22nd. Not sure why there were no results since May. * we need to move that job from Twitter CI to ASF CI. On Thu, Aug 20, 20

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

ding) >>> >>> All tests (including ROOT) pass on: >>> Ubuntu 14.04 (physical box) >>> >>> All non-ROOT tests pass on: >>> CentOS 7 (VirtualBox VM) >>> >>> Known issue (MESOS-3050) for ROOT tests on CentOS 7, non-blocker. >>>

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

temIsolatorTest.ROOT_VolumeFromSandbox >>> >>> [ FAILED ] LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost >>> >>> [ FAILED ] >>> LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint >>> >>> [ FAILED ] >>> Linux

Guidelines for new contributors

Hi folks, I've seen a bunch of new contributors and contributions pop up lately (awesome!), so wanted to take some time to provide some guidelines to newbies as its been a bit chaotic. Hopefully this will be part of the newbie doc that Tim and Diana are working on. *Shepherds*: It is really impor

Re: seeking a shepherd for autotools build changes

Tim, looks like you already reviewed some of these patches? Do you have cycles to shepherd this? On Wed, Aug 26, 2015 at 1:16 PM, James Peach wrote: > Hi all, > > Is anyone willing to shepherd or otherwise provide feedback on MESOS-2537? > > https://reviews.apache.org/r/33752/ >

Re: Prepping for next release

t use JDK7 when uploading. Not sure how easy it is to adapt our Mesos build tool chain for this. Anyone has expertise in this area? Thoughts? On Tue, Aug 18, 2015 at 3:14 PM, Vinod Kone wrote: > I re-encrypted the maven passwords and that seemed to have done the trick. > Thanks Adam! > &g

Re: Prepping for next release

here. On Tue, Sep 1, 2015 at 5:03 PM, Kevin Sweeney wrote: > I'm generally in favor of dropping support for JDK6 as it's been > end-of-life for years. > > On Tue, Sep 1, 2015 at 4:46 PM, Vinod Kone wrote: > >> +user >> >> So looks like this issue is rela

[VOTE] Release Apache Mesos 0.24.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.24.0. 0.24.0 includes the following: Experimental support for v1 scheduler HTTP API! This release also wraps up support for fetcher. Th

API client libraries

Hi folks, Now that the v1 scheduler HTTP API (beta) is on the verge of being released, I wanted to open up the discussion about client libraries for the API. Mainly around support and home for the libs. One idea is that, going forward, the only supported client library would be C++ library which

Re: Apache Mesos Community Sync

We'll have the next community sync tomorrow (Sept 3rd) at 3 PM PST. Please add items to agenda <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#heading=h.u1x3j7f3uixf> . On Wed, Aug 5, 2015 at 4:12 PM, Vinod Kone wrote: > We'll have the

Re: API client libraries

On Wed, Sep 2, 2015 at 11:49 AM, Vinod Kone wrote: > --> Might be a step backward because we would be officially dropping > support for Java and Python. This is probably a good thing? > s/officially dropping support/dropping official support/

[RESULT][VOTE] Release Apache Mesos 0.24.0 (rc2)

tested on our CI > > On Tuesday, September 1, 2015, Vinod Kone wrote: > >> Hi all, >> >> >> Please vote on releasing the following candidate as Apache Mesos 0.24.0. >> >> >> 0.24.0 includes the following: >> >> >> ---

brew install mesos doesn't work for 0.24.0

I'm trying to update the homebrew formula per the release guide . But when following instructions from homebrew regarding testing the changes

Re: brew install mesos doesn't work for 0.24.0

dLineTools/usr/lib/libsvn_delta-1.0.dylib > /Library/Developer/CommandLineTools/usr/lib/libsvn_delta-1.dylib > ... > > (this is where my understanding of homebrew ends, I'm afraid) > > *Marco Massenzio* > > *Distributed Systems Engineerhttp://codetrips.com <http://codetrip

Re: brew install mesos doesn't work for 0.24.0

hen, that simply doing: > > LD_LIBRARYPATH=/opt/twitter:$LD_LIBRARYPATH > > would solve the issue? > > > *Marco Massenzio* > > *Distributed Systems Engineerhttp://codetrips.com <http://codetrips.com>* > >> On Mon, Sep 14, 2015 at 7:44 PM, James Peach w

Re: Working Group List

+1 On Fri, Sep 18, 2015 at 10:55 AM, Niklas Nielsen wrote: > Hi folks, > > Per our last community meeting, I created a list on our Confluence Wiki to > keep track of and increase visibility into the running working groups. > We have previously created these groups implicitly, and as the communit

Re: MESOS-3421: Support sharing persistent volumes across task instances

I think shared persistent volumes are a great feature addition! Couple things that need to be addressed --> Who gets charged for the shared disk quota if multiple tasks share them? I'm assuming the one who creates a RW copy? --> How does the resource handling logic work in Mesos if a resource is

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

+1 (binding) Tested on CI for CentOS5 and CentOS6. On Fri, Sep 18, 2015 at 6:21 PM, Adam Bordelon wrote: > Hi friends, > > Please vote on releasing the following candidate as Apache Mesos 0.24.1. > > 0.24.1 includes the following: > >

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

+1 (binding) Tested on CI for centos5/6 @vinodkone > On Sep 23, 2015, at 3:45 PM, Adam Bordelon wrote: > > +1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04. > >> On Wed, Sep 23, 2015 at 10:25 AM, haosdent wrote: >> >> +1 test on Ubuntu 14.04 >> >>> On Tue, Sep 22, 2015 at

Re: brew install mesos doesn't work for 0.24.0

t; > > https://github.com/Homebrew/homebrew/blob/master/Library/Formula/mesos.rb#L98 > > >["native", "interface", ""].each do |p| > > > > should change to > > >["native", "interface", "cli", "

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

+1 (binding) Tested on CI for CentOS5/6. On Thu, Sep 24, 2015 at 6:12 PM, Adam Bordelon wrote: > +1 (binding) Tested on CI for CentOS7 and Ubuntu 14.04. > > On Thu, Sep 24, 2015 at 5:44 PM, Adam Bordelon wrote: > >> Hi friends, >> >> Here's a candidate for the last of the docker patch release

Re: mesos git commit: Added post-rewrite hook.

do we need the 'exec' keyword in there? i removed it in the pre-commit hook. On Tue, Oct 20, 2015 at 1:06 PM, wrote: > Repository: mesos > Updated Branches: > refs/heads/master 70fd9ce62 -> 5e68b23e7 > > > Added post-rewrite hook. > > Review: https://reviews.apache.org/r/38978 > > > Project: h

Re: Still Failing: apache/mesos#1269 (master - b74ed17)

+dominic Not sure who is the owner of this travis build for apache/mesos. Dominic? I would love for us to support one CI system (ASF), instead of having to learn 3. I see 3 different windows machines (Windows Server 2012, Windows Server 2008, Windows Server 2008 R2) in ASF CI. Does any of them f

Re: [jira] [Created] (MESOS-2353) Improve performance of the master's state.json endpoint for large clusters.

ds like you might be > interested in writing one while waiting for michael? > > > -- Forwarded message ------ > From: *Vinod Kone (JIRA)* > Date: Thursday, November 5, 2015 > Subject: [jira] [Created] (MESOS-2353) Improve performance of the master's > stat

Re: [jira] [Updated] (MESOS-3645) Implement stout/os/windows/stat.hpp

Hi Alex, When you want to bulk edit issues (for example unset target version), there is an option in JIRA to "bulk edit and not send an email notification". I would recommend to use that option (in the future) to reduce the noise on the mailing list. Thanks, On Thu, Nov 5, 2015 at 10:16 PM, Alex

Re: Website update frequency

That said, this can be automated as a step in apply-reviews script. For example, the script can check if something in site/ (or docs/ ?) is being committed and if yes, also do an svn update. @artem do you want to take this on as you revamp the apply-reviews script? On Tue, Nov 10, 2015 at 1:23 AM,

Re: Website update frequency

other script for committers > that > > will use apply-reviews.py? At some point you also mentioned that it would > > be good to have apply-reviews.py do the actual commits but we did not > > pursue the idea because it was not a relevant feature for most of the > &

Re: Website update frequency

ly before giving them a 'Ship It'. > > > > > > > > > > Regarding pushing the code, I don't have enough of context, so > could > > > you > > > > > please create a JIRA if you still think that it'd be great to have > >

Re: [BUG] Perf isolator (from 0.25.0-rc1) does not work on CentOS 7 with 3.10 kernel.

+cong,idownes On Tue, Nov 17, 2015 at 6:55 AM, Plotka, Bartlomiej < bartlomiej.plo...@intel.com> wrote: > This commit has changed that before 0.25.0-rc1: > https://reviews.apache.org/r/37462/ > In earlier Mesos versions in Perf isolator we had stout function > strings::tokenize instead of strings

Re: Configuration file?

We had this discussion a long while ago and the argument was that we already have a configuration file of sorts. It is a bash script with one flag per line that sets the environment. Is this not sufficient? Example: config.sh MESOS_WORK_DIR="/var/run/mesos" MESOS_QUORUM=2 $ source c

Re: What's the scope/version of v1 HTTP API?

HTTP API would be the recommended way for frameworks to interact with Mesos. The plan is to deprecate the driver based framework communication once we release 1.0 and remove the driver support in 2.0. Current status: Scheduler HTTP API is in beta. We are still fixing bugs and adding features (e.g.

Re: [proposal] Generalized Authorizer Interface

+modules On Fri, Dec 11, 2015 at 1:16 AM, Alexander Rojas wrote: > Hi Everyone, > > After looking at your comments and doing some extra design we have updated > the proposal for the Authorized Interface. Among the main changes is to > remove the attributes of all the parameters and making the ac

Re: First contribution

Welcome to the Mesos community Diego! I'll be happy to shepherd this for you. Also, added you as a contributor on the JIRA, so you can assign the ticket to yourself. On Wed, Dec 30, 2015 at 12:44 AM, Diogo Gomes wrote: > Hi guys, my name is Diogo and I’m from Brazil, I work for a big ecommerce

Re: Scheduler::executorLost() callback will be implemented in 0.27

+user On Mon, Jan 4, 2016 at 5:13 PM, Zhitao Li wrote: > Dear framework owners, > > Scheduler::executorLost() callback will be implemented in the future 0.27 > release. In previous versions, this callback in the scheduler interface >

Re: request to be added as a contributor

done On Thu, Jan 14, 2016 at 7:06 AM, Ezra Silvera wrote: > hi, > I want to be assigned myself to the jira issue > https://issues.apache.org/jira/browse/MESOS-4369 > for which I request to be included in the list of contributors > > Thanks > > Ezra Silvera > >

Re: request to be added as a contributor

done. welcome aboard. On Thu, Jan 14, 2016 at 7:06 AM, Ezra Silvera wrote: > hi, > I want to be assigned myself to the jira issue > https://issues.apache.org/jira/browse/MESOS-4369 > for which I request to be included in the list of contributors > > Thanks > > Ezra Silvera > >

Re: Ignite as Big Data project built on Mesos

Can you send a PR on github/apache/mesos or submit a review ?. On Wed, Jan 13, 2016 at 6:30 PM, Dmitriy Setrakyan wrote: > Hello Mesos community! > > Ignite community would like to add Apache Ignite to this page on Mesos > website

Re: Contribution Request

done On Fri, Jan 15, 2016 at 8:35 AM, Jiří Šimša wrote: > Please add me to the list of Mesos contributors. I would like to submit a > code review for the following JIRA > . > > Best, > > -- > Jiří Šimša >

Re: Contribution Request

Hi Disha, Thanks for asking. We cannot just rename the `authenticate` flag to `authenticate_frameworks` because that will break users who are already setting that flag, when they upgrade to the new version (that has this change). We always strive to do backwards compatible changes. The first ste

Re: Contribution Request

t; > > > On Saturday 16 January 2016 12:05 AM, Disha Singh wrote: > >> Yes,It does. If you could tell me where these flags are and where I should >> add them . I tried to figure it out in the git repository : >> https://github.com/apache/mesos >> >> Bu

Re: Contribution Request

Seems simple enough. Sure. On Fri, Jan 15, 2016 at 2:33 PM, Jiří Šimša wrote: > Thanks Vinod. Would you mind being a shepherd for this code review? Thank > you. > > Best, > > -- > Jiří Šimša > > On Fri, Jan 15, 2016 at 8:52 AM, Vinod Kone wrote: > > > done

Re: Contribution Request

, > > Alexander > > > On 15 Jan 2016, at 19:15, Vinod Kone wrote: > > > > Hi Disha, > > > > Thanks for asking. > > > > We cannot just rename the `authenticate` flag to > `authenticate_frameworks` > > because that will break users who are

Re: Contribution request

Added. Welcome! On Wed, Jan 20, 2016 at 10:51 AM, Abhishek Dasgupta < a10gu...@linux.vnet.ibm.com> wrote: > Hi, > I want to contribute to mesos project. So, please add me as a mesos > contributor. >I created Apache Review Board account as "a10gupta" and JIRA account as > "a10gupta". > >

Re: Need a shepherd for MESOS--3317

Sorry Abhishek, I don't have cycles :( On Tue, Jan 26, 2016 at 3:18 AM, Abhishek Dasgupta < a10gu...@linux.vnet.ibm.com> wrote: > Hi Vinod, > > Can you review the patch https://reviews.apache.org/r/42794/ ? Or, if you > can delegate someone else to review the patch. This is my first review > requ

Re: build error

On Thu, Jan 28, 2016 at 11:55 AM, Disha Singh wrote: > I am also unable to upgrade maven2 to maven3. > Have you tried asking on the maven user list? You would probably get better help regarding maven upgrade there. If you are not interested in maven/java bindings, you can try building mesos wit

Re: [VOTE] Release Apache Mesos 0.27.0 (rc2)

+1 (binding) Tested (non-root tests with ./support/docker_build.sh script) on ASF CI with the following configurations: NOTE: clang is intentionally disabled on centos and "clang + ubuntu + --verbose" build failed because of a do

Re: [VOTE] Release Apache Mesos 0.27.0 (rc2)

Git fetch --tags @vinodkone > On Jan 29, 2016, at 7:00 PM, Marco Massenzio wrote: > > Is there a 0.27.0-rc2 branch cut? > > $ git fetch --all > Fetching origin > > $ git co 0.27.0-rc2 > error: pathspec '0.27.0-rc2' did not match any file(s) known to git. > > > -- > Marco Massenzio > http:/

Re: Some initial thoughts on IPv6

Thanks for starting the discussion about this Evers! Supporting IPv6 has been a long awaited feature for Mesos, so glad to see that you are interested in working on this. I would also vote for #1 because it seems to get us far with minimal code changes. There is already a #networking working group

Re: Cron /x1/home/apsite/wrkdir/bin/build.sh

We moved the 'site' directory from svn into our git repo to make it easy for contributors to submit patches for the website. Is it possible for whatever is looking at the doap file to look at git/mesos/site instead?

Re: Contributor request

Done. Welcome to the mesos community! On Wed, Feb 3, 2016 at 11:25 AM, Michael Browning wrote: > Hello, > > I'd like to be added as a Mesos contributor in JIRA, username "mrbrowning". > > Thank you, > Michael >

Re: Contributor request

Done. Welcome! On Wed, Feb 3, 2016 at 1:07 PM, Erik Weathers wrote: > Please add me as a contributor in the Mesos JIRA project. > Apache JIRA username: erikdw > > Thanks! > > - Erik >

Re: Questions about release process

Looks like this didn't show up in the CHANGELOG because the "Fix version" was not set on the ticket. Typically the release manager(s) ensures all fixed tickets have a Fix version before cutting the release, but looks like this fell thro

Re: Questions about release process

se/MESOS-4212 > https://issues.apache.org/jira/browse/MESOS-4251 > https://issues.apache.org/jira/browse/MESOS-4252 > > > > On Thu, Feb 4, 2016 at 10:34 AM Vinod Kone wrote: > > > Looks like this didn't show up in the CHANGELOG because the "Fix version" > &g

Re: Mesos 0.27.1

I've already set target versions for some tickets to 0.27.1. Can that be automatically pulled into the dashboard? On Fri, Feb 5, 2016 at 12:41 PM, Michael Park wrote: > Hello, > > I've recently been notified that the JSON output from the `/state` endpoint > contains duplicate keys which breaks s

Re: Specifying a preferred host with a Resource Request

What you want here are dynamic reservations and persistent volumes. Take a look at our docs for these features. @vinodkone > On Feb 6, 2016, at 10:31 AM, Jagadish Venkatraman > wrote: > > Hi Guangya, > > Thanks for the response! Let me provide more background to this request. > > Backgrou

Re: MESOS-4126 request to be assigned

Done. Welcome! Please find a shepherd *before* working on the issue. On Mon, Feb 8, 2016 at 4:36 PM, Jacob Janco wrote: > Hello, > > I would like to be assigned to this issue marked newbie++. My screen name > is jjanco. This is my first jira ticket for the Mesos project. > > Thanks! > > Jacob J

Inconsistent naming of support scripts

Some the scripts in the "support" directory have dashes ("-") in their names (e.g., apply-review.sh, apply-reviews.py), whereas some have underscores ("_") (e.g., docker_build.sh, mesos_split.py). This is really confusing and we should stick with one style. I propose to change all them to use unde

Re: Slave Terminology Rename Proposal

What do you mean by keeping the old symbols? For example, in the case of the `Allocator::addSlave()`, are you suggesting that when we add `Allocator::addAgent()`, we keep `Allocator::addSlave()` as well? Master will only call `Allocator::addAgent()` from that point onward, so I'm not sure what's t

Re: Inconsistent naming of support scripts

en++. Is google friendly apparently. Also less keys to press :) > > > > -Jojy > > > > > > > >> On Feb 11, 2016, at 12:43 PM, Greg Mann wrote: > >> > >> +1 > >> > >> On Thu, Feb 11, 2016 at 11:41 AM, Vinod Kone > wrote:

Re: Inconsistent naming of support scripts

es are meant as source or > > >> otherwise supplementary to the binary produced (e.g. a supplementary > > >> python library that the main python program imports). I'm not sure > > >> where I inherited this convention from, but it's always been the way > >

Mesos release process (survey)

Hi folks, We are looking for feedback on how we can improve the release process, mainly around better vetting and voting of the release candidates. If you have a few minutes, please take this very short survey to give us feedback. This will help us improve the process. http://goo.gl/forms/1yqgtT

  1   2   3   4   5   6   7   8   9   10   >