<div dir="ltr"><div>Linode-stuff is right down my alley. Something I could probably do while still sleeping. Hence, I'm volunteering.<br><br></div><div>/Alexander Rydekull<br></div><div><br><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Jan 23, 2013 at 2:40 AM, Karsten 'quaid' Wade <span dir="ltr"><<a href="mailto:kwade@redhat.com" target="_blank">kwade@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All:<br>
<br>
I'm going to be on vacation from 25 Jan to 08 Feb, with a few days of<br>
concentrated in-the-office on 31 Jan, 01 Feb (and a visit to FOSDEM<br>
following that.) We should plan that I won't be available at all during<br>
those two weeks. (I'll check in, I'll have a phone, but let's not rely<br>
upon me for emergencies, OK?)<br>
<br>
This (and other reasons) prompted me to write down who is assigned to<br>
what for this team:<br>
<br>
<a href="http://www.ovirt.org/Infrastructure_team_assignments" target="_blank">http://www.ovirt.org/Infrastructure_team_assignments</a><br>
<br>
Looking at what I may be the only person who can do:<br>
<br>
1. Manage Linode via their dashboard.<br>
2. Manage Mailman - new lists, fixes, etc.<br>
3. Do obscure things on the Linode.<br>
4. Run ovirtbot.<br>
<br>
Anything I'm missing?<br>
<br>
To address:<br>
<br>
1. For Linode, I can add other users to give them full permissions to do<br>
what I've been doing - restarting the VM, etc. Anyone interested, able,<br>
or willing to do this?<br>
<br>
2. For Mailman, anyone with ssh + sudo on Linode can do the usual tasks:<br>
<br>
<a href="http://www.ovirt.org/Creating_and_configuring_mailing_lists" target="_blank">http://www.ovirt.org/Creating_and_configuring_mailing_lists</a><br>
<br>
3. Obscure Linode things should all be documented here:<br>
<br>
<a href="http://www.ovirt.org/Category:Infrastructure_documentation" target="_blank">http://www.ovirt.org/Category:Infrastructure_documentation</a><br>
<a href="http://www.ovirt.org/Category:Infrastructure_SOP" target="_blank">http://www.ovirt.org/Category:Infrastructure_SOP</a><br>
<br>
4. Anyone with ssh+sudo on <a href="http://linode01.ovirt.org" target="_blank">linode01.ovirt.org</a> can restart the bot:<br>
<br>
<a href="http://www.ovirt.org/Running_ovirtbot" target="_blank">http://www.ovirt.org/Running_ovirtbot</a><br>
<br>
Result: if a few folks can volunteer to be Linode admins, then we'll<br>
have complete coverage and backups for me while I'm not available.<br>
<br>
Final items on my mind:<br>
<br>
* Both sets of new servers are available, I'll be putting everyone's<br>
sshkeys + sudo on those boxes so you can do work immediately on Jenkins<br>
master and slaves.<br>
<br>
* Let's proceed with Jenkins migration work but we probably want to wait<br>
until I'm back available before we actually migrate anything.<br>
<br>
* If you think you can handle e.g. Jenkins master migration entirely, we<br>
just need to make sure someone @<a href="http://redhat.com" target="_blank">redhat.com</a> will request and manage the<br>
DNS change.<br>
<br>
* Dave offered to work on the Mailman migration plan so we can execute<br>
that as soon as I'm back available.<br>
<br>
Thanks - Karsten<br>
<span class="HOEnZb"><font color="#888888">--<br>
Karsten 'quaid' Wade, Sr. Analyst - Community Growth<br>
<a href="http://TheOpenSourceWay.org" target="_blank">http://TheOpenSourceWay.org</a> .^\ <a href="http://community.redhat.com" target="_blank">http://community.redhat.com</a><br>
@quaid (<a href="http://identi.ca/twitter/IRC" target="_blank">identi.ca/twitter/IRC</a>) \v' gpg: AD0E0C41<br>
<br>
</font></span><br>_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>/Alexander Rydekull
</div>