[Pulp-dev] RPM plugin meeting notes

Tatiana Tereshchenko ttereshc at redhat.com
Thu Sep 12 17:38:38 UTC 2019


Pulp 2:

   -

   Multi-repo copy merged, Kersom nearly finished with test
   -

   2.21.0 dev freeze complete, RC1 scheduled for September 18
   -

   Investigating Katello content view publish issue
   -

      Terrible performance, taking >40 minutes to publish content view with
      depsolving enabled (for baseos and appstream repos)
      -

      Have reproduced with Katello, but not with Pulp, still unsure what
      the problem is
      -

      https://bugzilla.redhat.com/show_bug.cgi?id=1748426


Pulp 3:

   -

   Areas/features which needs to be resolved before going GA - aka any
   items which might bring backward incompatible changes or correctness
   problems (there is no goal to be Katello-feature complete for the pulp_rpm
   3.0 GA):
   -

      all REST API endpoints should be established so only additional
      changes are introduced. e.g.
      -

         Upload
         -

         Copy
         -

         Two proposals:
         -

            https://pulp.plan.io/issues/5403
            -

            https://pulp.plan.io/issues/5344
            -

         Related discussion :
         -


            https://www.redhat.com/archives/pulp-dev/2019-September/msg00010.html
            -

      closure issues need to be resolved (any additional content
      validation, filtering at a repo version level, e.g filter by
signing keys,
      keep last N versions, etc)
      -

         Likely a change to pulpcore-plugin so it’s fine to add/change
         things after GA
         -

         https://pulp.plan.io/issues/3541 and some related issues
         -

      the per-repo uniqueness (repo_key feature)
      -

         https://pulp.plan.io/issues/5008
         -

         Blocker (correctness problem)
         -

      modulemd content types
      -

         https://pulp.plan.io/issues/4908
         -

      Auxiliary content types (incl. comps.xml) **blocks kickstarts, though
      the support of custom metadata can be a workaround
      -

         https://pulp.plan.io/issues/5112
         -

      kickstart content types
      -

      Applicability?
      -

         Low likelihood of blocking
         -

         LOTS of discussion to happen (esp at PulpKhan)
         -

      use Postgresql JsonField
      -

         https://pulp.plan.io/issues/5326



   -

   Kickstart update (david/fabricio)
   -

      Could not fully test publish -
      https://github.com/pulp/pulp_rpm/pull/1429
      -

         It initiates the installation
         -

         Needs comps.xml for getting groups of packages on software
         selection
         - Will also be unblocked by custom metadata support
         -

   Custom repository metadata update (fabricio)
   -

      Ready to review:
      -

         Model - https://github.com/pulp/pulp_rpm/pull/1438
         -

         Sync - https://github.com/pulp/pulp_rpm/pull/1439
         -

      Working on publish
      -

   Modularity update (ppicka)
   -

      Sync almost there, pulpcore-plugin needs adjustments
      -

      Started with adjusting tests for travis to pass
      -

      CI needs more packages to be installed, dkliban to solve it
      -

   Comps.xml update (dana)
   -

      Model relations discussed last time added
      -

      Sync almost complete
      -

      Need to add the actual interaction with libcomps to parse the files,
      similar to that w/ createrepo_c for Packages


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   -

   Triage etherpad https://etherpad.net/p/rpm_triage_grooming
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190912/97a9ef51/attachment.htm>


More information about the Pulp-dev mailing list