19:00:39 #startmeeting Infrastructure (2013-09-26) 19:00:39 Meeting started Thu Sep 26 19:00:39 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:39 #meetingname infrastructure 19:00:39 The meeting name has been set to 'infrastructure' 19:00:39 #topic welcome everyone 19:00:39 #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 19:00:39 Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 19:00:52 * relrod here 19:00:52 * tflink is lurking 19:00:53 * mirek waves 19:00:54 * pingou here 19:00:57 * threebean here 19:01:00 * anshprat here 19:01:02 * adimania is here 19:01:24 * robyduck is also here 19:01:38 i am here as always 19:01:40 * croberts croberts is here 19:01:40 * ausmarton is here 19:01:59 here too :) 19:02:08 i dont know how to do that i am here thing 19:02:20 /me\ 19:02:21 frankieonuonga: /me whatever 19:02:24 * pingou sorry 19:02:30 /me sorry # damn it! 19:02:41 * ynchen 19:02:42 :) 19:02:47 :) 19:02:48 * ynchen is here 19:02:51 * Xeladem waves 19:02:54 ok, lets go ahead and get started then... 19:03:05 * frankieonuonga is here 19:03:08 #topic New folks introductions and Apprentice tasks. 19:03:18 any new folks like to introduce themselves? 19:03:25 or apprentices with questions or comments? 19:03:38 hi i just joined this week, i looking to join the sysadmin-noc 19:03:51 Yes, me, I'm Robert Mayr from Italy, would like to help out also in the infra team :) 19:04:04 am working on speeding up askbot presently.. 19:04:13 robyduck: awesome, welcome :) 19:04:15 * croberts waves hi to robyduck 19:04:19 welcome everyone. ;) 19:04:29 Hi pingou, nice to meet you here :) 19:04:32 anshprat: thanks for that.. that will be nice :) 19:04:47 * threebean waves "hello" to robyduck 19:04:56 * pingou wonders how threebean does that 19:05:02 hey threebean :) 19:05:04 * frankieonuonga waves to the new crew 19:05:12 pingou ^^ 19:05:45 as always do chime in with any questions as we go... and #fedora-admin, #fedora-noc, and #fedora-apps are the place(s) to watch for things to do... 19:06:18 #topic Applications status / discussion 19:06:26 what do we have application wise this week or upcoming? 19:06:37 nuancier 19:06:58 we have a stagging version working: https://apps.stg.fedoraproject.org/nuancier 19:07:07 #info nuancier is rolling out soon! :) 19:07:18 and pkgdb2 w/ pkgdb1 data http://209.132.184.188/ 19:07:27 cool. 19:07:29 please test, break and let me know how it behaves :) 19:07:34 what are the next steps on pkgdb2? 19:07:40 https://fedoraproject.org/wiki/Infrastructure/RFR/Copr - any question to this? 19:08:03 for pkgdb2: polishing a little still, finish the API authentication question, pkgdb-cli update 19:08:09 more unit-tests 19:08:23 and that should be it 19:08:29 pingou: wow. cool. 19:08:51 mirek: yeah... I still have marked to reply to your message about resources... 19:08:54 but it takes ~3h to convert the db to the new model :( 19:08:54 just been swamped. ;) 19:09:08 so we'll need to schedule some down time when we do the migration 19:09:15 thats fine. 19:09:32 I'm also thinking to send a request for testing to the devel list 19:09:44 that I can get bug report and RFE as early as possible :) 19:09:45 pingou: +1 19:09:48 good idea 19:09:59 I'm not sure what is next in process of RFR, should you vote about it? or what? or can I ask for that DB...? 19:10:18 mirek: I have a number of questions. ;) 19:10:41 are the frontend/backend things we want to run in our normal infrastructure? or are they best still being in the cloud? 19:10:42 * oddshocks late 19:10:49 * pingou has still a point about nuancier, but will wait for after the copr section 19:10:57 * anshprat too 19:11:00 nirik: still in cloud. 19:11:22 nirik: but there is nothing cloud specific 19:11:36 https://fedorahosted.org/fedora-infrastructure/ticket/4023 and https://fedoraproject.org/wiki/Infrastructure/RFR/Copr 19:12:11 so, I wonder if this would be a good fit for something to be in the other RH cloud that we were offered resources in... since it needs more disk than we have around. 19:12:49 also, can you expand on whats in the currently used disk? 19:12:58 is it keeping everything ever built? or ? 19:12:58 nirik: I did not get response from rvokal about that, I'm asking him every other day thou 19:13:40 (how would the "new" cloud interact with the db?) 19:13:45 mirek: well, I can talk with Dan Yocum, who is who I was talking to about it... They don't have external ip's yet tho, which we would need. 19:13:48 our db, a dedicated node db? 19:13:55 nirik: right now it keeps all builds. I have to come with some policy which build will be deleted 19:14:29 if it's in the cloud, it would need it's own db also in the cloud most likely. 19:14:37 because our db host is not externally reachable. 19:14:57 nirik: well ask him :) you can make it only better :) 19:15:01 which I guess we could get around via vpn, but I'd rather not. 19:15:25 so we can also make it more easily accessible to mirek 19:15:31 mirek: will do. I can cc you on email. 19:16:17 I can prepare playbook for frontend (which use db) to be deployed as normal fedora service and backend can stay in cloud 19:16:29 nirik:can the cc be to copr-devel 19:16:37 we would need just 22 and 443 ports between those two machines 19:16:39 keeps everyone in the loo[ 19:16:43 loop i mean 19:16:57 well, this is an implementaion detail, but I can send whatever I find out there too. 19:17:07 * nirik will subscribe 19:17:48 I did a bodhi masher update yesterday which will hopefully fix the duplicate notice updateinfo.xml issue 19:18:03 mirek: that might work... the frontend would need credentials to talk to the cloud, but we could probibly setup that. 19:18:20 lmacken: cool. ;) pesky timestamps. 19:18:24 mirek: but then the frontend should be packaged :) 19:18:33 nirik: ok, I will still count with 3 options, ordinary fedora service, staying in fed.cloud, or that hosting, we will see what will look better next week 19:18:44 pingou: it is already 19:18:53 pingou: happily it just passed review. ;) 19:18:53 pingou: even with selinux :) 19:19:06 nirik: thanks for that btw 19:19:17 \ó/ 19:19:17 no problem. 19:19:21 champagne! 19:19:25 hooray! 19:19:47 mirek: where is the storage used for packages? off the frontend? 19:19:57 nirik: on backend 19:20:08 ok 19:20:08 mirek: I still owe you a couple of patch for the API/CLI 19:20:43 pingou: and I'm still waiting :) 19:20:54 I think we may want a pretty agressive pruning policy... but we can see I suppose. 19:21:44 yes, I will discuss it on copr-devel and copr deployment is delayed to next week, do you agree? 19:21:46 mirek: any other coprs questions we should look at for now? 19:21:57 yep. I need to subscribe there, but will do so. :) 19:22:05 abadger1999: did you have any other copr questions? 19:22:41 nope 19:22:56 cool. Any other upcoming application news? 19:23:03 about nuancier 19:23:20 so it generate thumbnails for the pictures 'candidates' to an election 19:23:30 atm these pictures are installed by hand on each node 19:23:49 while the cache is generated by the frontend and thus only on one node 19:23:59 dumb question: are these the same size/format the wiki uses? 19:24:10 pingou: I found a bug and an issue in nuancier.. ping you after the meeting.. 19:24:21 but we can easily generate the cache by hand on each nodes, so this might be the simplest solution for the moment for nuancier 19:24:23 anshprat: please :) 19:24:58 in the long term, when nuancier will handle upload of the candidates, then we should probably look into a shared storage 19:25:06 nirik was proposing glusterfs 19:25:19 (eof) 19:25:21 we could do gluster or just do a nfs netapp volume... 19:25:40 we already have one for the wiki, we could also just reuse part of that... 19:26:06 either way is fine for me, my question is more, do we want to have this already or should we wait for nuancier full feature? 19:26:13 but If you are ok with manual for now, we can just revisit it later. 19:26:37 when is the go-live date? 19:26:40 nirik: the pictures themselves are pretty big (not sure what the wiki uses, but likely the same), the thumbnails are 128x128px 19:26:43 for the upcoming election? 19:26:45 nirik: Monday 19:27:09 pingou: is there a way to download and try out the images ? 19:27:22 yeah, I'd say manual for now, revisit after this election. 19:27:24 (full res I mean) 19:27:43 anshprat: yes, right click on the 'google' icon when hovering over the image 19:27:48 nirik: wfm, thanks :) 19:28:18 #info bodhi fix for duplicate updates hopefully out 19:28:32 #info coprs going to discuss best deployment path and revisit next week 19:28:55 #info nuancier going to go with manual cache/thumbnailing for now, revisit after the upcoming voting. 19:29:03 mashing in koji discussions underway :) 19:29:10 cool :) 19:29:19 yeah. :) I added some thoughts to that thread. 19:29:25 would be great to move that into koji 19:29:49 from a bodhi perspective, it has to end up in /mnt/koji anyway, so bodhi could simply flip symlinks 19:30:14 * lmacken should chime in on the thread :) 19:30:17 yeah, it's a lot of data to shlep around too... and needs enough space to write it. 19:30:44 yeah, moving it from the builders to the hub, etc, would be a lot of work 19:30:47 lmacken: how would we handle signing? just like now? get a list, sign, push and hopefully everything in there is signed? 19:31:08 signing doesn't have to change at all, right? 19:31:18 yeah, it could be the same 19:31:57 #topic Sysadmin status / discussion 19:32:03 ok, on the sysadmin side... lets see. 19:32:14 #info new ansible on lockbox with some nice new features. 19:32:29 One of the new nice things in ansible 1.3.x is 'accelerate' mode. 19:32:44 its fireball but without the zeromq libs :) 19:32:47 I think we should just look at enabling that everywhere and using it. It makes things much much faster 19:32:53 +1 19:32:56 yep. It's more simple... no zmq 19:33:14 what was zmq used for already? 19:33:24 it does need python-keyczar on each node. 19:33:30 but thats got only a few deps. 19:33:33 2-6x faster than ssh apparently 19:33:55 ah, all we do is add 'accelerate: true' to our playbooks?? 19:34:07 gallery playbook: with accel: 32sec, without: 1minute 50 seconds. 19:34:13 wow 19:34:17 its fun :) 19:34:32 lmacken: and install python-keyczar on the hosts being playbooked 19:34:41 cool 19:35:06 * abompard coming in late 19:35:26 #info close to having the new cisco ucs blade server working 19:35:44 I have one of the blades asking for dhcp correctly now... but then it ignores the ip. ;( 19:36:03 I'm going to schedule 2 outages for next week: 19:36:47 1. on tuesday for buildsys stuff. Will move some guests around on bvirthosts, and also will move lookaside cache on pkgs01 to netapp storage, and also apply updates/reboots 19:37:23 2. on wed for class a/non buildsys stuff. moving some guests to a new virthost15 and updates/reboots. 19:37:36 I'll file outages for them and send announcements later today. 19:37:50 If there's anything else someone needs an outage for let me know. 19:38:39 We are trucking thru the backlog of stuff waiting for the freeze to be over... 19:38:51 if anyone sees tickets that were waiting on that that haven't been applied yet, please note them. ;) 19:39:13 anything else on the sysadmin side? 19:39:20 #topic Upcoming Tasks/Items 19:39:21 https://apps.fedoraproject.org/calendar/list/infrastructure/ 19:39:33 calendar should be up to date on our milestones now. ;) 19:39:38 * nirik figured out how to edit it 19:39:45 \ó/ 19:40:17 just to note: I am going to be out next friday, all the following week and then back the monday after that. 19:40:32 I'll possibly check emails and say hi, but won't be on vastly much. ;) 19:40:42 nirik: will someone else run the meeting? 19:40:56 nirik: enjoy 19:41:00 nirik: have fun :) 19:41:01 the break 19:41:07 yeah, need to line someone up. ;) Usually smooge does. 19:41:13 cool :) 19:41:55 our next freeze is after I get back... 19:42:01 #topic Open Floor 19:42:02 I should be around if he can't be 19:42:14 anything else anyone would like to discuss or note? 19:42:20 relrod: thanks. 19:42:47 I am going to send in a commit for the FAS newslink and get that ticket closed 19:42:59 and file the upstream bug that you suggested nirik 19:43:01 croberts: excellent. 19:43:03 i can help relrod 19:43:16 croberts: there's a few more wiki related tickets if you are looking for more. ;) 19:43:35 nirik: nice :) I will check out the trac and look at them 19:43:58 cool. 19:44:58 I'm in the process of trying to set up a dpsearch instance and get frankieonuonga access to it, but our temp instance playbooks are running into various issues with the ansible update 19:45:17 sorry been cleaning up. 19:45:47 relrod: I can assist some too... I cleaned up some various issues with other playbooks. 19:46:16 smooge: no worries. 19:46:22 smooge: anything to note for the meeting? 19:46:27 * frankieonuonga agreeing that relrod has been of great assistance 19:47:08 frankieonuonga: :) 19:48:19 ok, will close out in a min if nothing else... 19:49:18 Thanks for coming everyone. Do continue in our normal channels. :) 19:49:20 #endmeeting