GitLab is down: urgent

[davean]

There is the haskell-infrastructure group, who has access. Its knowledge of
the peculiarities of each of the very different services that's harder to
keep up to date between people.

If Ben was hit by a bus it is prepared to be handled. With this diversity
and level of manpower though stepping in tends to be a high cost operation
so it is done when necessary.

-davean

On Fri, Mar 19, 2021 at 10:00 AM Richard Eisenberg <rae at richarde.dev> wrote:

> Hi Ben,
>
> Thanks for getting the fix in so quickly.
>
> However: suppose you were unavailable to do this, due to a well-deserved
> holiday perhaps. Who else has the credentials and know-how to step in?
>
> I feel as if we should have a resource somewhere with a definitive list of
> critical services and who has access to what. Perhaps this list should be
> kept private, in case the knowledge itself is a (small) security risk --
> but it should be written down and shared widely enough that it is unlikely
> for all people with access to be unavailable at the same time.
>
> Do we have such a resource already?
>
> Richard
>
> > On Mar 19, 2021, at 9:47 AM, Ben Gamari <ben at smart-cactus.org> wrote:
> >
> > Simon Peyton Jones via ghc-devs <ghc-devs at haskell.org> writes:
> >
> >> GHC's GitLab seems to be down.  Ben?
> >> (I just get 502's)
> >
> > Everything should now be back to normal. I have sent a post-mortem
> > describing the failure mode and fix. Apologies for the inconvenience!
> >
> > Cheers,
> >
> > - Ben
> > _______________________________________________
> > ghc-devs mailing list
> > ghc-devs at haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20210319/c94a8e14/attachment.html>