Page MenuHomePhabricator

Investigate database options in Labs for running the program dashboard
Closed, ResolvedPublic

Description

(see T127390: Meet with Security and Ops about a long-term productionization plan for background)

Since a fully production dashboard is still a long way off, we need to run the application with as much stability and performance as can be afforded by Labs infrastructure. The question came up in our meeting about whether it's possible to get read/write access from Labs to a single database on bare metal hardware (or at least something with a performant/non-ephemeral volume), or whether we should instead set up DB replication across a handful (2+) of Labs instances to ensure better availability and balance reads.

Event Timeline

@fgiunchedi assigning this to you only because you mentioned that you'd look into it during our meeting. Feel free to pass it back if you don't have the time and I'll reach out to others.

@dduvall no worries!
there is no "database as a service" in labs ATM (though something like that might be available for tools labs?)
though it should be fairly simple to setup mysql on a labs instance via mariadb::misc role, I haven't looked into replication still though, HTH!

Thanks, @fgiunchedi! I guess that answers that question. I'll assess the mariadb::misc role.