Change Details

This task will detail the overall migration of the maint-announce queue in RT into phabricator. The maint-announces come in via an alias, and then are piped into RT. Once in RT, the ops clinic person triages announcements and ensures they are placed on the operations tracking gcal. We'll need to relocate this queue/project into phabricator, as it is the last remaining use of RT. Currently, maintainance notifications are triaged by our ops clinic duty person for the week. Their steps are detailed on https://wikitech.wikimedia.org/wiki/Ops_Clinic_Duty#Responsibilities They include: * Maintain the 'maint-announce' queue and calendar: ** This is the ONLY RT queue left for Ops Clinic Duty coverage. ** Modify ticket Subject to prepend dates of effect in big-endian order (ex: 2014-11-06 to 2014-11-09: Equinix chiller maintenance) ** Merge follow-up tickets as needed so that there is one per maintenance event ** There is [https://office.wikimedia.org/wiki/Office_IT/Calendars#Human_calendars a gcal shared with all WMF named 'Ops maintenance & contracts']. All maint-announce queue tickets should be entered into this calendar. *** Include the circuit IDs and RT#s in the entry. (See entries on 2014-10-07 for examples.) *** Update the ticket in RT from 'new' to 'open' and comment that it has been added to the ops tracking gcal.

This task will detail the overall migration of the maint-announce queue in RT into phabricator. The maint-announces come in via an alias, and then are piped into RT. Once in RT, the ops clinic person triages announcements and ensures they are placed on the operations tracking gcal. We'll need to relocate this queue/project into phabricator, as it is the last remaining use of RT. Currently, maintainance notifications are triaged by our ops clinic duty person for the week. Their steps are detailed on https://wikitech.wikimedia.org/wiki/Ops_Clinic_Duty#Responsibilities They include: * Maintain the 'maint-announce' queue and calendar: ** This is the ONLY RT queue left for Ops Clinic Duty coverage. ** Modify ticket Subject to prepend dates of effect in big-endian order (ex: 2014-11-06 to 2014-11-09: Equinix chiller maintenance) ** Merge follow-up tickets as needed so that there is one per maintenance event ** There is [https://office.wikimedia.org/wiki/Office_IT/Calendars#Human_calendars a gcal shared with all WMF named 'Ops maintenance & contracts']. All maint-announce queue tickets should be entered into this calendar. *** Include the circuit IDs and RT#s in the entry. (See entries on 2014-10-07 for examples.) *** Update the ticket in RT from 'new' to 'open' and comment that it has been added to the ops tracking gcal. Please note that when this is done, RT can be made read-only and all mail relays from RT killed (NOT FORWARDED). The maint-requests go to aliases, not to RT, they can be redirected to phabricator.

This task will detail the overall migration of the maint-announce queue in RT into phabricator. The maint-announces come in via an alias, and then are piped into RT. Once in RT, the ops clinic person triages announcements and ensures they are placed on the operations tracking gcal. We'll need to relocate this queue/project into phabricator, as it is the last remaining use of RT. Currently, maintainance notifications are triaged by our ops clinic duty person for the week. Their steps are detailed on https://wikitech.wikimedia.org/wiki/Ops_Clinic_Duty#Responsibilities They include: * Maintain the 'maint-announce' queue and calendar: ** This is the ONLY RT queue left for Ops Clinic Duty coverage. ** Modify ticket Subject to prepend dates of effect in big-endian order (ex: 2014-11-06 to 2014-11-09: Equinix chiller maintenance) ** Merge follow-up tickets as needed so that there is one per maintenance event ** There is [https://office.wikimedia.org/wiki/Office_IT/Calendars#Human_calendars a gcal shared with all WMF named 'Ops maintenance & contracts']. All maint-announce queue tickets should be entered into this calendar. *** Include the circuit IDs and RT#s in the entry. (See entries on 2014-10-07 for examples.) *** Update the ticket in RT from 'new' to 'open' and comment that it has been added to the ops tracking gcal. Please note that when this is done, RT can be made read-only and all mail relays from RT killed (NOT FORWARDED). The maint-requests go to aliases, not to RT, they can be redirected to phabricator.