Hi,
Pungi / Mash roadmap meeting -- 2017-07-13
Attendees: stickster, threebean, jcline, dustymabe, kushal, mboddu, bowlofeggs, mcurlej,
sayanchowdhury, lsedlar, puiterwijk
kushal: found that it would be hard to do just ostree generation from bodhi using pungi
dusty: I don't think this is true. All we have to do is provide repo URLs for the
repos that
were just mashed. I have a pungi config that can accept repo URLs and create
ostrees
already - we can use a url like this for the repo:
https://kojipkgs.fedoraproject.org/mash//updates/f26-updates-testing-1707...
mcurlej: In middle of work on pungi -- hope to have something to demo next week
* pungi config is only coded for RHEL at the moment, but working on that
* threebean: mcurlej work on pungi masher doesn't replace the bodhi masher -- bodhi
masher would still respond to push requests, but pungi masher would do modules and... ?
* [threebean] - that's about it. The motivation behind separating them was so that
we wouldn't risk any major changes to the mainline bodhi masher while working on the
module support.
Questions
* kushal: Can we use pungi currently with a config file to do a normal mash?
* [threebean] Yes, we think so -- if we need to shell out to pungi-koji for mainline
compose, so be it. Would be good to make that a jinja2 template to make it more flexible
* Note: Bodhi does understand jinja2 templates
* Can Pungi make drpms?
* [pfrields] And if it can, can this process avoid the long delay associated with drpms
when we create trees? (i.e. parallelize or a spinoff process?) -- IIRC this is one of the
most costly parts of the process
* Not currently; it is an option in createrepo_c and bodhi currently does it with mash
(which has createrepo_c?)
*
https://pagure.io/pungi/issue/344
* Can Pungi make updateinfo.xml?
* AFAIK no. Bodhi right now inserts updateinfo.xml after masher is done creating the
repo. (This feature is kept same in the WIP PR from kushal).
* if we are running a pungi compose for updates-testing what tag do we need to pull
from?
* f25-updates-testing
*
* if we are running a pungi compose for updates what tag do we need to pull from?
* f$version-updates(-testing)
* This tag is defined in bodhi's DB in the release table (for each release).
Blockers for this effort:
* We believe there is an issue where pungi does not create deltarpms (some issue with
createrepo_c)
*
https://pagure.io/pungi/issue/344
Action Items:
* Lubos: We need
https://pagure.io/pungi/issue/344 fixed, or some other way to get drpms
into a pungi-composed bodhi repo
* Randy: will verify that updateinfo.xml can be generated separately
* Kushal: schedule a sync time next week (invitees TBD, probably don't need
everyone)
* Dusty, Randy, Kushal: Get Bodhi staging able to mash with pungi. (build a pyramid
together, no pun intended)
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org