Autoscaling/ Cluster Events

[zimt28]

It would be nice if we could run code on certain events. For example, if the average load is more than 90%, launch a new server (I think DigitalOcean & friends allow this using their APIs). Or at least notify the admin. Or remove a server, if the load goes below a certain value. And having a number of current servers would be nice, so we could scale but check before removing servers so that we keep at least three servers or so.

I'm not sure what events and data would be helpful, but basically a cluster API would be nice :)

[rhyslbw]

👍

[ghost]

I really like the idea too. But I think this logic should be outside the productive instances. What we need is an administration layer which knows everything about all the cluster instances and let us manage the nodes, start instances, create new instances on DigitalOcean (with the DO API) and collect all the system and analytics data we need to run our app efficiently. What we need is a BigBrother instance, but I personally like the term MotherShip more ;)

[devonbarrett]

👍

[rhyslbw]

Kadira is the natural place for this, utilising the existing alerts module to setup scaling triggers etc. By that point I'm guessing there would be a Cluster API that can be used to create a management service app if not wanting to use Kadira.

See #22

[arunoda]

Good idea.

On Sun, May 10, 2015 at 7:34 AM Rhys Bartels-Waller <
[email protected]> wrote:

Kadira is the natural place for this, utilising the existing alerts module
to setup scaling tiggers etc. By that point I'm guessing there would be a
Cluster API that can be used to create a management service app if not
wanting to use Kadira.

See #22 #22

—
Reply to this email directly or view it on GitHub
#18 (comment).

[sakulstra]

Are there any news on this? I would love to somehow help with this. We're currently running an app which needs like 5-6 instances in prime time and 1-2 and night. Would be nice to automate the start/shutdown process.