19:00:04 <nirik> #startmeeting Infrastructure (2013-11-14)
19:00:04 <zodbot> Meeting started Thu Nov 14 19:00:04 2013 UTC.  The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:04 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:04 <nirik> #meetingname infrastructure
19:00:04 <zodbot> The meeting name has been set to 'infrastructure'
19:00:04 <nirik> #topic welcome everyone
19:00:04 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk
19:00:04 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean
19:00:33 * lmacken 
19:00:36 <nirik> who alll is around for a infra meeting?
19:00:39 * pingou 
19:00:41 * threebean is here
19:00:55 * ausmarton is here
19:01:15 * relrod is here but won't be for the entire meeting :(
19:01:17 * abompard is here
19:01:18 * mirek is here
19:01:28 * anshprat here
19:01:36 <pingou> relrod: we'll miss you :)
19:01:46 <frankieonuonga> where is relrod going ?
19:02:12 <relrod> pingou: Oh I'll be doing much more fun things like waiting for my mom while she has a doctor appointment ;)
19:02:32 <pingou> relrod: don't forget your phone/laptop/book ;-)
19:02:37 <relrod> yep :)
19:02:41 <pingou> relrod: and hope she does all right ;)
19:02:47 * wraeth is here and would like to introduce himself when appropriate
19:02:48 <frankieonuonga> wish you the best relrod
19:02:50 <nirik> ok, lets go ahead and dive in.
19:02:51 <pingou> (or alright, I never know which is which)
19:02:58 * frankieonuonga is here
19:02:59 <nirik> #topic New folks introductions and Apprentice tasks
19:03:13 <nirik> any new folks want to introduce themselves? or apprentices with question/comments?
19:03:20 <nirik> wraeth: ? :)
19:03:25 <wraeth> hello people :)
19:03:41 <wraeth> I'm Sam (wraeth) - sent the intro email a couple of days ago
19:04:03 <wraeth> i'll just be lurking around while I get a feel for things if that's okay
19:04:29 <nirik> excellent. welcome!
19:04:41 <anshprat> askbot stg looking good
19:04:51 <nirik> it's absoletely fine... ask questions as they come to you.
19:04:53 <anshprat> am just closing on the login part
19:05:04 <wraeth> will do :)
19:05:08 <nirik> anshprat: great work. ;) the multlingual is still not working tho right? ;(
19:05:08 <jimikirk> I also like to introduce myself as an apperentice, My name is James (jimikirk) and I've been looking forward to contribute as a sys admin to fedora project
19:05:18 <anshprat> nirik: nope, another crash
19:05:41 <nirik> welcome jimikirk.
19:05:42 * abadger1999 sorta here... but mostly in fpc meeting
19:06:06 <jimikirk> nirik: thanks, first time here, hope I can help
19:06:07 <nirik> wraeth / jimikirk: you are both interested in the sysadmin side of things? or also application devel/coding/
19:06:30 <anshprat> nirik: threebean: I am hitting the roads again for 10 days, so will update the bug, we should be good to release a package
19:06:43 <wraeth> i'm interested in coding, but only have experience in scripting - self taught VB long time ago, but want to learn C++
19:06:44 <threebean> anshprat: safe travels!
19:06:45 <anshprat> echevemaster will mostly pick it up from the bug
19:06:50 <anshprat> threebean: thanks :)
19:07:02 <jimikirk> nirik: I have experience in python, perl, ruby and shell/awk/sed as well as C and C++
19:07:17 <nirik> anshprat: sounds good. I hope we might be able to also get the theme setup for the update at the same time too.
19:07:25 <anshprat> jimikirk: wraeth: welcome aboard
19:07:55 <anshprat> nirik: alright..
19:07:56 <nirik> wraeth / jimikirk: cool. See me in #fedora-admin after the meeting and I can set you up in our apprentice group... and see #fedora-apps for our application development/coding folks.
19:08:08 <jimikirk> anshprat: thanks, looking forward to be part of the community
19:08:25 <wraeth> nirik, anshprat: thanks and will do
19:08:47 <nirik> cool. Any other apprentice questions or new folks? if not, moving along...
19:08:49 <jimikirk> nirik: will do
19:09:05 * docent is a bit late ;)
19:09:12 <nirik> Hey docent.
19:09:15 <docent> I'm newcomer - hello guys :)
19:09:31 <docent> I sent my introduce msg yesterday
19:09:40 <nirik> docent: welcome!
19:09:53 <docent> I got some exp in RHELs envs, also use Feodra as my main desktop OS :)
19:09:54 <nirik> docent: are you more intested in sysadmin stuff? or application devel/coding? or both?
19:10:26 <docent> Both. I'm RHCE working full time for the last 12 years ;) I can code safely in Bash / Python / Perl
19:11:27 <nirik> docent: cool. See me in #fedora-admin after the meeting and I can set you up in our apprentice group... and see #fedora-apps for our application development/coding folks.
19:11:39 <nirik> #topic Applications status / discussion
19:11:43 <threebean> fwiw, I already added docent to fi-apprentice this morning.
19:11:50 <nirik> threebean: excellent. thanks.
19:11:57 <mirek> Copr have credentials stored in private infra repo now.
19:11:58 <mirek> Copr got fedmsg certificate and emits messages to bus (thanks to ralph).
19:12:00 <mirek> Copr consumed 10 GB of storage so far, so current storage will last one year. Unless copr become more popular.
19:12:01 <mirek> Hopefully next week will land changes there, that will allow building of software collections there.
19:12:06 <docent> For now I'm looking into http://fedoraproject.org/easyfix/ so will be able to pick something for the beginning
19:12:12 <pingou> (for later: I have a remark regarding the wording on the introduction page)
19:12:29 <nirik> mirek: cool. ;)
19:12:35 <docent> threebean: not true - that was afternoon! ;)
19:12:42 <nirik> mirek: will be interesting to see how usage goes over time.
19:12:43 <threebean> docent: true, true!
19:13:06 <mirek> nirik: yes, I'm watching that closely
19:13:46 <nirik> #info coprs launch going well, 10GB of storage used so far. Next week SCL building hopefully.
19:13:46 <pingou> mirek: I wonder if we would be interested in a /stats page w/ the number of users, repo, copr
19:14:32 <threebean> #info new version of fedora-tagger landed in production today.  some enhancements requested by community members.
19:14:32 <mirek> pingou: I would be, but this is just "nice-to-have" and there is long list "we-need-this"
19:14:37 <threebean> https://apps.fedoraproject.org/tagger
19:14:44 <pingou> #info pkgdb2 is up for testing at http://209.132.184.188/ feedback/bug reports/rfe welcome at https://github.com/fedora-infra/packagedb2/
19:14:52 <pingou> mirek: ok
19:15:00 <nirik> threebean: is there a concise changelog/news ?
19:15:05 <mirek> but i plan to do some health status api call, so we can integrate it with status.fedoraproject.org
19:15:07 <nirik> pingou: have you had much feedback yet?
19:15:14 <pingou> #info fedocal 0.3.0 tagged an deployed today
19:15:22 <threebean> nirik: not readily availble.  I can blog that if you think it'd be useful.
19:15:23 <pingou> nirik: I got a couple of bug report and RFE yes
19:16:07 <pingou> one of the bug report had to do w/ the db, took me the whole day to re convert pkgdb1 to pkgdb2 correctly, update and the bug flew away :)
19:16:13 <nirik> threebean: well, if they aren't a big deal not worth it, but if it's worth letting a wider audience know...
19:16:43 <threebean> nirik: cool, I'll give it a look over.
19:16:58 <nirik> hurray on fedocal. ;)
19:17:22 * nirik wonders if we should capture all those updates/changes and push one email/blog post with changes this week... or just do them per app.
19:17:23 <pingou> there has been many many bugfixes that kparal found and reported!
19:17:26 * frankieonuonga has to go.
19:17:44 <nirik> no problem, thanks for coming frankieonuonga
19:17:47 * frankieonuonga will catch the meeting logs
19:17:49 <pingou> I'll probably announce fedocal 0.3.0 as I did last time, but tomorrow :]
19:17:53 <frankieonuonga> thanks nirik
19:18:28 <nirik> so, we have a pretty short unfrozen window...
19:18:37 <nirik> any other plans for things to roll out before next freeze?
19:18:45 <lmacken> I'm going to roll out a new bodhi today, at least to the mashers
19:18:52 <nirik> as always, I'd love to see hotfix numbers go down. ;)
19:19:00 <lmacken> I don't think we'll need to update bodhi on any of the app servers during this window
19:19:03 <nirik> lmacken: cool.
19:19:17 <tflink> we're planning to update blockerbugs production next week
19:19:47 <nirik> tflink: cool.
19:20:44 <nirik> lmacken: reminds me... I don't recall if I filed a bug on this or not...
19:20:57 <nirik> bodhi doesn't seem to always remove tags from builds when someone deletes an update.
19:21:35 <lmacken> nirik: hm, I'll have a look
19:21:57 <nirik> ok. I might have failed to file it, but it's hit me a number of times. ;(
19:22:03 <nirik> ok, any other applications news?
19:22:38 <abompard> nirik: maybe a quick HyperKitty update?
19:22:41 <abadger1999> mm... /me is reminded he needs to make a python-fedora hotfix for the app servers.
19:22:57 <nirik> abompard: please... ;)
19:23:03 <nirik> abadger1999: can we just do a release? ;)
19:23:08 <abompard> it'll be quick: I've been working on the front page redesign that mizmo has mocked up
19:23:13 <abadger1999> nirik: still blocked on two issues.
19:23:26 <abompard> and fixing a few selinux-related bugs on the staging server
19:23:40 <abadger1999> we could revert the present otp code.  that would unblock one thing.
19:23:59 <abadger1999> the other isn't a regression so we could roll out a release without fixing it.
19:24:01 <nirik> abompard: cool. What are next steps?
19:24:03 <abompard> it's not pushed yet because I depend on a pull request from her, but it'll be merged soon
19:24:17 <nirik> abompard: ok.
19:24:26 <abompard> when I can merge it I'll push my changes, update the staging server, and make sure it all works
19:25:12 <nirik> ok.
19:25:23 <threebean> abompard: can you give me a ping when you do?  I'd like to take another stab at fedmsg there after the next push.
19:25:25 <nirik> abadger1999: well, hopefully we get unblocked at some point. ;(
19:25:36 <abompard> oh by the way, that's more for threebean but if you send an email to a list on the staging server, the actual subscribers have been imported, so it will be distributed to them...
19:25:49 <threebean> abompard: hooray :P
19:26:08 <abompard> threebean: yeah :-) so better not run tests with devel@lists.fp.o
19:26:08 <abadger1999> nirik: yeah... seems like we need one more pair of hands to get anywhere.
19:26:28 <nirik> which reminds me that we are going to have to put on our thinking caps when we make a prod mailman3
19:26:44 <abompard> yup.
19:27:36 <abompard> nirik: I'd say make sure all emails sent from this machine go to /dev/null, then add it to the email alias for the regular list
19:27:48 <abompard> and see how it goes
19:28:00 <pingou> threebean: we need also to seat and have a look at fedocal, I'm not sure it's sending msg yet (or we didn't ask him to send msg in places I thought we did)
19:28:03 <nirik> well, the problem is... lists.fedoraproject.org already is mailman2
19:28:27 <nirik> so we need to make it something else or figure some clever way to only redirect part of it/part emails
19:28:44 <abompard> nirik: can't we send the received messages to both mailman2 and the new mailman3 on stg?
19:29:47 <nirik> when we are ready to roll this out for production use we need to make a production instance. we don't want to reuse our staging in production, thats bad form.
19:29:54 <abompard> Oh well, we'll discuss it then. It'll be fun!
19:30:02 <abompard> nirik: true
19:30:03 <nirik> yeah, I'm sure we can work something out.
19:30:28 <abompard> OK that's all for HK
19:30:34 <nirik> I was thinking the prod one would start empty, then as we move lists over to it we migrate them one by one (starting with just a few at first to work out bugs)
19:30:46 <abompard> nirik: yeah, I like that
19:30:57 <nirik> but we might have to call it 'newlists' or something.
19:31:18 <threebean> pingou: sure thing.. I've added the task.
19:31:25 <pingou> \ó/
19:31:32 <abadger1999> threebean and pingou were talking about schedule for fedmsg-notification and pkgdb2 this morning :-)
19:31:48 <pingou> we were?
19:31:48 <threebean> oh, that's right.
19:31:54 <threebean> fedmsg-notifications due in staging mid december.
19:32:01 <nirik> #info mailman3 work moving along. Hopefully ready for a prod instance before too long.
19:32:11 <pingou> threebean: what was the hashtag you used earlier again ? :)
19:32:22 <nirik> #info python-fedora release blocked by 2 issues. Help wanted to move it along.
19:32:45 <pingou> more seriously, the idea is to use fedmsg-notification to do  pkgdb2's notifications
19:32:58 <pingou> which spare me/us from having notifications w/in pkgdb2
19:33:14 * threebean nods
19:33:25 <threebean> and we're aiming for pkgdb2 to land shortly after the f20 final release in 2014.
19:33:46 <nirik> yeah, I am looking forward to fedmsg-notifications. I think it will be mucho cool.
19:33:47 <pingou> same time frame for fedmsg-notification in prod
19:34:04 <nirik> and might help us drop a bunch of other stuff from other apps too.
19:34:11 <threebean> over time, yes.
19:34:16 <nirik> yeah.
19:34:25 <threebean> badges never grew its own email code in anticipation ;p
19:35:02 <nirik> right.
19:35:07 <pingou> \ó/
19:35:08 <nirik> ok, anything else app wise?
19:35:17 <nirik> #topic Sysadmin status / discussion
19:35:24 <pingou> fedocal is moved to ansible :)
19:35:29 <threebean> awesome
19:35:32 <nirik> so, I'm planning an outage next week... 2013-11-20
19:35:34 <threebean> I didn't realize that was already done.
19:35:41 <nirik> #info fedocal moved to ansible today
19:36:35 <nirik> #info outage next week
19:36:47 <nirik> want to roll up updates and also resize db01's disk
19:37:47 <nirik> since we are out of freeze I have been trying to apply all the piled up stuff from freeze time.
19:37:55 <nirik> there's still a bit more, but getting there.
19:38:11 <nirik> If there is anything someone didn't do due to freeze, do look back and see if it can be rolled out now.
19:38:45 * abadger1999 needs to check if nirik's httpd log change fixed fasClient runs
19:38:55 <nirik> abadger1999: it did. ;)
19:38:59 <abadger1999> Yay!
19:40:06 <nirik> I also am likely going to check rdiff-backup's a final time and then disable bacula.
19:40:53 <nirik> #topic Upcoming Tasks/Items
19:40:54 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/
19:41:04 <nirik> anything upcoming anyone would like to schedule or note?
19:41:48 <threebean> nothing here, other than the new fedmsg-notifications and pkgdb2 due dates.
19:42:01 <nirik> cool.
19:42:06 <nirik> #topic Open Floor
19:42:21 <nirik> anyone have any items for open floor? anything to suggest/discuss?
19:43:07 <pingou> oh yes
19:43:15 <pingou> in the front page for newcomers
19:43:26 <pingou> we ask, what's they background basically
19:43:48 <pingou> but I wonder if it doesn't make people believe that since we know what they are capable of doing
19:43:53 <pingou> we will assign tasks
19:44:00 <nirik> perhaps.
19:44:19 <pingou> so I wonder if maybe we should phrase something on how we are working
19:44:20 <nirik> I think one of the biggest problems we have for new folks is that they do expect to be assigned things. ;)
19:44:32 <nirik> and we are much more 'self motivating'
19:44:36 <pingou> yes
19:44:44 <docent> Yes, we could think about that like this ;)
19:45:08 <pingou> docent: you made me realize this a little earlier
19:45:16 <nirik> we could move to a more mentor driven setup, but sadly, most of us are very busy for that...
19:45:20 <wraeth> nirik, pingou: it could sound like that, i guess, but i felt it was more a case of "what are you capable of now, and what do you want to do later"
19:45:56 <docent> Although I found somewhere note saying that If one wants to startin contributing he could check the easyfix and comment in issues he's interested in
19:45:57 <nirik> ideally shorter term we would have more easyfix tickets... it's hard to come up with good ones all the time tho
19:46:00 * anshprat agrees that folks expect assignments
19:46:01 <pingou> nirik: it would be easier to mentor if they know when they arrive what they want to work on :)
19:46:29 <nirik> pingou: sure, but often folks do not even know what all we have in place to work on. ;)
19:46:39 <pingou> that's true :)
19:46:50 <threebean> yup
19:47:30 <nirik> it's not an easy problem. ;(
19:47:42 <pingou> just food for thought, maybe tomorrow I'll see if I can change a little the wiki page and send the changes for review on the list
19:47:59 <wraeth> one possibility is task/infrastructre related introductions - an overview of what the infrastructure team encompasses what sorts of tasks are involved with them...?
19:48:09 * threebean nods
19:48:55 <pingou> good idea :)
19:49:00 <wraeth> there's a pretty comprehensive of the networking setup, but most of the rest is kind of left to interpretation, from what i could tell so far
19:49:10 <wraeth> *comprehensive introduction
19:49:25 <nirik> yeah, it's hard to think of everything tho. ;)
19:49:32 <wraeth> true :)
19:49:42 <anshprat> documentation is always a royal pain in the wrong place :)
19:50:00 <docent> Hmm honestly at the beginning I was little lost, but in the end I finished at http://fedoraproject.org/easyfix/ and knew that I could pick something from there, so I'm not sure it thsis is that big issue. I mean - there is really good explanation on Your wikis how to proceed, how to go on with things.
19:50:09 <nirik> one thought I had a while back was to try and do some monthly 'intro' class thing.... have apprentices attend and present on various things we do.
19:50:25 <docent> All I had to do was to read those: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
19:50:31 <anshprat> +1 to classroom
19:50:32 <nirik> yeah.
19:50:49 <pingou> nirik: we have a nice couple of movie of threebean :)
19:50:54 <pingou> movies*
19:50:57 <anshprat> and I volunteer for a session ;)
19:51:02 <nirik> yeah, true. we should link those in getting started.
19:51:13 <threebean> never got the last sysadmin-y one made.
19:51:26 <threebean> frankieo I think said he was going to work on it.
19:51:39 <nirik> ah yeah, thats right.
19:52:30 <nirik> ok, I guess we should close out unless there's some further action item on this we can do?
19:53:04 * mirek would welcome sessions too
19:54:14 <nirik> yeah, I'll look into that more perhaps then. ;)
19:54:22 <nirik> ok, thanks for coming everyone!
19:54:24 <nirik> #endmeeting