Pulpcore Meeting Minutes

Minutes
#37

Pending AIs

[bmbouter] open proposal issue to remove queues
[fabricio/dennis] ask katello if they want ruby bindings docs
[brian/matthias] open django prefetch bug

March 22

March 15th

  • memory PoC concluded
    • adjusting batch size is effective at reducing memory
    • dynamically adjusting it doesn’t keep it within a “target amount”
    • it runs extremely slow 10x plus
    • memory is never returned to the OS, the pages mostly just stay allocated and later
    • new memory charting debugging feature added:
    • proposal: to expose the batch size to users, the batch size is likely the single best adjustment to reduce memory
    • we need each plugin to also look at their own first-stage code to see if it can be memory optimized
    • proposal: https://github.com/pulp/pulpcore/issues/2069#issuecomment-1066853598
  • maintainability policy
    • how far should we keep ensuring old branches are working?
    • single container currently does latest 3 y-stream
    • pulp-cli tests with 5 y-streams
#38

Pending AIs

[bmbouter] Go through possible close query Issues · pulp/pulpcore · GitHub

March 29

#39

Pending AIs

[someone] open issue to audit and establish an upper bound for our requirements.txt deps

April 5th

#40

Pending AIs

[fabricio] audit and establish an upper bound for our requirements.txt deps

April 12th

#41

Pending AIs

  • [bmbouter] talk about plugin compatibility policy for 3.20+ on discourse

April 19th

#42

Pending AIs

[matthias] find a slot for downloaders SIG kick off meeting (ipanova, dalley, bmbouter)
[grant] will open ticket with legals re:logo licensing

April 26th

  • Discussion around list APIs for Exporters and Remotes
  • Downloader SIG: need to schedule kick-off meeting
  • Release rotation - time to rotate?
    • Brian will take care of 3.20 release
    • what to do with the blogposts on the pulpproject.org? Probably we will drop those and have only discourse release announcements
    • need to fix deps requirements( upper bound) on older releases and main branch before 3.20 release
  • decision on compatibility release?
    • if 3.25 then it wil be 9-10 months roughly until next breaking change. 3.25 it is
  • Is the Pulp logo available under Creative Commons, CC0, CC-BY, or CC-BY-SA licenses?
    • our logo is unlicensed
    • we need to open a ticket with legals
  • Streaming support needs a little more work around content ranges and caching; test will probably a new ci scenario with sftp storage
  • triage security alerts?
    • yes, add them next to the PR review ( from the next meeting)
#43

May 3rd

#44

May 10th

  • Look through remaining maybe-finished issues
  • z-releases
  • 3.20 tentative release date? first go/no-go?
  • status of django 2.2 in pulpcore 3.7 / 3.14
    • updating core/3.7 to last 2.2LTS, will require a change in (at least) matching pulp_container version
    • need to evaluate other plugins (Required PR: ?)
    • need a plan for who/when/testing
  • bmbouter and dkliban are updating pulp_file tests to use pytest, merging them with pulpcore
#45

May 24th

#46

May 31st

#47

Pending AIs

[dkliban] release pulpcore 3.19.1
[bmbouter] to propose majority use of nightly tests
[bmbouter] to highlight UI component creation on discourse

June 7th

  • telemetry pr in-review
  • CI Update
    • Functional tests to be run inside the container instead of the host
      • Installation is a nightmere today
      • More similar to dev-environment
  • Reducing CI runtime:
    • moving most tests to nightly
  • Collaboration with david N on using galaxy NG generic React + Patternfly components for a future Pulp UI
#48

Pending AIs

[dkliban] release pulpcore 3.19.1
[bmbouter] to propose majority use of nightly tests
[bmbouter] to highlight UI component creation on discourse
[matthias] figure out where sort is coming from

June 14th

#49

Pending AIs

[x9c4] Post on discourse about uninstalling pep8speaks
[x9c4] Investigate and post on Discourse about squashing migrations

July 12, 2022

#50

July 19, 2022

#51

August 9th, 2022

#52

August 23th, 2022

#53

August 30, 2022

  • pulpcore 3.21 release plans?
  • need someone to regularly go to katello integration call and report for pulpcore
    • dkliban to take over the reporting role for pulpcore
  • We need to have rules for approvals.
    • proposal: Require one Approval from SME and one non-necessarily-SME.
    • rationale: We do not have enough people to find two SME for each PR. Admin-merge is not a good solution (and an even harder requirement). Each pulpcore committer should be able to find code smells.
      • We’re supposed to have two SMEs for each component, so couldn’t we have two SME reviewers?
        • even when we do - if one (of the two) SMEs submits the PR, we’re still short a reviewer
      • problem: we don’t have the SMEs for pulpcore components written down somewhere
        • solution: mdellweg to write up SME components and list
  • FYI: pulp-smash proposal to be put into read-only mode on Sept 5th
  • set prio-list label
    • to review asynchronously and propose 3 items via pulp-dev, then we will review next week
    • added prio-list query to the top of this hackmd Issues · pulp/pulpcore · GitHub
  • review/unblock any assigned tickets, so folks have no more than 2 items assigned (or find a good reason to increase the limit)
  • backport discussion
    • still doing updating automated CI updates for every release branch back to 3.14
      • suggestion: have a list of explicit “supported releases”
      • AI for dkliban to write up and implement
    • suggestion: after a product release drops active support, we do stop eager backports
      • e.g. Once Satellite 6.N+1 comes out, “active” support stops and they only patch critical issues, z-streams not planned in advance
#54

September 6, 2022

  • Update list of SME
  • content-type change affects a pulp_ansible test
  • Discussion on https://github.com/pulp/pulpcore/pull/3136
    • Suggestion: instead of using uuid directly, provide a pulp_uuid function which we can change the implementation of without needing future migrations
      • Can be done independently of whether we adopt UUIDv7 right now
    • Discuss further at 3.21 go-no-go meeting
#55

September 13, 2022

#56

September 20, 2022

  • There’s an ask for more opinions
  • Some kanban reflections
    • Outbound: How do issues move off the Kanban board? Lots of “done” issues currently, clutters the per-repo view
      • Pulp Kanban board · GitHub
      • it is not implemented yet, but Tanya’s idea was manually dispatching a workflow to clean the done tasks at the beginning of the planning
    • Inbound: many plugins have nothing on the board, is that an accurate portrayal of priority or a process issue? Do we need to add items more frequently?
      • Only 2 “free to take” issues outside of the RPM plugin
    • Challenge: How do we manage the prio-list label with full inclusivity in an async environment?
    • We lack hard limits on the in progress/review columns
    • Items with reviews must move back to “in progress” if not ready to merge.
    • What to do with PRs that never had ‘prio-list’ ( community contributions, some old issue before kanban era, )