18:00:03 <nirik> #startmeeting Infrastructure (2016-10-13) 18:00:03 <zodbot> Meeting started Thu Oct 13 18:00:03 2016 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:03 <zodbot> The meeting name has been set to 'infrastructure_(2016-10-13)' 18:00:04 <nirik> #meetingname infrastructure 18:00:04 <zodbot> The meeting name has been set to 'infrastructure' 18:00:04 <nirik> #topic aloha 18:00:04 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson 18:00:04 <zodbot> Current chairs: abadger1999 dgilmore lmacken nirik pbrobinson pingou puiterwijk relrod smooge threebean 18:00:04 <nirik> #topic New folks introductions 18:00:07 <clime> hey! 18:00:21 <trishnag> Hi 18:00:24 <jflory7> .hello jflory7 18:00:25 <zodbot> jflory7: jflory7 'Justin W. Flory' <jflory7@gmail.com> 18:00:37 <nirik> morning everyone 18:00:49 <wind85> hi everybody! 18:00:53 <puiterwijk> .hello puiterwijk 18:00:54 <zodbot> puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' <puiterwijk@redhat.com> 18:00:58 <marc84> hi 18:01:19 <nirik> any new folks like to give a short one line introduction? 18:02:52 <nirik> any new folks like to give a short one line introduction? 18:03:07 <nirik> I think mostly I know the active nicks... but might be someone new lurking out there. :) 18:03:37 <jcline> .hello jcline 18:03:38 <zodbot> jcline: jcline 'Jeremy Cline' <jeremy@jcline.org> 18:04:23 * threebean waves 18:04:23 <nirik> ok, lets go on to status/info then... 18:04:35 <nirik> #topic announcements and information 18:04:35 <nirik> #info fedora-flask-admin and mirrormanager2 now in Fedora/EPEL - patrick 18:04:35 <nirik> #info Fedora 25 Beta released! - everyone 18:04:35 <nirik> #info modernpaste plans sorted out - relrodg 18:04:36 <nirik> #info database replication setup with koji.stg, please test - kevin 18:04:46 <nirik> anything else anyone wants to note or add or discuss from those? 18:04:55 <nirik> Oh, there's a new pagure in production now. 18:05:05 <nirik> has a bunch of fixes we have been waiting for 18:05:11 <puiterwijk> #info mirrorlist2 in staging now a container, scripting waiting - patrick 18:05:39 <nirik> #info pagure 2.7.2 live in production, migrations can resume now 18:06:10 <threebean> cool :) 18:06:48 <nirik> puiterwijk: so whats next steps on that? we need to make sure we can build it in a controlled way/for security updates... then deploy on one prod to test? 18:07:07 <puiterwijk> nirik: I'm going to build it on OSBS, that should do the security stuff etc 18:07:12 <puiterwijk> so I need to help Adam fix that tonight :) 18:07:19 <puiterwijk> After that, we deploy and write scripts 18:07:23 <bowlofeggs> .hello bowlofeggs 18:07:24 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com> 18:07:52 * nirik nods. excellent 18:08:16 <nirik> ok, on to discussion items 18:08:19 <nirik> #topic Modularity and F26 18:08:25 <nirik> threebean: I think this was likely you? ;) 18:08:30 <threebean> yup yup :p 18:08:42 <saunind> hi all 18:08:48 <threebean> so, in the modularity side of things we're starting to narrow in on some goals for the f26 release 18:09:04 <saunind> U am a new one) 18:09:05 <nirik> cool. 18:09:09 <threebean> which starts to bring the infra/apps/releng requirements into a more sharp relief. 18:09:33 <threebean> it's not finalized yet, but the goal (I think) is to build and ship most of F26 as we do today. 18:09:34 <nirik> welcome saunind. Can you wait for this topic to be over and then give us a one line introduction? 18:09:53 <saunind> of cause no problem 18:10:05 <threebean> but we're going to try and have Fedora Server built up from this new "base-runtime" module we're trying to put together 18:10:30 <nirik> sounds fun. 18:10:45 <threebean> it's unclear if there will *only* be a Fedora Server derived from base-runtime, or if we'll do a normal Fedora Server in addition to a new modular Fedora Server. but, that's where we're at. 18:11:19 <threebean> I wanted to bring it here, because that means we'll need to get some things ready for production and see if they work how we want before the F26 alpha freeze, which is at the end of February. 18:11:59 <threebean> it's mainly still just in the build and compose parts of the pipeline. 18:12:31 <threebean> we've got this module build service that's still in prototype phase. we would need to get close to deploying that. 18:12:48 <threebean> and there's also some pungi changes we haven't scoped out yet, but they wouldn't be a huge departure from what we do today. 18:12:52 <nirik> cool. Mostly bolted on to koji? 18:12:55 * threebean nods 18:12:59 <threebean> nirik: on both counts, yeah. 18:13:16 <nirik> and perhaps a new compose box to do these composes? or I guess it could share with the others 18:13:38 <threebean> yeah, hopefully it could share. we would want to be out of development and have these be "real" composes by then. 18:13:44 <nirik> are you thinking we might need more HW for any of this? we are just rough drafting budget for next year if you have any asks we should ask 18:13:49 * threebean shakes his head 18:14:01 <threebean> no new expectations on hardware. just a handful more VMs. 18:14:56 <threebean> in the f27 timeframe, we may want to look at more hardware for both taskotron and koji builders if that's a possibility but we haven't exhausted other options for optimizing things in software yet. 18:15:29 <threebean> there are a number of other bigger changes we want to make in the f27 time frame (that we'll start dev on soon), but they won't impact us for f26. 18:15:31 <nirik> cool. makes it more flexable. :) 18:16:12 <threebean> those far-off things include automated rebuild stuff. the fancy pkgdb/dist-git branching model changes pingou, I, and others talked about at Flock. pipeline visualization tools (a.k.a. the BPO) 18:17:16 <threebean> I dunno. I just wanted to say all this to the group. nothing more from me for now. any questions or anything? 18:17:44 <nirik> all sounds good to me. Happy to help in moving stuff to production... 18:17:56 <threebean> I will say (again on the F27 timeframe) that I met the guys who wrote Zuul at AnsibleFest this week and it's really cool. 18:18:11 <nirik> oh yeah, ansible is moving to using that right? 18:18:12 <threebean> we cooked up *possible* plans to add a pagure frontend and some resultsdb/fedmsg backends for it. 18:18:28 <nirik> that might be nice. 18:18:39 <threebean> nirik: both ways. Zuul is moving to use ansible under the hood. and the ansible infra is moving to use it for development of ansible itself. 18:18:58 <threebean> nirik: it could provide us a nice self-service way for people to do mass rebuilds of big stacks (like GNOME or KDE) 18:19:08 <threebean> and to get CI feedback into pull-requests in pagure/dist-git. 18:19:29 <threebean> "will the patch break rawhide?" before it's merged into master. 18:19:32 <nirik> nice. we sort of have that with jenkins now... but thats not super ideal. ;) 18:20:13 <threebean> yeah. the gem in there is that zuul can coordinate a set of changes across multiple repos, which afaik jenkins can't do on its own. 18:20:33 <threebean> so I can say "these two python-requests and python-urllib3 changes depend on each other". 18:20:45 <nirik> yeah. 18:21:07 <nirik> worth looking into for sure. 18:21:14 <threebean> someday, someday. 18:21:14 <nirik> ok, anything else on this? 18:21:23 <threebean> not from me. :) 18:21:59 <nirik> excellent. thanks threebean for keeping the communication open and often on the modularity stuff. :) 18:22:11 <nirik> #topic Apprentice Open office hours 18:22:14 * threebean salutes 18:22:21 * kushal is also here today 18:22:24 <nirik> any apprentices with questions or comments? or looking for things to do ? 18:23:11 <wind85> yep.. is there an infrastructure map sort of thing I can have a look at :)? 18:23:25 <nirik> wind85: there's actually a ticket open to make such a thing. ;) 18:23:43 <nirik> https://pagure.io/fedora-infrastructure/issue/5290 18:24:08 <nirik> so, I'm afraid we don't have one currently, but you are welcome to help work on making one 18:24:37 <wind85> cool... in terms of starting out with real work, should I just pick a ticket and try to fix it? 18:24:59 <nirik> yeah. Normally we have some easyfix tickets we have marked that are good for new folks... 18:25:12 <nirik> I need to go relabel some since I dropped that labeling when we moved to pagure.io 18:25:27 <puiterwijk> nirik: I think there's still a couple labeled 18:25:38 <nirik> yeah, I did a few, but probibly should do some more. 18:25:42 <puiterwijk> right 18:25:43 <wind85> Ok I'll start from there :) ... thanks a lot guys... 18:26:02 <nirik> and if anyone thinks of some good easyfix things we need to do, we should file tickets. Sometimes it's hard to think of them... 18:26:31 <nirik> sankarsh`: you want to give a short intro? and are you more interested in application development or sysadmin type things? or both? 18:27:28 <clime> saunind perhaps? 18:27:34 <saunind> yes 18:27:49 <nirik> sorry, tab failure. sorry sankarsh` 18:28:11 <saunind> My name is Dmitry, GMT+4, currenty network engineer woth UNIX administration experience. :) 18:28:35 <clime> welcome! 18:28:55 <saunind> Intresrted in Linus sys admin 18:28:57 <saunind> thx 18:29:20 <saunind> And i want to learn Python programming 18:29:31 <nirik> saunind: excellent. Welcome. I can add you to our apprentice group to look around if you like... just let me know your fedora account system login... 18:29:42 <saunind> saunind 18:29:49 <nirik> yeah, most of our applications are in python. Folks in #fedora-apps can help you get started there. 18:29:58 <nirik> https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix is the easyfix tickets list 18:30:16 <skala> Are you using only python2? 18:30:43 <nirik> mostly python2 still, but we do have some python3 applications. 18:30:47 <saunind> Should i start with easyfix tickets? right? 18:31:22 <nirik> yep. 18:32:39 <nirik> saunind: ok, I added you, will take 10-20min to sync out... there's a link on the apprentice page for how to setup ssh config to get into machines. 18:33:02 <nirik> any other apprentice questions? 18:33:20 <saunind> Where can i find apprentice page?) 18:33:26 <saunind> sorry for silly questions) 18:33:54 <skala> if you want, I'll help you after meeting 18:33:59 <nirik> not silly at all. 18:34:02 * nirik digs up link 18:34:14 <nirik> https://fedoraproject.org/wiki/Infrastructure_Apprentice 18:34:15 <mizdebsk> https://fedoraproject.org/wiki/Infrastructure_Apprentice 18:34:39 <saunind> <skala> okk)) 18:35:09 <nirik> you're also welcome to ask anytime in #fedora-admin... someone can assist/answer when they are around. 18:35:14 <nirik> #topic Open Floor 18:35:28 <nirik> ok, anyone have any other items? questions, comments, favorite video games? 18:35:48 <clime> armagetronad :) 18:35:55 <clime> but that used to be. 18:35:56 <nirik> nethack forever. ;) 18:36:10 <puiterwijk> neth.. yeah, that :) 18:36:17 <aikidouke> turning down the thermostat in my house 18:36:17 <vivek_> where can i learn stuffs that pingou and puiterwijk keep talking (different everyday, mostly) about in fedora-apps? 18:36:46 <puiterwijk> vivek_: what stuff do you mean? 18:36:50 <nirik> vivek_: well, I guess in there? :) 18:37:14 <puiterwijk> vivek_: if you want to know about anything, don't hesitate to ask me and/or pingou to explain :) 18:37:29 <vivek_> ok, okay. Thanks :) 18:37:41 <nirik> yeah, questions are great. Sometimes if there's an outage or whatever people can't answer then, but they can answer later... 18:37:59 <wind85> guys, when will it be the next apprentice workday? Does anybody know? 18:38:21 <aikidouke> i think we were waiting until after f25 release 18:38:23 <puiterwijk> wind85: I'm not sure any have been scheduled. So come up with a date and submit it to the list for discussion? 18:38:30 <nirik> wind85: we haven't scheduled one, but we could... probibly after f25 is out... yeah 18:38:53 <aikidouke> if you have an idea maybe open an issue on the pagure-infra? 18:38:57 <wind85> sorry guys it's only my second meeting I don't know how it all works yet :) ... 18:39:08 <aikidouke> no - great reminder wind85 18:39:14 <aikidouke> wind85++ 18:39:14 <zodbot> aikidouke: Karma for wind85 changed to 1 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:39:19 <nirik> probibly best to discuss on list... 18:39:27 * aikidouke nods 18:39:31 <nirik> but yeah, I am all for having another one. 18:40:19 <nirik> ok, if nothing else I will close out in a few here and everyone can get a bit of their day back. :) 18:40:31 <mizdebsk> what is status of infra builds in koji? 18:40:39 <puiterwijk> mizdebsk: live, in production 18:40:47 <mizdebsk> are these builds installable on all machines? 18:40:50 <puiterwijk> yes 18:40:57 <puiterwijk> well, all our machines :) 18:41:12 <nirik> there's a doc on that. 18:41:18 <nirik> should likely send to the list announcing it. 18:41:19 <mizdebsk> so i can just build there and "yum install" them, without sysadmin-main intervention any longer? 18:41:31 <puiterwijk> mizdebsk: yep. 18:41:40 <puiterwijk> Ask nirik to grant you permissions for that 18:41:41 <mizdebsk> great news! thx 18:42:03 * nirik looks for doc 18:42:15 <puiterwijk> (I'd like to not give those permissions out to anyone, but mizdebsk is fine with me) 18:42:28 <puiterwijk> nirik: https://infrastructure.fedoraproject.org/infra/docs/infra-repo.rst ? 18:42:41 <nirik> yes, thats it. 18:42:46 <puiterwijk> mizdebsk: ^ that has instructions 18:42:56 <nirik> yep. Happy to add mizdebsk 18:43:58 <mizdebsk> that would be good 18:44:25 <mizdebsk> (yes, i can see that now you need "autosign" permission) 18:44:51 <puiterwijk> mizdebsk: no, autosign is only for the final tag. The -canddiate are "infra" 18:45:01 <nirik> done 18:45:05 <puiterwijk> The distinction is in that document 18:45:47 <nirik> ok, thanks for coming everyone. Do continue in #fedora-admin, #fedora-apps and #fedora-noc. 18:45:50 <nirik> #endmeeting