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. ;( > > 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. > 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. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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
