Pulp Ansible Meeting Minutes

[x9c4]

The Pulp Ansible meeting is the place to discuss features and issues that will affect the pulp_ansible codebase. It’s mostly attended by committers and integrators, but anyone interested in pulp_ansible can come.

When

Usually every week Mondays at 15:30-16:00 Central European (Summer) Time.

Where

On Google Meet
Video call link: https://meet.google.com/gcv-ceqg-eqx

Agenda

Anyone can add to the agenda.

[x9c4]

Nov 29

• Collection Signing
  • https://github.com/pulp/pulp_ansible/pull/754
• Roles PR broke pulp_ansible CI in interesting way
• Git-sync integration continues
  • blocked on CI issues
  • https://github.com/pulp/pulp_ansible/pull/756
• Backport to release pulpcore 3.15.z
  • Backport #9584: Backport 9542 to pulpcore 3.15 - Pulp
• What’s next for?
  • https://github.com/pulp/pulpcore/pull/1723
• API Refactor discussion on wednesday
• Writing a document describing what can be backported in the upstream
  • TL;DR any bufix without a migration. no features, no bugfixes with migrations
• Next pulpcore plugin API breaking changes will be pulpcore==3.20
  • Increasing Pulpcore Compatibility with Plugin Versions | software repository management
• Next pulpcore release, 3.17 scheduled for Dec 6-7

[x9c4]

Dec 6

• Do you want the collection deletion APIs in pulp ansible?
  • Probably yes
• Is it possible to have a worker router for tasking system?
  • e.g: I want a task to run in a specific worker
    • Short Answer: No
    • It would not be to hard to implement, but we have some serious reservation about the implications
      • What if you request a set of capabilities that no worker provides? → Tasking system jammed.
      • Needing a specific (type of) worker can slow down the task distribution significantly
    • Maybe such a thing is needed, when you cannot make the single hardware crypto device available to all machines running workers

[x9c4]

Dec 13

• OOM sync issue - https://github.com/pulp/pulp_ansible/issues/765
  • temporarily raised limits on pulp-operator
• New tasking system on consoledot - https://issues.redhat.com/browse/AAH-1150

[x9c4]

Jan 10

• update on collection signing
  • Branches seem to be incompatible across projects
  • Signing service setup in CI is a challenge
    • Solutions can be found in other plugins
      • https://github.com/pulp/pulp-cli/blob/main/.ci/container_setup.d/10-install-signing-service.sh
      • https://github.com/pulp/pulp_rpm/blob/main/.github/workflows/scripts/post_before_script.sh
• bug in migrations 35 and 36
  • https://github.com/pulp/pulp_ansible/issues/791
  • fix in-progress: https://github.com/pulp/pulp_ansible/pull/793
• How does galaxyNG want to use the pulpcore APIs?
  • Mainly tasking / status
  • other: Container, SigningService

[x9c4]

Jan 17

• Bringing pulp_ansible and pulp_container together for all the things
• Issues surrounding access policies in the galaxy APIs
  • https://github.com/pulp/pulp_ansible/issues/794
• update on collection signing
• How does galaxyNG want to use the pulpcore APIs?
  • what to do about the Task API
• Check-in on creation_hooks and policy customization discussion
  • How should Pulp handle different default permission classes? - #6 by x9c4
• Migration issue https://github.com/pulp/pulp_ansible/pull/793

Action Items

• @mdellweg to invite @ipanova reocurring
• @davidN and @mdellweg to collaborate on it via the issue
• mdellweg to followup with @gerrod tomorrow to merge the signing PR
• @bmbouter to setup 30 min meeting on using (or not using) the pulp APIs, e.g. the Tasking API
• Creation hooks planning to discuss at Jan 18th RTFM meeting with @davidN
• @fao89, @bmbouter, @mdellweg to discussion the migraiton issue on the PR