# Pulpcore/katello/pulp_deb integration meeting, 2021 archive
## 2021-12-07 1000-1030 GMT-5
### Attendees: ggainey, mbucher, quba42, jsherrill
### Regrets:
### Agenda:
* Heads up: We found a nasty bug in the pulp_deb 2to3 migration.
* Upstream issue: https://pulp.plan.io/issues/9616
* 2to3 Distribution tree problems are blocking the ATIX 2to3 testing effort.
https://pulp.plan.io/issues/9583
* What is Katello's process for adding bugfix releases to pulpcore-packaging. Examples to consider:
* On 3.14 pulp_rpm 3.14.6 is packaged, but 3.14.8 is available on pypi.
There is a PR that is sort of trying to update to 3.14.7:
https://github.com/theforeman/pulpcore-packaging/pull/326
* pulpcore 3.14.9 for 3.14 was approved three weeks ago, but is not being merged:
https://github.com/theforeman/pulpcore-packaging/pull/327
* My personal preference: Package bugfix releases as soon as they are available (automated pipeline to provide the PR, which can then be manually checked/approved/merged?).
* Development environment (forklift) when a change also requires a change in a pulp component?
* See https://projects.theforeman.org/projects/katello/wiki/Pulp_3_Integration#Using-a-2nd-server-as-a-pulp-server-for-use-in-development
* pulp_deb 2to3 is having old-tasking-system task-hang
* looks like TaskReservedResource table has zombies
* can try "trunc core_taskreservedresource and restart"
### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39
* ## 2021-11-02 1000-1030 GMT-5
### Attendees: quba42, mbucher, jsherrill
### Regrets: ggainey, msinghal
### Agenda:
* Promoting changed pulp-repo-settings into Katello after 2to3-migration (best-practise)
pulp_deb-distribution/-release list (comma- to whitespace-separated)
Options (using rake-task):
* just change it in Katello(, Candlepin?)
* get current settings from pulp3(-API) and sync them to Katello
* rake task or db migration since its a pure db change would work
* whatever suits us best, there is no strong upstream preference one way or another (in this case)
* Advanced Sync Options: What underlying pulp feature do they use for pulp_rpm?
* pulp_rpm uses `optimize=false` for the advanced sync in Pulp 3.
* This is most likely plugin specific (not a pulpcore feature), so pulp_deb will just end up doing "its own thing".
* How best to find out what Pulp API calls a given Katello action actually triggers?
* Set this to true, client bindings will start logging: https://github.com/Katello/katello/blob/master/app/models/katello/concerns/smart_proxy_extensions.rb#L180
* State of PRs:
* got many deb related Katello PRs merged! Thanks to everyone!
* Nearing completion: https://github.com/Katello/katello/pull/9634 (Oracle ULN related)
* Will have one more look at the failing tests.
* Set the release version on the Foreman issue for automatic cherry-picking into that release (post merge)
* (How) should we (ATIX) be thinking about backports?
* We are not anticipating any more 3.18, 4.0 (and probably 4.1) bugfix releases, so there is no need to backport to those versions unless some major reason to do so appears.
### Action Items:
* quba42 to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39
* jsherrill to have a quick look at the failing tests on https://github.com/Katello/katello/pull/9634
## 2021-10-12 1000-1030 GMT-5 (moved due to conflicts)
### Attendees: msinghal, quba42, mbucher, jsherrill, ggainey
### Regrets:
### Agenda:
* Happy news: https://github.com/Katello/katello/pull/8277 is merged!
If I may direct your attention to: https://github.com/Katello/katello/pull/7961 (needs rebasing, and then Much Discussion)
* More happy news: https://github.com/Katello/katello/pull/9676
Prompted by: https://community.theforeman.org/t/katello-on-demand-sync-repo-sync-option-for-ubuntu-deb-packages/25345
How to check what Katello release this will be in? (post in community demo as well?)
* see 'target release' in issue
* when do we report back to community-demo RE 'which release'?
* see https://community.theforeman.org/t/foreman-community-demo-101/25360
* Fixed Pulp 3 to Pulp 3 smart proxy sync for deb content: https://github.com/Katello/katello/pull/9706
* could use a katello review 'sooner rather than later'
* jsherrill to add to their review-board
* https://github.com/Katello/katello/pull/9634
* waiting on contrib? - why?
* also to be added to katello's review-please list
* Patching Pulp at the pulpcore-packaging level? E.g.: https://github.com/theforeman/pulpcore-packaging/pull/278/files
* release-packaging-horror-story-time ensues
* Mirror on sync and metadata: https://pulp.plan.io/issues/9316#note-19
* mirror=False broken in pulp-deb (multiple instances of metadata in same repo is bad)
* pulp_rpm has a bunch of problems as noted in 9316
* quba42 will bring up in pulp-open-floor
* Repository Creation in Katello
* Making Release field mandatory (debian requires this field)
* required **if** a remote-url provided
* easy to add validation at create-time
* problem is updating-repo does one-field-at-a-time
* katello has run into the same issue, painful to address at update
* msinghal doing a lot of work on UI-hints for users for deb-in-katello
* If repository creation fails due to pulp error should it rollback katello repositry creation as well?
* katello has done work to make this cleaner
* 4.1.1 katello should have made the 'remote fails at repo-creation time'
* https://projects.theforeman.org/issues/32867
* https://github.com/Katello/katello/pull/9497
* 4.2.0 has a fix for the update issue
* https://projects.theforeman.org/issues/33251
* pulp_rpm and http proxy and ULN repos - bring up at pulp OpenFloor
### Action Items:
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39
## 2021-09-14 1000-1030 GMT-5
### Attendees: ggainey, quba42, mbucher, jsherrill
### Regrets: msinghal
### Agenda:
* Smart Proxy sync development environment with forklift?
* atix having some issues w/ forklift
* need a smart-proxy sync env, community bug reports in this setup
* "proxy cannot activate puppet" at foreman-install
* combining centos7-katello-devel-stable w/ centos7-proxy-devel
* who should atix work with?
* make puppet-module-existence match on server/proxy
* open a thread if we continue being unable to fix
* error logs:
```
vagrant up centos7-proxy-devel
2021-09-14 08:49:23 [ERROR ] [configure] Proxy centos7-proxy-devel.example.com has failed to load one or more features (Puppet), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-09-14 08:49:23 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[centos7-proxy-devel.example.com]/features: change from ["Container_Gateway", "Logs", "Pulpcore", "Puppet CA", "Registration", "Templates"] to ["Container_Gateway", "Logs", "Pulpcore", "Puppet", "Puppet CA", "Registration", "Templates"] failed: Proxy centos7-proxy-devel.example.com has failed to load one or more features (Puppet), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-09-14 08:49:24 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[centos7-proxy-devel.example.com]: Failed to call refresh: Proxy centos7-proxy-devel.example.com has failed to load one or more features (Puppet), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-09-14 08:49:24 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[centos7-proxy-devel.example.com]: Proxy centos7-proxy-devel.example.com has failed to load one or more features (Puppet), check /var/log/foreman-proxy/proxy.log for configuration errors
2021-09-14 08:49:25 [NOTICE] [configure] System configuration has finished.
```
* Hard to diagnose 2to3 migration issues.
* how do we get better prob-det info from user-reports?
* there is no good answer for this :'(
* `foreman-maintain content migration-reset`
* Katello deb package applicability PR:
* https://github.com/Katello/katello/pull/8277
* lots of discussion/review has happened already
* vercmp - can this be done in sql?
* deb rules don't let us play the same tricks we do in rpm
* need to be able to define a new string-type w/ it's own operators
* installing the type 'correctly' requires root-access
* jsherrill to review test-state in PR
* Pulp/Katello import/export feature?
* exists in katello - rpm/ansible/file
* "super easy" to add new types
* jsherrill to share PR that enabled a new type in katello
* ggainey owes folks links to imp/exp docs ASAP
* https://docs.pulpproject.org/pulpcore/plugins/plugin-writer/concepts/subclassing/import-export.html
* https://hackmd.io/@ggainey/pulpimport_export_design
* https://hackmd.io/@ggainey/importexport_lowlevel_naturalkeys
* Think about subjects for pulpcon!
### Action Items:
* ggainey: imp/exp links fwded
* ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39
## 2021-08-03 1000-1030 GMT-5
### Attendees: ggainey, jsherrill, msinghal, mbucher, quba42
### Regrets:
### Agenda:
* We need a final path forward for deb_version_compare postgres extension.
* will need to be in pulp_deb #soon
* pulp_rpm includes as a db-migration
* if we do that in pulp_deb, how do we keep in sync w/ work being done in katello-rpm?
* having it in two places has downsides
* building in SCL is running into build-obstacles
* on the plus-side - doing it as a migration makes handling external-dbs **much** simpler
* net: pulp_deb will mirror what pulp_rpm is doing
* Seen on Katello: "Updated to use mirrored metadata for library repo syncs & capsule syncs"
https://github.com/pulp/community/discussions/4#discussioncomment-1033849
=> How to ensure pulp_deb is not forgotten as "mirror mode" is adopted by Katello
* upgraded to 3.14 gave katello 'mirror mode' almost incidentally
* katello adjusted to "just use returned publication" if there is one
* look at pulp_rpm, see if pulp_deb can make it work for smart-proxies
* broken currently, according to community input
* need to look into katello-changes and see if verbatim-publication can be modelled/used as pulp_rpm is?
* How exactly is Katello handling the drop in python 3.6 and 3.7 support (with pulpcore 3.15?)
* build-team will handle all the plugins at once
* pulp_deb nightly CI is perennially broken due to infrastructure issues => Where do I raise this issue? https://pulp.plan.io/issues/8642
* will bring up on OpenFloor
* Best strategy for plugin_template application to older release branches?
* community-discussion provided an answer
* PostgreSQL function for deb-version compare in Katello (new PR):
https://github.com/Katello/katello/pull/9507
* katello to merge, look into applicability-pr for deb
### Action Items:
* ggainey to extend schedule for this mtg
* ggainey to add minutes to https://github.com/pulp/community/discussions/7
## 2021-07-13 1000-1030 GMT-5 (rescheduled from 6-JUL due to mtg conflicts)
### Attendees: ggainey, mbucher, jsherrill
### Regrets: quba42
### Agenda:
* Katello users reporting pulp_deb bugs that may be pulpcore relevant
E.g.: https://community.theforeman.org/t/add-debian-10-repository/24157/10
* What's the correct reporting process?
* postgresql-debversion-evr packaging discussion (RPM comparison)
https://github.com/theforeman/pulpcore-packaging/pull/169
* how do we make it available?
* build as a file, then every-db-migrate always recreates form that file?
* there exists a debian-errata PR for katello, needs some attention/love before being re-reviewed
* ~~What are Katello's thoughts on the new pulp tasking system?
https://pulpproject.org/2021/06/21/a-new-tale/~~
* ~~Pulp CLI in Katello?~~
* Improving the deb content smart proxy sync
* Permutations of Pulp 2 and Pulp 3 on Katello vs. the smart proxy instance
* pulp2-proxy-to-pulp2 proxy supported now
* katello-4.0/.1 supports pulp2-proxy-to-pulp3-katello
* pulp3-proxy-to-pulp3-katello supported 4.0/.1
* katello 4.2+ supports only pulp3-to-pulp3
* Mirror/Verbatim sync instead of republish(including signing)?
* katello isn't supporting mirror yet
* pulp_deb has it implemented (and pulp_rpm)
* doing this as mirrored means "no need to resign content" - which, for deb, would include the metadata, using a key that the proxy doesn'[t have :(
* katello hoping to look into/start on mirror support in next 6 weeks(ish)
* Katello 3.18.4 release when/what/todos?
* remains on pulpcore-3.7
* jturel@(?) may be the person to talk to
* release-prep to start when last packaging-pr merges
* https://github.com/theforeman/foreman-packaging/pull/6588
* Hanging pulp2 tasks: https://pulp.plan.io/issues/9011
* prob an earlier version than katello-3.18
* "handled" currently by spreading out syncs ( :( )
* another instance of "sleeping worker handed work to do but never runs"
### Action Items:
* ggainey to add minutes to https://github.com/pulp/community/discussions/7
## 2021-06-01 1000-1030 GMT-5
### Attendees: quba42, mbucher, ggainey, jsherrill, manisha
### Regrets:
### Agenda:
* AI review
* release-wiki updated? - DONE
* VCR-review? - moved to AI
* Taking stock: Latest (for the relevant pulpcore version) pulp_deb versions now available for Katello >= 4.0.1; Now just waiting on the Katello 3.18.4 release (3.18.3 is meant to be released this week?)
* 3.18.3 is, in fact, imminent
* Cherry Pick the following to Katello 3.18 (before 3.18.4 release)?
* https://github.com/Katello/katello/pull/9306
* deb-structured-mode-pub
* already in 3.18.3 (marked in attached issue)
* pulpcore Django incompatibility problem (https://pulp.plan.io/issues/8691)
* bmbouter is contact if backport-info required
* Pulp 3 Smart Proxy modes/features
* Pulp2/squid setup ATIX uses
* Pulp3/katello - plans for non-syncing pulp passthru?
* mirrored-metadata support for RPM makes sync way more efficient
* that and on-demand
* pulp3 lazy - doesn't actually store RPMs at all
* Manisha will be working on CV-filtering for deb in katello
* katello new-UI work largely in place
* Samir working on CV-UI-side
* new UI originally aimed to 4.3 - 4.5 may be more likely
* if ATIX work aimed at 4.2/4.3 - focus on old-UI
* deb-vers-compare discussion
* deb-vers are more exciting than rpm nevra compare
* working to get compare-fn building in pulpcore-packaging, migration
### Action Items:
* VCR-review - AI for jsherrill and quba
* AI: ggainey to schedule next meeting [DONE]
* first-Tues for Jul/Aug/Sep, same timeslot
* AI: ggainey to send minutes to pulp-dev@
* experimenting w/ GitHub discussions - post there, point from pulp-dev@
* https://github.com/pulp/pulpcore/discussions/1381
## 2021-05-04 1000-1031
### Attendees: quba42, mbucher, ggainey, jsherrill
### Regrets:
### Agenda:
* Taking stock: pulp_deb updates are now planned for Katello 4.0.1 and 3.18.4 (complete for devel)
* Remaining open [packaging PRs](https://github.com/theforeman/foreman-packaging/pull/6587) are red.
* re-running job should fix
* [rubygem-katello.spec changes](https://github.com/theforeman/foreman-packaging/blob/3a0e355a86196383225b9f3d08d0852c7c501dd9/packages/katello/rubygem-katello/rubygem-katello.spec#L59) are still missing.
* will happen "automatically" for release (but not nightly)
* When will the next pulpcore version branch be created for pulpcore-packaging?
* please invite/notify quba42 next time we do this so he can learn How It All Works
* can we add pulp-dev@ , foreman-dev@ to the email to build-team requesting next branch?
* AI: jsherrill to add to wiki, heads-up to Evgeni
* Is Katello 3.18 the last version on which 2to3 migrations are possible?
* correct - by the time you're on katello-4.0, you're done with 2to3
* What about pulp_deb "cassette test" coverage?
* AI: jsherril to sched 30 min "How to do VCR tests" pair-programming exercise
* Are there plans for Katello to adopt the new (pulpcore 3.13) Pulp "autopublish" feature?
* katello will prob not take advantage of this
* Can version level dependencies from Katello to Pulp components be made explicit?
* Goal: A new package in a pulpcore-packaging repo should never break existing releases.
* Consider a multi node scenario where Pulp is on a different node from Katello.
* This is a hard problem, and we need to think about how we can solve it
* Multiple stakeholders on multiple schedules with multiple needs makes everything Fun!
### Action Items:
* AI: jsherrill to update release-wiki with a note to notify pulp-dev@ when starting a release-branch
* AI: jsherrill to schedule a 30-min "How to VCR" exercise w/ quba42, mbucher
* AI: ggainey to schedule next meeting for beginning of June [done, 01-JUN]
* AI: ggainey to send minutes to pulp-dev@
## 2021-04-13 1000-1030
### Attendees: ggainey, quba42, jsherrill
### Regrets: mbucher
### Agenda:
* Katello's dependency-requirements thought process
* What version of pulpcore goes/will go with which version of katello?
* Do we need to do this meeting regularly?
### Minutes:
* quba42:
* "What's katello's POV RE integrating w/pulpcore? When/how does katello decide to update pulpcore?"
* katello-3.18/pulpcore-3.7 currently - can/would we ever move up from 3.7?
* jsherrill: upstream katello integration-points stay close to product-levels
* lots of QE work on integration already happened
* stability highly desirable
* quba42:
* what if you have to backport something that needs a migration?
* lots of sad engineering noises followed
* katello-master: currently on 3.9
* just updated to 3.11 yesterday
* what's katello upgrade/update strategy?
* jsherrill:
* packaging is the biggest time sync for updating reqs
* packaging process discussion
* AI: jsherrill to send process-doc-link to quba42
* quba42:
* who should quba42 work with, to get pulp-deb packaging upgraded? Evgeni?
* AI: jsherrill to walk quba42 thru process? - No
* discussion about need for future/regular meetings
* do we even need to?
* maybe once a month?
* AI: have one a month from now, re-evaluate at that time
### Action Items:
* AI: jsherrill to send process-doc-link to quba42 (done)
* AI: ggainey to sched 15-min mtg for May (done)
* AI: ggainey to send minutes to pulp-dev@ (done)
###### tags: `Minutes`
Sign in with Wallet
Connect another wallet