<div dir="ltr"><div id="gmail-magicdomid4" class="gmail-">Pulp 2:</div><div id="gmail-magicdomid5" class="gmail-"><ul class="gmail-list-bullet2"><li>Modularity dep solving</li><ul><li>automatic module_default copy works!! but is buggy, *crashes* - under investigation </li><li>"too many packages/modules are copied" issue - clear what to do, just needs to be done</li></ul><li>Multiple source/target repositories support for recursive copy</li><ul><li><a href="https://pulp.plan.io/issues/5067">https://pulp.plan.io/issues/5067</a></li><li>for that we are adding multi-resource locking to the tasking system</li><ul><li><a href="https://pulp.plan.io/issues/5108">https://pulp.plan.io/issues/5108</a></li></ul><li>potential concern is resource utilization </li><ul><li>need some katello input on sequence of calls for their workflows - sync/publish/applicability </li><li>concern is to end up with N-2 idle workers for some time </li><li>AI: dkliban to work w/katello(partha) on api-workflow/resource-utilization</li><li>to consider: instrument 'waiting for available worker' state (% calls run into, amount of time spent waiting)</li><li>to consider: ask field engineering about customer workflows, to make sure we're testing those.</li></ul></ul></ul></div><div id="gmail-magicdomid10" class="gmail-">Pulp 3:<ul class="gmail-list-bullet2"><li>Modularity (ppicka) </li><ul class="gmail-list-bullet2"><li>modulemd models PR open</li><li>simple upload PR open</li><ul><li>can be used to test the models PR </li></ul><li> few prerequisities for ansible installer are added </li><ul><li>todo: temporarily install ubuntu package for libmodulemd in travis</li><ul><li>to be able to test rpm plugin until containers work is done and we can use Fedora/Centos there</li><li>AI: dkliban to share relevant info with ppicka </li></ul></ul></ul></ul></div><div id="gmail-magicdomid1269" class="gmail-ace-line"><ul class="gmail-list-bullet2"><li>Roadmap for RPM plugin </li><ul><li>discussed LOE for major items </li><li>AI: ttereshc to put the discussed roadmap into the redmine</li><li>highlights:</li><ul><li>prioritize tasks which might affect pulpcore, so we can change something before pulpcore goes GA, candidates: </li><ul><li>kicktstarts</li><li>sync option to verify content (files are corrupted or removed from the FS, the DB is ok - there should be a way to fix it)</li><ul><li>it's not RPM-specific, other plugins will benefit from it as well </li><li>AI: dkliban to write a story to start discussion</li></ul></ul><li>before we start working on applicability, ggainey will demo and share his experience with VMaaS <a href="https://github.com/RedHatInsights/vmaas">https://github.com/RedHatInsights/vmaas</a></li></ul></ul></ul></div><div id="gmail-magicdomid1688" class="gmail-ace-line"><ul class="gmail-list-bullet2"><li><a href="https://pulp.plan.io/issues/5092">https://pulp.plan.io/issues/5092</a> Files are not deleted when deleting uploads</li><ul><li>not RPM-specific, core question </li><li>discussion is needed to figure out if any resource reservation is required for upload workflow, including the deletion of uploads.</li><li>the outcome of the discussion (whenever it happens) should be posted on the issue</li></ul></ul></div><div id="gmail-magicdomid14" class="gmail-">Triage:</div><div id="gmail-magicdomid15" class="gmail-"><ul class="gmail-list-bullet1"><li>Un-triaged bugs <a href="https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30">https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30</a></li><li>Triage etherpad <a href="https://etherpad.net/p/rpm_triage_grooming">https://etherpad.net/p/rpm_triage_grooming</a></li><ul><li>all triaged </li></ul></ul></div></div>