Jenkins build is back to normal : AuroraBot #3761

See

Re: [VOTE] Graduate Apache Aurora as a TLP

+1

Soliciting feature requests for 0.8.0

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. W

Re: [VOTE] Graduate Apache Aurora as a TLP

+1 On Wednesday, February 18, 2015, Jake Farrell wrote: > Based on community discussions on the project mailing lists and the current > state of Apache Aurora (incubating) I would like to start a community VOTE > for Apache Aurora (incubating) to graduate from the Incubator and become a > Top Le

Re: Soliciting feature requests for 0.8.0

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 wrote: > Hi Folks,

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 wrote: > Woul

Re: [VOTE] Graduate Apache Aurora as a TLP

+1 ! — Sent from Mailbox On Thu, Feb 19, 2015 at 11:32 AM, Alexius Ludeman wrote: > +1 > On Wednesday, February 18, 2015, Jake Farrell wrote: >> Based on community discussions on the project mailing lists and the current >> state of Apache Aurora (incubating) I would like to start a community

Fwd: Help us review #MesosCon 2015 proposals

Given the overlap that exists between the Aurora and Mesos communities, I thought it would be worthwhile to pass along this invitation to review #MesosCon 2015 proposals -- reviewing is a great way to get the pulse of what the Mesos community is actively working on. Cheers, Dave - Original m

Re: Soliciting feature requests for 0.8.0

I would like to see AURORA-1132 and AURORA-1133 addressed for 0.8.0. I would also like us to document how to set up mesos/aurora besides the vagrant script. On Thu, Feb 19, 2015 at 9:47 AM, Joshua Cohen wrote: > Big +1 for getting Shiro in, as it will require a deprecation cycle before > we can

Re: Soliciting feature requests for 0.8.0

Things I'd like to see because they'd make my life easier: AURORA-987 Create a first-class REST-like scheduler interface. AURORA-1107: Add support for mounting external volumes into docker containers. +1 on the documentation front also; there's a lot I've had to figure out myself (by asking on IR

Have your questions answered by tonight's Apache Aurora user panel

Hi All, At tonight's Apache Aurora meetup[1], we'll have a panel discussion with Aurora users. We're encouraging folks to tweet us questions before the meetup that you'd like the panel to answer. You can reply here: https://twitter.com/ApacheAurora/status/568485945978314752 For those that can't

Re: Soliciting feature requests for 0.8.0

A script and/or a document that explains how to quickly set up Aurora in Amazon EC2 or Google Cloud would really help the project get traction. Dave Lester mentioned this in a conversation with me, and it made a lot of sense. On Thu, Feb 19, 2015 at 10:53 AM, Hussein Elgridly < huss...@broadinstit

Making sense of Aurora terminal states

I've just spent the afternoon making a flowchart out of TaskStateMachine.java in an attempt to figure out what Aurora states actually mean. Given that all the jobs I submit have unique names and I don't permit retries, I would like to put together a set of rules that determine whether a job is _rea

Re: Soliciting feature requests for 0.8.0

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 ___

Re: Making sense of Aurora terminal states

On Thu, Feb 19, 2015 at 1:27 PM, Hussein Elgridly < huss...@broadinstitute.org> wrote: > I've just spent the afternoon making a flowchart out of > TaskStateMachine.java in an attempt to figure out what Aurora states > actually mean. Given that all the jobs I submit have unique names and I > don't

Re: [VOTE] Graduate Apache Aurora as a TLP

+1 Sent from my iPhone > On Feb 18, 2015, at 5:26 PM, Jake Farrell wrote: > > Based on community discussions on the project mailing lists and the current > state of Apache Aurora (incubating) I would like to start a community VOTE > for Apache Aurora (incubating) to graduate from the Incubator

Re: Soliciting feature requests for 0.8.0

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 wrote: > We would be interested in the Shiro authentication track as well. > > As I understand it, is a prereq