How to AutoScale about mysql HOT 5 CLOSED

We have an open issue to implement telemetry hooks #16. The operator would then get use information provided by the ContainerPilot telemetry endpoint to feed into whatever is scaling the instances (presumably not Compose but whatever lightweight scheduler you might be using).

I don't know if this was the correct place to ask this, is there a mailing list?

This is the right place to ask. There is intentionally no mailing list.

from mysql.

Which Scheduler fits the Triton ecosystem best? Any suggestions?

from mysql.

Unfortunately the Docker ecosystem/community has largely gone the route of "giant mega-orchestrator" over "lightweight scheduler." In the meantime, we've seen workable results with Mesos, and at least one Triton Enterprise customer is driving Compose via their CI/CD systems (this is more-or-less how Joyent's own web properties are deployed). In the near future "Mariposa" will be the best choice.

from mysql.

@Smithx10: one of the first questions to answer here is what metric(s) we'll use to determine when to scale up or down. ContainerPilot 2.0 introduced a telemetry feature specifically to support the monitoring of key metrics that can help determine scaling. I opened #16 to implement that for MySQL in this repo.

Feedback, suggestions, or pull requests in #16 would be greatly appreciated.

from mysql.

Closing as a duplicate of #16. Please continue the conversation there.

from mysql.