Hi. The database for toolsadmin.wikimedia.org (aka Striker) is hosted on m5. We're planning to set up a second Striker installation for usage on the Toolforge testing deployment (toolsbeta), and need a second database for that. I assume m5 would be a logical place for that as well.
- QPS: Occasional bursts of few queries as a small number of humans sometimes use the site.
- Size: (An estimation is fine) I'd guess a double-digit number of megabytes.
- DB Name: striker_toolsbeta
- User: striker_toolsbeta / striker_toolsbeta_admin
- Accessed from server (s): cloudweb1003/4 (via the proxies)
- Backup Policy: Needed? Frequency? This is test data that's mostly non-canonical so strictly speaking it doesn't need to be backed up, but I believe you're taking some backups for the entire section which would include this database?
- Grants needed: same as the current striker/striker_admin users but on the new database