It might be a first step towards that, but I don't think the currently scoped authentication work includes limiting read access via the UI.
On Thu, Feb 19, 2015 at 2:22 PM, Erb, Stephan <stephan....@blue-yonder.com> wrote: > We would be interested in the Shiro authentication track as well. > > As I understand it, is a prerequisite for a more refined security model > (including the observer deprecation) where we can hinder users from looking > into each others sandboxes. > > Regards, > Stephan > ________________________________________ > From: Joshua Cohen <jco...@twopensource.com> > Sent: Thursday, February 19, 2015 6:47 PM > To: dev@aurora.incubator.apache.org; jfarr...@apache.org > Subject: Re: Soliciting feature requests for 0.8.0 > > Big +1 for getting Shiro in, as it will require a deprecation cycle before > we can remove the old auth system, and the less time we have both hanging > around the better. > > I'd love to see better packaging/distribution as well (AURORA-951). > > On Thu, Feb 19, 2015 at 9:40 AM, Jake Farrell <jfarr...@apache.org> wrote: > > > Would love to see AURORA-951: debian packaging make it into 0.8.0. > > > > AURORA-1031: pesos seems like it might be a big change and might be worth > > waiting till 0.9.0 so it can get more eyes on it and some time to soak in > > tests > > > > -Jake > > > > > > > > On Thu, Feb 19, 2015 at 12:19 PM, Bill Farner <wfar...@apache.org> > wrote: > > > > > Hi Folks, > > > > > > I'd like to get the ball rolling on 0.8.0 by seeking input from the > > > community about what you all would like to see in the next release. > Bear > > > in mind that we are aiming to release about once per month, so that > > > duration should help guide the number and complexity of features we > > target. > > > > > > We seeded this discussion in this week's IRC meeting, and had a few > early > > > suggestions: > > > > > > AURORA-809: authentication with shiro > > > > > > AURORA-1024: dual read thermos checkpoint data (a step towards retiring > > the > > > thermos observer) > > > > > > (no ticket): lift server-side job update coordination to default, > > deprecate > > > client-orchestrated updates > > > > > > AURORA-1031: replace libmesos in the executor with pesos, simplifying > the > > > python build significantly > > > > > > > > > Jake Farrell has volunteered to act as Release Manager for 0.8.0 > (thanks, > > > Jake!), but if any other PPMC member would like to cut their teeth at > > this, > > > he will happily be relieved of the duty :-) > > > > > > So with that, please feel free to +/-1, +0 individual features listed > > > above, or suggest additional features we should target! > > > > > > > > > -=Bill > > > > > >
