Seeking volunteers to create scheduler REST API RFC

[Bill Farner <wf...@apache.org>]

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

Re: Seeking volunteers to create scheduler REST API RFC

[Joshua Cohen <jc...@twopensource.com>]

+1 to not breaking the effort down into smaller pieces. The eventual
finished product should be a consistent across the individual resources
which would be much more difficult if the various APIs were designed in
isolation.

On Tue, Feb 10, 2015 at 7:50 PM, Bill Farner <wf...@apache.org> wrote:

> 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 <jo...@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 <wi...@apache.org>
> wrote:
> >
> > > +1
> > >
> > > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <jc...@twopensource.com>
> > > wrote:
> > >
> > > > I'd love to help out with this as well.
> > > >
> > > > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wf...@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
> > > > >
> > > >
> > >
> >
>

Re: Seeking volunteers to create scheduler REST API RFC

[Bill Farner <wf...@apache.org>]

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 <jo...@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 <wi...@apache.org> wrote:
>
> > +1
> >
> > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <jc...@twopensource.com>
> > wrote:
> >
> > > I'd love to help out with this as well.
> > >
> > > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wf...@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
> > > >
> > >
> >
>

Re: Seeking volunteers to create scheduler REST API RFC

[Bill Farner <wf...@apache.org>]

Fantastic, thanks!

On Tuesday, February 10, 2015, Henry Saputra <he...@gmail.com>
wrote:

> BIll,
>
> I helped built Telemetry RESTful APIs before so I could help.
>
> Count me in please.
>
> - Henry
>
> On Tue, Feb 10, 2015 at 4:55 PM, Bill Farner <wfarner@apache.org
> <javascript:;>> wrote:
> > Reviving this thread.  I would love to see a non-Twitter employee
> > collaborate on this for a more diverse panel.
> >
> > -=Bill
> >
> > On Tue, Feb 10, 2015 at 11:14 AM, Joe Stein <joe.stein@stealth.ly
> <javascript:;>> wrote:
> >
> >> 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 <joe.stein@stealth.ly
> <javascript:;>> 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
> <javascript:;>>
> >> > wrote:
> >> > >
> >> > > > +1
> >> > > >
> >> > > > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <
> >> jcohen@twopensource.com <javascript:;>>
> >> > > > 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
> <javascript:;>>
> >> > > 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
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
>


-- 
-=Bill

Re: Seeking volunteers to create scheduler REST API RFC

[Henry Saputra <he...@gmail.com>]

BIll,

I helped built Telemetry RESTful APIs before so I could help.

Count me in please.

- Henry

On Tue, Feb 10, 2015 at 4:55 PM, Bill Farner <wf...@apache.org> wrote:
> Reviving this thread.  I would love to see a non-Twitter employee
> collaborate on this for a more diverse panel.
>
> -=Bill
>
> On Tue, Feb 10, 2015 at 11:14 AM, Joe Stein <jo...@stealth.ly> wrote:
>
>> 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 <jo...@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 <wi...@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 <wf...@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
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>

Re: Seeking volunteers to create scheduler REST API RFC

[Bill Farner <wf...@apache.org>]

Reviving this thread.  I would love to see a non-Twitter employee
collaborate on this for a more diverse panel.

-=Bill

On Tue, Feb 10, 2015 at 11:14 AM, Joe Stein <jo...@stealth.ly> wrote:

> 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 <jo...@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 <wi...@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 <wf...@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
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Seeking volunteers to create scheduler REST API RFC

[Joe Stein <jo...@stealth.ly>]

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 <jo...@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 <wi...@apache.org>
> wrote:
> >
> > > +1
> > >
> > > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <jc...@twopensource.com>
> > > wrote:
> > >
> > > > I'd love to help out with this as well.
> > > >
> > > > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wf...@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
> > > > >
> > > >
> > >
> >
>

Re: Seeking volunteers to create scheduler REST API RFC

[Chris Lambert <cl...@twitter.com.INVALID>]

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 <jo...@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 <wi...@apache.org> wrote:
>
> > +1
> >
> > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <jc...@twopensource.com>
> > wrote:
> >
> > > I'd love to help out with this as well.
> > >
> > > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wf...@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
> > > >
> > >
> >
>

Re: Seeking volunteers to create scheduler REST API RFC

[Joe Stein <jo...@stealth.ly>]

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 <wi...@apache.org> wrote:

> +1
>
> On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <jc...@twopensource.com>
> wrote:
>
> > I'd love to help out with this as well.
> >
> > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wf...@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
> > >
> >
>

Re: Seeking volunteers to create scheduler REST API RFC

[Brian Wickman <wi...@apache.org>]

+1

On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen <jc...@twopensource.com>
wrote:

> I'd love to help out with this as well.
>
> On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wf...@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
> >
>

Re: Seeking volunteers to create scheduler REST API RFC

[Joshua Cohen <jc...@twopensource.com>]

I'd love to help out with this as well.

On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wf...@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
>