Vacation coverage: quaid

[Mike Burns]

On Tue, 2013-01-22 at 17:40 -0800, Karsten 'quaid' Wade wrote:
> 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.

I can do the above in an emergency, but I don't have time to really
volunteer as a point person.  But if things break, then I can probably
help.

Mike

> 
> 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
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra