Yup, I can take the lead on this, I'll work on a design doc first to get
the story straight before I dive into coding.
On Thu, Feb 1, 2018 at 10:28 PM, Meghdoot bhattacharya wrote:
> Thx David. Renan can you take a lead on this?
>
> Yeah we do have separate orchestration for multi aurora cluster
Thx David. Renan can you take a lead on this?
Yeah we do have separate orchestration for multi aurora cluster geo deploy and
blue-green deploys within each cluster but we have also a requirement to
support the flexible controlled rolling deploy inside each cluster like in old
platform. And we r
Yeah that is definitely not possible right now in Aurora. We've built
something external to Aurora (like Spinnaker) that our users use to do this
type of thing (also do it across multiple Schedulers).
Adding this type of "acknowledge before continuing" functionality to the
updater is certainly pos
David here is the scenario that we are looking. Its most likely not supported
but let us know if the changes can be made without much hassle. We can then
research and do a PR.
The use case arises from our current non mesos platform.
Lets say the app has 100 instances. Here is how we will roll i
It's not currently possible with a single API call, you'd have to submit
multiple calls to startJobUpdate, changing the JobUpdateSettings each time.
When you say the size of the batch could change each step - could it change
dynamically (e.g. after you've submitted the call to the Scheduler), or is
