fedora_infrastructure_ops_daily_standup_meeting
LOGS
18:00:09 <smooge> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:09 <zodbot> Meeting started Mon Mar 30 18:00:09 2020 UTC.
18:00:09 <zodbot> This meeting is logged and archived in a public location.
18:00:09 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:09 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:09 <smooge> #chair cverna mboddu nirik smooge
18:00:09 <zodbot> Current chairs: cverna mboddu nirik smooge
18:00:09 <smooge> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:09 <smooge> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:10 <smooge> #topic Tickets needing review
18:00:11 <smooge> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:14 <smooge> good day
18:00:18 * nirik stands up.
18:00:30 <nirik> .ticket 8791
18:00:32 <zodbot> nirik: Issue #8791: Unclear how to admin old fedorahosted.org mailing list - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8791
18:00:46 <cverna> hi all
18:00:48 <nirik> Just need to write up info for them... I can just do it now.
18:01:05 <nirik> well, or ater the meeting I guess
18:01:05 <mboddu> Hello all
18:01:12 <nirik> assign to me, waiting for asignee
18:01:22 <nirik> monday everyone
18:01:34 <nirik> .ticket 8792
18:01:37 <zodbot> nirik: Issue #8792: deleting release tar ball - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8792
18:01:40 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8791: lists, low-trouble, and medium-gain https://pagure.io/fedora-infrastructure/issue/8791
18:01:41 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8791 https://pagure.io/fedora-infrastructure/issue/8791
18:02:09 <nirik> I guess this just needs doing, but with a nice "you shouldn't do that" admon. :)
18:02:33 <cverna> yeah I though we could not delete a tar ball
18:02:45 <nirik> we can... it's just a bad idea...
18:02:46 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8792: low-gain, medium-trouble, and pagure https://pagure.io/fedora-infrastructure/issue/8792
18:02:47 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8792 https://pagure.io/fedora-infrastructure/issue/8792
18:02:50 <cverna> thought*
18:03:05 <nirik> .ticket 8793
18:03:09 <zodbot> nirik: Issue #8793: Spam account: busybeaverair - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8793
18:03:10 <cverna> ok
18:03:37 <fm-admin> pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8793 to smooge https://pagure.io/fedora-infrastructure/issue/8793
18:03:39 <nirik> cverna: I mean, it's their project, it's not like src.fedoraproject.org... but it will cause all kinds of pain for their users. :)
18:03:51 <nirik> smooge: did you want to take this one?
18:04:11 <nirik> .ticket 8795
18:04:12 <zodbot> nirik: Issue #8795: Communishift: Request access to lbrabec's projects - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8795
18:04:15 <fm-admin> pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8793 https://pagure.io/fedora-infrastructure/issue/8793
18:04:16 <cverna> nirik: ha yeah I did not see that it was not on src.fp.o :)
18:04:16 <fm-admin> pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8793: "Spam account: busybeaverair" https://pagure.io/fedora-infrastructure/issue/8793#comment-638869
18:04:34 <nirik> I think I can do this one... but I will have to figure out how. :)
18:05:02 <fm-admin> pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8795: communishift, medium-gain, and medium-trouble https://pagure.io/fedora-infrastructure/issue/8795
18:05:03 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8795 https://pagure.io/fedora-infrastructure/issue/8795
18:05:13 <smooge> done
18:05:19 <nirik> thats the needs-reviews.
18:05:24 <cverna> ha we could put a ticket for the FAS operator
18:05:30 <nirik> any blockers, pr's waiting review, or other tickets to discuss?
18:05:47 <nirik> cverna: well, do we have the thought that anyone would work on that anytime soon?
18:05:48 <cverna> I had a quick colo move question
18:06:08 <nirik> I'd prefer a plan before making a ticket, because discussion in tickets sucks. :)
18:06:18 <cverna> nirik:  since lrossett and mkonecny are looking at ansible operator for mbbox, we could see how hard it would be to do
18:06:45 <nirik> or perhaps better... a noggin operator? :)
18:06:49 <lrossett> I can help in the planning part ig you want to
18:06:54 <lrossett> *if
18:07:21 <nirik> we already have a ticket open to sync groups... could also reuse that.
18:07:28 <cverna> So about colo move, I would like to finally do the aarch64 cluster for OSBS in prod but if this resources are not going to be available for MVF there is little interest
18:07:47 <cverna> I prefer to wait post move
18:07:58 <nirik> ok... let me think
18:08:04 <cverna> SO the question is did we plan for aarch64 OSBS in MVF or not ? :)
18:08:33 <nirik> I doubt we did. but I could be wrong.
18:08:47 <nirik> smooge: what was the move time for buildvmhost-a64-osbs-01.arm.fedoraproject.org?
18:09:05 <smooge> june
18:09:16 <cverna> yeah that's why I prefer to ask, because I assume we did not
18:09:19 <nirik> ok so yeah... after move would be better.
18:09:45 <cverna> +1
18:09:50 <cverna> it just good to know :)
18:10:40 <nirik> yep.
18:10:49 <cverna> I have another question related to the dashboard, I remember a cli tool that was able to track ticket in pagure, bugzilla, github etc ...
18:11:06 <nirik> huh... not sure what that would be.
18:11:19 <cverna> I believe someone at Red Hat was developing it, anyone would remember the name of that tool ?
18:11:24 <nirik> or, are you thinking of 'did' ? it scrapes for things that were done already?
18:11:36 <cverna> ha yeah that's it
18:12:01 <nirik> huh, yeah, I wonder if we could get it expanded to 'doing' ?
18:12:10 <cverna> :)
18:12:43 <cverna> yeah it is worth having a look since I think most of the communication logic with the different source of work will be there
18:12:43 <nirik> There's also bugwarriror... that scrapes places and feeds into task...
18:12:56 <nirik> but then everyone would have to use task.
18:13:41 <nirik> https://did.readthedocs.io/en/latest/
18:14:03 <cverna> yeah that get some time to get used to it
18:14:10 <cverna> thanks will look at that
18:14:15 * nirik has thought of using did with his weekly status, but it seems a bit too detailed for that
18:15:28 <nirik> ok, if nothing else, will close out in a minute.
18:15:37 <cverna> nothing else from me :)
18:15:56 <nirik> ok, thanks for coming everyone
18:16:21 <fm-admin> pagure.issue.comment.added -- jaruga commented on ticket fedora-infrastructure#8751: "Creating "medical-sig" group (FAS/Kochei) and "biology" (only Kochei) group" https://pagure.io/fedora-infrastructure/issue/8751#comment-638881
18:16:36 <nirik> #endmeeting