15:11:07 <smooge> #startmeeting Infrastructure (2018-12-06)
15:11:07 <zodbot> Meeting started Thu Dec  6 15:11:07 2018 UTC.
15:11:07 <zodbot> This meeting is logged and archived in a public location.
15:11:07 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:11:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:11:07 <zodbot> The meeting name has been set to 'infrastructure_(2018-12-06)'
15:11:07 <smooge> #meetingname infrastructure
15:11:07 <smooge> #topic aloha
15:11:07 <zodbot> The meeting name has been set to 'infrastructure'
15:11:07 <smooge> #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny
15:11:07 <zodbot> Current chairs: cverna mkonecny nirik pingou puiterwijk relrod smooge tflink threebean
15:11:10 <mkonecny> smooge: I even forced you to change this in calendar
15:11:12 <abompard> I'll be here in an hour so it doesn't matter to me
15:11:21 <nirik> morning
15:11:29 <cverna> o/
15:11:30 <mkonecny> evening
15:11:32 <abompard> morning / afternoon people!
15:12:12 <relrod> morning
15:12:27 <smooge> hello. my computer calendar told me this but my cut and paste told me 1600
15:12:39 <smooge> my apologies everyone
15:13:03 <smooge> #topic New folks introductions
15:13:03 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
15:13:03 <smooge> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
15:13:08 <aikidouke> haloo
15:13:17 <smooge> hi aikidouke how are things?
15:13:50 <aikidouke> a bit pear shaped, but I am upright and so on. Happy Thursday to all
15:14:19 <cverna> aikidouke: o/
15:14:31 <smooge> sorry to hear about the pear
15:14:48 <aikidouke> :) salut cverna
15:14:58 <aikidouke> all will be well - ty smooge
15:15:18 <smooge> #topic announcements and information
15:15:18 <smooge> #info tflink is on extended PTO
15:15:18 <smooge> #info nirik in PTO 2018-12-2? -> 2018-12-27
15:15:18 <smooge> #info smooge is on PTO 2018-12-27 -> 2019-01-07
15:15:19 <smooge> #info there will be no infrastructure meeting 2018-12-20/2018-12-27
15:15:20 <smooge> #info devconf is happening from 2019-01-27 -> 2019-01-31?
15:15:30 <cverna> aikidouke: :D salut
15:16:18 * nirik will update the vacation calendar and send his schedule to the list once I sort it out
15:16:36 <nirik> but I should be around all the time for emergencies/etc
15:18:21 <mkonecny> #info mkonecny is on PTO 2018-12-18 -> 2019-01-07
15:18:36 <bowlofeggs> .hello2
15:18:37 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <rbarlow@redhat.com>
15:18:43 <bowlofeggs> sorry i'm late - was talking to a roofer
15:19:06 <smooge> mkonecny, I have added that for future meetings
15:19:07 <nirik> #info newcloud nears completion. Just need to finish setting up access to the dashboard and add aarch64 support (when all the parts are in place for that)
15:19:18 <smooge> yay
15:19:24 <bowlofeggs> #info bodhi 3.11.3 released and deployed
15:19:28 <nirik> bowlofeggs: does that make you the roofy?
15:19:38 <bowlofeggs> nirik: yes, yes it does!
15:19:38 <nirik> roofie
15:19:51 <smooge> just say no
15:20:11 <mkonecny> smooge: thanks
15:22:38 <smooge> #topic Oncall
15:22:38 <smooge> #info smooge is on call from 2018-11-29->2018-12-06
15:22:38 <smooge> #info puiterwijk is on call from 2018-12-06->2018-12-13 (smooge has 2018-12-07)
15:22:38 <smooge> #info bowlofeggs is on call from 2018-12-13->2018-12-20
15:22:38 <smooge> #info smooge is on call from 2018-12-20->2018-12-27
15:22:40 <smooge> #info ??? is on call from 2018-12-27 -> 2019-01-03
15:22:41 <smooge> #info ??? is on call from 2019-01-03 -> 2019-01-10
15:22:43 <smooge> #info smooge is on call from 2019-01-10 -> 2019-01-17
15:22:45 <smooge> #info Summary of last week: (from smooge )
15:23:05 <nirik> I can do one or both of the over the holidays ones...
15:23:10 <relrod> I will take 3-10
15:23:12 <smooge> OK this week has been rather noisy today. copr is getting rebuilt and the current f29 sudo is noisy and problematic. I will be working with clime on this
15:23:37 <smooge> nirik, can you do the 27 -> 03 ?
15:24:19 * smooge misses on-call bonus pay... but then again I don't miss the 15 minutes to answer a pager any hour
15:24:37 <nirik> sure
15:25:46 <smooge> #topic Tickets discussion
15:25:46 <smooge> #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
15:26:14 <smooge> we are at 105 tickets.. we need to close out 20 tickets
15:26:25 <nirik> I wish it worked that way. ;)
15:26:35 <smooge> I am thinking we should go with the F27 bugzilla rule
15:26:46 <nirik> sorry, your ticket has been chosen by lottery to be closed, too bad.
15:26:59 <smooge> if it has been open for 2 releases..
15:27:27 <nirik> anyhow, I should be able to go back on tickets after this openstack work is done....
15:27:59 <nirik> I would ask everyone who is assigned tickets to look them over, they might already be done! :)
15:28:27 <smooge> if not you will be docked 4 karma by next meeting
15:29:04 * cverna checks if he has any tickets assigned to him
15:29:17 <smooge> anything else on tickets?
15:29:37 <smooge> #topic Apprentice Open office minutes
15:29:37 <smooge> #info A time where apprentices may ask for help or look at problems.
15:29:53 <smooge> aikidouke, anything on your list?
15:30:20 <aikidouke> :) usually - but waiting to give others a chance
15:31:19 <smooge> I would say you are it this week
15:31:24 <aikidouke> I guess if nobody else has anything. I've noticed that zod's scripts do have some tests...maybe He with beans of three wrote them
15:31:25 <nirik> there's one trivial ticket out there... would be nice to learn PR's on
15:31:51 <aikidouke> what is our general feeling on test frameworks - pytest all the things?
15:32:35 <puiterwijk> aikidouke: per-app decision usually
15:32:57 <cverna> most of the applications are using nose and unittest, but pytest is fine too
15:33:14 <bowlofeggs> nose is kinda dead iirc
15:33:14 <aikidouke> thanks gentleman
15:33:24 <bowlofeggs> pytest is the one true test framework
15:33:36 <puiterwijk> python "import unittest" for the win
15:33:59 <abompard> bowlofeggs: +1 on pytest
15:34:11 <aikidouke> puiterwijk - what factors do you look at when deciding? Im just learning TDD so - thats probably a deeper topic than a 1 hr meeting
15:34:32 <puiterwijk> aikidouke: 1. whatever the system currently uses, 2. whatever I can think of at the time.
15:34:46 * aikidouke nods
15:34:47 <puiterwijk> But typically not py.test, iirc.
15:34:54 <aikidouke> makes sense to me
15:35:00 <puiterwijk> I really dislike pytest, but that's me
15:35:25 <aikidouke> nirik did you want to discuss that ticket?
15:36:03 <nirik> the trivial one?
15:36:05 <bowlofeggs> i love pytest, on the other hand :)
15:36:30 <aikidouke> nirik: yes - before I start a test-framework-war-for-the-ages
15:36:33 <aikidouke> :)
15:36:35 <nirik> https://pagure.io/fedora-infrastructure/issue/7378
15:36:37 <mkonecny> I think it's better if you can just use the unittest itself, but the pytest is fine
15:36:39 <nirik> not much to say
15:38:41 <aikidouke> does an apprentice have the ability to assign issues to themselves? or do I? I think I'm still a member of main...but I wouldnt swear to it.
15:39:46 <smooge> .group sysadmin-main
15:39:47 <zodbot> smooge: sysadmin-main: Fedora Main Sysadmin Group
15:39:55 <smooge> .members sysadmin-main
15:39:56 <zodbot> smooge: Members of sysadmin-main: @ausil codeblock jstanley @kevin maxamillion mizdebsk pbrobinson pingou puiterwijk ralph @smooge tflink
15:40:18 <nirik> no apprentices don't have perms, but we can assign for you, or you can just note in ticket you are doing it
15:40:20 <maxamillion> o/
15:40:48 <aikidouke> yeah - guess not then :) maybe was just part of badges group for awhile
15:40:55 <aikidouke> .group badges
15:40:56 <zodbot> aikidouke: There is no group "badges".
15:41:04 <smooge> .members sysadmin-badges
15:41:05 <zodbot> smooge: Members of sysadmin-badges: adimania aikidouke asamalik bex churchyard codeblock cydrobolt jflory7 mleonova +nb @puiterwijk +sayanchowdhury
15:41:26 <aikidouke> there you go...ty smooge.
15:41:32 <aikidouke> ok thanks nirik
15:41:54 <puiterwijk> Hum... I'm going to try to get out of that group. Who wants admin on that group?
15:42:00 <aikidouke> anyone else got dibs on nirik's issue?
15:42:09 <smooge> puiterwijk, give it to nb I think
15:42:13 <puiterwijk> ok
15:42:20 <nirik> I almost just did it, but it's a good first issue. ;)
15:42:36 <smooge> you are it aikidouke .. go forth and commit
15:42:49 <aikidouke> puiterwijk: I haven't done anything with badges in ages, not that I wouldn't if needed, but if you want to keep it clean, it's fine to remove me
15:42:59 <aikidouke> thank you sir smooge
15:43:16 <smooge> #topic Sysadmin group cleaning.
15:43:20 * aikidouke takes up the lance of committing, the shield of git
15:43:57 <smooge> So speaking of groups.. and such. I was thinking that next spring we look at who is in all the sysadmin groups, see who still works on the things in that group and remove the rest
15:44:27 <nirik> sure, +1
15:44:40 <smooge> but nothing 'soon' after devconf
15:44:54 <smooge> cool
15:45:46 <smooge> ok with that
15:45:50 <smooge> #topic Open Floor
15:45:51 <mkonecny> smooge: devconf is in winter
15:47:19 <smooge> mkonecny, I was setting expectations. I have said 'next <season>' and people say 'what next week? HOW CAN YOU??'
15:47:56 <smooge> so giving them a firm date to not start planning for it seemed clearer
15:47:56 <mkonecny> Next week is OK :-)
15:49:42 <cverna> Do we want to do a VFAD or apprentice day before the Christmas break ?
15:50:02 <cverna> We could tackle the tickets list :)
15:50:40 <smooge> cverna, I don't know
15:50:56 <nirik> kinda short notice...
15:51:24 <cverna> smooge: me too that's why I was asking :P
15:51:51 <cverna> yes we don't have much time left before the break
15:52:03 * relrod thinks short notice as well. Might perhaps be better after, when people are re-energized?
15:53:16 <cverna> yes that could be after devconf then
15:53:38 <cverna> since devconf will arrive quickly after the break
15:53:41 <smooge> so Feb14th
15:53:45 <nirik> yeah.
15:54:07 * nirik may be going to phx2 after devconf too...
15:54:11 <aikidouke> we shoot arrows of love at our issue list?
15:54:41 <smooge> I expect the earliest would be Feb 19th when everyone would be available
15:55:43 <cverna> ok sounds good
15:56:04 <smooge> alright
15:56:18 <nirik> Oh, I had one thing to mention real quick...
15:57:02 <nirik> For openshift apps: if we want to use auto-scaling (perhaps we don't), we need apps to set cpu limits... https://docs.openshift.com/container-platform/3.11/dev_guide/compute_resources.html#dev-cpu-requests
15:57:35 <smooge> do we set them for them or do they do it?
15:58:03 <nirik> well, it needs to be set by someone. I guess we could mass set it on all apps
15:59:01 <nirik> anyhow, I can continue that on list
15:59:42 <smooge> okie dokie
15:59:44 <smooge> I would like to thank the studio audience and our musical guests this week. Please come back next week at 15:00 where puiterwijk and bowlofeggs will sing a medley of tunes.I would like to thank the studio audience and our musical guests this week. Please come back next week at 15:00 where puiterwijk and bowlofeggs will sing a medley of tunes.
16:00:07 <smooge> and I would like to thank C-Z/C-V
16:00:12 <bowlofeggs> those openshift docs are kinda thin about what unit of "cpu" you use
16:00:25 <smooge> #endmeeting