Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAA7ooCAU4ww5RAJ-cRR5SvfVNg-kzLqQHPNGPNiSM0ZRngk=bQ@mail.gmail.com>
References: 
 <CAGRA8uPfC+WcUNh6Q1dRbSDmZ+33aARxgGbzUBke2d=PZC0n_A@mail.gmail.com>
	<CAMnduq-W1ELgAv0SKqxEfE_JybzPn2=Bh0ZUjjZ+mZr6w0XisQ@mail.gmail.com>
	<CAFTdr0BNbuKKZ88c-8qMiVViPE3-q_qcUExqVdnf1NtAk8KFww@mail.gmail.com>
	<CAA7ooCAU4ww5RAJ-cRR5SvfVNg-kzLqQHPNGPNiSM0ZRngk=bQ@mail.gmail.com>
Date: Tue, 10 Feb 2015 19:50:41 -0800
Message-ID: 
 <CAGRA8uPf2R9R-ERgh1eoKv6j_3otpHymtukUN5d4=NcmLfaAAg@mail.gmail.com>
Subject: Re: Seeking volunteers to create scheduler REST API RFC
From: Bill Farner <wfarner@apache.org>
To: "dev@aurora.incubator.apache.org" <dev@aurora.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a11c0dd403ed951050ec7e85d

--001a11c0dd403ed951050ec7e85d
Content-Type: text/plain; charset=UTF-8

Joe, i just realized i did not reply to your question.  My intuition has
been that the REST API will eventually become the only external API to the
scheduler, but i'm willing to hear alternative opinions on that.

As for breaking up the design effort, i don't think that is the best path.
I don't anticipate the API design to be a tremendous workload (famous last
words?), and i think it may be difficult to come up with a consistent
approach if we try to divide and conquer.

-=Bill

On Mon, Feb 9, 2015 at 7:26 PM, Joe Stein <joe.stein@stealth.ly> 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 <wickman@apache.org> wrote:
>
> > +1
> >
> > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <jcohen@twopensource.com>
> > wrote:
> >
> > > I'd love to help out with this as well.
> > >
> > > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wfarner@apache.org>
> 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
> > > >
> > >
> >
>

--001a11c0dd403ed951050ec7e85d--