Hi Florian,
have you looked at what Mesos is already offering out of the box [1]? Maybe
there is a way to implement your features by relying on Mesos directly, instead
of making the Aurora implementation more flexible.
As you've mentioned, the lifecycle endpoints abort and quit seem to be qui
If i'm reading the code correctly, the only way to use mesos' health checks
is with the command executor? Can somebody check my work on that?
Some other context around health checks to keep in mind:
- there is a review [1] in-flight for the executor to delay the transition
to RUNNING until the fi
To answer OP:
(1) seems perfectly reasonable, i don't foresee any pitfalls
(2) seems reasonable as well. Thrift unions help a bit here. Just
spitballing, but this general arrangement comes to mind:
struct TcpCheck {
...
}
struct HttpStatusCheck {
...
}
struct HttpPayloadCheck {
...
}
Aha, docs in the proto file confirm my read of the implementation:
// A health check for the task (currently in *alpha* and initial
> // support will only be for TaskInfo's that have a CommandInfo).
> optional HealthCheck health_check = 8;
-=Bill
On Sat, Feb 21, 2015 at 10:47 AM, Bill Far
>
> Might I suggest folding this information into the user guide?
You seem like you are now sufficiently-equipped to add this doc. Any
chance you're game to write the doc you wish you had read? :-)
Just to be absolutely clear on this: KILLING -> LOST will _never_ result in
> a reschedule? What
> You seem like you are now sufficiently-equipped to add this doc. Any
> chance you're game to write the doc you wish you had read? :-)
Possibly. Time constraints aside, my concern is that the questions I've
asked (and the answers I was seeking) were based on the assumption that my
jobs all had u
+1
On Fri, Feb 20, 2015 at 3:42 PM, Joseph Jacks wrote:
> +1
>
> Thanks,
> JJ.
>
>
> > 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
+1
On Sat, Feb 21, 2015 at 11:24 PM, John Sirois wrote:
> +1
>
> On Fri, Feb 20, 2015 at 3:42 PM, Joseph Jacks wrote:
>
> > +1
> >
> > Thanks,
> > JJ.
> >
> >
> > > On Feb 18, 2015, at 5:26 PM, Jake Farrell wrote:
> > >
> > > Based on community discussions on the project mailing lists and the
Hi,
There's been some talk on IRC about better documentation for deploying
Aurora in a non-Vagrant environment, and requests that users share their
deployment notes. Our devops folks are putting together Puppet scripts for
our production environment, but meanwhile I've been using Mesosphere as a
d
