19:00:03 #startmeeting Infrastructure (2013-05-16) 19:00:03 Meeting started Thu May 16 19:00:03 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:03 #meetingname infrastructure 19:00:03 #topic welcome y'all 19:00:03 #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean 19:00:03 The meeting name has been set to 'infrastructure' 19:00:03 Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean 19:00:08 * skvidal is here 19:00:12 * cyberworm54 is here 19:00:20 * abadger1999 here 19:00:56 * nirik waits for folks to wander in 19:01:05 hola 19:01:18 * puiterwijk 19:01:21 * pingou 19:01:25 * threebean 19:02:00 * bitlord (idling, listening, want to join :-) 19:02:51 ok, lets go ahead and start in. 19:02:58 #topic New folks introductions and Apprentice tasks. 19:03:08 any new folks like to say hi, or apprentices with questions or comments? 19:03:35 >.> 19:04:06 I want to say hi. (I'm new to fedora, want to contribute, interested in infrastructure stuff, sysadmin stuff, scripting ,....) (but n00b) 19:04:32 welcome bitlord. ;) 19:04:39 thanks :-) 19:04:55 do ask questions and hang out in our normal channels and I'm sure something will come along for you to work on. 19:04:58 welcome bitlord 19:05:39 Guess I'll say hi. Deciding if I want to invest in the project. I work on Linux infrastructure, systems and networking for a living. Impressed with the Fedora community, mostly coming from Arch Linux (for non-professional interests). 19:05:52 welcome Apsu` 19:06:14 Danke 19:06:21 wilkomen Apsu` 19:06:27 bitlord / Apsu`: you might look at http://fedoraproject.org/wiki/Infrastructure_Apprentice and if thats something you might be interested in, see me after the meeting in #fedora-admin. 19:06:42 Will take a look. 19:06:47 cool. 19:06:54 #topic Applications status / discussion 19:07:03 any applications news from this week or upcoming? 19:07:05 lots of stuff :) 19:07:09 * nirik notes we are still in freeze 19:07:37 threebean: you start :) 19:07:45 #info calendar is adding new calendars all the time, looking good so far. 19:07:47 I sent in two freeze break requests for tagger. Both have been carried out now and things look stable. I hope to not touch it anymore for a while. ;) 19:08:10 datagrepper is in prod 19:08:15 #info some freeze break fixes for tagged went in today. 19:08:19 #undo 19:08:19 Removing item from minutes: 19:08:23 #info some freeze break fixes for tagger went in today. 19:08:36 I bothered *a lot* threebean for datagrepper (and a little for datanommer) 19:08:44 I pushed out a new bodhi release on monday 19:08:55 #info datagrepper is in production and use cases are starting to appear. 19:08:59 with some ideas in mind: 1) the fedora-owner-change script I sent about yesterday 19:09:04 #info new bodhi on monday just before the freeze. 19:09:15 and 2) a little surprise I've been working on as of few weeks ago: 19:09:17 http://ambre.pingoured.fr/fedora-news/ 19:09:20 :) 19:09:28 pingou++ 19:09:34 pingou: quick calendar question: is there a way to get _all_ calendars ical in one link? 19:09:40 nirik: yes 19:10:10 nirik: https://admin.fedoraproject.org/calendar/ical/ 19:10:16 (just don't specify a calendar) 19:10:19 pingou: great. thanks. 19:10:33 cool. that fedora-news is interesting. Just a collection from fedmsg? 19:10:39 nirik: you asked me for that one ;) 19:10:54 nirik: for updates, packages and builds yes 19:11:02 for planet and fedocal (not there yet) no 19:11:10 pingou: it's mobile-friendly, correct? 19:11:24 it works fine on my firefox-os and should work fine as well on Android 19:11:28 threebean: completely 19:11:51 It's pretty much designed to be a (html5) mobile app 19:11:59 okay that fedora-news thing is slick 19:12:03 oh nice. 19:12:06 * swa_work late but here 19:12:16 w/ local caching so that you can catch up with the planet posts on the subway/train/tunnel 19:12:19 when we get the meta information in datagrepper it'll be even better. links to the events will make it off the hook. 19:12:37 threebean: +100 :) 19:12:47 * nirik isn't getting the data, it's just refreshing. Probibly a midori/webkit issue. 19:12:52 * skvidal opens it up on his phone 19:13:18 I want to bother Ruth to ask her if/where we have a central place for general annoucement 19:13:32 pingou: how does that app work? 19:13:39 like stuff about flock should arrive there 19:13:43 skvidal: html and js 19:13:55 pingou: no - I mean - how is it populated? 19:14:04 is that the job you were asking about running somewhee? 19:14:07 err somewhere? 19:14:13 http://ambre.pingoured.fr/fedora-news/js/fedora_apps.js this is pretty much the whole app 19:14:37 oh - so it's all happening client-side? 19:14:41 skvidal: nope, that job is to send email on the devel list about package ownership change 19:14:45 skvidal: yes 19:14:51 pingou: oh that is very attractive 19:14:53 nirik: still loading? 19:14:55 pingou: well done 19:15:06 nirik: it's working here in chrome -lemme check ff 19:15:07 pingou: yeah, something isn't happy on the midori side. We can debug out of meeting. 19:15:11 works in firefox ok 19:15:15 skvidal: how does it look on your phone? 19:15:31 nirik: ok, sure :) 19:15:38 pingou: looks good 19:15:42 it asks me to 'install' on firefox 19:15:44 which is amusing 19:15:45 very nice. will poke around at it more. ;) Thanks pingou 19:16:02 skvidal: it's an app, you can install it 19:16:16 pingou: put it on github. I want to send PRs ;p 19:16:26 threebean: will do :) 19:16:40 infra or pypingou? 19:16:46 * threebean suggests infra 19:17:29 works fine in ff on my phone too. 19:17:40 yah, nice 19:17:49 infra it is then 19:18:31 I could see this also being nice for things like flock schedule/info or whatever too. 19:19:09 ok, any further apps news? 19:19:11 Having a flock app for the schedule would be nice for sure 19:19:18 shouldn't be too hard to do either 19:19:40 yeah, much nicer to look on your phone than pull out a laptop, or try and read a wiki page in the mobile browser. 19:20:10 threebean: https://github.com/fedora-infra/fedora-news 19:20:22 with hyperkitty we could also do lists back and forth, which would be very nice. 19:20:45 I have to ask spot if I can use the Fedora logo as icon when installing the app 19:20:54 (which I already do but... :) 19:21:02 pingou: https://plus.google.com/117445388364195221637/posts/BDitX5aJ5r9 19:21:12 skvidal: <3 19:21:17 that's how it looks on my phone :) 19:21:27 took me a minute to remember how to take a screen shot on the n4 :) 19:21:39 skvidal: that's how is supposed to look :) (and does completely on my peak because of a bug ^^) 19:21:40 pingou: awesome 19:22:03 spot: you around? 19:22:09 yes 19:22:13 spot: if so - you should take a look at this thing pingou did 19:22:17 it's kinda pretty 19:22:19 so know I can say I didn't get that phone for nothing ^^ 19:22:50 is this an app for the store, or a web app? 19:22:55 pingou: is there any way to make it fill the space with the little boxes width-wise? 19:23:00 spot: and I have to you if I can use the logo :) 19:23:37 spot: html5 we can distribute them outside any store 19:23:59 and I don't really know if they can be included in the android store 19:24:03 so we could publish this in infra for people to just run/install right? 19:24:10 apps.fp.o/news 19:24:11 nirik: yes 19:24:14 (well, when it's all ready, etc) 19:24:15 * spot would feel a tiny bit better about using the logo if it lived on our server 19:24:24 but sure, you can use it either way 19:24:36 spot: I can bother Ryan or Mó for a logo otherwise :) 19:24:42 nirik: afaict there's not much for them to 'run' 19:24:48 true. 19:24:56 nirik: if by run you mean 19:24:59 'download a web page' 19:25:05 :) 19:25:15 skvidal: to answer your question yes but I need to find a way to increase these logos, atm it's not looking that nice :/ 19:25:30 pingou: I just opened it on the n7 - that's why I asked 19:25:43 skvidal: n7 == tablet? 19:25:49 skvidal: well, yeah, or download an 'app' which I guess means "shortcut to your browser running this page" right? 19:26:35 nirik: yes 'app' 19:26:37 so, lets explore how we want to do this and what we want to add, etc out of meeting? 19:26:39 pingou: nexus 7 - yes 19:26:52 but pretty slick. Kudos pingou 19:27:18 thanks :] and thank threebean and ianweller for datagrepper :) 19:27:45 pingou: https://plus.google.com/117445388364195221637/posts/jEGruPjRWoz 19:28:02 skvidal: does look less nice :) 19:28:23 #topic Sysadmin status / discussion 19:28:24 :) 19:28:46 so, on sysadmin side... we have a kernel update pending, we did emerg reboots of some of our critical systems. 19:28:57 we should probibly just do all of stg soon too. 19:29:01 and the rest after the freeze 19:29:15 nirik: a couple of other updates trickled in between the last update and the kernel emergency 19:29:30 like a new nagios/nagios-common from epel 19:29:39 which fills me with dread about upgrading during a freeze 19:29:43 #info kernel security update out, rebooted some ciritical machines, will do the rest after freeze. 19:29:50 yeah, agreed. 19:29:53 so I'm likely to ONLY update the kernels rather than a global update 19:30:04 I'm fine to hold off until after freeze for anything else. 19:30:07 ok 19:30:16 Is our policy for cloud boxes and critical updates still "owner of instance is responsible"? 19:30:18 but we could do *stg* 19:30:37 nod 19:30:39 abadger1999: yeah, currently. we could force terminate everything and redeploy it I guess. 19:30:50 nirik: except for a handful of boxes 19:30:57 nirik: we could force everyone apply this update :) 19:31:08 b/c we have access to all the rest afaik 19:31:51 yeah, since this is local only, I am not too worried. we do want to do it sometime... 19:32:03 cool 19:32:28 #info new storage is coming on line soon, working on getting that working. 19:32:54 #info ansible web quickstart next week for anyone interested in ansible 19:32:58 * nirik digs up link. 19:33:15 http://www.ansibleworks.com/quickstart/ 19:33:40 it's on the 22nd iirc 19:33:55 yeah. 19:34:10 Any other sysadmin type items? 19:34:12 Interesting. You guys are using (or going to use) Ansible? 19:34:20 Apsu`: we are moving to it yeah. 19:34:20 we are using it now 19:34:25 and we are moving toward it more 19:34:34 Fun. Decided against chef/puppet? 19:34:34 Apsu`: our repos are public 19:34:48 http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/ 19:34:53 Cool 19:34:55 skvidal / smooge: did you get that kernel box all ansibled yesterday? happy to help further on that... 19:35:22 nirik: I setup a stub group playbook for smooge to work with 19:35:32 nirik: but the short answer is 'mostly' 19:35:37 I think we should/could look next at adding in the virthost-comm0*.qa boxes... they should be pretty simple. 19:35:44 I think it needs fas-client added to it 19:36:00 I had a fas_client task already setup... but yeah. 19:36:10 nirik: I also had to clean up some of the el6-ish assumptions in our base tasklist :) 19:36:17 yeah, good. 19:36:59 #topic Private Cloud status update / discussion 19:37:00 made some notes on where it needs to break out 19:37:02 anything on clouds? 19:37:12 skvidal: cool. I am sure we will need to adjust things as we go some. 19:37:20 not much has changed - the internal discussion over networking is still 'meh' 19:37:29 cool 19:37:32 * nirik has not had time to do much on clouds this last week. 19:37:38 nirik: essentially it is this 19:37:40 I still do plan to setup grizzley on the other ones. 19:37:57 I need help with the next steps 19:38:01 nova on folsom and instances tlaking to each others public ips 19:38:02 are bleah 19:38:09 not likely to improve much 19:38:10 Btw, I this is specifically what I do for a living. 19:38:20 Rackspace private cloud team, working on openstack. :) 19:38:35 ah ha. ;) 19:38:36 Worth discussing the issues you're referring to here? 19:38:41 Apsu`: lovely - then maybe you can explain why using public ips - nodes can't talk to each other? 19:38:46 sure, happy to. :) 19:38:55 Apsu`: I'll be happy to discuss in copious and painful detail :) 19:39:07 Probably! 19:39:08 yeah, perhaps in #fedora-noc after the meeting? 19:39:12 Sure. 19:39:24 thanks. 19:39:30 #topic Upcoming Tasks/Items 19:39:54 https://apps.fedoraproject.org/calendar/list/infrastructure/ 19:39:56 :) 19:40:00 I need to add some more stuff there. 19:40:20 this is shorter than I remembered :) 19:40:21 the bugzilla upgrade has moved to the 19th 19:40:35 yeah 19:40:49 here's the info dump: 19:40:51 #info 2013-05-14 to 2013-05-28 BETA infrastructure freeze 19:40:52 #info 2013-05-19 - bugzilla upgrade. 19:40:52 #info 2013-05-28 F19 beta release 19:40:52 #info 2013-05-31 end of 1st quarter 19:40:52 #info 2013-06-01 nag fi-apprentices 19:40:53 #info 2013-06-08 drop inactive apprentices 19:40:54 #info 2013-06-18 to 2013-07-02 FINAL infrastructure freeze. 19:40:56 #info 2013-07-01 nag fi-apprentices 19:40:58 #info 2013-07-02 F19 FINAL release 19:41:00 I'll add those all into the calendar moving forward. 19:41:06 anything anyone wants to note or schedule? 19:41:49 #topic Flock 19:42:01 any further thoughts on flock? I submitted 2 things... 19:42:05 I know other folks have as well. 19:42:45 MOAR THINGS. SUBMIT ALL THE THINGS! 19:42:50 sorry. 19:42:59 http://flock-lmacken.rhcloud.com/proposals 19:43:05 :) 19:43:17 wow. we hit 50. nice. 19:43:18 spot: there will be a selection in the submition right? 19:43:37 pingou: I think the plan is for all the talks to be given all at once and whomever is loudest wins 19:43:38 pingou: yes, there will be a selection committee to review all proposals 19:43:52 skvidal: awesome :) 19:44:03 spot: cool, so I can add more ideas as they come :) 19:44:03 spot: any news on the hotel? 19:44:23 skvidal: not yet, Ruth is traveling right now, and she's handling that 19:44:36 (flights prices haven't changed since last time :() 19:45:13 spot: thx. 19:45:17 #info everyone do submit talks / hackfests / sprints / workshops 19:46:10 skvidal: at least you don't have to do a ansible talk, since there's already one. ;) 19:46:24 that's mdehaan 19:46:29 yep. 19:46:42 #topic Open Floor 19:46:53 any items for open floor? comments? suggestions? 19:47:04 we have to check what we do with jenkins 19:47:13 pingou: ? 19:47:18 skvidal: login is broken 19:47:33 what happened? 19:47:35 oh yeah, we have a fix ready... 19:47:42 puiterwijk have a solution but it consists on unpacking a jar, replacing some of the libraries and repacking it 19:47:44 just need to work with puiterwijk to get it in ansible 19:47:53 oh 19:47:56 yeah, that. 19:47:57 Ugh. Jenkins woes. 19:47:58 puiterwijk: just yell at me 19:48:06 I can make all those things show up 19:48:09 Can has travis? Or... anything else really? :P 19:48:27 Apsu`: it does the job 19:48:46 When it decides to not fail horribly, sure. 19:48:47 pingou: no, not unpacking 19:48:56 just putting them in place 19:49:10 skvidal: sure, will contact you after the meeting on that 19:49:17 puiterwijk: okay 19:49:28 though I though nirik said he'd handle it last time, but let's do that togethetr 19:49:59 * nirik thought he was going to help you get it into ansible, but didn't have time right then. ;) 19:50:05 anyhow, we can get it done. 19:50:30 ah no, I remember. you wanted to ask pingou on it 19:50:38 could be yeah... ;) 19:50:49 let's talk about this after the meeting :) 19:50:52 ok, if nothing else will close out in a minute... 19:51:40 one thing 19:51:46 sure, shoot. 19:51:49 relrod asked about adding fedmsg messages to fpaste. 19:52:01 should we do it? 19:52:29 hum. 19:52:42 so, by default pastes are marked 'private' so you have to know the url... 19:52:56 the reason we did that was to prevent people from just scraping them all for sensitive info... 19:52:59 * abadger1999 thinks no for private pastes 19:53:06 * threebean agrees with abadger1999 19:53:22 no we shouldn't do private pastes? or no we shouldn't do fedmsg? 19:53:40 no we shouldn't fedmsg enable private pastes. 19:53:51 Not sure about public pastes 19:53:52 yeah. 19:54:08 well, public ones already have a rss feed, so fedmsg should be fine. but not sure how much use it would be. 19:54:15 right 19:54:30 yeah. perhaps statistics. maybe relrod has another usecase in mind. 19:54:32 threebean: do you have a nidea of how you'd summarize the paste? 19:54:43 no clue yet 19:55:02 b/c "Oh look, another /usr/bin/python -tt paste" is probably not that helpful :-) 19:55:05 relrod: volunteered to write the patch and all too.. but we decided to bring it to the rest of the team before proceeding. 19:55:18 yeah, I would say not to bother unless we have a better use case. 19:55:48 I'll link to these meeting notes in the ticket we have for it so we can refer back to it later. thanks! 19:55:53 but we can discuss more and see? sure. 19:55:54 thanks. 19:56:17 thanks for coming everyone! 19:56:21 #endmeeting