Re: Mirror maintenance windows, related communication, order of checks (Was: Re: pl1.php.net Disabled)
[email protected] (Patrick Schaaf)
| Newsgroups | php.mirrors |
|---|---|
| Message-ID | <CAJ26g5SbFkVpqz82BHDFXbWWRq5Hpsm4X64Hq9GyQwAP1nwktA@mail.gmail.com> |
Am 30.04.2015 19:07 schrieb "Patrick Schaaf" <[email protected]>: > > Would you also like to be prenotified when I update PHP or the OS/kernel on the boxes, which when it happens, sometimes takes 30 seconds for a reboot or rollback in case of problems? So far during the last few years, I simply relied on the automation to spot somewhat prolongued (unplanned) episodes, and for short upgrades including reboots I just did it. If we want to go down this path, and I can see it would be good for the users, maybe a way for us mirror operators to actively disable and reenable the mirror, would be the best (least amount of up front communication and time coordination)? I'm thinking about a dedicated "enable/disable" SSH key per mirror, with some automation at php.net central that the key could trigger to take the mirror out of service, and back into service. If you are interested, I'd certainly volunteer for co-development and testing of such a mechanism. best regards Patrick