19:00:00 #startmeeting Infrastructure (2011-09-15) 19:00:00 Meeting started Thu Sep 15 19:00:00 2011 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:01 #meetingname infrastructure 19:00:01 #topic Robot Roll Call 19:00:01 #chair smooge skvidal codeblock ricky nirik abadger1999 lmacken 19:00:01 The meeting name has been set to 'infrastructure' 19:00:01 Current chairs: abadger1999 codeblock lmacken nirik ricky skvidal smooge 19:00:22 here 19:00:32 * abadger1999 here 19:00:33 mostly watching a console trying to boot 19:00:43 please ping when you need my attention 19:00:49 * athmane is here 19:01:19 ok got it to pause. really here 19:01:53 * lmacken 19:02:28 ok, I guess lets go ahead and dive in... 19:02:36 #topic New folks introductions and apprentice tasks/feedback 19:02:55 any new folks want to introduce themselves? 19:02:57 * ke4zvu3 is here too but hasn't sent the introductory email yet to join and such 19:03:04 or any apprentice tickets or tasks we want to discuss? 19:03:11 welcome ke4zvu3. :) 19:03:25 * CodeBlock is here, sorry. 19:04:17 ok, I guess lets go ahead and drive on. 19:04:28 #topic Password/Ssh-key/Cert reset flag day discussion. 19:04:47 So, there was some discussion of this on list and some more in the most recent board meeting. 19:04:59 Anyone have any further input on it? 19:05:39 I would like to have docs updated and perhaps a nice wiki page to point people to before we announce anything. 19:06:38 and we do still need to determine timing. 19:07:05 If we're changing the password reqs it would need a little FAS coding too. 19:07:15 yeah, that too. 19:07:18 how much? 19:07:53 non-invasive (modify one method) but how much depends on how complex an algorithm. 19:08:03 If it's "20 chars" it's easy :-) 19:08:06 For timing, I am thinking perhaps a month after f16 might make sense... or 2 weeks. That way people who are busy with the release can push it out until it's done and have time to do changes then. 19:08:26 .ticket 2804 19:08:28 nirik: #2804 (Decide on FAS password requirements.) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2804 19:08:31 nirik, that sounds good. 19:08:38 we had a more complex set in that ticket we talked about. 19:09:41 which we could of course revisit. 19:09:50 ah, but that was before the xkcd ;-) 19:09:57 still digesting 19:10:00 true. ;) 19:10:01 heh 19:10:53 I think perhaps the next step here is to gather all these things and post a plan... 19:10:54 I would add one line to cover that. 19:11:11 * skvidal is here 19:11:11 if its over 20 characters only lower case and spaces is needed :) 19:11:14 oh, there is also another issue if we want to make sure people don't reupload their old certs. ;) 19:11:25 welcome skvidal. 19:11:25 nirik: what's that? 19:11:53 well, we need to code a check in fas to save the last key and verify the new one isn't it. 19:12:16 nirik: OR 19:12:25 we could just do it as a nightly cron job 19:12:32 grab a copy of the pubkeys now 19:12:44 and compare them with ones each night 19:12:55 if they are same as before 'nuke the key and send an email' 19:12:59 well, there's also the case of 'upload crap key, then reupload old key', but not sure people would go to that length. ;) 19:13:20 well that's why we grab their keys now 19:13:23 but yes 19:13:24 you're right 19:13:47 also, if it's in fas it might be nice moving forward.. 19:14:24 true 19:14:25 nirik, oh I am sure one or 2 would :). 19:14:33 so, let me do this (or anyone else): collect things we need to put in place and a suggested timeline and go from there? 19:15:14 tht sounds good 19:15:18 ok 19:15:25 fas password changes, fas key reuse checking, docs to point people at about good security, way to notify everyone (mass email?), and deadline/what happens if you fail. 19:16:04 we could also restrict the ssh key requirement to only some groups? or do we not want to do that? 19:17:11 ie, anyone who could actually use them in fedora? but then that would leave someone who uploaded one, then gets sponsored and has an old key. 19:17:13 as long as null is an okay state, I'd be more in favor of all. 19:17:30 yep, for the reason you just stated. 19:18:21 ok. will whip up a plan... 19:18:28 #action nirik will whip up a plan/schedule. 19:18:37 anything else on this? 19:18:44 nope 19:18:57 * pingou late 19:19:27 I'm sure we will see pushback on the ssh key thing... so I think it's impotant we have good docs and announcement that explains why we want to do this. ;) 19:19:37 hey pingou 19:19:45 #topic Bastion outages/openvpn discussion. 19:19:59 So, bastion03 has been hitting what looks like a nasty virtio bug. ;( 19:20:15 I've changed it to use e1000 for it's network, so hopefully it will be stable again. 19:20:49 if it croaks again, we should switch back to bastion02 for now. 19:21:09 due to this issue, it's gotten me thinking about how we could better do our vpn setup... 19:21:26 but none of the options look too great to me. 19:21:46 yeah 19:21:47 The best currently is to resetup heatbeat after the freeze... so at least we have failover. 19:22:44 so, if anyone has brilliant ideas for improving the setup, please do share them with the list/etc. 19:23:30 #info bastion03 hopefully stable now. 19:23:42 #info will look at setting heartbeat back up after the freeze. 19:23:55 any other comments on this?/ 19:24:17 looking at rhel5 for this if rhel6 is not stable 19:24:30 ie bastion02 19:24:44 yeah, we still have bastion02(rhel5) around. 19:24:55 but I'd really like to get us migrated to 6. ;) 19:25:29 #topic Upcoming Tasks/Items 19:25:29 well I mean el5 on kvm 19:25:42 smooge: yeah, I suppose we could... as a last resort. ;) 19:25:52 sorry my brain is feeling like someone hit it with a brick twice 19:25:54 ok, so we are in freeze currently. 19:26:10 So, this is a good time to work on docs and such... 19:26:36 askbot is moving along toward production. 19:26:47 paste is doing so as well, but not yet in stg. 19:27:01 any other upcoming items people are working on they want to talk about? 19:28:12 can i ask a question about paste? 19:28:34 Oh, another after the freeze thing: I want to move some vpn hosts around... move hosts that don't need much vpn access to a subnet that is more iptables locked. 19:28:38 ke4zvu3: sure. 19:28:39 is the intention to take over the fpaste.org domain from Unity or would the production FQDN be paste.fedoraproject.org ? 19:29:01 we don't own fpaste.org 19:29:06 ke4zvu3: I think the plan was to take over the domain, but it's still unknown if the domain owner wants to move it over. 19:29:10 and the owner has not been very communicative I believe 19:29:15 if not, then paste.fedoraproject.org. ;) 19:29:17 understood, thanks. 19:30:20 Oh, we also do have all the beta tickets. I filed them yesterday. 19:30:34 .ticket 2945 19:30:35 nirik: #2945 (Fedora 16 Beta - New website) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2945 19:30:37 .ticket 2946 19:30:38 nirik: #2946 (Fedora 16 Beta - verify mirror space) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2946 19:30:41 .ticket 2947 19:30:43 nirik: #2947 (Fedora 16 Beta - release day ticket) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2947 19:30:47 .ticket 2948 19:30:48 nirik: #2948 (Fedora 16 Beta - verify release permissions with rel-eng) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2948 19:30:49 .ticket 2949 19:30:52 nirik: #2949 (Fedora 16 Beta - Mirrormanager redirects for beta) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2949 19:31:27 nirik, ok I will take my usuals :) 19:31:29 thanks 19:31:32 smooge: cool. ;) 19:32:11 #topic Open Floor 19:32:17 Any items for open floor? 19:32:32 ppc is a lovely architecture and I have no idea why it never took off 19:32:38 smooge: haha 19:32:41 ^^ 19:32:41 ha 19:32:43 smooge: LIAR LIAR 19:32:55 skvidal: "be nice" :) 19:33:01 smooge: but it's ultra secure... not booting and all. ;) 19:33:16 pingou: :) 19:33:18 :) 19:33:24 yes.. and all you need to do to make a box not boot is take out its working drive and PUT BACK the drive 19:33:57 I haven't had this much fun since the great days of playing with HPUX-5 19:34:14 joy. 19:34:28 ok, I guess lets wrap up and go back to infrastructuring. 19:34:32 thanks for coming everyone! 19:34:39 #endmeeting