We'd like to store some version control metadata in a database. The first consumer of this database will be "headless try" (bug 1055298). We're looking to create a bi-directional mapping between bundle id/url <-> changesets, along with some other metadata, such as parent changeset for the root changeset in each bundle. Exact schema will come later. Takeaway is that the database will be modest in size. Looking at tens of megabytes with an upper bound on a few hundred thousand rows. Over time, I have ideas for how this database will evolve to capture a lot more data. I'm not sure if we should plan for scale now or wait and do a hardware migration later. The SLA of this database should be no less than our SLA for version control and Firefox automation. An outage of this database will cause Try and corresponding parts of Firefox automation to go down. I'm not sure what implications this has for backup, replication, etc. With what I want to eventually accomplish with this database, I can make the argument that a graph store like Neo4J is better suited. However, we can cross that bridge later. We know how to deploy relational databases. Let's stand a modest one up to solve the problem at hand.
Summary: PostgreSQL database for storing version control data → PostgreSQL database and/or server for storing version control data
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/279] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/762] [kanban:engops:https://kanbanize.com/ctrl_board/6/279]
Happy to review schema or help out in any way! :)
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/762] [kanban:engops:https://kanbanize.com/ctrl_board/6/279] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/762]
Removing this as a blocker for headless try. We'll use a local SQLite database for the short to medium term.
If we want to go down this road, it will almost certainly be in EC2 and I'll be able to feed myself.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.