20:01:04 #startmeeting infrastructure 20:01:04 Meeting started Thu Mar 3 20:01:04 2011 UTC. The chair is CodeBlock. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:01:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:01:11 #chair smooge skvidal 20:01:11 Current chairs: CodeBlock skvidal smooge 20:01:15 shall we? 20:01:21 yay meeting start 20:01:22 #topic roll call 20:01:27 * averi is around 20:01:29 * skvidal is here 20:01:32 * CodeBlock blinks a few times :) 20:01:57 alrighty 20:02:04 #topic Transifex migration to tx.n 20:02:13 so...someone talk. :) 20:02:14 here 20:02:49 nirik: your topic :) 20:02:50 goozbach: what's on the agenda (or even the secret agenda) 20:02:50 ok we are further along. a notice has gone out to the lists from jsmith-busy and we will be working out a plan for the last itmes 20:02:52 * sijis is here 20:03:14 skvidal: the first topic is the topic now 20:03:18 Translation already started normally, we have 50 teams already on Tx. 20:03:20 oh I see 20:03:21 then infra meeting tickets 20:03:56 I was going to suggest that I go and close out the tx related tickets we have... 20:04:01 and point people to tx.net. 20:04:01 http://lists.fedoraproject.org/pipermail/infrastructure/2011-March/009974.html 20:04:05 is that ok for everyone? 20:04:11 nirik: +1 20:04:19 +1 20:04:59 Alright then 20:05:05 * marchant is here 20:05:10 * nirik will go do that later today. 20:05:10 Any other comments/questions/topics about Transifex? 20:05:34 how many were left? 20:06:12 * abadger1999 here 20:06:35 tickets? there's a number... 10-20? 20:06:46 mostly with old issues from our old tx.net instance. 20:07:23 Think he meant projects...but I have no clue how many 20:07:55 eh, he's busy in -noc :) 20:08:07 yeah, not sure on that... 20:08:08 #topic Ticket time 20:08:34 hm 20:08:55 .ticket 2591 20:08:56 CodeBlock: #2591 (Move blogs.fp.o to wordpress.com) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2591 20:09:13 So, since we're talking about migrations and such, where is this at? 20:09:14 yeah, i didn't get around to send you guys my finding on blogs and users 20:09:19 you'll get that in the next day or two 20:09:39 sorry about that. i know i said i was gonna send it last week 20:09:42 sijis: thx 20:09:56 sijis: alright, no worries 20:10:15 .ticket 2574 20:10:17 CodeBlock: #2574 (Perform regular inactive account prunings and possibly a password reset policy.) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2574 20:10:22 smooge: poke 20:10:32 sorry 20:11:02 What's status on our pruning? 20:11:06 I am updating the list after this meeting and will mail out this afternoon. Its just me going through and putting them into groups 20:11:27 Alright 20:11:31 so that we can say "oh wait notting needs that access even if he doesn't use it" 20:11:47 hm? 20:12:06 :) 20:12:19 smooge: alright 20:12:34 notting, sorry name pulled ut of blue 20:12:39 heh 20:12:43 any other comments on that? 20:13:02 whee, this is going to be a short meeting :) 20:13:09 .ticket 2563 20:13:10 CodeBlock: #2563 (upgrade MediaWiki to 1.16) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2563 20:13:14 ianweller: you around? 20:13:19 CodeBlock: I think everyone is being pulled in other directions 20:13:26 skvidal: yeah 20:13:28 which is fine 20:14:06 well then 20:14:09 let's do this: 20:14:11 #topic open floor 20:14:21 any comments for the good of the meeting and life as we know it? 20:14:33 heh... this "meeting" is like trying to have a meeting of "ADHD Anonymous" 20:14:44 Ok so the mediawiki is basically waiting on doing it on staging 20:14:45 how'd the ibliblio stuff go? 20:14:57 * skvidal can help on that one 20:14:57 I think all modules are in epel now 20:15:04 but need to double check 20:15:11 so the machine move to the new colo for ibiblio went smoothly 20:15:15 sijis, it went very well. The only issue was ipv6 20:15:20 bringing up the hosts and migrating the ipv4 networks went well 20:15:26 ipv6 was a pain 20:15:37 typical. ;) 20:16:00 however I learned a lot and feel like I know why its such a security nightmare 20:16:02 the only other hiccup we ran into was that Iforgot to do a git-grep to look for puppet being dumb 20:16:10 and re-networking some boxes after I changed them 20:16:19 to be fair - I wasn't the only one who forgot :) 20:16:30 but it got straightened out and the box is running fine afaict 20:16:35 no I forgot 20:16:50 it was on my checklist and I missed it 20:16:55 smooge: yes - everyone forgot. I personally blame one of the ricky's but I'm not sure which (/me is completely kidding) 20:16:56 I learned about git grep 20:17:12 I was doing find . -type f | xargs grep 2002: 20:17:17 noc02 had issues with puppet wasn't running on it for some reason (even --enable wouldn't kill the lock), and so nagios-external didn't know about the new IPs. Then there were some other config issues with nagios-external that showed up after I fixed that 20:17:22 So those are taken care of 20:18:01 sijis: does that answer your question? 20:18:05 oh and in case anyone is interested 20:18:14 ibiblio has some VERY nice new digs 20:18:19 in the ITS manning building at unc-ch 20:18:24 yup. was curious. i did see a bunch of stuff for ipv6 giving smooge problems ;) 20:18:29 skvidal: blame ricky one. :) He's not here, so we don't have to worry about him imposing death threats upon us, until he reads the log. :) 20:18:43 CodeBlock: it was definitely ONE of the ricky's 20:18:46 anyway 20:19:03 that's how ibiblio move went 20:19:32 what else is out there that people are concerned about? 20:19:43 #info ibiblio move went well, and one of the ricky's is automatically blamed for something, but we aren't sure which one. :) 20:19:44 (or just curious) 20:20:01 CodeBlock: good choice that should get ricky's attention ;) 20:20:11 :P 20:20:26 dgilmore, ping. looking for f15 installation repos 20:20:31 are there any other upcoming moves or the like? 20:20:40 or should be quiet for a bit? 20:20:58 kwright: there on every mirror 20:21:08 smooge: the new server? 20:21:15 smooge: the one you want to xfer backup02 to? 20:21:35 well its now on its way to PHX2 20:21:41 #agreed nirik will go and clean out tx tickets 20:21:43 does it have an ETA? 20:21:55 there is no power for it at RDU so we couldn't put it there 20:21:57 (don't mind me, trying to document earlier meeting for minutes) 20:22:04 ok server installation: 20:22:20 dgilmore, currently pointing at http://serverbeach1.fedoraproject.org/pub/alt/stage/15-Alpha.RC2/Fedora/i386/os/ 20:22:30 kwright: why 20:22:57 we have several EOL and soon to be EOL xen boxes. Mike had put in for a couple last fiscal year 20:23:01 dgilmore, this is the url that shows up in the installation gui. 20:23:10 dgilmore, what should I be using? 20:23:15 kwright, could you do this elsewhere please 20:23:24 kwright: well alpha is not available yet 20:23:25 smooge, sure 20:23:31 dgilmore, okay. thanks 20:23:33 #info sijis to send items from findings on blogs and users 20:24:03 also, FYI, app06 bodhi alerts have annoyed me, so I am going to dig more into why it's doing that and fix it, even if I have to strace things. ;) 20:24:09 how many servers do ya'll maintain? 20:24:17 I ordered the last one but sent it to the wrong place. It looked like a perfect fit as a replacement for backup02 (which is in ibiblio) but it turns out it could not stay in RDU 20:24:23 CodeBlock: yes? 20:24:27 * ianweller just got to his lab 20:24:31 so it went to PHX2and will be there next week. 20:24:31 but you can bother me 20:24:42 #info smooge to send update RE accounts to close 20:24:42 ianweller: Was poking you about the mediawiki update as we were going through meeting tickets 20:24:51 CodeBlock: standstill on my end 20:24:54 -ENOTIME, etc 20:25:33 PHX2 will have a second big KVM box then and we can continue the EL6 dance with fas01 moving onto better hardware 20:25:37 LyosNorezel: 136 being monitored by nagios, give or take some. 20:25:48 holly holy 20:26:16 CodeBlock: physical? or virtual/ 20:26:18 ? 20:26:26 more virt than physical 20:26:32 ah 20:26:35 skvidal, does that answer? 20:26:54 * nirik notes many virtuals... many less physical machines. 20:27:13 how many physical servers/ 20:27:13 ? 20:27:33 * CodeBlock shrugs 20:27:42 heh 20:27:57 smooge: yah 20:28:00 smooge: thanks 20:28:18 #topic Freeze/Release 20:28:31 We are going to be in Freeze til next week when Alpha should release 20:28:31 ya'll gonna tell me the infra team doesn't know how many physical servers they manage? 20:28:55 not in the middle of a meeting when I am dealing with other stuff 20:29:04 LyosNorezel: I can give you a specific number in a bit 20:29:25 skvidal: ok 20:29:47 we are on track for release other than the differences between our i2 downloaders and PHX2 ones 20:30:03 I am sending in a change request for that but not sure it will happen 20:30:40 after the release we will be rebuilding a set of boxes and taking of all main download services 20:31:52 I don't think we have had any issues with this release circle. Hopefully the beta will be better organized :) 20:32:04 #topic back to open floor 20:32:53 any news on nagios3/noc01 to rhel6? More testing in stg needed? 20:33:12 marchant sent out a test plan. 20:33:27 it looks good and should be followed. once its checked off we can move to it after the freeze is done. 20:33:37 nirik: I believe nagios is gold. I'm more worried about the other services on noc01 20:33:57 zodbot? 20:33:59 we can then start rewriting the "modules" into being more parent-child so that when ibiblio is down we get one page and not 400 20:34:07 cool. Where did the test plan go? 20:34:19 infra@ I think 20:34:26 * nirik looks, didn't see it. 20:35:34 google is pausing very long for me 20:36:04 I'd eventually like to talk about fedorahosted a bit, but..think I'll hold off, maybe until after-freeze 20:36:19 #topic FedoraHosted 20:36:24 your ball 20:36:29 the net is full of fail today. 20:36:30 smooge: eh 20:36:30 still don't see it, be might just be me. ;) 20:36:30 or conch shell 20:36:43 okay 20:36:44 oh wait I didnt read the last of your sentance. 20:36:50 so question about fedorahosted 20:37:07 new trac would be nice... which should be quite possible now. 20:37:09 do we get rid of projects which are requested to be removed? 20:37:10 smooge: I can do it now, it's just more I think most people have more important stuff on their plates atm 20:37:11 https://fedorahosted.org/fedora-infrastructure/ticket/2528 20:37:34 skvidal: basically what I was told was that it's fine to remove them, but generally keep a copy of them around in your homedir for a while, just to be safe 20:37:58 nirik: it'd be nice to have a more.... active failover config for the hosted* boxes 20:38:02 that's what... I believe mmcgrath told me. 20:38:12 nirik: or better yet an actual cluster for them 20:38:15 CodeBlock: sounds good 20:38:19 averi: ^^^^^^^ 20:38:20 There's quite a few things that would make hosted "better" I think 20:38:47 skvidal, great, so keeping a copy of their git repo should be fine for a while 20:38:56 averi: nod 20:39:02 For one -- like skvidal just said, I really *really* want to see about doing a cluster-esque thing for it, or something to distribute it out. I'm tired of every time I log into hosted it has a load of 5+ 20:39:04 perhaps we should have a policy to keep old projects for X days to make sure no one has a "oops, I need X from there" 20:39:08 and what about the trac istance for that project? 20:39:21 nirik: 14 days is a fine one imo 20:39:29 averi: you can just tar the whole thing up 20:39:32 and stowe it 20:39:35 but I would like to suggest something 20:39:40 instead of doing it in a homedir 20:39:46 does anyone know if the sourceforge keep it forever was for "legal" reasons or something else? 20:39:55 clustering would be great, but not sure how well trac handles that. Perhaps we could investigate ways to do it with trac. 20:40:08 smooge: don't know and I don't want to become sourceforge 20:40:18 we have a dir /srv/tmp on hosted1 20:40:26 how about we stuff our backup/holdover copies in there 20:40:36 * nirik nods. Sounds reasonable to me. 20:40:39 what I've done in the past is mv the files to there with a new name 20:40:40 nirik: yeah. Or even if we can't, let's move some of the other things off of that box. Maybe make a new host for hosted-lists01 and such. 20:40:55 CodeBlock: whats causing the load? 20:41:00 mv someproject /srv/tmp/someproject-hold-until-YYYY-MM-DD 20:41:10 nirik: git 20:41:13 nirik: and bz 20:41:15 and git 20:41:18 mostly git 20:41:19 from apache 20:41:35 ok, wonder if newer git will help that. ;) 20:41:40 it might 20:41:45 what skvidal said + it spikes way high when we generate the list of projects for the front page I think 20:41:46 * nirik has to take the cat and dog into the vet... back in a bit. 20:41:53 also the git-web that kernel.org would 20:41:59 Which...would it be worth looking into generating that list dynamically? 20:42:06 skvidal, fully agreed, a backup to be pushed on /srv/tmp should be fine 20:42:07 umm 20:42:08 well 20:42:13 not dynamically 20:42:14 I thin kgenerating it dynamically would be worse 20:42:16 okay 20:42:17 good 20:42:25 but.. hm 20:42:39 there's a new trac/rhel6 on one of the publictest boxes, perhaps we could test and gather more info? 20:42:41 some way that doesn't require it to spike like it does >.> 20:42:50 * nirik really goes for a bit mow. 20:43:03 smooge: To address your "are we like sourceforge" question -- it was not for legal reasons that I know. 20:43:13 skvidal: maybe a database of projects... maybe pull the list from FAS groups or something, I don't know 20:43:26 smooge: The original plan was to allow getting rid of inactive hosted projects (ie: without an owner) 20:43:44 CodeBlock: fine by me - easy to do in sqlite - sounds like a fun project for you :) 20:43:45 smooge: But the first time we attempted to reap, a large number of people complained. 20:44:54 abadger1999, it is my guess it is the case with every hosting place. 20:45:04 skvidal: Would you mind expanding on your cluster idea a bit? (I've lately been thinking of things/ideas for hosted.. I really would like to help improve it a bit) 20:45:12 have to find out why the dog is barking brb 20:45:21 CodeBlock: so - there are two ways I can think of doing it 20:45:29 both require a lot of testing 20:45:34 sure 20:45:46 so trac clustered, I'm sure is hairy b/c of the sqlitedbs 20:46:05 but what if we distributed the features out to multiple hosts writing to a common disk space 20:46:19 so that if we lost a host we just lost a feature, we didn't lose the whole thing 20:46:46 option 2 is to figure out how to cluster trac 20:47:07 and then have a shared disk pool that the cluster nodes can access and either LB or rrdns them 20:47:21 it's simplistic, I admit - but so is our current setup 20:47:44 as far as mailing lists go - if we change how we do archives 20:47:46 fwiw, I just logged into it (hosted01), and it has 8.92 9.27 9.97 .. that is what I'm talking about 20:47:57 we could easily replicate the archives but not the mailing lists themselves 20:48:41 CodeBlock, part of that can be fixed with a better gitweb and running git gc on projects every now and then 20:49:04 I suspect that some of our issues have known solutions - it is a matter of investigating and testing them 20:49:08 but that all takes time 20:49:11 I thought you guys ran gitweb caching? 20:50:58 yep.. time is what we are lacking on 20:50:59 we could also split projects by name or something... a-k and l-z or whatever. or some more even distribution. 20:51:28 nirik: sharding them out is fine by me too 20:51:34 smooge: As for git gc, when hosted is updated to git-1.7, that should happen more automatically, IIRC. 20:51:45 right now hosted2 is pretty much idle right? hot spare? 20:51:48 nirik: I still think a common disk backend that is replicated across N machines (or maybe to the netapp) might be worth the time 20:51:54 nirik: luke-warm spare 20:51:56 yeah, could be. 20:51:59 nirik: if hosted1 DIES DIES 20:52:01 we'll have all the data 20:52:09 but I'm not positive it will pretty moving it over 20:52:25 I suspect we could move the hosted1 puppet config over 20:52:27 and ugh 20:52:28 and MOST of it would come back 20:52:33 its at serverbeach 20:52:34 but the mailq would be a problem 20:52:39 smooge: both are 20:52:43 1 and 2 20:52:45 yep.. 20:53:42 skvidal: I do like the common disk space idea 20:53:55 CodeBlock: so - if we were going to start 20:54:08 I 'd like to see us extend our cloudfs testing 20:54:30 jdarcy: have you had any change in the patches to make auth happen 'server side' for that? 20:54:57 skvidal: Not so far. End User Summit kind of interrupted everything. 20:55:05 jdarcy: understood. 20:56:59 alright 20:58:00 skvidal: it's just something that's been on my mind. Hosted is used -- quite a lot (seen by hosting request tickets and by the constant load averages)... and I'd like to make it into something great 20:58:09 nod 20:59:42 ok my head is not getting any better and I think we are getting to the end here. 21:00:04 15 21:00:16 One questin just to throw out there 21:00:32 Is there anyone presently in infra who likes to do software release management? 21:00:33 ok 21:00:44 define pleasE? 21:01:25 ie: get a herd of cat^Wdevelopers to finish up features, test, pester devs to fix found bugs, then tar things up, build rpms, and such? 21:01:46 oh that.. I have done it multiple times 21:01:57 I wonder if its something I should be doing and havent 21:02:04 Rephrase.. does anyone like to and have spare time :-) 21:02:26 abadger1999: what project needs it :P 21:02:45 Reason: some of our services (fas, pkgdb, etc) are getting patches slowly... but we aren't making releases as frequently as the patches come in. 21:02:46 * CodeBlock wouldn't be good for it probably, but is curious 21:03:13 Mostly because someone needs to sanity check that the tree is in a releasable sttate and then get people to fix any obvious issues. 21:04:37 Anyhow -- if anyone wants to do that sort of thing, I'll help get you started on either fas or pkgdb. 21:04:46 do you guys have any clue about where trac stores project files? 21:05:12 Well I would like for us to have something like pkgdb for our services 21:05:19 averi: one sec 21:05:22 I was in multiple windows 21:05:24 abadger1999: but it sounds like this person would need python experience, right? 21:05:44 averi: /srv/web/trac 21:05:44 Thought I'd mention it as it's been one of those not-quite-easy-but-not-too-hard things that I've been thinking I could get someone else to manage much better than I have been. 21:05:49 skvidal, you rock, thanks 21:05:54 averi: /srv/web/trac/projects to be precise 21:05:54 sijis, a little.. I have been RL manager and had no coding experience 21:06:03 it was more about following a schedule and beating people 21:06:13 haha. gotcha. 21:06:15 sijis: Preferably. But mostly, packaging, testing, and good people skills. 21:06:18 we could clone rbergeron again 21:06:36 Oooh... /me was unaware that we had an rbergeron cloning facility. 21:06:42 I'll take five please. 21:06:51 :-) 21:06:53 although the way i understand abadger1999 talking about it, sounds like a 'programmer with managing skills' 21:07:27 yes or a manager with programming skills 21:07:29 they are rare 21:07:32 anyhow, i just wanted to understand the idea a little better 21:07:42 sijis: Well, I'm a programmer, so I understand how a programmer can work on it from that angle.. but the other way around would likely work well too. 21:08:11 anyhow. Just putting it out there as a way for someone to lend a hand where it's needed. 21:10:41 :) 21:10:54 15 21:11:06 5 21:11:15 #endmeeting