Pulp/Galaxy integration meeting

[x9c4]

Nov 14th

Action Items

[gerrod] release pulp_ansible after “lockless import” is merged.
[davidn] file an issue for “private” on ansible repositories.

Priority List

1. Repo managment
2. Namespace sync

In the priority Queue

Pulp

• Pulp_ansible
  • Lockless import is blocked by how to run tests.
  • Want a release after it.
• Pulp_container
• Pulpcore

Galaxy

• https://github.com/pulp/pulp_ansible/pull/1279 merged, think ready for a pulp-ansible y-stream release
  • In theory yes, we want to wait for “lockless import”.
• https://issues.redhat.com/browse/AAH-2000 private ansible repos
• status of https://github.com/pulp/pulp_ansible/issues/1105?
  • Waiting for collection-upload refactor: https://github.com/pulp/pulp_ansible/pull/1176
• pulp zero downtime, will invite infra for next meeting

[x9c4]

Nov 21

Action Items

[gerrod] release pulp_ansible after “lockless import” is merged.
[davidn] file an issue for “private” on ansible repositories.
[mdellweg] find and prioritize the pulp_ansible RBAC issue.

Priority List

1. Repo managment
2. Namespace sync

In the priority Queue

Pulp

• Pulp_ansible
  • Galaxy PR for collection-upload refactor
    • https://github.com/ansible/galaxy_ng/pull/1463
• Pulp_container
  • there is an issue with pulp-container signing service https://github.com/pulp/pulp_container/issues/1135. It affects only manifest lists. AH should not be affected as long as only image manifests are signed by pulp signing service; it’s being worked on.
    • Podman cannot verify signatures properly once the verification policy is configured.
• Pulpcore

Galaxy

• object permissions for repositories and remotes
  • Looks like the time has come to add RBAC to pulp_ansible.

[x9c4]

Feb 20

Action Items

[dnewswanger] file an issue for pulp_ansible copy.

Pulp

• Pulp_ansible
  • cross repo search performance requiring a new approach.
  • RBAC is close to be ready for final review.
  • Associated Content must be managed separately with modify.
    • A copy (that takes a source repo) could carry associated parts.
  • Namespace api seems to introduce some breaking changes.
    • e.g. image upload vs url
    • API’s may be coexisting for a while
• Pulp_container
  • Any updates for https://issues.redhat.com/browse/AAP-8823?
    • We have plans to improve the container registry operations. That is not a solution to the underlying issue, yet to be identified. +1
• Pulpcore

Galaxy

[x9c4]

Feb 27

Action Items

Pulp

• Pulp_ansible
  • Dependency issue with black
    • needs more investigation
    • my be just dev_reqs
    • pulp_ansible → galaxy-importer → ansible-lint
  • collection Mark https://github.com/pulp/pulp_ansible/pull/1326
• Pulp_container
• Pulpcore

Galaxy

• https://issues.redhat.com/browse/AAH-2158
  • PR https://github.com/pulp/pulp_ansible/pull/1376

Mar 06

Action Items

Pulp

• Pulp_ansible
• Pulp_container
• Pulpcore
  • Django 4.2 is going to be released in April (pulpcore v3.25)

Galaxy

• Need reviews on https://github.com/pulp/pulpcore/pull/3622
• https://issues.redhat.com/browse/AAP-8823

Mar 13

Action Items

Pulp

• Pulp_ansible
• Pulp_container
• Pulpcore

Galaxy

• (event conflicts with galaxy team meetings thanks to DST now)
• alikins leaving red hat
• reviews, reviews, reviews
  • RBAC
  • Collection search
  • more to come?
• Thoughts on https://github.com/pulp/pulp_ansible/pull/1393?
  • API endpoint for copying/moving collections to multiple repos

March 20th

Pulp

• Pulp_ansible
  • Final PRs needed for next release?:
    • RBAC: https://github.com/pulp/pulp_ansible/pull/1338
      • What is expected behavior of a Private repo?
    • Pre-release fix: https://github.com/pulp/pulp_ansible/pull/1392
    • X-Repo search: https://github.com/pulp/pulp_ansible/pull/1357
      • Will this be used on console.rh?
    • New namespace PR coming down the pipeline
• Pulp_container
  • [lmjachky] We are going to take the import/export and image building features out of tech preview (the API is stable and functioning properly)
    • https://github.com/pulp/pulp_container/issues/1236
• Pulpcore
  • pulpcore 3.23 is out now
    • Domains (you should not see if you don’t switch on)
    • CI update to plugins has stated. “Integrate with released versions, test with lowerbounds.”

Galaxy

April 27th

Action Items

Pulp

• Pulp_ansible
  • Sync after changing requirements slack discussion
    • issue issue
• Pulp_container
  • leadership change announcement
  • [lmjachky] hassle around the keycloak integration bug one day before dev-freeze (https://github.com/pulp/pulp_container/issues/1254)
    • Is there anything that can be done in the future to avoid similar situations?
• Pulpcore

Galaxy

• [awc] Is it still the future plan to release pulp* frequently as-needed, perhaps weekly, when pulp and galaxy have active development? (to avoid galaxy_ng using pulp dev branches)
  • pulpcore bugfix releases are out every week given that there are fixes to roll out

May 15

Action Items

Pulp

• Pulp_ansible
  • 0.17.1 released last week
• Pulp_container
  • https://github.com/pulp/pulp_container/pull/1273
    • adding pending blobs and manifests (1 repository version per image push)
    • will be released, possibly, with 2.15, pulpcore 3.25 compatible release
• [lmjachky] hassle around the keycloak integration bug one day before dev-freeze (https://github.com/pulp/pulp_container/issues/1254)
  - Is there anything that can be done in the future to avoid similar situations? Discuss with David N.
  - keycloak not present in the CI pipeline at the moment (just ldap)
• Pulpcore
  • every tuesday new Y (if possible)/X release
  • released pulpcore 3.25 (breaking change release)
    • comes with django 4.2
    • all plugins need comptability migrations (the release for pulp_file and pulp_certguard already handled)
    • next breaking release will be 3.40

Galaxy

• pulp_ansible 0.17.1 unblocked the performance/investigation work

May, 22nd

Action Items

Pulp

• Pulp_ansible
  • x-repo search
    • certain slowdown in tasks (with 35 000 collections)
    • https://github.com/pulp/pulp_ansible/pull/1466
  • pulpcore 3.25 compatible release planned soon.
• Pulp_container
  • Planning to release 2.15 soon compatible with 3.25.
• Pulpcore
  • 3.26 released

Galaxy

• Beta Galaxy to Production
  • Discovered some bottlenecks
    • Namespace meta data query maxing out db, will first need namespace sync to be resolved
• https://issues.redhat.com/browse/AAH-2262
  • reupload of collections that got removed is impossible until cleaned up by orphan cleanup
  • adding a checksum may be too dangerous
    • We need to understand the implications better.

[x9c4]

June, 05

Action Items

Pulp

• Pulp_ansible
• Pulp_container
  • [lmjachky] Usage of the image builder feature (https://github.com/pulp/pulp_container/pull/1287) - davidn agreeded on having the image building feature in tech preview
    • no other features on the radar to be included within the product
  • [lmjachky] Is the issue about updating remotes via DRF still relevant (https://github.com/pulp/pulp_container/issues/1071)?
    • perhaps
• Pulpcore
  • 3.27 out
• any updates on the OSTree needs for GalaxyNG?
  • no

Galaxy

• [awcrosby] For galaxy-authored PRs that are higher priority & need pulp reviews, what is best way to mark/ask?
  • Keep chasing people in chat channels.
  • Add short information about the change and why they are a priority.
• [awcrosby] What is best way to handle backport PRs… pulp reviewer, galaxy reviewer, patchback pr w/ no CI issues
  • We use patchback.
  • A single review is needed to merge; if everything goes smoothly, the original author can do that.
• Galaxy to production
  • stability and performance https://issues.redhat.com/browse/AAH-2346
  • download counts (https://github.com/pulp/pulp_ansible/pull/1477)