18:00:01 #startmeeting Infrastructure (2016-03-31) 18:00:01 Meeting started Thu Mar 31 18:00:01 2016 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:01 The meeting name has been set to 'infrastructure_(2016-03-31)' 18:00:01 #meetingname infrastructure 18:00:01 #topic aloha 18:00:01 #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson 18:00:01 #topic New folks introductions / Apprentice feedback 18:00:01 The meeting name has been set to 'infrastructure' 18:00:01 Current chairs: abadger1999 dgilmore lmacken nirik pbrobinson pingou puiterwijk relrod smooge threebean 18:00:42 welcome everyone. quiet today, not sure how many folks are around. ;) 18:00:48 Heya! :) 18:00:54 I am :) 18:01:08 .hello smdeep 18:01:09 smdeep: smdeep 'Sudeep Mukherjee' 18:01:28 Any new folks want to give a short one line introduction on themselves? 18:01:33 * jflory7 is idling around 18:01:39 Sure 18:01:44 * sayan is here 18:01:44 or any apprentices with questions/comments/ideas? 18:01:45 * tflink is around 18:01:49 hi, gkadam here 18:02:12 * Ganesh here 18:03:15 new folks: fire away when ready with a short intro. ;) 18:03:36 Dimitar here, decided I want to join the Fedora Project, Infra group in particular, in the beginning of this month. Years of experience of QA, moving into the Ops team /work. Decided to join because I loved Fedora ever since I started using it, hopefully I'd be able to help out around. All kinds of questions welcome, don't hesitate at all :) 18:04:05 ^ not sure how much to include as 'short' info, that's why ask away 18:04:17 welcome winterchillz! :) 18:04:31 are you more interested in sysadmin type work? or development? or both? 18:05:31 Thank you, nirik, it's an honor to be here :) Sysadmin type of work, was looking to the hosted and noc sysadmin groups. Development as far as writing some small Bash/Python scripts so far, might involve further with time but I want to know my skills would be sufficient before jumping into the deep 18:06:00 great. See me after the meeting in #fedora-admin and I can get you setup in our apprentice group... 18:06:04 Hi, I am here to learn sysamdin skills,configuration management and coding. I know basics of linux administration,nagios-core,bash and python. 18:06:15 Understood 18:06:17 gkadam: welcome! 18:06:44 gkadam: likewise I can help get you started after the meeting... if you can see me in #fedora-admin after will try and point you the way. :) 18:07:00 nirik, sure ! thank you! 18:07:12 any other new folks or apprentice questions? 18:07:53 alright, moving on to status/info... 18:08:05 #topic announcements and information 18:08:05 #info Bugzilla messages are now live on our fedmsg bus! - threebean 18:08:05 #info Fedora 24 Alpha was released tuesday (2016-03-29) - everyone 18:08:05 #info New calendar for modularity effort - kevin 18:08:05 #info Feedback in ask now goes in ask questions with meta tag - kevin 18:08:06 #info Lots of small ansible changes pushed out after freeze - kevin/patrick 18:08:08 #info db-koji01 still under heavy load for some reason - kevin 18:08:10 #info New bodhi release pushed to production https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/6CMQ7KE4XMCYEPAG3XDSRB2O47K37LOH/ - lmacken 18:08:18 anything else anyone would like to add or expand on? 18:09:14 ok, then, can move on to discussion items... 18:09:58 * nirik doesn't see aikidouke around... 18:10:05 #topic fedmsg from bugzilla brainstorming session - kevin / threebean 18:10:23 so, as some of you may know we finally have fedmsg's from bugzilla.redhat.com coming in. 18:10:37 (It's been a long time planning... many thanks to threebean for herding it along) 18:10:58 We already have some ideas for how to use the info there, but I thought I would throw it out to the meeting to think of things. 18:11:50 There were some things mentioned on the list already... badges, some scripts... 18:12:59 I guess if folks come up with more ideas, adding them on the list would be good. 18:13:04 * nirik goes to dig up the thread 18:13:05 * threebean is here 18:13:16 sorry I'm late :p was off in a codebase. 18:13:27 nirik: maybe making a wiki page with the ideas is an idea? 18:13:32 http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/RBOXBFIVGH77EYQNF7FP6SMZT7QSSFMH/ 18:13:51 we could I guess... although... does 'fedmsg' overall have a TODO or the like? 18:14:01 or IDEAS 18:14:12 nirik: heh, no it does not. we had a 'status' page to track things like that in the beginning, but it grew too large and became unmaintained. 18:14:41 yeah, I guess somewhat iit's out of scope there... its using it, not changing anything it already does 18:14:44 the span is a bit wide. I'd say, if possible we could file each idea in the respective system or team tracker. 18:14:58 so, we should file a badges ticket. if blockerbugs in QA land can benefit, we should file a ticket there. 18:15:05 for fedora-packages, we've got this one ready to be rolled out: https://github.com/fedora-infra/fedora-packages/pull/232 18:15:09 Yeah, that sounds like a good idea. 18:15:31 yeah, there were badges tickets and Churchyard already moved them all from 'impossible to implement yet' to the ok stage. ;) 18:15:39 yay! 18:15:46 mhroncok++ 18:15:46 threebean: Karma for churchyard changed to 3 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:16:16 very nice on packages. ;) 18:16:30 threebean: blockerbugs already has a ticket - https://phab.qadevel.cloud.fedoraproject.org/T393 18:16:53 cool :) 18:17:18 makes me wonder: flock workshop to make fedmsg use more awesome. and just brainstorm/file/fix easy ones... 18:17:18 the commops group is excited about accessing the bz data too.. but I dunno if they have a concrete plan yet (which is fine) 18:17:37 cool :) 18:17:57 could we call it an automation workshop (same gist, just different branding..)? 18:18:11 sure! 18:18:40 * threebean will file the idea in regcfp asap. 18:18:52 cool. 18:19:25 ok, anything else for now on this? or shall we move on? 18:20:33 #topic CDN use? - kevin 18:20:40 what's this about? :) 18:20:51 so I just filed a ticket on this, but there's a CDN provider that wants to sponsor us for some amount of usage. 18:21:11 so, we need to figure out how best to use this or if we can easily, etc. 18:22:07 I've not looked super closely yet, but I think the basic thing is you setup some site in their control panel then it gives you a CDN url to your stuff... 18:22:27 so you can in turn replace your links with that and it will hit their CDN which will hit your site if it doesn't have it cached yet 18:22:36 and they have an api so you can invalidate, etc. 18:22:59 nirik: do we know what amounts they are willing ot provide us with? 18:23:03 I think this could be nice for us on heavily downloaded things... but perhaps we need to id what those are. 18:23:31 "some amount of TB/month in the US/EU." 18:23:39 Right. 18:23:43 so it's not clear really. 18:23:48 would we want to use this for things like OS content (images, repos, etc..?) or for website resources like css/js assets.. stuff that we do with varnish now? 18:23:51 But then I think that for most of our content, we have the mirror network 18:24:26 threebean: well, thats a good question. ;) I don't think we would want to start out with OS content as it's large and unclear what parts are heavy usage... 18:24:57 they do have plugins for things like wordpress, so we could try it on the magazine sites perhaps (with approval from those groups) 18:25:32 websites still might be also pretty easy to try... just replace links to assets... 18:25:56 but do those really get hit too much or would this kind of be a waste? 18:27:02 Also, it seems centos folks are also exploring this, so we could perhaps speak with them some too. 18:28:18 looks like they are using it for OS content 18:28:47 And CentOS are speaking with the same guys? 18:29:09 http://buildlogs.centos.org/centos/7/isos/x86_64/CentOS-7-livecd-x86_64.iso 18:29:11 yep 18:29:39 they are using a redirect it looks like... 18:29:49 yeah, indeed. 18:29:55 To buildlogs.cdn.centos.org 18:30:10 yep. 18:30:39 so, we don't have to decide anything right now, but I wanted to get people thinking how we can best use this. 18:30:49 So, I think that wordpress might be a good one to try. 18:31:52 so how best would we work that... 18:32:19 Well, as soon as we have info on how to set it up, I can look at how to integrate it with wordpress 18:32:37 There's a plugin, but I don't know what it replaces, etc. 18:32:50 Yeah, so I'd have to look into that 18:33:24 ok. I was going to also make an account there and look at the admin side of things 18:33:26 Maybe we can ask them to give us an account so we can test some of our sites? Then I can probably set it up for magazine/commops 18:33:47 anyone can make a account that is good for 14 days of service. 18:33:59 Ah, okay, sounds good. 18:34:05 note on ssl tho: 18:34:33 if you get a url with your name... like buildlogs.cdn.centos.org it's http only unless you upload your ssl cert/key to them 18:34:47 or you can use https with their long url... 18:35:07 Right. So we'd need to request a new cert for it 18:35:08 * nirik doesn't want to upload our wildcard cert to them 18:35:16 nirik: yeah, agreed. 18:35:35 So we could try with magazine then, since that has its own cert. 18:35:37 yeah, for every new site of those... unless we just do a 'cdn.fedoraproject.org' one 18:35:53 or we can just use their urls. Not sure how many people care. 18:36:42 Well, that would limit what you can host there 18:36:43 so anyhow, if folks are ok trying out things with wordpress and going from there that sounds like something of a plan. 18:37:02 how so? 18:37:06 If you want to host javascript things for example, they need to be under a subdomain or the like, depending on their CORS headers 18:37:25 ah yeah, true. 18:38:12 So, are you planning to create an account for Fedora Infra in general? Or shall I just register my own to test magazine? 18:38:17 another possible thing to look at: pagure or possibly mailman3 18:38:38 I was thinking of making a fedora one, but you can if you like and put the creds in ansible-private. 18:38:50 Sure, sounds good 18:38:57 I'll create one after the meeting 18:39:01 or another possible one: copr 18:39:28 It would be nice to know where we have high hits/usage, but we really don't know 18:39:38 Right. Although there there's so much content that none of them is likely to become "often used" 18:39:55 yeah, same problem with a lot of OS stuff. 18:39:58 Well, we could find out by just analyzing the httpd log files I guess... 18:40:02 isos and the like might be worth it. 18:40:36 we can ask smooge to add that to the list of things we want from stats. 18:40:48 Yeah, sounds like a good idea. 18:41:00 Although... One problem with COPR 18:41:14 It's very easy for people to replace files with other content with the same name. 18:41:29 (by just deleting a build and then restarting a build with the same nevr) 18:41:44 true, that could be a issue. 18:41:51 So we should be careful of those kinds of things, unless COPR adds code to deal with a CDN 18:43:00 It also might be possible to setup the CDN like it was a mirror and have mirrormanager offer it first (or high pri) to everyone... 18:43:19 but thats likely going to be complex and might be more BW/files than the CDN wants to serve for us 18:43:30 Well, I'm not sure that that's going to be a good idea 18:43:44 me either, but I thought I would toss it out there. :) 18:43:47 Since that would mean that lots of files would get requested, and probably not many of them ever make it into the cache. 18:44:02 And then people are all still downloading from the master mirror 18:44:39 anyhow, lots of possibilities out there. :) 18:44:43 anything else on this for now? 18:45:26 I had puiterwijk talking about RFE process sometime, but not sure today is a good day for it. ;) Should we just drop that and reschedule it someday later? 18:45:46 Yeah. 18:46:05 can do. I can also try harder to line up people to talk about things. ;) 18:46:09 #topic Open Floor 18:46:21 anyone have anything for open floor? ideas/comments/questions? 18:47:11 ok, will close out in a minute then and we can all get back to our days. ;) 18:47:57 Thanks for coming everyone. Do continue in #fedora-admin, #fedora-noc, #fedora-apps. ;) 18:48:00 #endmeeting