Manual for ops on duty

Revision as of 21:20, 20 November 2012

a page that is supposed to help the current "op on duty" in charge of typical "ops-requests" RT tickets

how to handle IRC requests

If reasonable politely ask to turn into an RT ticket in the "ops-requests" queue by either simply mailing to RT or by using the web interface. If requestor lacks a real RT user (real = not just auto-created via mail without decent permissions) and is staff, offer to create one. If user relies on email replies to a ticket ensure to use "Reply" in RT instead of just commenting.

common, small "ops-requests" tickets

mail aliases

These are handled on mchenry. Just ssh there and edit files in /etc/exim4/aliases/. You may want to create a backup copy of files just in case, especially if you make larger changes. It is nice to add the corresponding RT ticket number in a comment near changed aliases. Experience shows that it can be quite handy to be able to quickly answer questions like when exactly something has been changed and who requested it. There is one file or symlink per domain name. 95% of the time the requests are just regarding the "wikimedia.org" file. In other cases make sure you check for possible symlinks and realize which domains you are actually changing when editing a specific file.

LDAD group changes

For example new hires should be added to "wmf" or newly created labs users who were svn users in the past.

See "modify-ldap-group" on Help:Access on labsconsole wiki.

also see LDAP

access requests

powercycling / reboots