View source for Manual for ops on duty

a page that is supposed to help the current "op on duty" in charge of typical "ops-requests" RT tickets ([[Interrupts Rotation]])

== 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 <code>/etc/exim4/aliases/</code>. 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 [https://labsconsole.wikimedia.org/wiki/Help:Access Help:Access] on labsconsole wiki.

also see [[LDAP]]

=== access requests ===

If a request asks for things like new shell accounts, access to additional servers, log files, personal data, admin roles in systems like mailman, Bugzilla, data center access, opening a firewall rule etc. then it is an access request and should be moved from the regular ops-requests queue to the "access-requests" queue. There is also a tag for access requests in RT but it has been superseded by the separate queue. Make sure the tickets have valid approvals before processing or at least before merging them. Approvals could either be on the RT ticket or on a gerrit change. In that case link from the ticket to the gerrit change.


==== creating new shell users ====

Always make sure you use a new UID that has not been used before.

==== IRC channel access ====
 /query chanserv
 help access
 access #channel list
 access #channel add *!*@wikimedia/cloak 

 14:07 -ChanServ(ChanServ@services.)- Flags +Aiortv were set on ...

=== powercycling / reboots ===

== Duty desk rotation - who is next? ==

* 12/24 - Leslie
* 12/31 - Faidon
* 1/8 - AOtto
* 2/11 - PYoungmeister