# Pulpcore/katello/pulp_deb integration meeting See also: https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## Overview * Purpose: Facilitate release-planning between Pulp3, Katello, and pulp_deb releases * Attendees: pulpcore, katello, pulp_deb reps; others as needed ## Template ``` ## YYYY-MM-DD 1000-1030 GMT-5 ### Attendees: ### Regrets: ### Agenda: * Previous AIs: ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ``` # 2024 ## YYYY-MM-DD 1000-1030 GMT-5 ### Attendees: ### Regrets: ### Agenda: * Previous AIs: * Apparently it is not possible to "request a review" from arbitrary people in GitHub (perhaps this requires merge access? or maybe you can't do it if there already are two reviewers on the PR?), so we did a normal ping instead: https://github.com/Katello/katello/pull/10905/#issuecomment-1980695028 * quba42: Who is the expert on js/UI bugs? https://projects.theforeman.org/issues/37240 * Forklift, lived practice questions (quba42): * Which boxes do you use for development? (centos8-katello-devel, centos8-katello-devel-stable, centos8-katello-nightly-stable, ...? So many to choose from...) * Do you upgrade your active box, or just vagrant destroy and re-create it? * How long do you tend to keep your boxes? * I keep randomly getting `An error occurred saving the Repository: uninitialized constant ForemanTasks::TimeoutError` only for things to succeed if I take the same action again?! ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2024-03-05 1000-1030 GMT-5 ### Attendees: ggainey, iballou, sjha, sweta, quba42, hstct ### Regrets: ### Agenda: * Previous AIs: none? * quba42: I would like to learn to better understand these posts: https://community.theforeman.org/t/katello-4-11-1-release-process/36915 * how to go from this, to "how long should I wait to rely on the release-rpms being available?" * hard to give a solid "how much time left" * ping release-owner/engineer for status if/when/as needed * quba42: How to add a new RPM?: https://github.com/theforeman/pulpcore-packaging/pull/881 * need help on how to generate the initial .spec file for a new package * is there a good tool? * pulp-cli-deb is currently blocked waiting on pulp-glue-deb * prob should wait till odilon is less-busy to have a conversation * quba42: ATIX Katello PRs near completion: * Katello fix ready for final review: https://github.com/Katello/katello/pull/10905 * Looks like final review is already requested, but I add it for completeness: https://github.com/Katello/katello/pull/10900 * one can use the github request-reviewer/re-review tools to get some attention if/when/as needed * requesting new core/3.48 for new katello * updating to new pulp_deb as well * core/3.49 coming out "today", includes https://github.com/pulp/pulpcore/issues/5086 * can we tighten the window between katello-announce and build-accepts? * there is always going to be some window * iballou to investigate maybe taking 3.49 instead * pulp-glue discussion happening in katello-land * change smart-proxy talk to pulp instead of katello * would solve the N-2 problem * discussion continues * core/3.55 is coming! * discussion around pulp eventually going to retrieve-when-content-exists * should there be pressure on plugins to change this behavior to the default? ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2024-02-13 1000-1030 GMT-5 ### Attendees: ggainey, mbucher, sja, iballou, quba42, hstct ### Regrets: ### Agenda: * Previous AIs: * ~~ggainey to archive 2023 minutes~~ * ~~https://hackmd.io/@pulp/pulp-deb-katello-integration_2023~~ * meeting in person at conference was Really Useful! * fun with Forklift - lots of fixing has happened! * discussion between ATIX/katello * discussion around katello/UI bug in 4.11 * needs an upstream issue opened? * discussing next-pulp-version for katello/4.13 * prob whatever the latest-Y is at branch-point * would be good if a pulp_deb-Y right before katello-branch so katello gets latest * pulpcore discussed "supported branches" this week * discussion ensues * how can we get katello reviews happening more quickly on pulp-deb/ATIX Stuff? * can we get ATIX approve-access to the affected repos? * sure - there is A Process, let's do it! * Process: https://theforeman.org/handbook.html#Becomingacommitter * iballou to bring up w/ katello team * ATIX needs a candidate to start doing regular katello-reviews? * work w/ iballou/sja to iron out details * ATIX customer is "losing publications"?!? * heavy CVV user * old CVV "loses" pub? * ATIX investigating - rake cleanup task? * how can a repo-version exist, but associated publications are gone?!? * check if pulp was told to delete? * katello/4.7 (we think) is what's in use * might be a related fix, in a newer katello? * sja: there exists a PR to "freeze" repo-access while a publication is happening ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 ## 2024-01-09 1000-1030 GMT-5 ### Attendees: bsuttner, quba42, iballou, ggainey, dalley, pbrochado, sweta ### Regrets: ### Agenda: * Previous AIs: * ~~ggainey: schedule mtgs for 2024~~ * ~~iballou: summarize discussion RE global-repair into PR~~ * ~~iballou: Poke People to get other katello PRs reviewed~~ * hstct to report back on customer experience once RemoteArtifact indices applied * no answers yet * Are we looking into [this](https://community.theforeman.org/t/proxy-sync-10x-slower-with-foreman-3-8-katello-4-10/35887/7)? * looks like "yes" based on discussion there * seems to be improving for reporting-user * appears to be resolved now * I can't sync Python on Katello 4.7 (`python39-pulp-python-3.7.3`) * There is a successfull sync task, but no actual content is synced. * The Pulp remote being used looks exactly like the example in the pulp_python docs. * I could be missing something incredibly obvious since I have never used pulp_python before. * might be an old katello bug getting in the way? * maybe retry on 4.11 * https://community.theforeman.org/t/storing-secure-information/36195 * katello issue * secure-storage for things like ssh/gpg keys/uname-pwd * could/should this be a new feature for foreman? * is there/what is the "standard"/existing way foreman stores this kind of info? * feedback/discussion should continue on the thread above * ATIX Katello PRs: * Structured upload: https://github.com/Katello/katello/pull/10639 * sjha out till end of Jan * needs a new katello person to do the merge * Fix deb copy API: https://github.com/Katello/katello/pull/10734 * needs review * Export/Import for deb: https://github.com/Katello/katello/pull/10749 * needs review/merge * Requires: https://github.com/theforeman/pulpcore-packaging/pull/819 * merged, available * Host details tab for deb: https://github.com/Katello/katello/pull/10744 * actively in review/discussion * Incremental update concurrency: https://github.com/Katello/katello/pull/10781 * already on katello-review-list * Heal broken publications on sync: https://github.com/Katello/katello/pull/10776 * merged ### Action Items: * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 * ggainey to archive 2023 minutes ### Action Items: * AI: [ggainey] schedule 6 months starting first tues in March * AI: [ggainey] clean up mtg-doc * ggainey to add minutes to https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39 # 2023 * Archived: https://hackmd.io/@pulp/pulp-deb-katello-integration_2023 # 2022 * Archived: https://hackmd.io/@pulp/pulp-deb-katello-integration_2022 # 2021 * Archived : https://hackmd.io/@pulp/pulp-deb-katello-integration_2021 ###### tags: `Minutes`