18:00:34 #startmeeting Infrastructure (2015-11-12) 18:00:34 Meeting started Thu Nov 12 18:00:34 2015 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:34 #meetingname infrastructure 18:00:34 #topic aloha 18:00:34 #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson 18:00:34 The meeting name has been set to 'infrastructure' 18:00:34 Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pbrobinson pingou puiterwijk relrod smooge threebean 18:00:35 #topic New folks introductions / Apprentice feedback 18:01:02 * threebean is here 18:01:10 * dotEast2015 here 18:01:10 .hellomynameis smdeep 18:01:11 smdeep: smdeep 'Sudeep Mukherjee' 18:01:16 * aikidouke present 18:01:42 morning everyone 18:01:52 morning 18:02:00 morning 18:02:20 any new folks like to introduce themselves? or apprentices with questions or comments? 18:02:30 hi guys 18:02:40 Hi there, first meeting here 18:03:02 nirik, I am an apprentice and I would like to start in earnest from next week 18:03:11 Been a festival season here in India 18:03:16 this 18:03:18 week 18:03:24 cool. ;) no problems... 18:03:26 happy diwali 18:03:30 welcom cortopy 18:03:38 :) 18:03:49 I sent an email this week to the mailing list introducing myself 18:04:00 not sure what the dynamic is, should I say a few lines about me? 18:04:53 sure, please do. ;) 18:05:11 and let us know if you are more interested in sysadmin work or application development type stuff.... or both! 18:05:22 Ok, I'm Juan from London 18:05:40 I was thinking about starting with something small like ansible 18:05:59 I read about the meeting next week, and thought it'd be a great starting point 18:06:09 cortopy, would love to learn with you 18:06:11 sysadmin would be great 18:06:22 server setups, mnitoring,etc. 18:06:24 yeah, we are having a apprentice work day next wed... hopefully we can help folks get involved there. 18:06:45 also interested in app development, but not sure what languages are used by the Fedora project 18:06:59 I can write Python, JS, and basic bash 18:07:19 most of our stuff is using python... with flask and pyrimid. 18:07:55 anyhow, see me after the meeting over in #fedora-admin and I can get you started in the apprentice group. ;) 18:08:00 I kind of gathered that's the case by reading the discussions in the mailing list 18:08:12 Ok, that's great. Thanks nirik 18:08:14 any other new folks like to introduce themselves? or questions? 18:08:17 * kushal is here 18:08:37 hello 18:08:51 looking forward to the apprentice day :) 18:09:11 d3prof3t, same here 18:09:15 is there a certain format that is followed for intros? 18:09:33 smdeep, cool 18:09:40 djb_: just a line or two about yourself and what your interests are. 18:11:35 ok, I work as a network admin, been using fedora off and on since fedora core 5 along other distros. My interests are systems and programming though, I have very little expereince in the latter other than tinkering and do messing around with my raspberrys 18:12:00 cool. Are you more interested in the sysadmin side of things then? or application development? 18:14:21 ok, lets move on to status and info... 18:14:25 #topic announcements and information 18:14:25 #info Setup ticket for phx2 site visit in jan: https://fedorahosted.org/fedora-infrastructure/ticket/4948 18:14:25 #info Setup ticket for re-arranging networks: https://fedorahosted.org/fedora-infrastructure/ticket/4949 18:14:25 #info Have done some ansible 2.0 testing and upstream has been fixing issues - kevin 18:14:28 #info Got reproducer for sigul batch signing issues and updated bug - kevin 18:14:28 * relrod here late -- sorry :( 18:14:30 #info arm02/arm04/buildvm's all re-installed as Fedora 23 - kevin 18:14:36 anything else anyone would like to note or discuss from there? 18:14:40 welcome relrod 18:15:59 more of the sys admin side but I'd like to be involved with code too 18:16:05 did mdapi get deployed? 18:16:33 threebean: I think so in stg at least, but not sure. 18:16:37 cool :) 18:16:40 * mirek-hm is here 18:16:56 There's some old tickets to discuss in the discussion section. 18:17:02 yeah! 18:17:03 welcome threebean, mirek-hm. 18:17:04 https://apps.stg.fedoraproject.org/mdapi 18:17:26 should I jump in here? 18:17:33 #topic discussion - old tickets 18:17:46 aikidouke: sure, if you want to run this section, fine by me. ;) 18:17:58 :) keep me on track please 18:17:59 #chair aikidouke 18:17:59 Current chairs: abadger1999 aikidouke dgilmore lmacken mdomsch nirik pbrobinson pingou puiterwijk relrod smooge threebean 18:18:03 .ticket 1055 18:18:04 aikidouke: #1055 (Fedora Search Engine) – Fedora Infrastructure - https://fedorahosted.org/fedora-infrastructure/ticket/1055 18:18:12 yeah, so this is still out there... 18:18:23 but it's a ton of work and the last people working on it seem to have moved on. 18:18:46 right - that is kind of what I thought - is anyone working on replacing mediawiki still? 18:19:01 no? that was never planned that I know of 18:19:26 ok...I'm making that up then...so verdict on this? would we cancel or close it? 18:19:28 The wiki search is horrible, so it's something that could be replaced by an external search product. 18:19:51 well, I guess we could close it and reopen someday if someone else wants to try again. 18:20:05 should we put that to a vote? 18:20:23 * kushal wants to write a search engine :) 18:20:28 someday :D 18:20:43 I don't think there's a need to do that... does anyone disagree? 18:21:19 I do not disagree - just wanted to discuss...going once on disagreements? 18:21:21 lets close it with a 'file new ticket or reopen if someone wants to move this forward again' 18:21:28 +1 to close. Current FOSS search engine options are... lacking, at best 18:21:50 anyone else? 18:22:11 +1 to close. 18:22:30 ok - I will close that with 'file new ticket or reopen' if I can 18:22:42 next up - Fedora elections infra license 18:22:44 .ticket 1510 18:22:46 aikidouke: #1510 (Status of converting Elections to conform with Infrastructure Licensing) – Fedora Infrastructure - https://fedorahosted.org/fedora-infrastructure/ticket/1510 18:23:23 nb was working on that. 18:23:27 * nirik re-reads tho 18:23:31 7 months ago pingou asked if this was still needed b/c the elections process had changed since the original request 18:24:22 yeah, close. 18:24:25 no longer needed. 18:24:30 new elections is GPLv2 18:24:44 close it with a comment then. 18:24:50 great 18:25:09 * nirik nods. 18:25:26 .ticket 3525 18:25:27 aikidouke: #3525 (New mediawiki redirect behaviour is annoying) – Fedora Infrastructure - https://fedorahosted.org/fedora-infrastructure/ticket/3525 18:25:41 so this hasnt been touched in two + years 18:25:54 one user did not like the redirect behavior? 18:26:15 yeah, I think there was thought about fixing it or chaning it or adding a pref, but that never got done. 18:26:28 close 18:26:36 anyone disagree? 18:27:01 I could see close or ask in ticket if anyone is still planning anything here, and close in a week if no answer. 18:27:01 moving on then 18:27:16 close is fine, someone can reopen if they plan to work on it. 18:27:23 .ticket 4458 18:27:25 aikidouke: #4458 (downloads from fedoraproject.org are slow) – Fedora Infrastructure - https://fedorahosted.org/fedora-infrastructure/ticket/4458 18:27:38 I'd like to ping folks again on this and see if anyone is still seeing it. 18:27:49 Even if they are I suspect there's not much we can do. 18:28:00 ok sounds good - should i post a comment in ticket? 18:28:54 I can. 18:29:02 ok - good deal 18:29:10 thats all I had for old tickets 18:29:19 cool thanks 18:29:26 ty 18:29:28 aikidouke, thanks 18:29:53 thanks aikidouke. :) 18:30:02 :) happy to do it 18:30:19 aikidouke++ for cleaning up old tickets! 18:30:20 pingou: Karma for aikidouke changed to 2 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:30:22 we will get down to 0 in no time. ;) 18:30:28 pingou: you ready to talk about mdapi? 18:30:34 nirik: sure am 18:30:36 https://fedoraproject.org/wiki/Infrastructure/GettingStarted 18:30:42 sigh. wayland. 18:30:49 #topic Learn about: mdapi - pingou 18:30:55 take it away pingou 18:31:05 so mdapi for MetaData API 18:31:28 it lives at: https://apps.stg.fedoraproject.org/mdapi/ for in staging instance and http://209.132.184.236/ for its dev instance 18:31:57 basically, the idea is to serve as quickly as possible information stored in the metadata of the yum repositories we have 18:32:13 there are basically 3 sqlite DBs in the yum repo metadata 18:32:37 the main one, that will serve info such as package, version, release, epoch, source package and so on 18:32:43 this is what https://apps.stg.fedoraproject.org/mdapi/rawhide/pkg/kernel uses 18:32:43 .nsg zodbot aikidouke++ 18:33:06 needs to leanr to type 18:33:07 the second is the filelists db 18:33:24 as the name says it provides the list of all the files in every packages 18:33:34 so that you can do things like yum/dnf install /usr/bin/ansible 18:33:47 for example https://apps.stg.fedoraproject.org/mdapi/rawhide/files/guake 18:33:54 finaly, there is the other db 18:33:59 so this is to be used by things that don't want to use dnf api or such overhead? or? 18:34:09 that containts, amon other the changelog, used at: https://apps.stg.fedoraproject.org/mdapi/rawhide/changelog/kernel 18:34:16 nirik: yes 18:34:38 it should be snappier than using dnf's api as there is no download of the cache involved 18:34:51 but relies on network 18:35:04 so there are cases where it might be slower I guess 18:35:26 currently when you ask for a package it looks at: updates-testing, updates, release 18:35:28 you can ask it to give you the info for just one package, instead of having to download the dbs containing all the info for all the packages, and extracting that yourself. 18:35:30 for a given branch 18:35:39 (branches being listed at: https://apps.stg.fedoraproject.org/mdapi/branches ) 18:35:59 I have been doing the fun part of the work, writing it :) 18:36:12 threebean has been doing the more serious and tedious part: using it :) 18:36:15 cool. what things do we have planned to use it? or ? 18:36:17 :p 18:36:29 fedora-packages ( https://apps.fedoraproject.org/packages ) is being re-written to use it 18:36:53 we still need to improve it to add element such as provides, excludes, requires & co 18:36:58 nice. 18:37:04 so we could also use it to build quickly dependency trees or so 18:37:18 fedora-packages historically has suffered from locally caching and querying those sqlite dbs which it had a tendency to mis-use and corrupt. now it can use mdapi to get the data in what feels like a more sane way. 18:37:23 * pingou has plans to play a little bit with it for this kinds of questions 18:37:45 mdapi opens a single db session for every requests made 18:37:55 so how does it update or how often/expensive is updating? 18:38:10 but sqlite has been handling the load fine so far 18:38:21 so the update of the metadata is done via a cron script 18:38:33 running every 20 minutes (which is also the refresh time for koji's repo iirc) 18:38:41 and icing on the cake 18:38:58 this cron publishes a fedmsg message announcing what changes in the databases :) 18:39:02 example message: https://apps.stg.fedoraproject.org/datagrepper/id?id=2015-513db0b1-e190-414c-9f21-ba69e97a73cb&is_raw=true&size=extra-large 18:39:07 (all thanks to threebean awesomness) 18:39:27 so fedora-packages can do smart cache invalidation upon seeing these messages 18:39:45 (no changes in F23: keep the old info, changes in rawhide: update) 18:40:13 threebean: awesome, I had not seen mdapi was plugged in already :) 18:40:27 * nirik thinks everyone clicked on that. waiting for answer. ;) 18:40:45 * dotEast2015 :) 18:42:56 I think we covered most of it 18:42:59 it's all in python3 18:43:11 cool. I think this is something that we will find more uses for as we think of them over time. :) 18:43:13 uses aiohttp which is a small web framework on the top of asyncio 18:43:14 could be quite handy 18:43:33 yes, I think we can make use of it :) 18:44:02 I wonder... was looking at repo2json eariler... If we couldn't do this for our rhel repos too. Might be too much information tho... dunno. 18:44:39 nirik: yeah, I'd love to, maybe we could ask 18:45:39 sure, just a thought. 18:45:54 ok, any other questions for pingou ? 18:46:17 oh and finally we deployed it as systemd service using the web-server in aiohttp 18:46:21 w/o proxy in front 18:46:26 we'll see how that goes 18:46:39 yep. always easy to adjust as we go. 18:46:53 pingou +1 :) 18:46:55 thanks pingou! 18:47:00 #topic Open Floor 18:47:03 welcome :) 18:47:13 anyone have anything for open floor? questions, comments, favorate type of coffee? 18:47:22 nirik, so I though I can talk here before replying to the list. 18:47:22 earl-grey? 18:47:33 * smdeep prefers Arabic coffee 18:47:43 hot, black, and plentiful 18:47:44 Darjeeling tea 18:47:50 reminder: we will be having a apprentice work day next wed in #fedora-admin... come if you can and we will try and help onramp folks and get them working on fun things. 18:47:58 Green is my latest passion for tea 18:48:12 nirik, Yes, we need mostly add new new images, and then run instances for short life time, for testing or writing more test cases. 18:48:14 Sure nirik 18:48:22 nirik, how to go ahead for this? 18:48:55 kushal: well, how many folks are we talking about? will they change much? or just a constant group? 18:49:19 if its changing often I would like to try and get the openid stuff in place. 18:49:31 nirik, for starting around 4 people, (they will not change much), but in future may get more people. 18:49:53 nirik, not changing often. 18:50:15 we could just hard code those in for now... if you can file a ticket with the people's login names? they will need fas accounts with their ssh keys in there so we can upload them to openstack 18:50:28 and should we just use the existing cloud-sig tenant? that would be easiest. 18:50:37 nirik, Okay, sounds good to me. 18:50:49 nirik, what is the amount of ram/cpu/instance for that tenant? 18:51:00 not sure off hand, can look. 18:51:13 nirik, you can tell me after meeting, thanks :) 18:51:20 nirik, this is good enough to start with. 18:51:43 nirik, btw, I will create a screencast about how to use the cloud, I hope that is okay? 18:51:56 sure. 18:52:05 yeah, we can also easily increase things if they hit limits. 18:52:16 nirik, cool 18:52:17 I wouldn't expect them to if it's just short term testing 18:52:24 nirik, I also do not. 18:52:52 * nirik nods. 18:52:57 ok, anything else for open floor? 18:53:03 or shall we call it a meeting? 18:53:11 call it 18:53:19 * dotEast2015 :) 18:53:23 * smooge gets his requesite 4 lines in a meeting 18:53:32 thanks for organizing nirik 18:53:47 no problem. Thanks for coming everyone! 18:53:50 #endmeeting