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 CB35717647 for ; Thu, 19 Feb 2015 22:25:47 +0000 (UTC) Received: (qmail 89328 invoked by uid 500); 19 Feb 2015 22:25:47 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 89274 invoked by uid 500); 19 Feb 2015 22:25:47 -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 89259 invoked by uid 99); 19 Feb 2015 22:25:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2015 22:25:47 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of Stephan.Erb@blue-yonder.com does not designate 80.67.31.94 as permitted sender) Received: from [80.67.31.94] (HELO smtprelay05.ispgateway.de) (80.67.31.94) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2015 22:25:21 +0000 Received: from [85.115.23.42] (helo=ex2013-2.phi-tps.local) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.84) (envelope-from ) id 1YOZUU-0001iW-3m; Thu, 19 Feb 2015 23:22:38 +0100 Received: from Ex2013-3.phi-tps.local (10.0.1.2) by ex2013-2.phi-tps.local (10.1.1.3) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Thu, 19 Feb 2015 23:22:37 +0100 Received: from Ex2013-3.phi-tps.local ([fe80::4d9e:6cb4:c9fc:a31c]) by Ex2013-3.phi-tps.local ([fe80::4d9e:6cb4:c9fc:a31c%14]) with mapi id 15.00.1044.021; Thu, 19 Feb 2015 23:22:16 +0100 From: "Erb, Stephan" To: "dev@aurora.incubator.apache.org" , "Jake Farrell" Subject: Re: Soliciting feature requests for 0.8.0 Thread-Topic: Soliciting feature requests for 0.8.0 Thread-Index: AQHQTGhYgOjckPisT0uCtTUHvbAL9Zz4LNIAgAAB/YCAAFsR9g== Date: Thu, 19 Feb 2015 22:22:16 +0000 Message-ID: <1424384972177.50126@blue-yonder.com> References: , In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-process: ESTProcessDone x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.193.0.30] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Df-Sender: MTE3NDQ4Ng== X-Virus-Checked: Checked by ClamAV on apache.org We would be interested in the Shiro authentication track as well. =0A= =0A= As I understand it, is a prerequisite for a more refined security model (in= cluding the observer deprecation) where we can hinder users from looking in= to each others sandboxes.=0A= =0A= Regards,=0A= Stephan=0A= ________________________________________=0A= From: Joshua Cohen =0A= Sent: Thursday, February 19, 2015 6:47 PM=0A= To: dev@aurora.incubator.apache.org; jfarrell@apache.org=0A= Subject: Re: Soliciting feature requests for 0.8.0=0A= =0A= Big +1 for getting Shiro in, as it will require a deprecation cycle before= =0A= we can remove the old auth system, and the less time we have both hanging= =0A= around the better.=0A= =0A= I'd love to see better packaging/distribution as well (AURORA-951).=0A= =0A= On Thu, Feb 19, 2015 at 9:40 AM, Jake Farrell wrote:= =0A= =0A= > Would love to see AURORA-951: debian packaging make it into 0.8.0.=0A= >=0A= > AURORA-1031: pesos seems like it might be a big change and might be worth= =0A= > waiting till 0.9.0 so it can get more eyes on it and some time to soak in= =0A= > tests=0A= >=0A= > -Jake=0A= >=0A= >=0A= >=0A= > On Thu, Feb 19, 2015 at 12:19 PM, Bill Farner wrote:= =0A= >=0A= > > Hi Folks,=0A= > >=0A= > > I'd like to get the ball rolling on 0.8.0 by seeking input from the=0A= > > community about what you all would like to see in the next release. Be= ar=0A= > > in mind that we are aiming to release about once per month, so that=0A= > > duration should help guide the number and complexity of features we=0A= > target.=0A= > >=0A= > > We seeded this discussion in this week's IRC meeting, and had a few ear= ly=0A= > > suggestions:=0A= > >=0A= > > AURORA-809: authentication with shiro=0A= > >=0A= > > AURORA-1024: dual read thermos checkpoint data (a step towards retiring= =0A= > the=0A= > > thermos observer)=0A= > >=0A= > > (no ticket): lift server-side job update coordination to default,=0A= > deprecate=0A= > > client-orchestrated updates=0A= > >=0A= > > AURORA-1031: replace libmesos in the executor with pesos, simplifying t= he=0A= > > python build significantly=0A= > >=0A= > >=0A= > > Jake Farrell has volunteered to act as Release Manager for 0.8.0 (thank= s,=0A= > > Jake!), but if any other PPMC member would like to cut their teeth at= =0A= > this,=0A= > > he will happily be relieved of the duty :-)=0A= > >=0A= > > So with that, please feel free to +/-1, +0 individual features listed= =0A= > > above, or suggest additional features we should target!=0A= > >=0A= > >=0A= > > -=3DBill=0A= > >=0A= >=0A=