Is there a pulpcore version, that completely solves this issue, or is it a case of “performance has improved over time to the point where it is no longer a critical issue”?
we think we’re happy w/ the kbase described above
lots of performance/memory fixes going into pulpcore - stay up to date(er)?
What else is needed to make this work for Katello 4.3.1/pulpcore 3.16.12?
may actually be working for ATIX - needs new-year-neurons to look at it
How should this meeting proceed in 2023?
nag paji as needed
1st Tues works
Feb is to be skipped - cfgmgt camp and lots of year-startup happening
AI: [ggainey] schedule 6 months starting first tues in March
Proposal: Archive 2021/2022 minutes into a separate doc
no major objection
AI: [ggainey] clean up mtg-doc
Action Items:
AI: [ggainey] schedule 6 months starting first tues in March
no, pulp_rpm isn’t dropping depsolve any time soon
How important a feature is ACS for pulp_deb?
My gut feeling is that people can live without this feature, and other priorities should take precedence. However, I am wondering if there are potential pitfalls in pulp_deb does not implementing this?
ACS will allow smart-proxies to sync directly from upstream-deb-repos
not ‘necessary’ to implement, totally optional
some RH users are excited about it, but we don’t have any metrics on actual uptake
S3-storage for pulp-artifacts in katello/foreman-proxy-content? Out-of-scope, on the roadmap, or waiting for someone to implement it?
Pulp implements this
needs installer-support to turn on the right cfg-options
katello has related issue
“switching to S3 broke things” - to be reviewed/fixed
Notes from Pulp Gang at CfgMgtCamp:
several community members were asking for RBAC in pulp_deb (Magnus and Alexander?)
ttereshc will ping Magnus to open an issue so y’all can talk directly
