19:00:00 #startmeeting Infrastructure (2013-04-25) 19:00:00 Meeting started Thu Apr 25 19:00:00 2013 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 welcome y'all 19:00:01 #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean 19:00:01 The meeting name has been set to 'infrastructure' 19:00:01 Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean 19:00:08 * relrod here 19:00:18 * lmacken 19:00:19 * ausmarton is here 19:00:29 * pingou here 19:00:30 is here - rl9x4 ;) 19:00:33 * threebean is here 19:00:47 * abadger1999 here 19:00:49 * tflink is here 19:01:25 cool. lets go ahead and start in... 19:01:31 #topic New folks introductions and Apprentice tasks. 19:01:37 * cyberworm54 is here 19:01:39 any new folks? or apprentices with questions or comments? 19:02:08 ...... 19:02:19 do note everyone should feel free to chime in with questions or comments as we go. ;) 19:02:39 #topic Applications status / discussion 19:02:46 so, new application news? 19:02:57 #info fedocal and blockerbugs apps are heading to production 19:03:13 #info pkgdb release to prod today already. ;) 19:03:22 #info new fedoratagger in production 19:03:33 something to test and provide feedback on: http://209.132.184.188/ 19:03:44 (lazy Sunday work) 19:04:04 cool. nice looking there pingou! 19:04:31 nirik: I will not hide where the inspiration from the theme comes from ;) 19:04:39 s/from/for/ 19:05:02 * skvidal is here 19:05:03 threebean: if you have time, a email with the tagger changes to devel list or something would be good. Like abadger1999 did for the pkgdb one? 19:05:05 sorry I am late 19:05:11 * nirik wonders if we shouldn't send those to devel-announce 19:05:18 welcome skvidal 19:05:33 nirik: will do.. I'm just waiting on a little feedback from hughsie first. 19:05:43 cool. 19:05:50 datagrepper should be on its way to staging soon, we're just waiting on a package review. 19:05:54 threebean: not sure we'll have it before tomorrow, it's 21:00 for him 19:05:55 #info ask02 created and in service now. 19:06:31 https://bugzilla.redhat.com/show_bug.cgi?id=955781 19:06:39 I need to take ask01 out soon and reinstall it. Might wait for tomorrow on that tho 19:07:37 pingou / tflink: so the openid support in fedocal/blockerbugs is waiting on a flask openid? or just time to recode the login stuff? 19:08:03 nirik: mostly flask openid, a little bit of coding/ui changes for fedocal 19:08:15 nirik: mostly coding changes and testing for blockerbugs 19:08:45 I was waiting for things to stabilize after all the changes for infra before swapping out FAS 19:08:46 ok, just trying to see where things were... 19:09:00 python-flask-openid-1.0.1-1.el6 is in epel-testing 19:09:29 Hi , I am Kushal Khandelwal an engineering undergraduate from India and I would like to be part of Infrastructure team. 19:09:40 welcome kushalkhandelwal 19:09:58 Thank you for the welcome nirik 19:10:21 How should I get started , any guidance would be helpful 19:10:34 kushalkhandelwal: were you more interested in sysadmin tasks? or application development? 19:11:00 Sysadmin tasks 19:11:11 and more interested in being a packager 19:11:36 ok, see me after the meeting in #fedora-admin and we can add you to our sysadmin apprentice group... 19:11:43 for packager, you want #fedora-devel 19:12:07 anyone have other application news? 19:12:19 Sure , would do that nirik 19:12:34 threebean: also had a nice and productive week-end 19:13:18 #topic Sysadmin status / discussion 19:13:25 ok, on the sysadmin side... lets see. 19:13:58 #info added hosted03/hosted04/collab03/collab04/fedocal01/fedocal02/blockerbugs01/blockerbugs02/ask02 in the last few days. 19:14:28 :) 19:14:34 :) 19:14:39 #info outage for hosted move tomorrow. 19:14:42 (re: python-flask-openid -- it's available for infra boxes. But you'll want to make sure you apply the hotfix from puppet too) 19:14:47 I'm going to move hosted02 -> hosted03 tomorrow. 19:15:08 early next week, I am going to have an outage to move collab02->collab03 19:16:00 we need to get monitoring added for all the new hosts. I might file some easyfix tickets for those. 19:16:37 any other things we want to note or discuss on the sysadmin side? 19:17:12 * skvidal tries to remember 19:17:16 bugzilla update? 19:17:23 oh yeah. 19:17:25 that's both sysadmin and app 19:17:30 #info bugzilla will be updated soon to 4.4 19:17:50 we have started to check things, but not everything is checked/done yet 19:18:06 lmacken: any idea if bodhi is ok with new python-bugzilla? 19:18:10 * nirik checks the rest of the list. 19:18:51 I think we are left with: 19:18:53 FAS bugzilla sync 19:18:53 PKGDB bugzilla sync 19:18:55 IIRC, I had to change my code for modifying and updating bugs with the new python-bugzilla 19:18:59 Bodhi 19:19:00 pkgdb-sync definitely broken 19:19:03 cnucnu 19:19:22 nirik: any movement on the backups - or is that waiting on netapp? 19:19:27 Seems taht bugzilla server is just too slow 19:19:44 abadger1999: might try the python-bugzilla list too... since you didn't get answers on irc. 19:19:52 19:20:12 skvidal: yeah. So, I need to write up a mail on our current backups and what we have, then we need to wait for new netapp space to do something better. 19:20:53 skvidal: I am thinking we can work something with rdiff-backup and then backup that to tape as desired. and also drop a bunch of things that aren't useful. 19:20:53 My plan for today was to explore just gettingit working with the json url then report to python-bugzilla list the hack and see if they have any ideas for improving it. 19:21:04 nirik: yah agreed 19:21:08 If it really is serverside slowness, I don't htink python-bugzilla will have any solutions 19:21:19 * Smoother1rOgZ is here 19:21:22 nirik: we've chatted about it before - but I think we can make our backups a lot simpler to deal with the common restore cases 19:21:25 abadger1999: :( yeah, is the json one available in prod? 19:21:35 skvidal: completely agreed. 19:21:41 nirik: hmm... actually, I kinda doubt it. I'll check. 19:21:51 skvidal: also, we can plan in opt in backups for cloud instances, etc. 19:22:04 nirik: indeed 19:22:25 #info will send email about backups and revamping them to the list soon. 19:23:23 ok, anything else sysadmin wise? 19:23:59 nirik: where do you want to go next on ansible migration? 19:24:04 since we're out of freeze 19:24:07 oh, on the bugzilla thing still... I couldn't find a hard date on when the update would happen, but it was mentioned before to be 26th/27th... 19:24:10 any particular simple wins you want? 19:24:45 yeah, so I was trying to migrate enough tasks over to be able to run against an arm SOC and set it up as a releng or qa machine. 19:24:52 The upgrade will take place on the evening of April 27th (EDT). 19:24:55 for bz 19:24:56 so, if we could finish that up to that point it would be excellent. 19:25:00 from the bz-announce-list 19:25:12 pingou: I saw mention of that a while back, but nothing recently confirming it... 19:25:24 nirik: the email is from Monday 19:25:29 ok, cool. 19:25:42 so, we don't have much time. ;) 19:25:54 yeah, that date was set a while ago but I thought it was pushed out until that email went out on monday 19:26:08 https://www.redhat.com/archives/bugzilla-announce-list/2013-April/msg00002.html 19:26:17 #info bugzilla upgrade scheduled for evening of the 27th 19:26:25 also of interest for the apps dev, lists a changes for the RPC calls 19:27:08 #topic Private Cloud status update / discussion 19:27:20 so, skvidal has been fighting a fight with the cloud this week. ;( 19:27:31 and am still doing it 19:27:47 pingou: thanks! 19:27:47 it's like I have a special job in life - to fight private clouds 19:27:49 yeah, such a rabbit hole. ;( 19:27:53 on the plus side 19:28:02 it is an acknowledged issue upstream 19:28:10 so we're not just 'special' in experiencing it 19:28:13 #info ready to install on fed-cloud01/03 for a test cloudlet 19:28:18 thats good at least 19:28:30 nirik: rdo on cloudlet? 19:28:42 nirik: seems like a good place to jump to, to me 19:28:43 so, is rdo just the repos? 19:28:45 or ? 19:28:51 nirik: ? 19:28:55 nirik: it's the pkgs 19:29:00 and the installer stuff 19:29:04 I mean, does it use puppet and have it's own installer? 19:29:12 sadly, yes 19:29:15 ok. ;( 19:29:27 aiui it is the packstack stuff 19:29:31 but yeah, a grizzley one to test both rdo and grizzley out would be good. 19:29:38 nod 19:29:48 and that would get us on a setup thats very 'standard' I would hope 19:30:11 #info will look at using RDO to install test cloudlet 19:30:29 skvidal: so, right now are those new nodes in the cloud? or out? 19:30:39 in 19:30:42 05 and 07 are in 19:30:49 and RIGHT now they are working fine 19:30:55 ok, cool. 19:30:56 the tricks are, of course, the dhcp lease timeouts 19:31:01 which I set down quite low this morning 19:31:05 means more dhcp noise 19:31:07 so any idea how much capacity we have available? still lots? 19:31:10 but we are LESS likely of hitting the issue 19:31:23 well - we added room for what? 48 cpus? 19:31:30 so. yah - lots 19:31:35 also, we still need to add more cinders I guess. 19:31:36 and network-wise we have plenty of room 19:31:40 skvidal: yeah, I noticed that on one of my nodes this morning :) 19:31:42 yes - cinder is the next bit 19:31:50 tflink: oh yah - no option, sadly 19:32:07 it explains why there were so many dhcp messages in syslog 19:32:13 yah 19:32:21 it has to do with dnsmasq-dhcp holding onto leases 19:32:32 despite having their config changed and being kill-HUP'd 19:32:40 #info will look at adding cinder volumes from each of the compute nodes to increase available volume space. 19:32:46 they are holding onto lease timeouts from terminated instances 19:33:08 nirik: on my list of things today is to try out the f19 alpha image as an instance in the cloudlet 19:33:18 yeah, that would be nice too for sure. 19:33:27 #info skvidal working on f19a image for cloud 19:33:40 nirik: I talked to mattdm about it 19:33:48 just use ks and make our own? 19:33:49 nothing dramatic left on it - so I'm going to dupe our f18 img 19:33:52 nirik: nod 19:33:57 well dupe our f18 ks 19:34:02 ok 19:34:19 I'm still chasing potential solutions to rhe external ip routing issue 19:34:21 with openstack 19:34:35 cool. Hopefully we can find a workaround. 19:34:36 anyway - off in the weeds 19:34:43 any other cloudy news? 19:34:56 nothing leaps to mind 19:35:10 #topic Upcoming Tasks/Items 19:35:34 19:35:34 #info 2013-04-26 - 19UTC hosted migration/switch hosted to openid 19:35:34 #info 2013-04-27 - bugzilla 4.4 upgrade? (tenative) 19:35:34 #info 2013-04-30 - 21UTC lists.fedoraproject.org migration. 19:35:34 #info 2013-05-01 nag fi-apprentices 19:35:34 #info 2013-05-08 drop inactive apprentices 19:35:34 #info 2013-05-14 to 2013-05-28 BETA infrastructure freeze 19:35:34 #info 2013-05-28 F19 beta release 19:35:40 any other items folks would like to schedule or note? 19:35:56 àny date for fedocal and tflink's app? 19:36:14 I was thinking later today or tomorrow. 19:36:21 the instances are all built 19:36:33 we just need to move the modules into production and setup proxy stuff 19:36:38 tomorrow will be fine for me, but early then (I have star-wars marathon planned in the evening) 19:36:45 nice. ;) 19:36:54 Note, I saw a howto this week on amking tg1 apps use openid to auth. So it would be possible to migrate unported apps to fas-openid if we decide to establish a drop-dead date sometime in the future. 19:37:16 abadger1999: cool. What apps are TG1 again? 19:37:29 nirik: I had the same question ;) 19:37:45 nirik: right now -- pkgdb, elections, bodhi, mirrormanager 19:37:47 fas 19:37:49 currently, FAS, pkgdb, elections, mirrormanager, bodhi 19:37:57 (but fas won't use fas_openid for obvious reasons :-) 19:38:04 why not? :) 19:38:07 * nirik kids 19:38:11 :-) 19:38:24 the most problematic in this list is MM 19:38:35 so yeah, that could be valuable if that works easier than porting them. 19:38:38 Everything except for mirrormanager has a planto migrate to a different framework in the coming year 19:38:44 yeah. 19:38:56 the ones going to flask have a provider written curtousey of puiterwijk 19:39:14 ok 19:39:17 the ones going to pyramid and tg2 may need to have a provider written for them. 19:39:27 so, also coming up, but I have no dates for yet: 19:39:33 packages is the last TG2 app, correct? 19:39:43 #info new bladecenter should arrive sometime in the next few weeks hopefully. 19:39:46 (If they need group info, they'll need more than a generic openid identity provider) 19:39:56 #info new netapp space should arrive sometime in the next few weeks or so 19:40:02 pingou: I think so. threebean, lmacken-- do you guys know that? 19:40:13 pingou: oh -- and maybe the undeployed badger app? tahrir? 19:40:21 *sigh* s/badger/badges/ 19:40:22 abadger1999: good point 19:41:09 * abadger1999 needs to write a badger app Then everyone else can have my same difficulty 19:41:27 so...stupid question.....what happens if I restart libvirtd and vms are running? >.> 19:41:39 actually wrong channel 19:41:49 I meant to post that on #rhel 19:41:52 :) 19:41:55 sorry 19:41:57 abadger1999: an app to badger people? interesting :) 19:42:11 #topic Open Floor 19:42:17 anyone have items for open floor? 19:42:20 tflink: Maybe it could tie into fedocal ;-) 19:42:35 so, one thing I've not done much on lately... 19:43:06 https://fedoraproject.org/wiki/Infrastructure_FedoraBugzilla <- do we want to bring that up on list(s) and start getting more input? 19:44:12 * nirik might try and poke at it more, we will need to gather requirements I think to move forward much 19:44:21 didn't someone bring up the idea of bugs associated with multiple components? 19:44:28 tflink: yeah. 19:44:50 there's lots of ways to rework things if starting from the ground up. 19:44:59 or things to try and accomodate anyhow. 19:45:24 assuming that it's worth all 19:45:31 the effort, anyways 19:45:43 yeah. 19:45:49 and it would be a lot of effort. 19:45:57 * pingou has the same feeling: is it worth it? 19:46:33 well, it's really: 19:46:45 nirik: did you ever run the scalability test you were talking about? 19:47:01 fedmsg and openid / not having those 19:47:11 tflink: the 15,000 component test? 19:47:14 yeah 19:47:28 yeah, I did. 19:47:41 it makes any pages with that on it take like 12-14 seconds to load 19:48:03 yikes 19:48:22 so, another thought was to do a tracker per component, but then there needs to be a way to move things between and find the tracker you want 19:48:23 tflink: so we looked at other ticket systems 19:48:35 tflink: notably debian doesn't have a list/pull down of pkgs :) 19:48:59 if we did one tracker per component we'd need to write some brand new code to move things between components 19:49:11 the long and short is - dumping 15000 items in a list works not well 19:49:45 I can look at making a better demo for roundup thats closer to what we want and see if I can get openid in it so anyone can test it. 19:50:15 nirik: so - unless we can crack the nut of the list of pkgs 19:50:18 it would be nice to have a single account system as well 19:50:28 I am not sure we're better off in roundup 19:50:49 tflink: yeah, the 2 things that even make us consider this: fedmsg and openid support. ;) 19:51:18 skvidal: yeah, although it sounds like bugzilla is going to not use the list anymore either soon, or at least they were talking about not. 19:51:32 nirik: they expecting users to input the pkg name? 19:51:33 nirik: good point, I wasn't thinking about openid and FAS as the same thing 19:51:36 I didn't see that discussion 19:52:04 tflink: well and if we were clever it might be somehting like $component.bugz.fedoraproject.org 19:52:31 so it's the pages that load all 15,000 components that take a long time to load? 19:52:42 it looks liek they are looking at a widget that searches name/description and shows some small number of matches. 19:52:52 tflink: in bz? or roundup? 19:52:56 either 19:53:06 yeah, both are slow with 15k components. 19:53:12 it's just a lot of data 19:53:31 nirik: gotcha 19:53:39 I wonder how hard it would be to do a google-style dynamic dropdown based on text entry 19:53:46 roundup is a lot faster for other pages... but that could be that it has less data, etc. 19:53:49 but that sounds kinda like what nirik is talking about 19:54:00 tflink: yeah, thats exactly what they were talking about doing for bz. 19:54:02 tflink: that's exactly what he';s saying 19:54:10 I'm not sure if it's done/landing, but they were talking about it. 19:54:18 * skvidal has another solution for this 19:54:21 fewer packages 19:54:23 :) 19:54:33 always an option :) 19:54:42 yeah, lets drop all the ones that start with 'p' and that would save us a lot. 19:54:50 would we have saner package:component mapping this way? 19:55:10 tflink: another NTH thing would be subcomponents. 19:55:12 I suppose it's not that bad, now that I think about it harder 19:55:27 kernel -> filesystems -> btrfs 19:55:35 just ran into some oddness when I was trying to map updates->bzcomponents 19:55:56 anyhow, I think we are still not sure if this is worth it, but further discussion would be good I think. 19:56:07 also, possibly more in person/higher BW discussion at flock or something. 19:56:09 nirik: I hear 'g' is a troublesome letter too 19:56:25 skvidal: followed by k? 19:56:30 yes 19:56:34 just leave 'x' 19:56:45 t* 19:57:02 anyhow, any other open floor items? or shall we call it a meeting? 19:57:08 l* 19:57:12 it is a meeting 19:57:32 congratulations smooge ! 19:57:54 thanks for coming everyone. :) Do continue over in #fedora-admin, #fedora-apps and #fedora-noc 19:57:58 #endmeeting