Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57D1610E53 for ; Tue, 10 Feb 2015 19:16:35 +0000 (UTC) Received: (qmail 78861 invoked by uid 500); 10 Feb 2015 19:16:00 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 78817 invoked by uid 500); 10 Feb 2015 19:16:00 -0000 Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.incubator.apache.org Delivered-To: mailing list dev@aurora.incubator.apache.org Received: (qmail 78802 invoked by uid 99); 10 Feb 2015 19:16:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 19:16:00 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com) (209.85.214.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 19:15:35 +0000 Received: by mail-ob0-f172.google.com with SMTP id nt9so33949515obb.3 for ; Tue, 10 Feb 2015 11:14:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=qnYiF1y6sQUp0wBXKngsxhdBYSPoV+Xc5QoXl/k/lPk=; b=C7L0ZoWgzKw+VtsZxyZjEaqswrouTjXAxrtSlV0PpgC6sywhnvLsPd2XSF19Jhx+t/ kuQqncZovwRS/zb0xc0og7ABidSdqwT1H0cJannlF21rpSV1SDpVc07GcRxWTpqoJkDD SISstcL7bXyC0q1yJdGLZrr3NxFjD/91MbJL6Q7DLb6ny3D79IyHmHW/HHTtW2raCH8B CgKPV/p0g8lT9pk1Y+GgFhUGRwzgN1/yW5vPlbK7vVDp3X2U/H1a4QLdWgtANxQNWTx/ 1kG30aS4M6y1tIwtZfQ6lrjdCbmdIb1xoNrFyJ2ntudoI/CMALuCV+qBpoVWDdwLatVR sAQA== X-Gm-Message-State: ALoCoQkTKZwoRjB/R+jlHh3UGEe1qzHHjxc7mjzNOVmVPzBbye9VMtwuONiLKIreWZ+8g3aMZD9t MIME-Version: 1.0 X-Received: by 10.182.75.194 with SMTP id e2mr12802961obw.17.1423595668540; Tue, 10 Feb 2015 11:14:28 -0800 (PST) Received: by 10.182.123.71 with HTTP; Tue, 10 Feb 2015 11:14:28 -0800 (PST) In-Reply-To: References: Date: Tue, 10 Feb 2015 14:14:28 -0500 Message-ID: Subject: Re: Seeking volunteers to create scheduler REST API RFC From: Joe Stein To: dev@aurora.incubator.apache.org Content-Type: multipart/alternative; boundary=001a11c1eac620a1dc050ec0b207 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1eac620a1dc050ec0b207 Content-Type: text/plain; charset=UTF-8 Chris, We are primarily hoping to integrate Apache Storm. It is important for us that the task preemption and quotas and all that great stuff is available from Aurora with the other frameworks we work with. ~ Joe Stein On Tue, Feb 10, 2015 at 12:06 AM, Chris Lambert < clambert@twitter.com.invalid> wrote: > Just curious, what kind of frameworks do you want to run on Aurora? > > Chris > > > On Mon, Feb 9, 2015 at 7:26 PM, Joe Stein wrote: > > > Hey, this looks really interesting. We have been toying with "how do we > run > > frameworks on aurora" and I think that is a good use case for this also. > > > > Can the pieces be broken up across a few different folks? > > > > Can we preserve the thrift objects and have that also as an option (along > > with json at least) to go over a http 2.0 end point? > > > > ~ Joestein > > > > On Mon, Feb 9, 2015 at 5:31 PM, Brian Wickman > wrote: > > > > > +1 > > > > > > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen > > > wrote: > > > > > > > I'd love to help out with this as well. > > > > > > > > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner > > wrote: > > > > > > > > > Hi folks, > > > > > > > > > > Before embarking on work [1] to build a REST* API for the > scheduler, > > > it's > > > > > important that we come up with a sound design. Following up from > > > today's > > > > > IRC meeting, i would like to gather a small contingent (<=4 people) > > to > > > > > collaborate on an RFC to drive a broader design discussion. > > > > > > > > > > Note that the RFC will be published to this mailing list, where it > > will > > > > be > > > > > completely open for discussion to change (it's a Request For > > Comments, > > > > > after all). > > > > > > > > > > Volunteers must be willing to research the landscape for patterns > and > > > > best > > > > > practices in designing web application APIs; prior experience in > this > > > > area > > > > > is a plus. > > > > > > > > > > Several people volunteered in the IRC meeting, but to keep the > > > canonical > > > > > discussion in one place i ask those still interested to volunteer > > again > > > > on > > > > > this thread. > > > > > > > > > > I'll start by volunteering myself. > > > > > > > > > > > > > > > -=Bill > > > > > > > > > > * Used as shorthand, whether it turns out to be REST, JSON-RPC, > > > HATEOAS, > > > > > etc. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/AURORA-987 > > > > > > > > > > > > > > > --001a11c1eac620a1dc050ec0b207--