19:00:01 <nirik> #startmeeting Infrastructure (2013-09-05)
19:00:01 <zodbot> Meeting started Thu Sep  5 19:00:01 2013 UTC.  The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:01 <nirik> #meetingname infrastructure
19:00:01 <nirik> #topic Greetings and felicitations
19:00:01 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk
19:00:01 <zodbot> The meeting name has been set to 'infrastructure'
19:00:01 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean
19:00:12 * relrod here
19:00:12 <oddshocks> Hello!
19:00:12 <smooge> hello
19:00:15 <smooge> world
19:00:16 <nirik> morning everyone.
19:00:25 * ausmarton is here
19:00:34 * threebean is here
19:01:12 <frankieonuonga> good evening here from Nairobi Kenya
19:01:17 * ianweller is here
19:02:01 <nirik> ok, lets go ahead and dive on in. ;)
19:02:07 <nirik> #topic New folks introductions and Apprentice tasks.
19:02:20 <nirik> any new folks like to infroduce themselves or apprentices with questions or comments?
19:02:52 <ausmarton> Hi, this is Ausmarton Fernandes here.
19:02:57 <oddshocks> ausmarton: welcome!
19:03:07 <nirik> welcome back ausmarton. :)
19:03:28 <frankieonuonga> yeah. I realized I have two accounts on the system....frankieonuonga and onuonga...is it possible to drop my onuonga for frankieonuonga
19:03:43 <adimania> nirik. shall we discuss the tasks after the meeting?
19:03:47 <ausmarton> I'm a developer working in India, but I like sysadmin stuff, and that's what I'm looking at doing here.
19:03:50 <nirik> frankieonuonga: yeah, you can just set the one you don't need anymore to 'inactive' and use the other. ;)
19:04:03 <threebean> ausmarton: cool, welcome!  :)
19:04:16 <nirik> adimania: sure... unless its something to discuss with everyone...
19:04:23 <adimania> not really
19:04:27 <nirik> ok. ;)
19:04:43 <frankieonuonga> nirik: might need us to reconfigure for ssh stuff also cause of work on system ....thanks.
19:05:00 <nirik> frankieonuonga: ok
19:05:08 <ausmarton> I was a part of this group earlier but had to leave since I couldn't find time to devote here. Now I've joined back since I feel I'm able to.
19:05:18 <nirik> frankieonuonga: just let me know if you need a different account in apprentice group or something.
19:05:29 <nirik> we can get it sorted out
19:05:45 <frankieonuonga> nirik: great
19:05:55 <nirik> ok, moving along then...
19:05:59 <nirik> #topic Applications status / discussion
19:06:11 <nirik> any applications news/plans/discussions this week?
19:06:28 <ianweller> datagrepper 0.2 is going to be released today
19:06:30 <nirik> #info pingou sent out a thing to the list on 2 factor auth. Feedback welcome there.
19:06:38 <nirik> ianweller: cool. What all is in it?
19:06:42 <ianweller> probably going to put it in staging tomorrow
19:06:53 <nirik> #info datagrepper 0.2 upstream release today. Staging soon.
19:07:06 <ianweller> biggest thing is the job queue system, so instead of having to request 100 messages at a time, you can request all the messages for a query
19:07:16 <nirik> cool.
19:07:17 <ianweller> and wait until the job gets done (listen to the fedmsg bus for that message)
19:07:24 <ianweller> and download a compressed version off the server
19:07:35 <ianweller> apart from that, bugfixes and other junk
19:07:41 <nirik> nice.
19:07:58 <nirik> planning on going to production after the freeze then...
19:07:58 <nirik> ?
19:08:09 * SmootherFrOgZ here
19:08:31 <ianweller> probably yeah.
19:08:39 <ianweller> i don't intend to break freeze for this
19:08:50 <nirik> #info mailman staging work is moving along. Hopefully something to test with soon.
19:09:10 <smooge> ianweller, when does datased come out?
19:09:18 <threebean> #info fedmsg-0.7.0 is out today on pypi..  It'll make its way into staging for the next few weeks.
19:09:38 <nirik> threebean: nice. general bugfixes?
19:09:57 <threebean> yeah, and all the new debian features (gpg crypto, replay from the original endpoint if configured)
19:10:12 <threebean> the new fedmsg-trigger command which we can test out for mirror triggering later on
19:10:30 <threebean> dns SRV endpoint discovery
19:10:41 <frankieonuonga> threebean: coool!!!!!
19:10:52 <smooge> cool
19:11:03 <relrod> mw-FedoraBadges is live for those who care/want to show off badges on their wiki userpage
19:11:18 <nirik> another easy target for the trigger would be the updates sync that runs on releng04... it's currently a every 30min cron... it could be a fedmsg triggered from bodhi thing
19:11:46 <relrod> (upstream is https://github.com/CodeBlock/mw-FedoraBadges)
19:11:49 * threebean nods
19:11:51 <nirik> #info mw-FedoraBadges live in production. You can now show your badges on your wiki user page.
19:11:55 <threebean> nirik: and genacls
19:12:14 <frankieonuonga> relrod: I saw this but have a suggestion...can we have a mouse over effect that will tell the user what badge this is.at the moment a user has to click on a badge to get info on it.
19:12:16 <nirik> threebean: yeah. another good one.
19:12:52 <relrod> frankieonuonga: Possibly ;) if nothing else, we should be able to add a title attribute with it, if we don't already
19:13:04 <threebean> or an "alt" :)
19:13:12 <frankieonuonga> relrod: great
19:13:31 <relrod> threebean: yeah, should have the same effect I think
19:13:32 <nirik> threebean: so on those we change them to trigger and perhaps have a fallback to once a day or something that alerts so we could see if there's dropped messages? Or just see if we actually need to care?
19:13:35 <threebean> frankieonuonga: can you file an issue for that?  https://github.com/codeblock/mw-FedoraBadges
19:13:58 <threebean> nirik: yeah.. I still got to team up with tflink to collect that data.
19:14:13 <frankieonuonga> threebean: sure...i am on it
19:14:39 * nirik nods. Just something to think about moving forward with acting on fedmsgs... if we never drop them no biggie, if we do we likely need to fix why or have a fallback.
19:15:20 * threebean nods
19:15:21 <nirik> ok, any more upcoming or recent application news to discuss?
19:15:25 <threebean> a question ->
19:15:36 <threebean> anybody have any ideas what to do with this?  http://threebean.org/fedora-releng-dash/
19:15:38 <nirik> fire away
19:15:41 <SmootherFrOgZ> I've an alpha release of fas-client ready for some trial
19:15:53 <threebean> there was a suggestion on my blog comments to roll it into status.fp.o..
19:16:04 <nirik> threebean: good question. what does it need to run?
19:16:16 <threebean> nirik: nothing.. just html and js
19:16:24 <threebean> it queries datagrepper
19:16:25 <ianweller> nirik: looks static, it hits datagrepper's API
19:16:26 <nirik> and it hits datagrepper for the info?
19:16:34 <nirik> jinx. ;)
19:16:36 <threebean> :D
19:17:05 <ianweller> if we include that, we should probably make sure datagrepper gets added to the status page too :P
19:17:06 <nirik> yeah, not sure where it best would fit.
19:17:19 <threebean> so -- having it with status is kind of nice because they're both simple static apps.
19:17:23 <nirik> it seems a bit more than status was meant for
19:17:27 <threebean> but.. its not really the same kind of info as status.fp.o.
19:17:30 <nirik> yeah
19:17:57 <frankieonuonga> brb
19:18:02 <threebean> we could just put it on the proxies in the same kind of place as the apps.fedoraproject.org landing page.. and give it a url like apps.fedoraproject.org/releng-dash
19:18:08 <nirik> I don't think adding it to status would be good... but not sure where it would be best then
19:18:18 <nirik> yeah.
19:18:29 <nirik> I guess that would work
19:18:33 <ianweller> or make it a more specific dashboard, and put in information for the last events on other webapps as well?
19:18:37 <ianweller> er, less specific
19:19:01 <ianweller> if there's been no git commits in 12 hours, we know something might be up
19:19:03 <threebean> ianweller: that sounds kind of like "fedora-news"
19:19:08 <ianweller> mm, true
19:19:18 <threebean> http://ambre.pingoured.fr/fedora-news/
19:19:46 <nirik> it almost might make sense in blockerbugs... well, the branched part, but not really the rawhide part.
19:20:15 <tflink> we are adding the ability to track part of the spin requests after alpha
19:20:32 * nirik is ok with the apps.fp.o/releng-dash/ I guess we could always move it later.
19:20:33 <tflink> ie, what builds beyond stable on X date were part of TC/RC
19:22:08 <nirik> anyhow, we could also just discuss it more and come up with a better idea after more pondering. ;)
19:22:16 <threebean> yeah.. and wait until after freeze any which way.
19:22:23 <nirik> yep
19:22:39 <threebean> cool, thanks :)
19:23:14 <nirik> #info more thoughts wanted on http://threebean.org/fedora-releng-dash/ and where to deploy or modify info
19:23:22 <nirik> anything else application wise?
19:23:41 <tflink> is it worth mentioning beaker?
19:23:47 <nirik> sure. ;)
19:24:00 * threebean wants to know what's up
19:24:12 <nirik> it's up and running now? and what are you planning on using it for exactly? ;)
19:24:13 <tflink> we have a trial installation of beaker set up: http://beaker.fedoraproject.org/bkr/
19:24:27 <tflink> http://beaker-project.org/
19:25:04 <tflink> there are two things we're interested in - getting some RHEL tests running on fedora and potentially using it for non-RHEL fedora integration tests
19:25:21 <nirik> so would this replace taskbot? or no?
19:25:31 <tflink> it would be a part of taskbot
19:25:49 <tflink> beaker is designed to have someone manually scheduling jobs and inspecting results
19:25:53 <nirik> ok, taskbot would run a job and ask beaker for a instance to run it on, etc?
19:26:25 <tflink> taskbot would schedule a job and beaker would take care of provisioning a machine, running the test and storing logs
19:26:55 <nirik> so, one thing I don't know if it's important but I wonder if we shouldn't have called this 'beaker-dev' or something in dns... beaker.fp.o might give people the idea that thats a production instance? or is that just my paranoia? ;)
19:27:15 <nirik> makes sense.
19:27:31 <tflink> I'm not planning to have a stg or dev instance of beaker anytime soon unless soneone else volunteers to do it:)
19:27:53 <frankieonuonga> nirik: you are probably right..not paranoia
19:27:54 <SmootherFrOgZ> +1 for -dev
19:27:58 <tflink> my original hangup on even setting it up was the maintenance burdon and theoretically, the beaker devs will be helping maintain it
19:28:20 <frankieonuonga> tflink: will sort it out...discuss after meeting
19:28:21 * tflink doesn't really think it makes a difference, but won't fight it
19:28:26 <nirik> sure, but if we start depending on it for release tasks we will likely want stg/prod so we can roll out new stuff cleanly, etc.
19:28:36 <nirik> it's not a big deal.
19:28:49 <frankieonuonga> think i would like to work on it
19:28:51 * tflink is starting to regret deploying it and bringing the topic up :)
19:29:20 <frankieonuonga> might not be for us but guidelines are so strict all over the project...of we let it slide may cause confusion
19:29:26 <abadger1999> tflink: genie's out of the bottle now :-)
19:29:39 <nirik> I don't want more work for anyone, but that also includes us down the road. ;)
19:29:43 <frankieonuonga> :-)
19:29:50 * pingou late sorry
19:29:50 <nirik> anyhow, lets see how much use it is, etc...
19:30:06 <tflink> yeah, at the moment it's as much of an experiment as anything
19:30:20 * tflink isn't sure that keeping the system around will be worth it
19:30:22 <nirik> right, it could end up being not useful, or too much work, or whatever.
19:30:29 <nirik> we don't know yet
19:31:29 <frankieonuonga> at work we might end up using it and we do things similar to the way fedora does....so maybe not...i am sure i can push it back up
19:31:41 <frankieonuonga> should not be a problem with my boss at all
19:31:58 <frankieonuonga> I can also document how we are using for context purposes
19:32:03 <nirik> anyhow, anything more on this for now? or shall we move on?
19:32:15 <pingou> on applucation there is nuancier-lite
19:32:15 <nirik> frankieonuonga: see tflink out of band if he could use any help with it.
19:32:20 <pingou> http://209.132.184.207/nuancier/
19:32:26 <nirik> pingou: does it live yet? oh, nice.
19:32:47 <pingou> ryan is working on the voting UI a little
19:32:57 <threebean> pingou: really nice work :)
19:32:58 <pingou> but first feedbacks from the design people is good :)
19:33:21 <threebean> is there a way to have multiple fas groups be admins?  so that, say, designteam members and sysadmin-noc members can login to see the stats ui?
19:33:31 <pingou> threebean: not atm but duable
19:33:36 <threebean> cool, cool.
19:33:49 <nirik> #info work on nuancier-lite ongoing http://209.132.184.207/nuancier/
19:34:03 <nirik> #topic Sysadmin status / discussion
19:34:11 <nirik> ok, on sysadmin side lets see...
19:34:29 <nirik> #info still playing with grizzley or havana cloud install on fed-cloud01
19:34:52 <nirik> #info yum repo config fixed on all the arm builders.
19:35:12 <nirik> #info fixed syslog on builders
19:35:36 <nirik> upcoming there's lots of little things.
19:35:44 <nirik> we have some new machines smooge is looking to bring on line.
19:35:53 <smooge> slowly
19:35:54 <nirik> our new blade server is still in limbo. ;(
19:36:24 <smooge> 15/16/17 almost gone from main mirrors.
19:36:49 <nirik> #info simple monitoring of builders now in place.
19:37:09 <nirik> I'm going to try and file off some tickets later today on things anyone intersted can work on. ;)
19:37:23 <nirik> - porting our last two func scripts to ansible
19:37:48 <nirik> - a simple zodbot plugin or alias to announce meetings to only a subset of channels who care.
19:38:30 <nirik> and some others. ;)
19:38:39 <nirik> any other sysadmin type news?
19:39:15 <nirik> #topic Upcoming Tasks/Items
19:39:16 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/
19:39:21 <threebean> (half joking - we should have a FAD just to file easyfix tickets)
19:39:27 <nirik> any upcoming items folks would like to schedule or note.
19:39:42 <pingou> threebean: more likely we would solve them then ;)
19:39:44 <nirik> threebean: ha. Or set aside some time in a meeting to do them or something.
19:40:00 <abadger1999> nirik: hmm... msuchy seemed to have a rough schedule for copr -- we probably should discus that later though.
19:40:12 <nirik> abadger1999: yeah, saw that...
19:40:25 <nirik> I was going to reply to the email thanking him for the discussion and ask that he keep us in the loop
19:42:06 <abadger1999> <nod>
19:42:36 <abadger1999> A concern of mine is that when skvidal was working on it, we were in the loop just by benefit of seth knowing about almost all of infra.
19:43:06 <abadger1999> with msuchy -- we need better communication because we don't know what will be needed and there might not be anyone to provide those things.
19:43:15 <nirik> yep.
19:43:35 <nirik> perhaps we could see if he's interested in working on it in infra github? then we could review/see things as they happen?
19:43:51 <frankieonuonga> I think we should try and assist him as much as possible.
19:43:57 <smooge> nirik, I have ppc nightmare going on
19:43:57 <pingou> commmits already go to the copr-devel list
19:44:00 <smooge> that is about it
19:44:26 <abadger1999> <nod> that will be good.  Probably also needs to either have an infra sponsor now or he needs to join infrastructure (the latter is probably better).
19:44:27 <nirik> pingou: ok, good to know.
19:44:40 <nirik> smooge: sorry. ;(
19:44:48 <nirik> smooge: waiting on new dvd's now right?
19:44:54 <smooge> dvd's are there
19:44:59 <smooge> the dvd that I need isn't
19:45:20 <smooge> dgilmore used it back in 2012 and it disappearred since then
19:45:33 <nirik> random thought: check the other ppc cd drive?
19:46:08 <nirik> #topic Open floor
19:46:21 <threebean> (sbueno is spamming the wiki to get badges...)
19:46:22 <nirik> anyone have items for open floor? general questions? comments? observations?
19:46:43 <smooge> nirik, yeah.. I am having them check it again
19:47:02 <frankieonuonga> yeah just to mention I have filed the issue as threebean had adviced
19:47:14 <nirik> threebean: idea: "cheater" badge you can get when you do things like that (non productive changes for the badge) that gives a -2 to your badge count. ;)
19:47:20 <threebean> frankieonuonga: thanks!  :)
19:47:46 <ianweller> i think we need a Frequently Requested Badges wiki page
19:47:48 <frankieonuonga> threebean: no problem at al
19:47:48 <ianweller> :P
19:47:58 <nirik> ianweller: indeed. ;)
19:48:03 <nirik> anyhow, if nothing else will close out in a minute.
19:49:01 <dgilmore> smooge: pretty sure i left the DVD in the machine
19:49:01 <nirik> thanks for coming everyone. Do continue in #fedora-admin, #fedora-noc, #fedora-apps.
19:49:08 <nirik> #endmeeting