14:00:07 <smooge> #startmeeting Infrastructure (2018-09-20)
14:00:07 <zodbot> Meeting started Thu Sep 20 14:00:07 2018 UTC.
14:00:07 <zodbot> This meeting is logged and archived in a public location.
14:00:07 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:00:07 <zodbot> The meeting name has been set to 'infrastructure_(2018-09-20)'
14:00:07 <smooge> #meetingname infrastructure
14:00:07 <zodbot> The meeting name has been set to 'infrastructure'
14:00:07 <smooge> #topic aloha
14:00:07 <smooge> #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna
14:00:07 <zodbot> Current chairs: cverna nirik pingou puiterwijk relrod smooge tflink threebean
14:00:17 <nirik> morning.
14:00:24 <smooge> good morning
14:00:40 <cverna> good morning all
14:00:41 <mkonecny> evening :-)
14:01:07 <cverna> mkonecny: good afternoon :D
14:01:17 <bowlofeggs> .hello2
14:01:18 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <rbarlow@redhat.com>
14:01:32 <smooge> #topic New folks introductions
14:01:32 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
14:02:44 <smooge> hello anyone new this week?
14:03:04 <nirik> each day is like it's new again! :)
14:04:04 <smooge> #topic announcements and information
14:04:04 <smooge> #info tflink is on extended PTO
14:04:04 <smooge> #info Beta Freeze is in effect. All changes to frozen systems in Infrastructure will require +1
14:04:09 * aikidouke thinks nirik may be using my brain or has a similar model
14:04:14 <smooge> There weren't any other announcements
14:04:24 <nirik> ha.
14:04:45 <nirik> yeah, it's been pretty quiet freeze week
14:05:25 <smooge> #topic Oncall
14:05:25 <smooge> #info Smooge is on call from 2018-09-13->2018-09-20
14:05:25 <smooge> #info Nirik is on call from 2018-09-20->2018-09-27
14:05:26 <smooge> #info ??? is on call from 2018-09-27->2018-10-04
14:05:26 <smooge> #info Summary of last week: (from Smooge)
14:05:31 <bowlofeggs> #info bodhi 3.10.0 is released and deployed to staging - waiting for freeze to end
14:05:42 <smooge> thanks bowlofeggs
14:05:44 <nirik> fall is coming!
14:06:07 <aikidouke> oh yes! ^ and autumn as well
14:06:37 <smooge> The biggest problem was reg-server on sundries went crazy on the weekend
14:06:47 <nirik> oh yeah, we still need to debug that?
14:06:59 <smooge> It needs a newer version installed which will look at multi-arch
14:07:21 <smooge> beyond that it was mostly pings
14:07:28 <cverna> I think we have that in staging
14:07:35 <smooge> I need to have someone to take the week after Nirik and the week afterwords
14:07:43 <cverna> multi-arch reg-server
14:08:12 <smooge> So 2018-10-04 -> 2018-10-11 and 2018-10-11 -> 2018-10-18
14:08:29 <smooge> cverna, I don't know if the rpm was done
14:08:38 <nirik> cverna: oh? I was working on the new rpm, but it wasn't finished.
14:08:40 <puiterwijk> smooge: feel free to give me one of the slots.
14:08:49 <nirik> and puiterwijk was going to look, but he's been busy
14:09:07 <smooge> puiterwijk, 2018-10-04 sound good?
14:09:11 <puiterwijk> smooge: sure
14:09:13 <cverna> nirik: smooge : ok I though relrod did that couple weeks ago but I might be wrong
14:09:19 <cverna> thought*
14:09:41 <smooge> oh foo I got the dates wrong
14:09:52 <smooge> 2018-09-27->2018-10-04
14:10:03 <smooge> does that still work or do you need the next week puiterwijk ?
14:10:13 <puiterwijk> smooge: sure
14:10:45 <smooge> ok thanks
14:10:49 <smooge> I have updated the gobby
14:11:17 <smooge> #topic container registry and Quay.io - cverna
14:11:30 <cverna> I take it over :)
14:12:05 <cverna> So yesterday I has some update from the Red Hat OSBS team and they are preparing to move to Quay.io
14:12:28 <cverna> Multi-arch and OCI support is expected to be available in October
14:12:40 <puiterwijk> cverna: is it open source yet?
14:12:45 <nirik> huh, any chance there will be koji integration? ;)
14:13:03 <cverna> I wanted to get the general feeling about moving Fedora's registry to Quay.io and not running the registry in our Infra
14:13:24 <puiterwijk> cverna: if it's FOSS: let's move ASAP. If not, wait until it is
14:13:40 <x3mboy> .hello2
14:13:41 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com>
14:13:43 <nirik> puiterwijk: +1
14:13:55 <cverna> It is not yet FOSS but as far I as I know docker hub is not FOSS
14:14:11 <cverna> nirik: the koji integration is managed by OSBS
14:14:20 <puiterwijk> cverna: we run https://github.com/docker/distribution
14:14:23 <puiterwijk> Which is FOSS
14:14:25 <nirik> oh, I see, this is the registry... misread
14:14:28 * otaylor notes that regindexer will still be necessary at least in the near-to-medium turn, but should be possible to  adapt to run against quay.io.
14:14:39 <cverna> puiterwijk: with Quay we would not run anything
14:14:51 <cverna> puiterwijk: we would just use Quay.io as a service
14:15:02 <puiterwijk> cverna: sure. But it's still not FOSS. Even for services, we strongly prefer/require FOSS
14:15:24 <smooge> cverna, there has been a lot of pushback from our community and at times the council to keep services we use FOSS
14:15:35 <cverna> Ok that's why I brought up the topic, I wanted to get a general feeling
14:15:41 <smooge> the github usage has been a thorn
14:15:50 <puiterwijk> Right. So the general feeling is: if it's FOSS: YES. If not: wait.
14:15:57 <pingou> note that greenwave/waiverdb is already using quay
14:16:01 <cverna> yes github and docker hub are definitely not FOSS
14:16:22 <puiterwijk> pingou: right. But there's a difference between us grabbing FOSS contents from a non-FOSS registry versus sending all our users there to download the official images
14:16:29 <cverna> the s2i image we use to build silverblue and coreos image is from quay.io too
14:16:32 <pingou> fair
14:16:37 <puiterwijk> cverna: see my note
14:17:50 <cverna> ok then we can stick with our current solution until Quay become FOSS
14:17:54 <nirik> is there plans to opensource quay? I would think so, but haven't seen anything specific
14:18:12 <smooge> I expect it is similar to getting tower opensourced
14:18:16 <puiterwijk> nirik: well, usually that's not shared until the message is "It's FOSS as of today", right?
14:18:34 <cverna> As I understand the quay team is one person
14:18:48 <cverna> so I think getting it FOSS is not priority currently
14:18:49 <nirik> wow, really?
14:19:10 <cverna> they are looking to expand but yeah
14:19:16 <bowlofeggs> note also that our registry hasn't required very much maintenance/upkeep
14:19:19 <pingou> it will end up FOSS
14:19:23 <pingou> but as usual no ETA
14:19:24 <bowlofeggs> so it's not costing us too much
14:19:37 <cverna> bowlofeggs: our user experience to the registry is horrible
14:19:48 <cverna> https://registry.stg.fedoraproject.org/repo/fedora/tags
14:20:03 <cverna> you can't even access which tags are available
14:20:28 <nirik> the new reg fixes that.
14:20:36 <nirik> but yeah, it's been a pain
14:20:40 <bowlofeggs> fair
14:20:55 <bowlofeggs> i was thinking more about the behind the scenes thing than the UI
14:21:09 * bowlofeggs hasn't ever touched the UI thing
14:21:33 <cverna> ok, so anyhow that was my head ups on this topic :)
14:22:18 <nirik> perhaps we also want to think of uploading to quay.io even if we don't advertise it as the main place?
14:22:30 <nirik> or is that too much work?
14:22:52 <cverna> we could do for base images
14:23:07 <cverna> like we are doing on dockerhub
14:23:40 <bowlofeggs> i'd be +1 to also uploading to quay, since that's similar to what we do with dockerhub
14:23:50 <nirik> yeah... then if we switch we are already ready and people won't see nothing there in the mean time
14:24:06 <bowlofeggs> it would also allow us to claim namespace
14:24:14 <nirik> yeah
14:24:40 <cverna> OK I ll open a releng ticket for that, and will look at what is needed
14:25:17 <bowlofeggs> i could expand bodhi's container support to allow publishing to a list of registries
14:25:27 <bowlofeggs> it currently wants to publish to exactly one
14:25:34 <bowlofeggs> unless we only care about the base image for now
14:25:45 <bowlofeggs> i also have like 0 time to work on that :(
14:25:51 <nirik> might be nice, but when one was down would that fail the push?
14:26:01 <bowlofeggs> nirik: can of worms!
14:26:02 <bowlofeggs> hahah
14:26:05 <nirik> yeah.
14:26:10 <smooge> bowlofeggs, bodhi is completely covered with tests so its done right? so you should have all the time in the world
14:26:16 <bowlofeggs> yeah i dunno what would be the right behavior there
14:26:23 <bowlofeggs> smooge: lol
14:26:28 <cverna> smooge: :D
14:26:34 <bowlofeggs> smooge: have you ever considered doing stand up?
14:26:48 <puiterwijk> bowlofeggs: let's do at least one a day!
14:26:55 <nirik> from a workflow standpoint it seems like uploading to ours and then having something sync from there to other places would make sense.
14:26:56 <bowlofeggs> hahaha
14:27:03 <bowlofeggs> nirik: yeah that's true
14:27:10 <bowlofeggs> that would be simpler
14:27:26 <bowlofeggs> skopeo on a cron
14:27:46 <bowlofeggs> we could just let jcline sit around all day with skopeo and run it by hand
14:27:58 <jcline> Sounds good to me
14:28:39 * nirik still thinks skopeo sounds like a 70's detective show
14:29:00 <cverna> It also depends how the registries work, for example dockerhub process requires us to push the images in a git repo :S
14:29:14 <bowlofeggs> cverna: yeah that one is super weird
14:29:17 <nirik> yeah, thats not ideal. ;(
14:29:27 <cverna> I have opened https://pagure.io/releng/issue/7828
14:29:27 * nirik wonders if we could push a redirect. ;)
14:29:36 <puiterwijk> nirik: nope.
14:29:43 <nirik> bummer
14:29:51 <smooge> ok do we have much more on this topic at the moment?
14:30:07 <cverna> Not on my side :) thanks all for the feedbacks
14:30:24 <nirik> thanks for bringing it up cverna. ;)
14:30:25 <smooge> Scopeo.. A Martin Quinn production!
14:30:49 <smooge> #topic Tickets discussion
14:30:50 <smooge> #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
14:31:09 <nirik> not sure I updated this this week.
14:31:19 <nirik> oh, perhaps I did.
14:31:28 <smooge> I thought those were last wekes
14:31:42 <nirik> yeah, did we get to them last week tho?
14:32:01 <smooge> yep
14:32:08 <smooge> threebean did a long talk on it
14:32:09 <nirik> ok, then moving on is fine. ;)
14:32:23 <smooge> so what I would like to do is ask if we could add another item
14:32:37 <smooge> should we move towards no unassigned tickets
14:33:05 <nirik> hum, not sure... the problem is that there are few of us and lots of tickets... and people might want to take something someone else has, etc.
14:33:09 <smooge> we have some set of tickets which have been unassigned for a long time
14:33:45 <smooge> so maybe we could go over which ones have been that way for a long time and just try to get one either assigned or closed per week?
14:33:48 <nirik> yeah, ideally we would finish//close the ones we have assigned and take more
14:34:15 <smooge> I took a couple of tickets this week that way myself.
14:34:38 <smooge> but the long term ones I am not sure anyone can work on without some discussion
14:34:53 <aikidouke> a script that asks the owner if they still need $thing fixed and, sleeps for 60 and then closes the issue?
14:35:09 <nirik> I don't think one size fits all.
14:35:17 * aikidouke needs more coffee
14:35:19 <smooge> yeah..
14:35:20 <nirik> but I'm fine discussing old tickets in meeting
14:35:36 <nirik> but the answer on some might be 'we still want to do this, no one is working on it, etc'
14:35:46 <smooge> well it was like most of my ideas at the spur of the moment...
14:36:04 <smooge> #topic Apprentice Open office minutes
14:36:04 <smooge> #info A time where apprentices may ask for help or look at problems.
14:36:05 <relrod> smooge: What are some examples of the longer-term ones? Could we reasonably knock a few of those out over a day or two vFAD?
14:36:40 <nirik> relrod: look at the last page of tickets...
14:36:41 <smooge> relrod https://pagure.io/fedora-infrastructure/issue/6750
14:36:49 <x3mboy> Hi
14:37:11 <aikidouke> vFAD is? virtual Fedora Apprentice Day?
14:37:13 <nirik> that ol chestnut
14:37:23 <relrod> aikidouke: activity day*
14:37:23 <x3mboy> Virtual Fedora Activity Day
14:37:25 <smooge> https://pagure.io/fedora-infrastructure/issue/5943
14:37:31 <aikidouke> :) ty
14:37:55 <x3mboy> Can we look at issue 7105?
14:38:06 <x3mboy> I'm not sure if it's still relevant
14:39:39 <smooge> .ticket 7105
14:39:42 <zodbot> smooge: Issue #7105: sudo is not working on f28-test.fedorainfracloud.org - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/7105
14:40:10 <nirik> hum. yeah I think thats fixed now
14:40:21 <nirik> after doing updates and poking at it.
14:40:23 <smooge> thanks for pointing that out x3mboy
14:40:23 <x3mboy> Ok :(
14:40:24 * nirik looks to see
14:40:34 <nirik> I don't know for sure...
14:40:47 <x3mboy> I will look for another ticket to work on
14:41:14 <nirik> yeah, looks like it's working... <insert shruggie here> :(
14:42:55 <nirik> sorry x3mboy, I should have updated that when I saw it working the other day.
14:43:44 <nirik> we need some more easyfix tickets. ;)
14:44:22 <x3mboy> Yeah! More easyfix!!!
14:44:39 <smooge> #topic Need more easyfix
14:46:38 <smooge> sorry that should have been info
14:46:40 <bowlofeggs> three's a handful of bodhi easyfixes (python)
14:46:42 <smooge> #topic Open Floor
14:46:55 <smooge> which fits also with open floor
14:46:55 <nirik> I'll try and think of some... but not sure off the top of my tired brain what they might be. ;)
14:47:35 <bowlofeggs> https://github.com/fedora-infra/bodhi/issues?q=is%3Aopen+is%3Aissue+label%3AEasyFix
14:47:38 <bowlofeggs> (currently 14)
14:48:07 <x3mboy> On Pagure the most recent easyfix is 10 month old
14:48:16 <mkonecny> I have plenty of easyfixes on Anitya https://github.com/release-monitoring/anitya/issues?q=is%3Aissue+is%3Aopen+label%3Aeasyfix
14:48:43 <pingou> x3mboy: wrong :)
14:48:58 * pingou added at least one earlier this week
14:49:03 <cverna> I think we need to add pointers to what needs to be done in our easyfix otherwise they might not be that easy :)
14:49:10 <nirik> x3mboy: you mean the fedora-infrastructre pagure instance?
14:49:17 <x3mboy> nirik, yes
14:49:25 <pingou> I stand corrected then :)
14:49:57 <nirik> easyfixes are hard... a thing thats easy to do, but you can live without it being done for a while even tho it might be a few minutes to fix
14:50:16 <bowlofeggs> yeah
14:50:20 <cverna> yes :S
14:50:36 <nirik> but they are important to get new folks up to speed on how things are setup... :)
14:50:41 <x3mboy> For me, the main problem is where the issues are displayed
14:50:42 <mkonecny> cverna: I'm adding task list to each easyfix
14:50:52 <cverna> mkonecny: cool :)
14:50:56 <x3mboy> e.g.: I always look on Pagure
14:51:10 <x3mboy> Now I'm seeing several githubs
14:51:38 <mkonecny> x3mboy: Look here https://fedoraproject.org/easyfix/
14:51:48 <cverna> x3mboy: if you are looking for sysadmin tasks the pagure repo is the right place to look
14:52:10 <x3mboy> cverna, yes, that's what I'm looking for
14:52:12 <bowlofeggs> also, github apparently supports new labels for this officially
14:52:18 <bowlofeggs> and they aren't the same as what bodhi uses
14:52:27 <bowlofeggs> but if i change bodhi it will break that easyfix app
14:52:28 <bowlofeggs> haha
14:52:47 <nirik> of course
14:52:47 <mkonecny> bowlofeggs: I also noticed this
14:52:53 <bowlofeggs> supposedly you can use "help wanted" or "good first issue" and github will direct newcomers to those in some way
14:53:06 <x3mboy> Oh tagger
14:53:09 <x3mboy> I will miss you
14:53:16 <bowlofeggs> i wish i could just click a bool on my EasyFix label in github and mark it as doing that for bodhi
14:53:23 <bowlofeggs> that would be better than magic string
14:53:24 <bowlofeggs> s
14:53:26 <bowlofeggs> but oh well
14:53:30 <mkonecny> we can use both on issues
14:53:39 <smooge> ok I need to bring this meeting to a close soon
14:53:46 <bowlofeggs> i might start using it and just send a PR to the easyfix app
14:53:54 <bowlofeggs> but no idea when such a patch could get deployed
14:54:39 <x3mboy> OMG I'm the contact for easyfix  in mindshare
14:54:43 <x3mboy> :P
14:55:32 <smooge> ok lets move this to the list and we can see how we are next week
14:55:41 <smooge> Thank you all for coming this week
14:55:44 <smooge> #endmeeting