14:00:24 <cverna> #startmeeting Fedora Infrastructure Sustaining Daily Standup Meeting
14:00:24 <zodbot> Meeting started Wed Mar 25 14:00:24 2020 UTC.
14:00:24 <zodbot> This meeting is logged and archived in a public location.
14:00:24 <zodbot> The chair is cverna. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:24 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:00:24 <zodbot> The meeting name has been set to 'fedora_infrastructure_sustaining_daily_standup_meeting'
14:00:24 <cverna> #chair cverna mkonecny siddharthvipul jednorozec mboddu lrossett
14:00:24 <zodbot> Current chairs: cverna jednorozec lrossett mboddu mkonecny siddharthvipul
14:00:39 <cverna> #info meeting is 30 minutes MAX. At the end of 30, its stops
14:00:39 <cverna> #info agenda is at https://board.net/p/fedora-infra-daily
14:00:59 <cverna> hello
14:01:08 <siddharthvipul> cverna: helloow
14:01:22 <mkonecny> .hello zlopez
14:01:23 <zodbot> mkonecny: zlopez 'Michal Konečný' <michal.konecny@packetseekers.eu>
14:01:32 <mboddu> .hello mohanboddu
14:01:33 <zodbot> mboddu: mohanboddu 'Mohan Boddu' <mboddu@bhujji.com>
14:01:35 * siddharthvipul is present
14:01:51 <cverna> #topic Item needing reviews
14:02:03 <siddharthvipul> nothing here :)
14:02:06 * mkonecny giving packing siddharthvipul for christmas
14:02:24 <mkonecny> Nothing from me
14:02:31 <cverna> I have quite a big PR for koji-fedmsg-plugin
14:02:34 <cverna> https://pagure.io/koji-fedmsg-plugin/pull-request/15
14:02:35 <mboddu> cverna: I updated the compose-tracker PR and your idea gave me another idea and it improved the code a ton
14:02:36 <siddharthvipul> haha, I am quite wide, would take a lot of paper to wrap me up XD
14:03:08 <mkonecny> cverna: This one is pretty big
14:03:17 <sfinn> Hi all
14:03:27 <mkonecny> Hi sfinn
14:03:33 * mboddu waves at sfinn
14:03:34 <sfinn> How are you?
14:03:36 <siddharthvipul> sfinn: heyy, welcome :D
14:03:38 <cverna> mboddu: yeah I gave it another look this morning and it looks good :) I added a few comments there for you :D
14:03:55 <mboddu> cverna: Ahh, come on :(
14:04:19 <cverna> o/
14:04:44 <sfinn> Anymore thoughts on our dashboard? Will I put a doc with a few points together on what we are investigating?
14:04:50 <cverna> mboddu: just a few more little things :)
14:06:15 <cverna> sfinn: don't think we started the discussion yet, we should kick an email thread about it
14:06:18 <cverna> #topic Work In Progress
14:07:01 <cverna> I am busy with Bodhi, I release 5.2.2 today to fixed a bug but there still seems to be some failures with the composes
14:07:13 <cverna> so I am looking at that
14:07:36 <mboddu> cverna: Yeah, your comments are nice, I am learning a lot, and I did try itertools.chain() but it didn't work, I will give it another shot
14:07:58 <sfinn> Perfect cverna I'll kick it off
14:08:06 <siddharthvipul> I sent out the new arch addition email to ci-user list yesterday after testing from python-cicoclient a couple of times. on public holiday today but from tomorrow the plans are to work on openshift template for jenkins with ACO or FAS (also look for ways to configure tokens automatically) will need to talk to senior ops soon
14:08:15 * mkonecny working on CRD for koji-builder for mbox operator
14:08:21 <cverna> sfinn: thanks :)
14:08:26 <siddharthvipul> right now (or from tomorrow) it's more of exploring what can be done
14:09:04 <sfinn> Anyone practising not working on non urgent tickets as they come in but reviewing them all on stand up and then prioritising ; ) ?
14:09:09 <cverna> siddharthvipul: if it is a public holiday you should not be there :P
14:09:22 <siddharthvipul> cverna: yeah, I am in lockdown :(
14:09:27 <siddharthvipul> what else I would be doing
14:10:09 * cverna did not had time to look at tickets with the Bodhi release so I guess I did practice it :P
14:11:26 <siddharthvipul> sfinn: I would but there are not tickets on backlog for CI on me, so nothing for now, but will make sure unless it's important I won't pay attention (and look at it on scheduled time)
14:12:05 <mkonecny> sfinn: Not receiving much tickets for Anitya or the-new-hotness, those that arrive, I only evaluate and add labels to them
14:13:44 <cverna> Ok moving on to blockers
14:13:48 <cverna> #topic Blockers
14:13:51 <cverna> Any blockers ?
14:14:14 <siddharthvipul> nothing here :) all's good
14:14:46 <mkonecny> Just the slightly documented operator-sdk is slowing me dows
14:14:54 <mkonecny> s/dows/down
14:15:42 <cverna> mkonecny: is this something we should be documenting more within mbbox, ie how things works ?
14:15:58 <cverna> to make future maintaince easier ?
14:16:19 <mkonecny> We are trying to help people starting developing it, but this is more about the tools and their documentation
14:17:06 <mkonecny> Developers of the operators SDKs think that everybody developing a operator is deeply familiar with Kubernetes
14:17:47 <mkonecny> I'm trying to learn more about it
14:17:56 <mkonecny> I'm glad to have lrossett in the team
14:18:12 <cverna> lrossett++
14:18:16 <cverna> :)
14:18:34 <cverna> #topic Questions
14:18:45 <cverna> Any questions or other topic ?
14:19:44 <mkonecny> Just the idea I already shared in mail, automatic container builds based on rpm releases
14:19:59 <mkonecny> Is this something, that could interest our team?
14:20:40 <mkonecny> It will make deployment of new versions in OpenShift much easier
14:21:17 <pingou> hm, how so?
14:21:39 <pingou> ah, new version in openshift, somehow I read new version *of* openshift
14:21:42 <sfinn> Great to hear cverna mkonecny and siddharthvipul
14:22:04 <cverna> I am not sure about the value against trouble on this one
14:22:20 <pingou> I think another team was/is looking at it
14:22:40 <pingou> so we may want to ask them first what's the status and if they stopped working on it, why
14:22:40 <cverna> that will need some improvement in OSBS because now you still have to maintain the version number of the container
14:23:17 <cverna> that could be a ticket for the container SIG, but the SIG is pretty much dead so that would not be useful :(
14:23:36 <mkonecny> This is just an idea right now, but it could be useful in long term
14:24:48 <mkonecny> The alternative is to build the container images for operator deployment manually each time a new version is out or let it on the team responsible for the app
14:26:08 <mkonecny> It was one of the requirements for mbbox
14:26:20 <mkonecny> To have automatic builds of images
14:26:29 <cverna> mkonecny:  is that specifically for koji ?
14:26:40 <mkonecny> cverna: MBS and Koji
14:27:11 <cverna> I ll check with bstinson how much of an hard requirment this is versus a nice to have
14:27:25 <mkonecny> I think it's more nice to have
14:28:00 <cverna> but we could check with the koji and mbs team if they would be interested to provide a container image of their application
14:28:13 <mkonecny> But for automatic lifetime management of mbox using operator, it will be really nice
14:28:26 <cverna> we can also use OSBS and have a container image in src.fp.o
14:28:50 <cverna> s/container image/ Dockerfile/
14:29:41 <bstinson> i'd call full automation a nice to have. a regular maintenance task for updates is ok, but it would be good to make that as simple as possible to build updated images
14:30:29 <mkonecny> I have few issues created for this on mbbox project
14:30:37 <mkonecny> They are free to take :-)
14:30:51 <cverna> cool thanks bstinson, I think we can keep this in the back of our mind and look at way to have a full automted workflow once we have something working
14:30:57 <fm-admin> pagure.issue.comment.added -- zveleba commented on ticket fedora-infrastructure#8757: "fedoraproject.org URI as XML namespace" https://pagure.io/fedora-infrastructure/issue/8757#comment-637528
14:31:01 <bstinson> +1 from me
14:31:31 <mkonecny> I will let the issues open
14:31:44 <cverna> ok we have reached the end of the meeting
14:31:47 <cverna> thanks all
14:31:50 <cverna> #endmeeting