Pulp Installers Meeting Minutes

Minutes
#80

October 31, 2023

  • Status of nested containers
    • Fixed an issue whereby the nested container needed 64K + 1 UIDs from the outer container (because UID 0 is already mapped in Podman but not Docker)
    • Hopefully the CI passes, we won’t need to run “podman system migrate” in the inner container, and I can move onto the pulp-container PR.
  • weird CI breakage for pulp-ansible / pulpcore version
  • pulp-operator dual Pulp deployment check
  • Update on testing 2 instances of pulp-operator with kind (K8s on container instead of VM)
    • we are maxing the limits of GHA CI
    • We got the rudimentary check done
1 Like
#81

Nov 14, 2023

  • [ttereshc] ansible branch for pulp-operator can be removed
    • a discourse post would be nice to have
    • [hyagi] We can replace it with a tag
      • [mikedep333] This will preserve git history
    • [mikedep333] I recommend renaming the branch to “deprecated-ansible” or “ansible-deprecated”
    • Agreed: Renamed branch or tag
  • [hyagi] ansible team is planning to use the galaxy-ng and galaxy-ui images in galaxy-operator, so, if they manage to make it work with these images, we can stop maintaining galaxy-web and galaxy-minimal
    • Agreed: Have discussions in #pulp-deployments matrix channel or in the #pulp slack channel
  • [dkliban] services team is putting on hold the request for the “watch all namespaces” feature
    • Looking into using pulp resources directly managed by clowder framework rather than clowder calling pulp-operator
    • [Ina] This would preclude the Open Operations Initiative
    • [dkliban] These services can be open, the example of console.fedoraproject.org (upstream for insights)
    • [dkliban] Clowder is specific to Red Hat currently, but could be used by other orgs.
    • [dkliban] As an example of stuff pulp-operator does do that we’d have to reimplement, is watching the config objects and then regenerating pulp settings (and applying them)
    • [Ina] There are people who test pulp-operator. Are they doing things to supplement it like how RH uses clowder?
  • [dkliban] services team is exploring switching the deployments on console.redhat.com to using Clowder https://docs.google.com/document/d/1I-ZI90_xEQpEl5GQdUt-Mcgs6PAwhjy88AHNHAQ_9T4/edit#heading=h.60zkfjl40xzp
  • [mikedep333] Status of fixing the compose data loss bug (PR 468)
    • probable issue with old podman & new podman-compose breaking the CI (the container is up)
    • So I tried upgrading podman, and now it’s trying and failing to install old pulp-file for some weird pip dependency reason
#82

Nov 28, 2023

  • [mikedep333] 2 things to review for pulp-operator
  • Status of multi-arch builds
    • [decko] had to revert this last week
    • mikedep333 to research multi-arch registries and review PR inbetween services work
#83

Dec 5, 2023

  • Status of multi-arch builds
    • Merged
  • podman-compose up issue
    • [dkliban] will try to reproduce again
  • About the operator release cycle
#84

Dec 12, 2023

  • Multi-arch builds
    • Seems to be reliable now!
    • Mike will probably test on a Raspberry Pi 4 soon (forget if 2GB or 4GB)
  • Upgrading image to EL9 / python 3.9
    • We will check that no downstream products use python 3.8
#85

Dec 19, 2023

#86

Jan 10, 2024

  • User requests for docker-compose with https
    • Point them to nginx container docs
  • Docs issue with navigation missing for a few pages
#87

Jan 16, 2024

#88

Jan 23, 2024

  • I merged a feature request to pulp-oci-images
#89

Jan 30, 2024

  • pulp_installer bug reports and PRs
    • Agreed: Close them
    • Agreed: Archive the repository
  • User is experiencing a problem with pulp-worker pods getting restarted when the DB connection drops
    • The behavior is different from pulp-api pods
    • Changing the behavior of pulp-worker would not fix the underlying problem that the DB is becoming unavailable
#90

Feb 7, 2024

  • Fixed 2 Ci issues
    • Pulp images are now publishing
  • Helping Daniel with EL9 upgrade and the logic for fixing the permissions on the mounted folder
    • Upgraded S6 (worth seeing if it fixes it)
  • Design for python versions vs os versions
    • We previously agreed on tags
    • We previously agreed to create a new image, pulp_ci_centos9
      • Old el8 pulp_ci_centos image will be kept around for both the old image branches and the old plugin template
    • Python 3.8 is only on el8
    • Python 3.9 is on both el8 and el9
    • Python 3.11 is only on el9 (el9 needed for other reasons too)
#91

Feb 13, 2024

  • S6 upgrade seems to have fixed the issue with the fix-perms feature.
  • After fixing the postgres version detection properly, and some minor changes to the commits, we merged the EL9 upgrade!
    • Remaining work
      • EL8 builds also (Python 3.8)
      • Multiple EL9 python versions
  • Need to show off how I created the repos on dockerhub & quay
#92

Feb 20, 2024

  • Outline for blog post on EL9 upgrade
    • Why we did it
      • Newer python versions
      • Other benefits?
      • We’re developing upstream - latest and greatest
      • Python 3.8 EOL
    • image naming
    • image tags for python versions
    • plugin-template updated
    • remaining work:
      • Fix NSS output issue that breaks oci_env (Daniel working on this FYI)
      • EL8 images again
      • Make multiple EL9 python versions available
  • Old branches for pulpcore releases have not been created for the past ~20 releases
#93

Feb 27, 2024

  • still need to write the blog post
#94

Mar 5, 2024

  • still need to write the blog post
  • In the middle of reviewing the big CI change / Python versions PR
#95

Mar 12

  • CI Change / Python versions PR
  • galaxy-operator now builds their own smaller images instead of using ours
    • TODO: Gerrod to find out if we can drop building galaxy images (altogether or just branches)
#96

Mar 19

#97

Mar 26

#98

Apr 2

#99

Apr 9

  • No agenda items, just did triage