On September 29, 2010, Martin Pool wrote: > On 30 September 2010 06:07, Francis J. Lacoste > > <[email protected]> wrote: > > I like the idea of a fixed downtime budget a lot. > > > > What do we need to make it happen? > > > > My thoughts: > > > > * A feedback mechanism allowing us to track how much of the budget is > > spent. * Something like a script that extracts a measure from the > > staging update? * Once the budget is spent, no more DB changes. > > * We probably need a way to input the budget for case where a OS > > maintenance task will shrink the DB budget. > > It seems like, by saying "no more DB changes", you're anticipating a > budget that refills only every several months or so. That's a pretty > interesting idea. I thought what Robert was saying, though, was a cap > at 90 minutes on any single outage.
No, I wasn't. I guess my third item caused confusion. Assuming a 90 minutes downtime budget. If we have a HW maintenance task that takes 30 minutes, we only have 60 minutes for DB changes this month. Hope this clarifies this. -- Francis J. Lacoste [email protected]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
