Merge lp:~wgrant/launchpad/ppa-reset-2.0-db into lp:launchpad/db-devel
Status: | Merged |
---|---|
Merged at revision: | 12710 |
Proposed branch: | lp:~wgrant/launchpad/ppa-reset-2.0-db |
Merge into: | lp:launchpad/db-devel |
Diff against target: |
16 lines (+12/-0) 1 file modified
database/schema/patch-2209-57-0.sql (+12/-0) |
To merge this branch: | bzr merge lp:~wgrant/launchpad/ppa-reset-2.0-db |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stuart Bishop (community) | db | Approve | |
Launchpad code reviewers | Pending | ||
Review via email: mp+223395@code.launchpad.net |
Commit message
Add Builder.
Description of the change
Add new database columns to implement the Launchpad virtual builder reset protocol 2.0 for Scalingstack (described in https:/
The schema will evolve in future as our builder model grows cloudier, and with some luck the clean_status column will be dead before the year is out. But it remains to be seen exactly how it should be replaced, so it will do for now.
A new protocol version enum column has been added, as well as a clean_status column to track whether a slave is currently CLEAN, DIRTY or CLEANING. Wherever the cleanliness is in question, it fails safe to DIRTY. There's also a timestamp of the most recent clean_status change, to let us more easily track when things are stuck.
https:/
All good.