On Sun, 7 Apr 2019 at 13:44, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On 4/5/19 10:34 AM, Stephen John Smoogen wrote: > > On Fri, 5 Apr 2019 at 13:15, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > > So I was leaving the definitions vague as some build boxes are high > > priority (no redundancy or major outage) and some are low priority > > because they have a large amount of redundancy. I was figuring > > Yeah, but you still need to notify people about those, and the audience > is different, so you will need to notify everyone and mention the > specific services. ;( > Yes. That should still be part of the process. I should have had that. > > > > low priority: > > - proxies not shared on high priority external virthosts > > - builders and other high redundancy build systems > > - openshift systems IF updated and drained properly > > - other external services which have low SLE > > Yeah, many or all of these could be done anytime, users shouldn't notice > an outage (prodixes can be taken out of dns, builders disabled, > openshift can migrate things around), etc. > If there is one thing I have noticed in the last 10 years.. is that someone always notices... and probably had something Important(TM) that this broke and want to make sure we notify. Even weekend reboots of builders seem to get some module build to fail and an angry developer comment in #fedora-devel (at least the last 3 reboot cycles). The proxies get similar issues because even if we pull it out of DNS.. we don't control everyone else who have DNS servers expecting 24 hours before stuff goes away. > > high priority: > > services with no redundancy: > > - databases > > - pagure > > - src > > - etc etc > > services with high outage effects > > - koji? > > - etc etc > > Yeah, although even here... for example, we can switch to koji02 and > reboot koji01 without people really noticing. Of course kojidb is > another matter. > That was the reason for the ?. Some things I know we can do and others I do and find out that 02 is actually not a redundant system but used for something else.. 'oh yeah I would rename that but was waiting until we redesigned after the next major overhaul.' So I figure we will need to go through each service and categorize this but we need to do that anyway for other reasons. > kevin > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
