RPM meeting

Pending action items:

• AI: [ggainey] stand up an rpm/deb/ansible install and experiment, to get hard details on the actual behavior (CopySerializer issue)
• discuss adopting zero-downtime-migration strategy
  • https://pulpproject.org/pulpcore/docs/dev/learn/plugin-concepts/?h=zero#zero-downtime-upgrades
• last copr issue https://github.com/pulp/pulp_rpm/issues/2271

Agenda template

### Month DD, 2023
Action Items:
Discussion Topics:
* Review PRs
* Triage new issues
* Check CI

Open, non-Draft PRs:

• https://github.com/pulp/pulp_rpm/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse

Un-triaged bugs:

• https://github.com/pulp/pulp_rpm/issues?q=is%3Aissue+is%3Aopen+label%3ATriage-needed

CI status check

• https://github.com/pulp/pulp_rpm/actions/workflows/nightly.yml?query=workflow%3A"Rpm+Nightly+CI%2FCD"

2025

Action Items

• Think about v4 changes

Upcoming

March 6, 2025

• pulp_rpm content-label perms need to be done differently (soon)
  • rework
• investigating "fun with aiohttp and SSL and self-signed certs" again

February 13, 2025

• ready for 3.28 release?
  • change-distribution-layout PR should be included
    • just investigating a test-fixture issue
    • consensus: wait 3.28 on this please
  • remove deprecated options
    • should we just…leave these?
    • does change the published-API, in ways that we don't really "have to"
    • consensus: not in 3.28, probably when Pulp 4 happens
  • "soon"!

January 30, 2025

• discussion around zero-downtime-migrations
  • review the rules
    • Probably when it becomes relevant ie. when we have a major migration of some kind
• null content origin pr
  • ggainey to make sure dalley/pbrochado have access
  • team will decide next week whether to adjust it or wait til he is back from PTO
• PRN support PR
  • no breaking news
  • implementation details are Fun
  • Q: on the view, check src/dest repo sanity
  • lots of discussion ensues

January 23, 2025

• discussion around checking GPG keys before adding to repo
• branch-protection-rulesd
  • we only had them for [0-9].[0-9]
    • so nothing after 3.9 had branch-protection
  • modified to match pulpcore - [0-9].[0-9]*
• discussion: PRN support PR
• discussion: Content Origin

January 16, 2025

Discussion:

• priorities
  • core/3.70 support
    • https://github.com/pulp/pulp_rpm/issues/3854
  • null-CONTENT_ORIGIN impacts
    • audit and fix
    • https://github.com/pulp/pulp_rpm/issues/3856
  • PRN support (eg, advanced copy):
    • https://github.com/pulp/pulp_rpm/issues/3853
    • audit to see where else we need to change
  • pulp-smash removal:
    • https://github.com/pulp/pulp_rpm/issues/3855
• did ggainey archive 2024 minutes?
  • yes : https://hackmd.io/@pulp/rpm_meeting_2024
• next pulp_rpm Y-release should include 3854, 3853, 3856
  • dalley creating a 3.28 milestone

January 9, 2025

• Rename this meeting to satellite?

  • maaaaybe - but we really don't talk much about non-rpm/file issues
    • e.g., container?
  • ggainey: we talk about Satellite/katello A LOT
  • pbrochado: we do spend time dealing with just-upstream-issues
  • dalley: we do talk about Satellite, but maybe only because it's the biggest stakeholder
  • anthomas: what about rpm/stakeholder?
  • dalley: the name may not be importnt, as long as we know what we're here for
  • ggainey: do we need a Satellite-specific meeting?
    • dalley: no - there's already the katello integration
  • consensus: let's not

• ttereshc: jira d2d dashboard updated/cleaned up

  • what else do we need/want on this dashboard for us? Let Tanya know!
  • some process-discussion has happened

• ttereshc: Story Points on any/everything you're working on

  • in-progress/closed, please
  • dalley: only on pulp-side? Yes please.
  • background:
    • goal is, Pulp team doesn't touch top-level Sat jiras
    • pulp-part is not a subtask, it's an issue in the Pulp tracker that gets linked
    • "shouldn't" need to set the Sat-jira-status
  • ttereshc:
    • do still need to set "fixed in" on the satellite issue
    • discussion/comments will prob happen on the satellite-jira
  • ggainey:
    • remind me what the process is when there are sat-jiras for each sat-version, that all map to "one gihub issue that is backported/released to mul.tiple pulp versions"
    • answer: RTFM, Grant!
      • https://docs.google.com/document/d/1V0rl8PNV6xEbu_xA__iEuoINubVTGWpXGpqK_eKXLeo/edit?tab=t.0&authuser=2&hl=en#heading=h.giqhjac9tqij
    • discussion when upstream finds problems when there are not yet any Sat-Jiras/customer-cases
      • def go to Sat-Eng and make it known
      • prob want to discuss at katello-integration-mtg the right thing to do
  • ttereshc to send anthomas doc/jiras on the current process and its logic

• PRN support with RPM advanced copy API?

  • discussion to bring anthomas up to speed on "what the hell are PRNs?"
  • needs a github issue - dalley volunteers to open one
  • where else might RPM need to do work?
    • specifically - things we don't just get "for free" from inheriting from core?
      • downloaders? content?
  • https://github.com/pulp/pulp_rpm/issues/3853

• pbrochado: discuss backporting migrations?

  • discussion on why we don't do this
  • there is a way to handle this for a specific fix under discussion
    • there is a django-command that can make this happen
    • if a migration has the same name/order/depends-on, in every single backported branch, then this can work

2024 minutes

2023 minutes

2022 minutes

2021 minutes

tags: RPM, Minutes