launchpad-dev team mailing list archive

["Francis J. Lacoste" <francis.lacoste@xxxxxxxxxxxxx>]

Thanks for the clarifications!

Also: Matt Revell will take care of writing a blog post and notifying
stakeholders that they should now expect "fastdowntime".

Cheers

On 11-09-08 11:33 AM, Stuart Bishop wrote:
> On Thu, Sep 8, 2011 at 10:26 PM, Francis J. Lacoste
> <francis.lacoste@xxxxxxxxxxxxx> wrote:
> 
>> Besides testing on staging, anything you can think of blocking this?
> 
> No, there is nothing blocking Slony-I 2.0. wgrant and myself have both
> been using it for testing locally, so we are pretty confident our
> automation all keeps working fine.
> 
>>> We are scheduled for a real run 2011-09-09 08:30 UTC, applying our
>>> backlog of database patches. The outage should be well within our 5
>>> minute window. It is not yet known which parts of soyuz will be kept
>>> live during the update, and which fragile parts will be shutdown for a
>>> longer period.
>>
>> I thought we were going to apply one patch per fastdowntime session, in
>> order to minimize risk? Is that still the plan? Or are we applying all
>> pending patches in one go?
> 
> I want to apply them all in one go, and managed to browbeat lifeless
> into that. I think there is less risk doing it this way than 7
> somewhat adhoc rollouts over the next week and a half, and the patches
> in the backlog are all benign and boring. My prime motivation though
> is getting devel and db-devel finally back in sync as this is blocking
> things within and outside of the team.
> 

-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature