Hi, I'm also be on PTO on at least some of these days, entering exams period for my MBA. So i probably can't take any of these responsibilities for those days.. But, i'll still keep an open eye for errors on linode and will start working on the new jenkins server, at least on all the pre migration stuff. Eyal. ----- Original Message -----
From: "Karsten 'quaid' Wade" <kwade@redhat.com> To: "infra" <infra@ovirt.org> Sent: Wednesday, January 23, 2013 3:40:06 AM Subject: Vacation coverage: quaid
All:
I'm going to be on vacation from 25 Jan to 08 Feb, with a few days of concentrated in-the-office on 31 Jan, 01 Feb (and a visit to FOSDEM following that.) We should plan that I won't be available at all during those two weeks. (I'll check in, I'll have a phone, but let's not rely upon me for emergencies, OK?)
This (and other reasons) prompted me to write down who is assigned to what for this team:
http://www.ovirt.org/Infrastructure_team_assignments
Looking at what I may be the only person who can do:
1. Manage Linode via their dashboard. 2. Manage Mailman - new lists, fixes, etc. 3. Do obscure things on the Linode. 4. Run ovirtbot.
Anything I'm missing?
To address:
1. For Linode, I can add other users to give them full permissions to do what I've been doing - restarting the VM, etc. Anyone interested, able, or willing to do this?
2. For Mailman, anyone with ssh + sudo on Linode can do the usual tasks:
http://www.ovirt.org/Creating_and_configuring_mailing_lists
3. Obscure Linode things should all be documented here:
http://www.ovirt.org/Category:Infrastructure_documentation http://www.ovirt.org/Category:Infrastructure_SOP
4. Anyone with ssh+sudo on linode01.ovirt.org can restart the bot:
http://www.ovirt.org/Running_ovirtbot
Result: if a few folks can volunteer to be Linode admins, then we'll have complete coverage and backups for me while I'm not available.
Final items on my mind:
* Both sets of new servers are available, I'll be putting everyone's sshkeys + sudo on those boxes so you can do work immediately on Jenkins master and slaves.
* Let's proceed with Jenkins migration work but we probably want to wait until I'm back available before we actually migrate anything.
* If you think you can handle e.g. Jenkins master migration entirely, we just need to make sure someone @redhat.com will request and manage the DNS change.
* Dave offered to work on the Mailman migration plan so we can execute that as soon as I'm back available.
Thanks - Karsten -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra