You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by Bill Farner <wf...@apache.org> on 2014/12/01 22:17:11 UTC

[DISCUSS] Features for 0.7.0

Now that 0.6.0 is buttoned up, it's time to think about what we would like
to shoot for in 0.7.0 [1]!

Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor'
release to allow us to wrap it up by mid Q1.  So while lofty goals are more
than welcome in JIRA, let's be somewhat resistant to them in the upcoming
release.

To summarize what's currently on the docket, we have:
- removal of several minor deprecated behaviors [2]
- begin phasing out the 'v1' client
- promote server-side updates, phase out client-side job update behavior

With that in mind, what else would you all (non-committers welcome) like to
see in 0.7.0?


[1] https://issues.apache.org/jira/browse/AURORA-872
[2] https://issues.apache.org/jira/browse/AURORA-423


-=Bill

Re: [DISCUSS] Features for 0.7.0

Posted by Bill Farner <wf...@apache.org>.
Docker support would be *awesome*.  I'll be happy to assist with getting
that patch in!

Mid Q1 is a very pessimistic measure, partially with the context that
peoples' time is spotty in December.  I would have no problem cutting 0.7.0
much earlier as long as we wrap up the deprecations.

-=Bill

On Mon, Dec 1, 2014 at 4:52 PM, Dave Lester <da...@davelester.org> wrote:

>
> For some reason I can see Dobromir's message in the markmail archive ([
> http://markmail.org/message/6v54d3lc5qwerzq5 ](
> http://markmail.org/message/6v54d3lc5qwerzq5 )), but never received the
> message to my personal email account. He wrote:
>
> "We have someone working on integrating Docker support into Aurora; it
> seems fairly minor and would be neat to get into the 0.7.0 release..."
>
> IMHO, Docker support in Aurora would be a large driver for adoption.
> Should there be a good patch, it'd be nice to get a release sooner than
> mid-Q1 which seems a ways off. Maybe we can up the release cadence a bit
> more to make this possible.
>
>
> Dave
>
> -----Original Message-----
> From: "Bill Farner" <wf...@apache.org>
> Sent: Monday, December 1, 2014 3:13pm
> To: "dev@aurora.incubator.apache.org" <de...@aurora.incubator.apache.org>
> Subject: Re: [DISCUSS] Features for 0.7.0
>
>
>
> If you think AURORA-915 can be completed by the end of January, i don't see
> any reason to keep it out.
>
> -=Bill
>
> On Mon, Dec 1, 2014 at 3:07 PM, Brian Wickman <wi...@apache.org> wrote:
>
> > In the deprecated behavior category, I'd like to get feedback on
> > https://issues.apache.org/jira/browse/AURORA-915 as possible candidate
> for
> > inclusion to 0.7.0 (at the very least, warn-on-import and providing a
> > binding helper for os.environ.)
> >
> > On Mon, Dec 1, 2014 at 3:04 PM, Bill Farner <wf...@apache.org> wrote:
> >
> > > It is not yet tracked in our end - we have yet to think about what
> mesos'
> > > presistent resources look like under Aurora. Given the timeframe we're
> > > shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and
> > > released by the time we cut 0.7.0.
> > >
> > > -=Bill
> > >
> > > On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <jo...@stealth.ly>
> wrote:
> > >
> > > > It might be minor, already tracked or maybe nothing todo but support
> > for
> > > > https://issues.apache.org/jira/browse/MESOS-1554 would be awesome
> :) (
> > > > once
> > > > released ) without forcing dedicated service.
> > > >
> > > > /*******************************************
> > > > Joe Stein
> > > > Founder, Principal Consultant
> > > > Big Data Open Source Security LLC
> > > > http://www.stealth.ly
> > > > Twitter: @allthingshadoop
> > > > ********************************************/
> > > > On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:
> > > >
> > > > > Now that 0.6.0 is buttoned up, it's time to think about what we
> would
> > > > like
> > > > > to shoot for in 0.7.0 [1]!
> > > > >
> > > > > Framing the discussion - i'd like to suggest we keep 0.7.0 a
> 'minor'
> > > > > release to allow us to wrap it up by mid Q1. So while lofty goals
> > are
> > > > more
> > > > > than welcome in JIRA, let's be somewhat resistant to them in the
> > > upcoming
> > > > > release.
> > > > >
> > > > > To summarize what's currently on the docket, we have:
> > > > > - removal of several minor deprecated behaviors [2]
> > > > > - begin phasing out the 'v1' client
> > > > > - promote server-side updates, phase out client-side job update
> > > behavior
> > > > >
> > > > > With that in mind, what else would you all (non-committers welcome)
> > > like
> > > > to
> > > > > see in 0.7.0?
> > > > >
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/AURORA-872
> > > > > [2] https://issues.apache.org/jira/browse/AURORA-423
> > > > >
> > > > >
> > > > > -=Bill
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Features for 0.7.0

Posted by Dave Lester <da...@davelester.org>.
For some reason I can see Dobromir's message in the markmail archive ([ http://markmail.org/message/6v54d3lc5qwerzq5 ]( http://markmail.org/message/6v54d3lc5qwerzq5 )), but never received the message to my personal email account. He wrote:
 
"We have someone working on integrating Docker support into Aurora; it seems fairly minor and would be neat to get into the 0.7.0 release..."
 
IMHO, Docker support in Aurora would be a large driver for adoption. Should there be a good patch, it'd be nice to get a release sooner than mid-Q1 which seems a ways off. Maybe we can up the release cadence a bit more to make this possible.

 
Dave
 
-----Original Message-----
From: "Bill Farner" <wf...@apache.org>
Sent: Monday, December 1, 2014 3:13pm
To: "dev@aurora.incubator.apache.org" <de...@aurora.incubator.apache.org>
Subject: Re: [DISCUSS] Features for 0.7.0



If you think AURORA-915 can be completed by the end of January, i don't see
any reason to keep it out.

-=Bill

On Mon, Dec 1, 2014 at 3:07 PM, Brian Wickman <wi...@apache.org> wrote:

> In the deprecated behavior category, I'd like to get feedback on
> https://issues.apache.org/jira/browse/AURORA-915 as possible candidate for
> inclusion to 0.7.0 (at the very least, warn-on-import and providing a
> binding helper for os.environ.)
>
> On Mon, Dec 1, 2014 at 3:04 PM, Bill Farner <wf...@apache.org> wrote:
>
> > It is not yet tracked in our end - we have yet to think about what mesos'
> > presistent resources look like under Aurora. Given the timeframe we're
> > shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and
> > released by the time we cut 0.7.0.
> >
> > -=Bill
> >
> > On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <jo...@stealth.ly> wrote:
> >
> > > It might be minor, already tracked or maybe nothing todo but support
> for
> > > https://issues.apache.org/jira/browse/MESOS-1554 would be awesome :) (
> > > once
> > > released ) without forcing dedicated service.
> > >
> > > /*******************************************
> > > Joe Stein
> > > Founder, Principal Consultant
> > > Big Data Open Source Security LLC
> > > http://www.stealth.ly
> > > Twitter: @allthingshadoop
> > > ********************************************/
> > > On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:
> > >
> > > > Now that 0.6.0 is buttoned up, it's time to think about what we would
> > > like
> > > > to shoot for in 0.7.0 [1]!
> > > >
> > > > Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor'
> > > > release to allow us to wrap it up by mid Q1. So while lofty goals
> are
> > > more
> > > > than welcome in JIRA, let's be somewhat resistant to them in the
> > upcoming
> > > > release.
> > > >
> > > > To summarize what's currently on the docket, we have:
> > > > - removal of several minor deprecated behaviors [2]
> > > > - begin phasing out the 'v1' client
> > > > - promote server-side updates, phase out client-side job update
> > behavior
> > > >
> > > > With that in mind, what else would you all (non-committers welcome)
> > like
> > > to
> > > > see in 0.7.0?
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/AURORA-872
> > > > [2] https://issues.apache.org/jira/browse/AURORA-423
> > > >
> > > >
> > > > -=Bill
> > > >
> > >
> >
>

Re: [DISCUSS] Features for 0.7.0

Posted by Bill Farner <wf...@apache.org>.
If you think AURORA-915 can be completed by the end of January, i don't see
any reason to keep it out.

-=Bill

On Mon, Dec 1, 2014 at 3:07 PM, Brian Wickman <wi...@apache.org> wrote:

> In the deprecated behavior category, I'd like to get feedback on
> https://issues.apache.org/jira/browse/AURORA-915 as possible candidate for
> inclusion to 0.7.0 (at the very least, warn-on-import and providing a
> binding helper for os.environ.)
>
> On Mon, Dec 1, 2014 at 3:04 PM, Bill Farner <wf...@apache.org> wrote:
>
> > It is not yet tracked in our end - we have yet to think about what mesos'
> > presistent resources look like under Aurora.  Given the timeframe we're
> > shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and
> > released by the time we cut 0.7.0.
> >
> > -=Bill
> >
> > On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <jo...@stealth.ly> wrote:
> >
> > > It might be minor, already tracked or maybe nothing todo but support
> for
> > > https://issues.apache.org/jira/browse/MESOS-1554 would be awesome :) (
> > > once
> > > released ) without forcing dedicated service.
> > >
> > > /*******************************************
> > > Joe Stein
> > > Founder, Principal Consultant
> > > Big Data Open Source Security LLC
> > > http://www.stealth.ly
> > > Twitter: @allthingshadoop
> > > ********************************************/
> > > On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:
> > >
> > > > Now that 0.6.0 is buttoned up, it's time to think about what we would
> > > like
> > > > to shoot for in 0.7.0 [1]!
> > > >
> > > > Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor'
> > > > release to allow us to wrap it up by mid Q1.  So while lofty goals
> are
> > > more
> > > > than welcome in JIRA, let's be somewhat resistant to them in the
> > upcoming
> > > > release.
> > > >
> > > > To summarize what's currently on the docket, we have:
> > > > - removal of several minor deprecated behaviors [2]
> > > > - begin phasing out the 'v1' client
> > > > - promote server-side updates, phase out client-side job update
> > behavior
> > > >
> > > > With that in mind, what else would you all (non-committers welcome)
> > like
> > > to
> > > > see in 0.7.0?
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/AURORA-872
> > > > [2] https://issues.apache.org/jira/browse/AURORA-423
> > > >
> > > >
> > > > -=Bill
> > > >
> > >
> >
>

Re: [DISCUSS] Features for 0.7.0

Posted by Dobromir Montauk <do...@tellapart.com>.
We have someone working on integrating Docker support into Aurora; it seems
fairly minor and would be neat to get into the 0.7.0 release...

On Mon, Dec 1, 2014 at 3:12 PM, Zameer Manji <zm...@twopensource.com>
wrote:

> I think providing a binding helper for os.environ is something we should
> ship in 0.7.0. The earlier we get it out the more time users have to
> rewrite their Aurora configs.
>
> On Mon, Dec 1, 2014 at 3:07 PM, Brian Wickman <wi...@apache.org> wrote:
>
> > In the deprecated behavior category, I'd like to get feedback on
> > https://issues.apache.org/jira/browse/AURORA-915 as possible candidate
> for
> > inclusion to 0.7.0 (at the very least, warn-on-import and providing a
> > binding helper for os.environ.)
> >
> > On Mon, Dec 1, 2014 at 3:04 PM, Bill Farner <wf...@apache.org> wrote:
> >
> > > It is not yet tracked in our end - we have yet to think about what
> mesos'
> > > presistent resources look like under Aurora.  Given the timeframe we're
> > > shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and
> > > released by the time we cut 0.7.0.
> > >
> > > -=Bill
> > >
> > > On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <jo...@stealth.ly>
> wrote:
> > >
> > > > It might be minor, already tracked or maybe nothing todo but support
> > for
> > > > https://issues.apache.org/jira/browse/MESOS-1554 would be awesome
> :) (
> > > > once
> > > > released ) without forcing dedicated service.
> > > >
> > > > /*******************************************
> > > > Joe Stein
> > > > Founder, Principal Consultant
> > > > Big Data Open Source Security LLC
> > > > http://www.stealth.ly
> > > > Twitter: @allthingshadoop
> > > > ********************************************/
> > > > On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:
> > > >
> > > > > Now that 0.6.0 is buttoned up, it's time to think about what we
> would
> > > > like
> > > > > to shoot for in 0.7.0 [1]!
> > > > >
> > > > > Framing the discussion - i'd like to suggest we keep 0.7.0 a
> 'minor'
> > > > > release to allow us to wrap it up by mid Q1.  So while lofty goals
> > are
> > > > more
> > > > > than welcome in JIRA, let's be somewhat resistant to them in the
> > > upcoming
> > > > > release.
> > > > >
> > > > > To summarize what's currently on the docket, we have:
> > > > > - removal of several minor deprecated behaviors [2]
> > > > > - begin phasing out the 'v1' client
> > > > > - promote server-side updates, phase out client-side job update
> > > behavior
> > > > >
> > > > > With that in mind, what else would you all (non-committers welcome)
> > > like
> > > > to
> > > > > see in 0.7.0?
> > > > >
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/AURORA-872
> > > > > [2] https://issues.apache.org/jira/browse/AURORA-423
> > > > >
> > > > >
> > > > > -=Bill
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Zameer Manji
>

Re: [DISCUSS] Features for 0.7.0

Posted by Zameer Manji <zm...@twopensource.com>.
I think providing a binding helper for os.environ is something we should
ship in 0.7.0. The earlier we get it out the more time users have to
rewrite their Aurora configs.

On Mon, Dec 1, 2014 at 3:07 PM, Brian Wickman <wi...@apache.org> wrote:

> In the deprecated behavior category, I'd like to get feedback on
> https://issues.apache.org/jira/browse/AURORA-915 as possible candidate for
> inclusion to 0.7.0 (at the very least, warn-on-import and providing a
> binding helper for os.environ.)
>
> On Mon, Dec 1, 2014 at 3:04 PM, Bill Farner <wf...@apache.org> wrote:
>
> > It is not yet tracked in our end - we have yet to think about what mesos'
> > presistent resources look like under Aurora.  Given the timeframe we're
> > shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and
> > released by the time we cut 0.7.0.
> >
> > -=Bill
> >
> > On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <jo...@stealth.ly> wrote:
> >
> > > It might be minor, already tracked or maybe nothing todo but support
> for
> > > https://issues.apache.org/jira/browse/MESOS-1554 would be awesome :) (
> > > once
> > > released ) without forcing dedicated service.
> > >
> > > /*******************************************
> > > Joe Stein
> > > Founder, Principal Consultant
> > > Big Data Open Source Security LLC
> > > http://www.stealth.ly
> > > Twitter: @allthingshadoop
> > > ********************************************/
> > > On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:
> > >
> > > > Now that 0.6.0 is buttoned up, it's time to think about what we would
> > > like
> > > > to shoot for in 0.7.0 [1]!
> > > >
> > > > Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor'
> > > > release to allow us to wrap it up by mid Q1.  So while lofty goals
> are
> > > more
> > > > than welcome in JIRA, let's be somewhat resistant to them in the
> > upcoming
> > > > release.
> > > >
> > > > To summarize what's currently on the docket, we have:
> > > > - removal of several minor deprecated behaviors [2]
> > > > - begin phasing out the 'v1' client
> > > > - promote server-side updates, phase out client-side job update
> > behavior
> > > >
> > > > With that in mind, what else would you all (non-committers welcome)
> > like
> > > to
> > > > see in 0.7.0?
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/AURORA-872
> > > > [2] https://issues.apache.org/jira/browse/AURORA-423
> > > >
> > > >
> > > > -=Bill
> > > >
> > >
> >
>



-- 
Zameer Manji

Re: [DISCUSS] Features for 0.7.0

Posted by Brian Wickman <wi...@apache.org>.
In the deprecated behavior category, I'd like to get feedback on
https://issues.apache.org/jira/browse/AURORA-915 as possible candidate for
inclusion to 0.7.0 (at the very least, warn-on-import and providing a
binding helper for os.environ.)

On Mon, Dec 1, 2014 at 3:04 PM, Bill Farner <wf...@apache.org> wrote:

> It is not yet tracked in our end - we have yet to think about what mesos'
> presistent resources look like under Aurora.  Given the timeframe we're
> shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and
> released by the time we cut 0.7.0.
>
> -=Bill
>
> On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <jo...@stealth.ly> wrote:
>
> > It might be minor, already tracked or maybe nothing todo but support for
> > https://issues.apache.org/jira/browse/MESOS-1554 would be awesome :) (
> > once
> > released ) without forcing dedicated service.
> >
> > /*******************************************
> > Joe Stein
> > Founder, Principal Consultant
> > Big Data Open Source Security LLC
> > http://www.stealth.ly
> > Twitter: @allthingshadoop
> > ********************************************/
> > On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:
> >
> > > Now that 0.6.0 is buttoned up, it's time to think about what we would
> > like
> > > to shoot for in 0.7.0 [1]!
> > >
> > > Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor'
> > > release to allow us to wrap it up by mid Q1.  So while lofty goals are
> > more
> > > than welcome in JIRA, let's be somewhat resistant to them in the
> upcoming
> > > release.
> > >
> > > To summarize what's currently on the docket, we have:
> > > - removal of several minor deprecated behaviors [2]
> > > - begin phasing out the 'v1' client
> > > - promote server-side updates, phase out client-side job update
> behavior
> > >
> > > With that in mind, what else would you all (non-committers welcome)
> like
> > to
> > > see in 0.7.0?
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/AURORA-872
> > > [2] https://issues.apache.org/jira/browse/AURORA-423
> > >
> > >
> > > -=Bill
> > >
> >
>

Re: [DISCUSS] Features for 0.7.0

Posted by Bill Farner <wf...@apache.org>.
It is not yet tracked in our end - we have yet to think about what mesos'
presistent resources look like under Aurora.  Given the timeframe we're
shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and
released by the time we cut 0.7.0.

-=Bill

On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <jo...@stealth.ly> wrote:

> It might be minor, already tracked or maybe nothing todo but support for
> https://issues.apache.org/jira/browse/MESOS-1554 would be awesome :) (
> once
> released ) without forcing dedicated service.
>
> /*******************************************
> Joe Stein
> Founder, Principal Consultant
> Big Data Open Source Security LLC
> http://www.stealth.ly
> Twitter: @allthingshadoop
> ********************************************/
> On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:
>
> > Now that 0.6.0 is buttoned up, it's time to think about what we would
> like
> > to shoot for in 0.7.0 [1]!
> >
> > Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor'
> > release to allow us to wrap it up by mid Q1.  So while lofty goals are
> more
> > than welcome in JIRA, let's be somewhat resistant to them in the upcoming
> > release.
> >
> > To summarize what's currently on the docket, we have:
> > - removal of several minor deprecated behaviors [2]
> > - begin phasing out the 'v1' client
> > - promote server-side updates, phase out client-side job update behavior
> >
> > With that in mind, what else would you all (non-committers welcome) like
> to
> > see in 0.7.0?
> >
> >
> > [1] https://issues.apache.org/jira/browse/AURORA-872
> > [2] https://issues.apache.org/jira/browse/AURORA-423
> >
> >
> > -=Bill
> >
>

Re: [DISCUSS] Features for 0.7.0

Posted by Joe Stein <jo...@stealth.ly>.
It might be minor, already tracked or maybe nothing todo but support for
https://issues.apache.org/jira/browse/MESOS-1554 would be awesome :) ( once
released ) without forcing dedicated service.

/*******************************************
Joe Stein
Founder, Principal Consultant
Big Data Open Source Security LLC
http://www.stealth.ly
Twitter: @allthingshadoop
********************************************/
On Dec 1, 2014 4:17 PM, "Bill Farner" <wf...@apache.org> wrote:

> Now that 0.6.0 is buttoned up, it's time to think about what we would like
> to shoot for in 0.7.0 [1]!
>
> Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor'
> release to allow us to wrap it up by mid Q1.  So while lofty goals are more
> than welcome in JIRA, let's be somewhat resistant to them in the upcoming
> release.
>
> To summarize what's currently on the docket, we have:
> - removal of several minor deprecated behaviors [2]
> - begin phasing out the 'v1' client
> - promote server-side updates, phase out client-side job update behavior
>
> With that in mind, what else would you all (non-committers welcome) like to
> see in 0.7.0?
>
>
> [1] https://issues.apache.org/jira/browse/AURORA-872
> [2] https://issues.apache.org/jira/browse/AURORA-423
>
>
> -=Bill
>