15:00:01 <bowlofeggs> #startmeeting Bodhi stakeholders (2017-08-15)
15:00:01 <zodbot> Meeting started Tue Aug 15 15:00:01 2017 UTC.  The chair is bowlofeggs. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:01 <zodbot> The meeting name has been set to 'bodhi_stakeholders_(2017-08-15)'
15:00:11 <bowlofeggs> #meetingname bodhi_stakeholders
15:00:11 <zodbot> The meeting name has been set to 'bodhi_stakeholders'
15:00:11 <bowlofeggs> #topic salutations
15:00:11 <bowlofeggs> #chair acarter bowlofeggs caleigh dgilmore masta mboddu nirik pbrobinson puiterwijk trishnag Kellin jcline
15:00:11 <zodbot> Current chairs: Kellin acarter bowlofeggs caleigh dgilmore jcline masta mboddu nirik pbrobinson puiterwijk trishnag
15:01:01 * masta salutates 0/
15:01:01 <dustymabe> .hello dustymabe
15:01:03 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
15:01:26 * nirik is here, but also there and there.
15:04:17 <bowlofeggs> #topic announcements and information
15:04:17 <bowlofeggs> #info A Bodhi 2.10.0 beta is deployed to staging
15:04:17 <bowlofeggs> #info Release notes available at https://bodhi.stg.fedoraproject.org/docs/release_notes.html
15:04:22 * mboddu kinda here
15:05:15 <bowlofeggs> greenwave integration is the really big feature in 2.10.0
15:05:39 <bowlofeggs> so far it is not possible to test that feature since we don't have a greenwave in stg
15:06:38 <bowlofeggs> #topic Looking forward
15:06:38 <bowlofeggs> #info Bodhi's high priority issue list https://github.com/fedora-infra/bodhi/issues?q=is%3Aopen+is%3Aissue+label%3A%22High+priority%22
15:06:38 <bowlofeggs> #info High priority means it's important, but not a show stopper
15:06:39 <bowlofeggs> Any filed issues that aren't on these lists that should be?
15:07:35 <dustymabe> bowlofeggs: don't think it's represented on that list - but the pungi+bodhi work is high priority in my mind
15:08:08 <dustymabe> i think we are pretty close - i'm going to open a PR with the code that I have
15:08:17 <dustymabe> which includes kushal's code
15:09:02 <bowlofeggs> dustymabe: it's on the list: https://github.com/fedora-infra/bodhi/issues/1182
15:10:16 <bowlofeggs> i don't have anything else on the agenda today, so let's move to open floor
15:10:22 <bowlofeggs> #topic open floor
15:12:08 <dustymabe> bowlofeggs: can I ask a technical question?
15:12:27 <bowlofeggs> sure
15:12:42 <dustymabe> are there any technical reasons why moving bodhi to use pungi can't be done for all update types?
15:12:47 <dustymabe> i.e. including epel
15:12:52 <dustymabe> nirik: ^^ you might know
15:13:05 <dustymabe> smooge: ^^
15:13:27 <masta> interesting question
15:13:42 <smooge> it used to not be possible due to RHEL-5
15:13:44 <bowlofeggs> that i don' tnkow
15:14:25 <nirik> I dont think there's any blocker these days, as long as it works correctly.
15:14:39 <dustymabe> also another question - bodhi is able to "resume" pushes, right?
15:14:51 <dustymabe> what part of the process is resumable?
15:15:01 <masta> in terms of gathering builds, and laying out yum repos... pungi should be able to work for epel (in theory)
15:15:25 <nirik> various parts. It saves state in a lock file... after it's tagged them, after it's mashed them, after its updated bugs, etc
15:15:31 <bowlofeggs> yeah it has some ability to resume, but i don't know what parts can and can't be resumed
15:16:04 <dustymabe> bowlofeggs: i'm interested in if moving bodhi to pungi vs mash takes us backwards from a resumable standpoint
15:16:55 <bowlofeggs> that would not be good
15:17:11 <bowlofeggs> because the tagging and what not has to be handled correctly
15:17:19 <dustymabe> so the real question 'is masher resumable'
15:17:25 <dustymabe> if not then there will be no regression
15:17:32 <bowlofeggs> since it's a long running process, it's important for proper transaction handling to work
15:17:46 <bowlofeggs> yeah it is, i believe it gets used whenever there's a failure
15:18:20 <bowlofeggs> this might be one reason why mcurlej's approach is more sound
15:18:37 <dustymabe> nirik: ^^ i know some koji tasks can be resumed. i'm not sure about pungi overall itself
15:18:38 <dustymabe> do you know?
15:19:26 <nirik> there's no way to resume a pungi run that I know of. It's not all in koji, it's doing a bunch of stuff on it's own.
15:20:00 <dustymabe> nirik: right. thanks. That's what I thought
15:20:02 <nirik> also things that it does as koji tasks... if they fail they could be resumed, but pungi will have seen the failure and moved on
15:20:14 <dustymabe> is there somebody that we know that knows more about 'masher'
15:20:23 <dustymabe> that we can ask some of these questions to
15:20:28 <bowlofeggs> it sounds like we'll need an analysis of what can be resumed today that wouldn't be resumable with that patch, and a comparison of that patch with mcurlej's patch
15:20:42 <nirik> afaik, bodhi only keeps track of 'have repos been made' or not
15:20:57 <dustymabe> nirik: ok, if that's the case then there would be no regression
15:21:11 <nirik> so today it fires off mash, waits and if it works says that repos have been made for that thing.
15:21:24 <dustymabe> bowlofeggs: ^^
15:22:27 <bowlofeggs> we should carefully analyze to make sure
15:22:58 <dustymabe> who wants to be responsible for that?
15:23:18 <bowlofeggs> i can take no further responsibility at this time
15:23:32 <bowlofeggs> i still have two huge features to focus on and am about to afk for 3 weeks
15:23:46 <dustymabe> i'll see if I can find a mash expert
15:24:11 <bowlofeggs> i think we more need to focus on masher, not so much mash
15:24:19 <bowlofeggs> masher being bodhi's masher.py
15:26:03 <dustymabe> bowlofeggs: that's what I was referring to
15:26:10 <dustymabe> what's the difference?
15:26:19 <bowlofeggs> masher uses mash to do what it does
15:26:31 <bowlofeggs> mash is a separate program than bodhi
15:26:45 <dustymabe> yeah
15:26:56 <dustymabe> i knew that - ok
15:28:59 <bowlofeggs> anything else for open floor?
15:30:27 <dustymabe> nope
15:31:15 <bowlofeggs> thanks for coming everyone!
15:31:17 <bowlofeggs> #endmeeting