14:01:43 <smooge> #startmeeting Infrastructure (2018-07-26)
14:01:43 <zodbot> Meeting started Thu Jul 26 14:01:43 2018 UTC.
14:01:43 <zodbot> This meeting is logged and archived in a public location.
14:01:43 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:43 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:43 <zodbot> The meeting name has been set to 'infrastructure_(2018-07-26)'
14:01:44 <smooge> #meetingname infrastructure
14:01:44 <zodbot> The meeting name has been set to 'infrastructure'
14:01:44 <smooge> #topic aloha
14:01:44 <smooge> #chair nirik pingou puiterwijk relrod smooge tflink threebean
14:01:44 <zodbot> Current chairs: nirik pingou puiterwijk relrod smooge tflink threebean
14:01:48 <pingou> o/
14:01:55 <clime> hello!
14:01:56 <nirik> good morning everyone.
14:01:57 <relrod> morning
14:01:59 <queue-tip> hello
14:02:01 <smooge> hello all
14:02:02 <clime> .hello2
14:02:03 <zodbot> clime: clime 'clime' <clime@redhat.com>
14:02:09 <puiterwijk> hi
14:02:32 <cverna> hello
14:02:33 <sapo> morning
14:02:38 <vgolwala> .hello2
14:02:39 <zodbot> vgolwala: vgolwala 'Vismay Golwala' <vgolwala@redhat.com>
14:02:59 <smooge> #topic New folks introductions
14:02:59 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
14:03:07 <smooge> hello are there any new people this week?
14:03:38 <bowlofeggs> .hello2
14:03:40 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <rbarlow@redhat.com>
14:04:08 <smooge> #topic announcements and information
14:04:08 <smooge> #info smooge is on PTO 2018-08-02->2018-08-07 (need someone to run meeting next week)
14:04:08 <smooge> #info tflink is on extended PTO
14:04:08 <smooge> #info many are unavailable during FLOCK
14:04:08 <smooge> #info FLOCK in Dresden is 2018-08-08->2018-08-13?
14:04:09 <smooge> #info visit to PHX2 will be happening 2018-08-15->2018-08-18
14:04:21 <smooge> Any other announcements from this week?
14:04:49 * nirik can't think of any off hand.
14:04:59 <smooge> #info bodhi is at 100% test coverage of code (bowlofeggs)
14:05:25 <nirik> #info almost all the infra-sig FTBFS are fixed.
14:05:41 <smooge> yay.. would hate for that to be removed
14:05:46 <nirik> #info pkgdb is finally fully off
14:06:26 <smooge> another good one.
14:06:35 <smooge> ok time to move on
14:06:39 <smooge> #topic flock 2018 - dresden - kevin
14:06:39 <smooge> #info who can make the infrafixfest workshop?
14:06:39 <smooge> #info who can make the infra plan and hackfest?
14:07:17 <smooge> and I skipped oncall.. will do that next
14:07:23 <abompard> .hello2
14:07:24 <zodbot> abompard: abompard 'Aurelien Bompard' <aurelien@bompard.org>
14:07:27 <cverna> #link flock schedule is out https://flock2018.sched.com/
14:07:37 <smooge> thanks cverna
14:07:45 <smooge> I was looking for that
14:07:54 <cverna> :)
14:07:56 <nirik> yeah, some parts of the schedule are unfortunate for me... but oh well.
14:08:06 <bowlofeggs> is that the planning and hacking and hacking and planning?
14:08:09 <smooge> you are in two places at the same time
14:08:13 <bowlofeggs> if so, i can make that
14:08:28 <bowlofeggs> oh yeah
14:08:31 <smooge> or that you were scheduled at the same time as every other infra persons talks
14:08:49 <bowlofeggs> yeah i can make both
14:09:17 <smooge> so everyone, please add your talks to the meeting next week so people can be aware and coordinate any "I need to be theres"
14:09:21 * nirik looks, they moved things around from the last time I looked
14:09:48 <cverna> I have the container workshop during the infra workshop, I ll try to jungle between both
14:09:55 <bowlofeggs> #info bowlofeggs and puiterwijk are doing a talk on saturday at 11:20 about infra and openshift
14:10:42 <nirik> the planning thing is before the fixfest so at least we can plan some things to fix. ;)
14:12:30 <smooge> ok
14:12:43 <smooge> #topic Oncall
14:12:43 <smooge> #info Kevin? is on call from 2018-07-26->2018-08-02
14:12:43 <smooge> #info ??? is on call from 2018-08-02 ->2018-08-07
14:12:43 <smooge> #Info Smooge is on call from 2018-08-07->2018-08-14
14:12:44 <smooge> #info ??? is on call from 2018-08-15->2018-08-23
14:12:45 <smooge> #info Summary of last week: (from Smooge)
14:13:08 <puiterwijk> I can take the 08-02 - 08-07 window
14:13:26 <nirik> I can take over after the meeting.
14:13:34 <pingou> I can take from 15 to 23rd
14:13:50 <pingou> but the 15th is a day off in France, so I may not be much around then
14:14:09 <puiterwijk> Maybe bowlofeggs then? I think he was also strill trying to get a lot
14:14:11 <puiterwijk> slot
14:14:19 <pingou> (if folks are happy with this I'm happy to take that slot)
14:14:29 <smooge> I have put you down
14:14:33 <puiterwijk> okay
14:14:53 <pingou> thanks
14:15:07 <smooge> I will be on a plane on the 15th to get to colo
14:15:27 <pingou> #info most of our FTBFS have been fixed
14:15:28 <nirik> I can take it for the 15th if desired.
14:15:40 <nirik> or people can just file tickets and not bother us. ;)
14:16:15 <smooge> OK so I have updated the gobby with those dates
14:16:39 <pingou> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&email1=infra-sig&emailassigned_to1=1&emailcc1=1&emailtype1=substring&list_id=9160947&query_format=advanced
14:16:45 <pingou> the infra-sig tickets
14:16:45 <smooge> I will not be able to run the meeting next week so it should be good for whoever is to just remove the top line and fill in the ??? on the bottom
14:17:13 <smooge> This week's oncall has been fairly quiet. A couple of people directly pinged other people I needed to remind not to do so
14:17:21 <nirik> pingou: thanks for dealing with a bunch of those...
14:17:34 <pingou> nirik: thanks for dealing with the others :)
14:17:36 <smooge> There has also been the freenode spam crap
14:17:39 <smooge> That is all on that
14:17:46 <nirik> smooge: yeah, unfortunately. ;(
14:18:01 <smooge> OK is it ok to move onto the next topic? cverna are you around for pPC?
14:18:13 <cverna> yes
14:18:28 <cverna> but I think we went through it last week
14:18:33 <smooge> ah ok
14:18:35 <bowlofeggs> does anyone know where i can read blog posts by freenode staff?
14:18:37 <smooge> I will remove from the meeting
14:18:44 <cverna> I forgot to remove it from gobby :)
14:18:52 <pingou> https://freenode.net/news/spambot-attack  bowlofeggs
14:18:55 <bowlofeggs> hahaha
14:19:01 <cverna> I still need to fill an infra ticket for that will do after the meeting
14:19:18 <smooge> #topic Tickets discussion
14:19:18 <smooge> #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
14:19:45 <smooge> Once again we have zarro tickets so we can go home
14:19:59 <cverna> \o
14:20:05 <nirik> ha.
14:20:15 <nirik> If there's any tickets people want to call out...
14:20:23 <nirik> feel free to add meeting to them.
14:20:26 <smooge> does nayone have a ticket to call out?
14:20:45 <nirik> I did fight us back under 100...
14:21:05 <puiterwijk> RFR for repoSpanner is filed, look forward to that going live soon.
14:21:19 <puiterwijk> (that's it from me)
14:21:23 <nirik> If everyone could look at any tickets assigned to them and see if they can finish them up that would be great:
14:21:32 <nirik> https://pagure.io/fedora-infrastructure/issues?status=Open&assignee=<your-fas-name-here>
14:21:47 <smooge> #topic Apprentice Open office minutes
14:21:47 <smooge> #info A time where apprentices may ask for help or look at problems.
14:21:57 <pingou> nirik: we should plan some time to discuss the loopabull situation with Mohan
14:22:18 <bowlofeggs> nirik is fighting the good fight
14:22:20 <smooge> which brings us to that.. if there are tickets which you also think someone can review as an apprentice also bring the up
14:22:24 <bowlofeggs> nirik: come get bodhi to under 100 too!
14:22:49 <puiterwijk> pingou: "loopabull situation" "Mohan"?
14:23:50 <pingou> puiterwijk: we wanted to use loopabull as a way to run some simple scripts acting on fedmsg message
14:23:53 <nirik> we should definitely start trying to use loopabull more...
14:24:10 <pingou> and the current loopabull is really tight into releng and is apparently somewhat used by releng
14:24:15 <smooge> I would like to ask that if we do so.. someone become an expert on it first
14:24:25 <smooge> s/someone/several people/
14:24:33 <puiterwijk> smooge: do my clones count?
14:24:33 <pingou> so when I looked at trying to revamp it some, I got stuck because I didn't want to break releng's setup
14:24:47 <smooge> puiterwijk, no because only one of them get to the keyboard at a time
14:24:51 <nirik> ah, so we need a more generic version...
14:24:52 <pingou> smooge: I have a fine understanding of it
14:24:55 <puiterwijk> pingou: you shouldn't need to revamp it I don't htink? I am reasonably sure me and Adam set it up in a reusable way....
14:25:03 <puiterwijk> nirik: I don't think so...
14:25:10 <pingou> puiterwijk: the git repo it uses it all but clear :)
14:25:22 <puiterwijk> pingou: Pretty sure we wrote docs on that one
14:25:35 <pingou> https://pagure.io/releng-automation
14:25:35 <puiterwijk> But let's discuss that some other time, I guess..
14:26:00 <pingou> which was my original asking :)
14:26:20 <puiterwijk> That is not really the repo with the loopabull stuff I believe. But okay
14:26:50 <pingou> it's where loopabull looks for its playbook to run
14:26:53 <smooge> #topic Open Floor
14:27:00 <smooge> since we seem to be there already
14:27:05 <pingou> which prooves my point, it's not really clear :)
14:27:16 <pingou> sorry smooge :s
14:27:56 <pingou> not sure when would be a good time to discuss this, any suggestion?
14:28:19 <pingou> should I just try to pick a time in everyone's calendar?
14:28:57 <nirik> pingou: sure, sounds fine to me.
14:29:01 <smooge> sounds good
14:29:10 <pingou> everyone being: puiterwijk Mohan nirik, I and anyone else that would be interested?
14:29:39 <nirik> sure.
14:29:45 <nirik> question though:
14:29:46 <smooge> I would stick with those 4 and anyone else can join in if they can make it but not important otherwise
14:30:09 <nirik> will loopabull still be happy with the new messaging system? I'd guess so?
14:30:24 <pingou> should be
14:30:34 <pingou> short term with the bridge
14:30:59 <pingou> long term it may require some changes, but iirc it was designed to support different notification systems
14:31:07 <pingou> so shouldn't be too hard to adjust it
14:31:09 <bowlofeggs> yeah i think all things should be compatible with the new messaging iiuc
14:31:31 <aikidouke> i came in late, dont mean to interrupt, but have 1 thing for open floor/tickets when we're ready
14:31:34 <nirik> fair enough
14:31:38 * pingou sees a spot where everyone is availabe: same time tomorrow?
14:32:19 <puiterwijk> pingou: I'm going to ask please not tomorrow...
14:32:30 * puiterwijk can't promise he'll be around tomorrow at all
14:32:48 <pingou> after that it'll be on Wed next week, same time
14:33:08 <puiterwijk> That should work for me
14:33:10 <aikidouke> an Availabe sounds like some kind of maritime calendar navigation tool :)
14:33:19 <nirik> same time as this meeting? thats early for me, but I can read back too...
14:33:39 <pingou> nirik: can you make 1/2 later than this meeting?
14:33:49 <pingou> so starting right now :)
14:34:06 <puiterwijk> .localtime kevin
14:34:07 <nirik> I guess
14:34:07 <zodbot> puiterwijk: The current local time of "kevin" is: "07:34" (timezone: US/Pacific)
14:34:11 <puiterwijk> pingou: ^
14:34:14 <pingou> yup
14:34:57 <puiterwijk> I think that about 1.5 or 2 hours later might be more hospitable to Kevin?
14:35:14 <pingou> it's then less to me :(
14:35:22 <smooge> especially since nirik is usually up to midnight working
14:35:33 <pingou> anyway, let's take this outside of this meeting and let aikidouke brings their subject :)
14:35:46 <smooge> aikidouke, your turn
14:35:49 <aikidouke> ty :0
14:36:00 <aikidouke> so .ticket 5290
14:36:13 <puiterwijk> .ticket 5290
14:36:15 <zodbot> puiterwijk: Issue #5290: Generate infrastructure map - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/5290
14:36:31 <aikidouke> I always get that wrong - sapo has been working on some data
14:36:54 <sapo> That's true.
14:36:58 <aikidouke> and I've been trying to look up some library that might make a good visualization
14:37:20 <aikidouke> but I havent found something yet
14:37:48 <aikidouke> I looked at apps.fp.o and it's js - which I think is something we want to avoid if possible?
14:38:10 <aikidouke> the request is asking for something static and not an app
14:38:47 <sapo> Problem is, that something static needs more maintenance.
14:38:55 <aikidouke> does anyone have any suggestions for a python3 library that has the ability to make a nice visual?
14:39:48 <aikidouke> and of course is packaged or is easy to package for fedora
14:40:16 * nirik doesn't know off hand. ;( you would think there would be something...
14:40:38 * aikidouke thinks im just not hitting the right search term
14:40:42 <cverna> if you want a nice visual, I think that will need javascript
14:41:10 <smooge> well I think the issue is that mizdebsk needs to define what visual kind of map they were wanting
14:41:25 <aikidouke> maybe cverna - Im sure I have seen python libs that will generate js
14:41:32 <smooge> everything else is throwing spaghetti at the walk and wondering if it is art
14:41:37 <cverna> we could start with just doing a simple html page with jinja2
14:41:38 <pingou> pygal?
14:41:39 <aikidouke> smooge: that is the point I coming too as well
14:41:42 <nirik> I think the idea was just something that could help new folks know what all machines/areas/datacenters we have...
14:42:03 <aikidouke> thanks pingou. will check that out
14:42:11 <cverna> I think html tables could do
14:42:25 <sapo> And also, can anyone give me a hint to a config or output file that I can scan to collect active server IP addresses?
14:42:26 <pingou> ascii drawings ? :)
14:42:49 <sapo> What I can collect so far in my script are:
14:43:13 <sapo> 1. Hostnames by function / function groups
14:43:26 <aikidouke> i also like the way you are thinking. I've done some stuff for myself with lua, but it's essentially the same as jinja templates
14:43:27 <sapo> 2. Virtual machines by virtual hosts
14:43:30 <smooge> well most of the ips should be set in the yaml inventory/hosts files
14:43:46 <smooge> if they aren't that should be a bug for that host
14:44:03 <sapo> Thanks smooge I'll look into it.
14:44:57 <aikidouke> can we start by getting some input on the requirements from mizdebsk before we put spaghetti all over the proverbial art museum?
14:45:16 <sapo> So in the first round I'll update my script to build a xml that collects hosts, it's functions, IPs and the hosts they running on.
14:45:52 <cverna> sapo: can you do json :P
14:45:53 <sapo> If mizdebsk is still around...
14:46:11 <sapo> Yes, I can do that too.
14:46:26 <nirik> oh, that reminds me. I was going to look at replacing our networkmanager/network config handling stuff with the linux-system-roles one... make it more standard and get a lot more features, but we will see how possible that is.
14:46:27 <sapo> Just xml seemed to be more logic in this case
14:46:46 <sapo> It all depends on the visualization.
14:46:58 <sapo> What is the easier one to visualize?
14:47:15 <aikidouke> sapo - have you logged into batcave and looked at the infra-hosts directory? that might help (if it is current?)
14:47:29 <smooge> no no it isnt
14:47:36 <aikidouke> oh :(
14:47:49 <smooge> unless someone did some fixing
14:47:57 <sapo> What I currently scan are:
14:48:10 <sapo> 1. virthost-lists.out
14:48:17 <sapo> 2. inventory
14:48:35 <sapo> From Nagios and Ansible
14:49:04 <nirik> yeah, infra-hosts is old/dead... we pulled all that info into ansible.
14:49:16 <sapo> Good to know.
14:49:17 <aikidouke> anyway - can we decide to change the ticket status to get more input on the visual from mizdebsk OR ??? have a workday where we prototype a few visualizations?
14:49:51 <aikidouke> OR something else?
14:50:06 <smooge> I think the second.
14:50:07 <nirik> I'd say yeah, ask questions in ticket.
14:50:13 <smooge> or what nirik says
14:50:38 <smooge> and then schedule a workday in 3 weeks?
14:50:42 <sapo> Meanwhile I'll keep digging for useful data to be collected.
14:50:47 <aikidouke> OK. I'll see if we can get more info on the ticket
14:50:53 <smooge> I would say 2 but flock will be then
14:51:01 <cverna> aikidouke: sapo :as you are both apprentice try to see what visualizations would be useful for you and that should be useful for all :)
14:51:08 <aikidouke> smooge: good idea.
14:51:14 <aikidouke> cverna: sage advice
14:52:27 <cverna> and I would not go to crazy at first
14:52:27 <cverna> let's do something simple first, it can always be improve, enhanced after :)
14:52:27 <smooge> ok I think we are looking at another meeting in 8 so I would like to close this out and allow coffee refill times
14:52:27 <aikidouke> I wont be at flock :( but that might be a good hack session if any other apprentices will be there?
14:52:27 <aikidouke> cverna: crazy? maybe too late for me... ;)
14:52:27 <smooge> are there any other issues for the open floor and can eveyrone move the party over to #fedora-admin?
14:52:31 <cverna> aikidouke: :D
14:52:47 <aikidouke> if anyone is interested in libravatar and working with clime
14:53:01 <smooge> Thank you all for coming this week. I will see you again in 3 weeks. Next weeks meeting will be chaired by someone else and the week after that is FLOCK so no meeting
14:53:01 <aikidouke> there is a meeting this sunday (I cant make it)
14:54:17 <clime> yup, that would be cool
14:54:17 <smooge> clime what time on Sunday ?
14:54:17 <aikidouke> libravatar is dying in 6 weeks
14:54:18 <clime> i think 7pm utc
14:54:18 <smooge> #info Meeting on libravatar replacement at 1900 UTC on Sunday
14:54:18 <smooge> ok and with that ...
14:54:18 <nirik> what all is left to do on it?
14:54:18 <aikidouke> ty smooge !
14:54:18 <clime> * 2018-07-29, 7pm UTC
14:54:18 <pingou> clime: irc?
14:54:23 <clime> * channel #libravatar at irc.freenode.net
14:54:28 <pingou> cool, thanks
14:54:45 <clime> also for completeness: * Preparation / Agenda: https://pad.riseup.net/p/libravatar-future-irc
14:54:49 <smooge> ok thanks
14:54:55 <clime> thx for mentioning it
14:55:04 <clime> aikidouke++
14:55:10 <smooge> #info meeting is channel #libravatar at irc.freenode.net 2018-07-29, 7pm UTC
14:55:18 <aikidouke> clime++ glad you are working on it
14:55:21 <smooge> #info agenda  Preparation / Agenda: https://pad.riseup.net/p/libravatar-future-irc
14:55:25 <smooge> ok good night
14:55:29 <smooge> #endmeeting