The infrastructure team will be having it's weekly meeting tomorrow, 2014-06-05 at 18:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices would like to ask general questions, they can do so in this part of the meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji, community, voting, tagger, packager, dpsearch, etc. If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week, or things that are upcoming.
#topic nagios/alerts recap
Here we go over the last weeks alerts and see if we can find ways to make it so they don't happen again.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
============================================ #fedora-meeting: Infrastructure (2014-06-05) ============================================
Meeting started by nirik at 18:08:59 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-06-05/infrastructure.20... .
Meeting summary --------------- * ready player one (nirik, 18:08:59)
* New folks introductions and Apprentice tasks (nirik, 18:10:19)
* Applications status / discussion (nirik, 18:14:24)
* Sysadmin status / discussion (nirik, 18:37:20) * LINK: http://infrastructure.fedoraproject.org/cgit/ansible.git (tflink, 18:41:52) * LINK: http://infrastructure.fedoraproject.org/infra/ansible/ (pingou, 18:42:00)
* nagios recap (nirik, 18:43:57)
* Upcoming Tasks/Items (nirik, 18:45:29) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 18:45:29)
* Open Floor (nirik, 18:56:19)
Meeting ended at 19:05:01 UTC.
Action Items ------------
Action Items, by person ----------------------- * **UNASSIGNED** * (none)
People Present (lines said) --------------------------- * nirik (88) * pingou (57) * threebean (14) * mapyth (12) * abadger1999 (11) * oddshocks (9) * puiterwijk (7) * bwood09 (6) * mpduty (6) * zodbot (5) * tflink (4) * mattdm (3) * hammad_ (2) * relrod (2) * tyll (1) * smooge (1) * webpigeon (1) * roshi (1) * lmacken (0) * mdomsch (0) * dgilmore (0) -- 18:08:59 <nirik> #startmeeting Infrastructure (2014-06-05) 18:08:59 <zodbot> Meeting started Thu Jun 5 18:08:59 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:08:59 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:08:59 <nirik> #meetingname infrastructure 18:08:59 <zodbot> The meeting name has been set to 'infrastructure' 18:08:59 <nirik> #topic ready player one 18:09:00 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 18:09:00 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 18:09:06 * bwood09 is here 18:09:10 <pingou> nice writing speed! 18:09:12 * pingou 18:09:17 <nirik> copy and paste for the win. ;) 18:09:24 <pingou> cheating ;-) 18:09:26 * puiterwijk lurking 18:09:39 <smooge> here 18:09:45 <abadger1999> Greetings 18:10:15 * oddshocks descends from a firehouse pole 18:10:19 <nirik> #topic New folks introductions and Apprentice tasks 18:10:30 <nirik> any new folks today who would like to introduce themselves? 18:10:37 <nirik> or apprentices with questions or comments? 18:10:48 * mpduty is here 18:11:11 <mpduty> ! 18:11:38 <pingou> mpduty: just speak :) 18:11:52 <mpduty> I am receiving a reminder from fedocal for APAC meeting two days after the meeting 18:11:53 <pingou> we don't use ! in this meeting :) 18:12:26 <pingou> mpduty: you should look at the headers of the email 18:12:39 <nirik> might be the meeting time is wrong in fedocal? 18:13:01 <pingou> I received it on the 23rd for a meeting on the 24th 18:13:09 <mpduty> but others say that they are receiving the reminder on time 18:13:14 <pingou> apparently, exactly 24h before the meeting 18:13:19 <nirik> ah, strange. 18:13:42 <pingou> mpduty: look at the headers of the email, one of the smtp server might be blocked it for some reasons 18:13:56 <mpduty> pingou: ok 18:14:03 <bwood09> So, no new apprentices this week? 18:14:17 <nirik> seems not. ;) 18:14:24 <nirik> #topic Applications status / discussion 18:14:46 <nirik> many of our application folks are traveling today back from the bodhi2 / taskotron FAD we just had. 18:14:58 <nirik> we got a lot of bodhi2 hacked on. 18:15:19 <abadger1999> Cool. Is it a shape that we'll deploy it soon? 18:15:22 <pingou> nice :) 18:15:27 <nirik> sadly not yet... 18:15:27 <pingou> stg/preview? 18:15:49 <nirik> it still needs more work to get it to that point... we were thinking of trying to get it to staging before too long and then do the cutover after f21 18:15:50 <tyll> where there any status updates mails this or last month? 18:16:09 <nirik> tyll: not last month, will be this month, I will be sending it out later today 18:16:37 <nirik> there are a number of bodhi2 consumers we don't control, so we want a lot of time for them to be able to adjust to new api. 18:17:07 <pingou> +1 18:17:21 <pingou> call for testers and announce API breaking :) 18:17:26 <nirik> absolutely 18:17:40 <mapyth> I would like to update you all on the status of bugspad. as we decided 18:18:00 <abadger1999> <nod> So the thread on major deployments on infra list might be helpful to create a plan from. 18:18:15 <mapyth> the ui is basic crud complete. 18:19:08 <mapyth> and we would be deploying on a server. for initial testing. 18:19:15 <nirik> abadger1999: I need to reply to that, haven't had time. 18:19:37 <abadger1999> nirik: <nod> Yeah ;-) 18:19:58 <nirik> mapyth: are you wanting resources from us for that? or what was the end goal of this application? 18:21:35 * nirik thought it was more of a thing for Fedora the community than anything infra would run. 18:21:43 <puiterwijk> quick update from me: FedOAuth 3.0 is finally feature complete and tested (big thanks to pingou for helping testing!), rolling the release now and going to deploy to stg in a bit 18:21:53 <pingou> puiterwijk: awesome 18:22:10 <pingou> nirik: it's a bug tracker in python and GO (iirc) 18:22:34 <nirik> pingou: yeah... 18:22:47 <oddshocks> Update on automatic cloud image uploading: Successfully pulling down image files and emitting fedmsgs upon successful download (such as to our internal FTP server). Currently hooking in proper AWS connections to upload images as AMIs to every EC2 region, which will also emit a fedmsg. 18:22:53 <oddshocks> Current code is at https://github.com/oddshocks/fedimg, I'd like to ask you all at this meeting today if you'd like to see it transfered to gh.c/fedora-infra or alternatively gh.c/fedora-cloud. 18:22:59 <oddshocks> I will also be adding a remote to https://git.fedorahosted.org/ at some point or folks who are opposed to git. 18:24:16 <abadger1999> puiterwijk: Congratulations! 18:24:29 <nirik> oddshocks: cool. we could transfer it to gh.c/fedora-infra if you like, or wait, whatever works. 18:24:42 <nirik> puiterwijk: what cool things aare in 3.0 again/ 18:25:49 <puiterwijk> nirik: well, mostly a full rewrite with a more stable codebase, multi-tab operation, and much more flexible to add more auth providers (openid connect, oauth, ...) in the future 18:25:50 <pingou> oddshocks: b/w fedora-infra and fedora-cloud I'd say it depends from which side/team you expect the most contributions 18:25:52 * nirik really needs to fix that a repeating 18:26:43 <oddshocks> pingou: in that case it's going to infra. the cloud org has only 2 repos and much less action because the cloud sig uses fedorahosted git more often it seems 18:26:55 <nirik> fair enough 18:27:28 <oddshocks> it has a lot to do with fedmsg and koji, too, so it fits 18:27:30 <puiterwijk> nirik: it should also finally fix the issue where you sometimes lose the session and get thrown back to the "You will be redirected here" homepage of fedoauth during an openid transaction 18:27:53 <pingou> oddshocks: also, for the record most (if not all) my projects are mirrored on hosted (just because :)) 18:27:56 <oddshocks> puiterwijk: nice! 18:28:12 <pingou> puiterwijk: looking forward :) 18:28:18 <puiterwijk> pingou: not just you :D 18:28:41 <puiterwijk> oh, and to get you even more hyped: I've got some ideas that I'm planning to announce at my talk at Flock for FedOAuth :) 18:28:44 <oddshocks> pingou: I will check with people if I can get permission to create repos like I have on GH. I think I had to be "added" to a repo before because I got an email about it. 18:28:49 * threebean waves "hello" 18:28:53 * pingou waves at threebean 18:28:54 * relrod waves too 18:28:58 * puiterwijk waves to threebean 18:29:00 <nirik> hello fadders. 18:29:05 <relrod> :) 18:29:06 * oddshocks waves at threebean 18:29:22 * roshi waves too since he's lurking :) 18:30:14 <nirik> ok, any other apps news? 18:30:14 <bwood09> Speaking of fedorahosted 18:30:26 <threebean> bodhi, bodhi, bodhi 18:30:26 <nirik> anyone from the FAD want to talk about bodhi2 status? ;) 18:30:32 <nirik> bwood09: yes? 18:30:50 <bwood09> I've been in school all the time lately, but I'm back on that guideline stuff 18:31:14 <bwood09> I've reviewed the feedback I got from mattdm, pingou, and other on the mailing list 18:31:29 <nirik> bwood09: cool. I saw the traac ticket on that the other day and thought about it briefly. ;) 18:31:30 <pingou> cool 18:31:48 <bwood09> I'm going to add that stuff to the doc, send it out again, and start figuring out statistics and implementation 18:32:05 <nirik> excellent. thanks bwood09 18:33:12 <mapyth> nirik: i would want for testing apps from the infra team . would be hosting it on my mentor's server. and would want the infra team to test it out and use. as an end goal would want it to be usable as an alternative bug tracking software. :) 18:33:38 <nirik> mapyth: ok, sure... happy to see what you have. ;) Do let us know when it's up for testing... 18:34:37 <hammad_> Hello, I would Like to update on Fedora-college. We have been doing the api for the project for these days. And done with the database models. Also, working on GUI side by side. 18:36:11 <nirik> ok. 18:36:21 * nirik really needs to read up more closely on these projects. ;) 18:36:46 <pingou> hammad_: nice, feel free to show us when you have something :) 18:36:54 <nirik> ok, thanks for status updates everyone. ;) 18:37:03 <hammad_> Surely pingou 18:37:20 <nirik> #topic Sysadmin status / discussion 18:37:27 <nirik> on the sysadmin side of things... 18:37:47 <nirik> dgilmore and I (and others) worked on our staging releng stuff... and it's a lot more usefull now. 18:38:00 <threebean> thanks for that :) 18:38:04 <pingou> cool :) 18:38:08 <nirik> koji01.stg can do builds, it has a builder, it has all the tags that prod has, etc. 18:38:12 <pingou> some much coolness @ FAD :-p 18:38:20 <nirik> and we should be able to do mashes and bodhi testing now too. 18:38:22 <abadger1999> Nice work! 18:38:34 <pingou> very nice :) 18:38:43 <nirik> we came up with a clever way to keep koji in sync... it uses the primary latest repos as external repos. 18:39:13 <nirik> I still need to rebuild pkgs01.stg in ansible and sync it (it's pretty out of date right now) 18:39:43 <nirik> Also, tflink and I had a lot of discussions around qa infrastructure. 18:40:01 <threebean> yeah, tflink's been working on a rewrite of rbac-playbook 18:40:06 <tflink> it'll be nice to get all of that done :) 18:40:12 <nirik> He's reworked rbac-playbook to be nicer/more featurefull and we are going to start merging their ansible stuff into our ansible repo. 18:40:18 <nirik> yeh. 18:40:42 <nirik> dgilmore and I also talked about moving the secondary stuff more into our ansible repo too. 18:41:01 <tflink> I think that the new rbac_playbook is ready for use but more eyes would be appreciated in case I missed something: https://bitbucket.org/tflink/rbac-ansible 18:41:21 <abadger1999> Tangent -- is the ansible repo something that we can make public? Or do we have legacy private stuff like we do in the puppet repo? 18:41:32 <tflink> isn't it already public? 18:41:43 <pingou> it is yes 18:41:46 <abadger1999> ah, it might be and I simply never looked for it. 18:41:50 <nirik> it is. 18:41:52 <tflink> http://infrastructure.fedoraproject.org/cgit/ansible.git 18:41:57 <nirik> public from the start. 18:42:00 <pingou> http://infrastructure.fedoraproject.org/infra/ansible/ 18:42:32 <nirik> we do still have a ansible-private/private repos, but those are mostly just passwords and keys and such 18:42:40 <abadger1999> <nod> 18:42:42 <abadger1999> Cool. 18:43:13 <nirik> smooge has been working on getting our new cloud boxes up so we can install cloud 2.0 18:43:41 <pingou> nice :) 18:43:57 <nirik> #topic nagios recap 18:43:59 <mattdm> yes nice :0 18:44:01 <mattdm> :) 18:44:02 <nirik> .tiny https://admin.fedoraproject.org/nagios/cgi-bin//summary.cgi?report=1&dis... 18:44:02 <zodbot> nirik: http://tinyurl.com/q8j48o9 18:44:10 <nirik> mattdm: you have a 'cloud' highlight? ;) 18:44:31 <mattdm> nirik only in my brain :) 18:44:49 <nirik> most of the nagios alerts this last week were the fedmsg monitoring stuff, and threebean pushed a hopeful fix for it. 18:44:57 <nirik> I don't think I have seen any of them since the fix was pushed. 18:45:02 * threebean nods 18:45:10 <threebean> yeah, there were two separate issues. fixes out for both. 18:45:21 <pingou> cool :) 18:45:24 <nirik> excellent. 18:45:28 <pingou> (did I already say that? :)) 18:45:29 <nirik> #topic Upcoming Tasks/Items 18:45:29 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/ 18:45:30 <threebean> there's a third and last issue with the fmn consumer, so it will continue to error out until I can get another release out there. 18:45:40 * nirik is quick on the paste, sorry. 18:45:51 <threebean> all good ;) 18:45:52 <nirik> any upcoming items folks would like to schedule or ntoe? 18:45:55 <nirik> note even 18:46:00 <pingou> the next fedocal release should be pretty cool :) 18:46:36 <nirik> oh yeah? whats in it? :) 18:46:54 <mpduty> :) 18:46:57 <pingou> auto-scrolling in the list view, so that it brings you directly to the future meeting 18:47:03 <pingou> a countdown that mpduty is working on 18:47:15 <pingou> (to know when is the meeting you're looking at) 18:47:20 <nirik> nice. 18:47:39 <pingou> shortcuts to add switch calendar view and get the iCal output easier 18:47:45 <pingou> and bug fixes :) 18:47:52 <threebean> mpduty, pingou: for the countdown, have you looked at moment.js? 18:47:55 <threebean> might be handy 18:48:12 <pingou> threebean: we were looking at some jquery based one 18:48:16 <pingou> but that's an idea 18:48:20 * threebean nods 18:48:31 <threebean> moment's api is quite nice 18:48:38 <mapyth> my net is giving me nightmares. was my message sent nirik? 18:49:25 <nirik> mapyth: about 10min ago? or newer? can you repeat to be sure? 18:50:16 <mapyth> am repeating. was wanting that once feature complete bugspad be tested with one or more apps from infra. 18:50:51 <mapyth> would be deploying on my mentor's server for testing 18:51:23 <nirik> I'm not sure what you mean by 'tested with one or more apps' ? can you expand on that? 18:51:37 <nirik> we can surely have people test it and look at it. 18:51:58 <mapyth> as a final goal would want it as a fast alternative to bugzilla. 18:52:12 <threebean> my and relrod's cab is here. gotta run 18:52:14 * threebean waves 18:52:21 <nirik> threebean: safe travels 18:52:32 <mapyth> testing as in using bugspad for tracking bugs of those applications 18:52:50 <nirik> mapyth: well, it's not too likely we will move fedora from bugzilla, but it's hard to say until we have more data I suppose. 18:53:49 <nirik> but sure, we are interested to look at it and see what needs it will match. ;) 18:54:31 <mapyth> nirik, okay then would want ppl from infra team to test it out once deployed. :) 18:55:51 <nirik> sure, let us know. 18:56:19 <nirik> #topic Open Floor 18:56:26 <nirik> any items for open floor? ideas, suggestions? 18:57:09 <pingou> I've had a bunch of changes to the elections app, we may want to cut a new release :) 18:57:57 <nirik> pingou: sounds good. no elections right now I don't think, so feel free. 18:58:07 * webpigeon is very late 18:58:09 <pingou> roger that, I'll prepare it then 18:58:24 <pingou> nirik: we also need to speak about the kerneltest-harness project 18:58:32 <pingou> I got a couple more fixes in today 18:58:36 <nirik> oh yeaah, where was that at? 18:58:40 <mapyth> what is open floor btw ? 18:58:41 <nirik> is it up anywhere we can look? 18:58:53 <pingou> seems to be ready feature-wise (just missing the fedmsg integration) 18:58:55 <nirik> mapyth: any items not covered by a specific topic... 18:59:14 <pingou> maybe jforbes has it running somewhere, I do not 18:59:20 <mapyth> nirik okay thanks. 18:59:42 <pingou> nirik: but before deploying I would not mind having a second set of eyes looking at the code 18:59:49 <nirik> pingou: cool. perhaps send to list? 19:00:00 <pingou> I'm still a bit chilly about anonymous uploads 19:00:07 <pingou> nirik: sounds good yes 19:00:36 <pingou> after that, since jforbes wants fedmsg integration, I think we have no choice but to put it in our traditional infra (vs the cloud) 19:00:50 <nirik> sure, yep. 19:00:53 <pingou> or to see with threebean if we can have a cloud instance talk on fedmsg 19:01:09 <pingou> note: that app has no unit-test atm :] 19:01:34 <nirik> we can, copr does. 19:01:47 <nirik> but might be better to move it to sundries server? 19:01:50 <pingou> ah, we have the choice then 19:01:55 <abadger1999> pingou: Hmm... well can it be used to upload any file? 19:02:00 <pingou> it's a web-app 19:02:07 <pingou> abadger1999: I try to restrict 19:02:19 <pingou> nirik: webapp on sundries ? :/ 19:02:26 <nirik> pingou: yeah, perhaps not then. 19:02:26 <pingou> if cloud is an option, I kinda like it 19:02:38 <nirik> oh, it needs a db tho right? 19:02:43 <pingou> it does yes 19:03:00 <nirik> which we could also run on the same cloud instance, but that makes it harder to backup, etc. 19:03:02 <pingou> good point 19:03:47 <nirik> we could still... we can think on it. 19:04:24 <nirik> ok, we are over time, so will close out in a minute if nothing else... 19:04:33 <pingou> abadger1999: actually, there are not really any :/ 19:05:01 <nirik> #endmeeting
infrastructure@lists.fedoraproject.org
-
Kevin Fenzi