arsenal-devel team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxx>]

On Thu, Feb 10, 2011 at 02:26:29PM +1100, Martin Pool wrote:
> On 10 February 2011 12:29, Bryce Harrington <bryce@xxxxxxxxxxxxx> wrote:
> > I run a heap of various automated scripts to process/measure/update bug
> > reports and other stuff on launchpad.
> > To solve this, I've dummied up a little script, launchpad-service-status:
> >
> >  http://bazaar.launchpad.net/~arsenal-devel/arsenal/python-launchpadlib-toolkit/view/head:/scripts/launchpad-service-status
> 
> Thanks for that.  During the downtime I was just contemplating
> <http://tumblruptime.icodeforlove.com/>.
> 
> Part of this is that Launchpad seems to reject even readonly api calls
> when Launchpad is in readonly upgrade mode.
> 
>   <https://bugs.launchpad.net/launchpad/+bug/716175>

Yep, I noticed this as well.  We've added readonly support to all the
scripts that can work without write access, so if it worked that would
largely take care of things.

> I wonder if lplib should map '503' into a more specific
> ServiceUnavailable exception, so that at least the failures are clean.
>  However as you say, you probably still care about expected vs
> unexpected errors.
> 
> Perhaps the 503 message should say "this is planned downtime until
> $time" in a machine-readable way.

Machine-readable sounds attractive.

Bryce