[Pulp-dev] RPM plugin meeting notes

[Daniel Alley]

### November 19, 2020

AI review: none

Pulp 3:

* Do we need to generate SQLiteDBs at all?
 * https://pulp.plan.io/issues/7851
 * https://pulp.plan.io/issues/7852
 * https://pulp.plan.io/issues/7842
 * introduce a switch, the default is not to generate sqlite metadata

* black PR: https://github.com/pulp/pulp_rpm/pull/1882

Pulp 2:
 * worked with Zhenech on releasing pulp_rpm-2.21.4-2 to fix [7849](
https://pulp.plan.io/issues/7849)
 * released today
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Daniel Alley]

### October 29, 2020

AI review: none

Pulp 3:

 * Need to be able to specify a custom 'gpgkey' string for a Publication.
 * Should do a new release - any blockers?
   * check for deprecations in pulpcore that affect the plugin
   * decide at next week's meeting

Pulp 2:

 * 2.21.4 release progressing w/pcreech

Open PRs:
 * https://github.com/pulp/pulp_rpm/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_rpm/issues?query_id=159
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Daniel Alley]

AI review: none

Pulp 3:
 * Content upload API improvement: https://pulp.plan.io/issues/7708
 * Valid UX problem, could be difficult to fix "correctly"
 * Potentially changes necessary to the task response
 * Pulp 4 change?
 * Multi-repo copy issues: https://pulp.plan.io/issues/7625
 * Investigation in-progress, could either be an RPM plugin issue or a
Migration-from-Pulp2 issue

Pulp 2: none

Open PRs:
 * https://github.com/pulp/pulp_rpm/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_rpm/issues?query_id=159
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Also available here: https://hackmd.io/@pulp/rpm_meeting

Pulp 3:
 * Sprint items https://pulp.plan.io/projects/pulp_rpm/issues?query_id=161
 * Grant will work on the copy issue and a pulp2 bug which already has
a patch to support Amazon Linux repositories
 * Pavel will likely cover the rest of the issues in the NEW state

Pulp 2:
 * 2.21.4 Release incoming
 * https://pulp.plan.io/projects/pulp/wiki/2214_Release_Schedule

Open PRs:
 * https://github.com/pulp/pulp_rpm/pulls

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

3-month planning prep (Jan-Mar):
 * RBAC - likely will still be not fully done
 * mirror repodata - Tanya needs to send a followup from PulpCon
 * auto-publish - likely a small amount of work
 * zchunk - can we squeeze it in?
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Also available here: https://hackmd.io/@pulp/rpm_meeting

AI review:


   - github merge options - done

Pulp 3:

   - As a Pulp Rpm user, I can have my repository synced, auto published
   and distributed https://pulp.plan.io/issues/7622
  - need to add more details before grooming
   - Pulp does not resync yum metadata files on change
   https://pulp.plan.io/issues/7030
  - pulp 2 gap
  - false positive no-op sync
  - add to the sprint

Pulp 2:

   - Impacted by https://pulp.plan.io/issues/7445
  - Grant will open a cloned issue/PR #soon

Open PRs:

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

Un-triaged bugs:

   - https://pulp.plan.io/projects/pulp_rpm/issues?query_id=159
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Also available here: https://hackmd.io/@pulp/rpm_meeting

General:


   - github merge options
  - leave only rebase option

Pulp 3:

   -

   https://pulp.plan.io/issues/7537
   - Would like to get into the pulp_rpm 3.8 if possible
 - +1
 - depending on the effort it might push back RBAC work
  -

   https://pulp.plan.io/issues/6926
   - does it depend on the changes which are needed in pulpcore?
 - can be worked on independently
  -

   https://pulp.plan.io/issues/7431
   - treat dist tree/comps as other content?
 -  yes

Pulp 2:

   - when reviewing Pulp 2 PRs, make sure to remove “Needs cherry-pick”
   label

Open PRs:

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

Un-triaged bugs:

   - https://pulp.plan.io/projects/pulp_rpm/issues?query_id=159
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Also available here: https://hackmd.io/@pulp/rpm_meeting

AI review:

   - ttereshc to investigate slow sync/publish for smart proxies in pup2
   - ggainey to look at power kickstart https://pulp.plan.io/issues/7303

Pulp 3:

   - proxy issue https://pulp.plan.io/issues/7321
   - distribution tree orphan cleanup problem
   https://pulp.plan.io/issues/7440
  - ugly “half-solution” https://github.com/pulp/pulp_rpm/pull/1836
  - ideas are welcome

Pulp2:

   - F32 sync issue https://pulp.plan.io/issues/7449
  - close, upgrade to pulp3

Open PRs:

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

Un-triaged bugs:

   - https://pulp.plan.io/projects/pulp_rpm/issues?query_id=159
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Also available here: https://hackmd.io/@pulp/rpm_meeting

AI review

   - ask katello if 3.6.1 release is needed 3.6.1. is out

General:

   - commit bit for ggainey
  - agreed

Pulp 3:

   - https://pulp.plan.io/issues/7298
  - put on the sprint for investigation for import/export issue vs
  duplicates handling
   - dep solving fixtures for katello
  - remove from the sprint, iballou will likely work on it
   - malformed oracle repository (module arch is missing sometimes)
  - still open but on QE
   - proxy issue https://pulp.plan.io/issues/7321
  - ppicka is on it, not reproduced so far
   - FIPS proposal

Pulp 2:

   - slow sync/publish for smart proxies
  - suspicion is that errata make publish operational more often than
  needed
  - might be related to the timestamp fixes in 2.21
  - ttereshc to investigate
   - power kickstart https://pulp.plan.io/issues/7303
  - ggainey to look into next week
  - need a URL to sync from

Open PRs:

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

Un-triaged bugs:

   - https://pulp.plan.io/projects/pulp_rpm/issues?query_id=159
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Also available here: https://hackmd.io/@pulp/rpm_meeting

AI review


   - ttereshc will create a hackmd doc for agenda/notes
   - ttereshc to take a look at pulp-internal list about fixing checksum
   mismatch

Pulp 3:

   - 3.6.1
  - file downloader is fixed
  - ask katello if release is needed
   - dep solving issues
  - one is on hold, waiting on libsolv maintainer reply
  - another is in progress
   - malformed oracle repository (module arch is missing sometimes)
  - https://bugzilla.oracle.com/bugzilla/show_bug.cgi?id=17353 (assigned
  state as of today)
   - dep solving fixtures for katello https://pulp.plan.io/issues/7333
  - Do these fixtures make sense to have at fixtures.pulpproject.org?
  in other words, would they benefit Pulp as well?
  - If so, maybe ask iballou for a PR? I (david) can do this.
 - +1 to add them

Open PRs:

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

Un-triaged bugs:

   - https://pulp.plan.io/projects/pulp_rpm/issues?query_id=159
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

The agenda with the meeting notes are now public
https://hackmd.io/@pulp/rpm_meeting.
Feel free to add any items which require RPM mini-team attention. We meet
once a week to go through the agenda items.

Notes from yesterday:

Pulp 3:

   - As a user, I want to be able to use ansible to manage a pulp rpm repo
   https://pulp.plan.io/issues/7222
   - What if we move this agenda to hack.md? +1
  - ttereshc will create a doc - done
   - 3.6 release
  - Likely Tuesday, Aug-18

Pulp 2:

   - How do we address PRs that are features
   https://github.com/pulp/pulp_rpm/pull/1799
  - solved
   - Email on pulp-internal list about fixing checksum mismatch
  - ttereshc to take a look

3-month planning prep:

   - Current plans (Jul-Sep)
  - RBAC (postpone?)
  - Zchunk support (postpone?)
  - Known bugs for Katello
  - Import/export
   - Sep-Nov planning
  - RBAC (if not done earlier)
  - Known bugs for Katello
  - Candidates (vote with +1s):
 - Items from previous planning which are not complete
- RBAC
- Zchunk support - postpone
 - As a user I can set/update repo_gpgcheck and gpg_check options
 https://pulp.plan.io/issues/6926 +1 to add +1+1 +1 +1
 - RPM signing and re-signing https://pulp.plan.io/issues/1686 +1
 - As a user, I can do a one-shot upload of custom repository
 metadata https://pulp.plan.io/issues/5433 +1 +1
 - As a user, I can view sub repositories
 https://pulp.plan.io/issues/5556
 - As a user, I want to be able to use ansible to manage a pulp rpm
 repo https://pulp.plan.io/issues/7222 - dkliban plans to work on
 it soon as a part of CLI effort +1 +1 +1
 - FIPS +1 +1
 - https://pulp.plan.io/issues/5510 - notes/tags +1 +1

Open PRs:

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

Un-triaged bugs:

   - https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Distribution Tree model changes
   -

  https://github.com/pulp/pulp_rpm/pull/1782
  -

   3.5 branching/release once DistTree change is merged
   -

   UpdateCollection model fixes and uniqueness - in progress


Pulp 2:

   -

   https://pulp.plan.io/issues/7141 - closed as works for me, but
   continuing to investigate with Katello devs to find a different reproducer


Open PRs:

   -

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


Triage:
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

AI review

   -

   ddavis to update 7096  with more
   explanation
   -

   Bmbouters to add comment to 7095 
   -

   Ppicka/dkliban to investigate 5847 
   (fix merged)


Pulp 3:

   -

   import/export
   -

  Natural-keys change waiting on 3.5 branch
  -

  UpdateCollection is going to be A Pain
  
  -

   3.5 compatible release
   -

  Kickstart-model-changes necessary before pulp_rpm 3.5 can happen
  -

  3.4.z compatible with pulpcore 3.5 - releasing today


Pulp 2:

   -

   smart proxy sync issue with mismatching checksum types
   https://access.redhat.com/solutions/5224911
   -

  ttereshc to review the pulp part
  -

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

  https://github.com/pulp/pulp_rpm/pull/1772
  -

  dkliban has a PR to fix this and then investigate how users will fix
  their existing installs. Either as part of ‘force’ sync or a separate
  script.


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Grant Gainey]

AI review

   -

   AI: ppicka to discuss relative-path investigation with Many Interested
   Parties, This meeting.
   -

   AI: daviddavis to file an issue RE “repo can have more than one
   distribution tree”
   -

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

Pulp 3:

   -

   Distribution tree copy bug https://pulp.plan.io/issues/7046
   
   -

  High prio
  -

  Needs some to pick it up
  -

   Relative_path (possibly) extend by https://pulp.plan.io/issues/5847
   -

  We need to be able to sync RHEL8, by 3.6 release
  -

  Needs discussion at mtg-end
  -

   import/export natural-keys
    - doc
   reviewed
   -

   Discussion around three-month-roadmap


Open PRs:

   -

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

   Dist-trees PR/createrepo_c hate each other, test needs to be fixed a
   diff way


Triage:

   -

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


AI:

   -

   ddavis to update 7096  with more
   explanation
   -

   Bmbouters to add comment to 7095 
   -

   Ppicka/dkliban to investigate 5847 
   -

  Talk to RHEL/Platform/katello team to figure out what’s going on?


G
-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

AI review

   -

   AI: dkliban will add commentary to issue
   -

  https://pulp.plan.io/issues/7046#note-3

Pulp 3:

   -

   Distribution tree copy bug https://pulp.plan.io/issues/7046
   
   -

  High prio
  -

   “retain_package_versions”
   -

  PR review needed https://github.com/pulp/pulp_rpm/pull/1752
  -

   RepoMetadataFIle issue (potentially relative_path problem)
   https://pulp.plan.io/issues/5847
   -

  High prio, needs to be resolved very soon
  -

  Need to come up with a ‘clever’ workaround, not to affect db and
  further migraitons
  -

  AI: ppicka to discuss investigation with interested parties, soon
  -

   Recursive copy
   -

  Copy prepared (depends on retain old PR)
  -

   Review next week for import/export natural-keys
    - please
   review and send comments/questions
   -

   It looks like a repo can have more than one distribution tree? How does
   this work?
   -


  
https://github.com/pulp/pulp_rpm/blob/546da71b4b7bb8fc2af57213b3249a409880401c/pulp_rpm/app/models/distribution.py#L89-L96
  -

  Should be only one
  -

  AI: daviddavis to file an issue


Open PRs:

   -

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


Triage:
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Kickstarts copy issue https://pulp.plan.io/issues/7046
   -

  Lots of discussion
  -

  AI: dkliban will add commentary to issue
  -

 https://pulp.plan.io/issues/7046#note-3
 -

   Retain old count
   -

  Basically done - writing a test, might rename the field
  -

 https://github.com/pulp/pulp_rpm/pull/1752
 -

AI: feedback is needed for the naming of user facing
configuration parameter
-

  Need to do a little more thinking about whether we can share an
  install of the extension with Katello or if we should just dump
the entire
  extension into the database ourselves with raw SQL
  -

 Katello has an RPM that provides it
 -

 If install custom-type via rpm, still need migration to take
 advantage of it
 -

Django can note existence/lack-thereof of a plugin
-

   Comps.xml relations removal and recursive copy
   -

  Copy is in progress, looks good so far
  -

  It’s preferable if all changes go together into one Y release
  -

   Mirrored metadata 
   -

  No time to move this forward
  -

  ttereshc will try to move it forward, had a knowledge/ideas dump from
  dkliban earlier today


Pulp 2:

   -

   2.21.3 - dev freeze today, beta - on Tuesday


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

AI review

   -

   discuss if other relations for comps needs to be removed or only
   packages to groups
   -

   bmbouter to remove  ‘Pulp3 RPM blocker’ tag
   -

   dkliban to try to come up with rough design during the sprint
   https://pulp.plan.io/issues/5200
   -

  started
  -

   dkliban to reach out to productmd dev https://pulp.plan.io/issues/6568
   -

   ttereshc to look at response/patch
   https://bugzilla.redhat.com/show_bug.cgi?id=1743776#c13


Pulp 3:

   -

   Retain old count
   -

  Q: how to install evr_t plugin for postgres?
  -

 Extension vs raw-migration
 -


 
https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/migrations/0004_add_fulltext_search_indexes.py
 -

  Django doesn’t like fields it doesn’t ‘own’
  -

 There exists a read-only extension for django
 -

 Needs to be installed by pulpcore?
 -

If used by one plugin only, it’s better to install as a part of
the plugin
-

see what pulp-ansible is doing :

https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/settings.py#19


-

   Mirrored metadata 
   -

  dkliban to continue working on rough design
  -

   daviddavis working on export of kickstarts
   -

   https://pulp.plan.io/issues/7004 (pulpcore/fixtures) blocks sles auth
   token test


Pulp 2:

   -

   2.21.3
   -

  mainly applicability regression fix
  -

  ttereshc to be a release shepherd


Open PRs:

   -

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

   Needs review
   -

   https://github.com/pulp/pulp_rpm/pull/1725
  -

 dkliban to look at it
 -

  https://github.com/pulp/pulp_rpm/pull/1745
  -

 dalley to look at it


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   comps.xml relation issues
   -

  PR for PackageGroups which removes relations completely
  -

 https://github.com/pulp/pulp_rpm/pull/1745
 -

 Backward incompatible change in REST API
 -

Ok, because it’s a bug fix
-

Likely no usage outside of copy which can handle it without
knowing the relations
-

AI: discuss if other relations for comps needs to be removed or
only packages to groups
-

   Rethinking SLES Remote as a separate Remote
   -

  Maybe it’s not more usable?
  -

  https://github.com/pulp/pulp_rpm/pull/1729#issuecomment-641478315
  -

 Keep one Remote
 -

 Make parameter name specific - sles_auth_token
 -

 Have one rpm specific downloader, don’t call it anything specific,
 so in the future we can add more functionality to it to avoid
the case with
 mutually exclusive downloaders
 -

   Do we still need the ‘Pulp3 RPM blocker’ tag or can we remove it?
   -

  We can remove it - bmbouter will handle it
  -

   Do we have any timeline for https://pulp.plan.io/issues/5200
   -

  dkliban to try to come up with rough design during the sprint
  -

   Client certs w/ Remote (newline problem)
   -

  Need to use at notation (@~/file) not a string for correct process of
  control chars
  -

   CentOS 8 kickstart repo bug - https://pulp.plan.io/issues/6568
   -

  dkliban to reach out to productmd dev


Pulp 2:

   -

   Failed content view deletions
   -

  https://bugzilla.redhat.com/show_bug.cgi?id=1743776#c13
  -

  https://git.io/Jf98f
  -

  AI: ttereshc to look at response/patch


Open PRs:

   -

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


Triage:

   -

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

  Didn’t have time to cover it, will do it online today or on Monday
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Ina Panova]

AI review:

   - None

Pulp 3:

   -

   Mirrorlist feature
   -

  Lubos updated PR, ipanova to review
  -

   Progress report. Seems like GroupProgressReport proposal is ok
   -

  Please provide feedback if there is any. ipanova to groom and put on
  the sprint the story after.
  -

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

   Retain old count - planning
   -

  Daniel is still looking into this→  talk to Ian
  -

  Katello has a 3rd implementation besides the two here that we should
  probably use (apparently much faster, also, Katello is using it already)
  https://pulp.plan.io/issues/5950
  -

   SLEs support
   -

  PR up, needs review


   - Bugs
  - (solved) Dep solving for katello https://pulp.plan.io/issues/6820

Pulp 2:

   -

   No-op syncs taking 80 seconds. Any way to optimize this?
   -

  What size is the metadata?
  -

  https://github.com/pulp/pulp_rpm/pull/1558


Open PRs:

   -

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


Triage:

   -

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



Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

AI review

   -

   dalley to email amatej w/r to the drpm library support
   -

   dkliban takes AI to write up cert-getting ticket
   -

   ppicka to talk to dkliban and file an issue about suse auth token
   -

   ttereshc to file an issue about import/export
   -

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

   ipanova to review mirror list support
   -

  Started, needs more input from the team
  -

   ipanova to reply to user on the pulp-list about upgrade issues from rc
   to the latest ga


Pulp 3:

   -

   Features
   -

  SUSE repos, auth token
  -

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

 Agreed to have a separate Remote and require auth token
 -

 No new problems for migration but need to add the support
 -

 Need to discuss with Katello
 -

  Retain old count - planning
  -

  DRPM support NOT needed - Katello is dropping the feature with 4.0/4.1
  -

  Mirrorlist support
  -

 Design proposal:
 https://github.com/pulp/pulp_rpm/pull/1690/files#r431910746
 -

   Bugs
   -

  Dep solving for katello https://pulp.plan.io/issues/6820


Open PRs:

   -

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


Triage:

   -

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


Sprint planning prep:

   -

   Dep solving for katello https://pulp.plan.io/issues/6820 - Daniel or
   Grant
   -

   SUSE auth - Pavel
   -

   Retain old count - design/planning - Daniel (if priorities permit)
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   AI review
   -

   3.3.2 is out with the upgrade fix
   -

   Features
   -

  SUSE repos, auth token
  -

  Retain old count 5367 
  -

 EVR comparison
 -

Ggainey’s cut at it


-

Ian Ballou started w/the above, but I believe he has a better
answer now?
-

 Ggainey to add some interesting edge cases
 -

See 5367#note-11  and
5367#note-12 
-

 Need a proper planning for this feature
 -

  Mirror metadata/relative path timeline
  -

 daviddavis to ask jsherrill about the pulpcore version
 -

 jsherrill: need this by august (pulpcore 3.5 or 3.6)
 -

  Import/export
  -

 Need to add all advisory models to the IMPORT_ORDER
 -

 Distribution trees are not handled properly yet but it’s a known
 gap
 -

   Tests
   -

  Coverage
  -

 Hook for PRs in place
 -

  High prio tests are identified and being worked on
  -

 as of now, only ‘copy’ tests missing from prio identified
 -

  This is the last week of test-only work
  -

   Docs
   -

  Tested in CI, thanks Fabricio
  -

  Copy API docs are merged
  -

   AI:
   -

  dalley to email amatej w/r to the drpm library support
  -

  dkliban takes AI to write up cert-getting ticket
  -

  ppicka to talk to dkliban and file an issue about suse auth token
  -

  ipanova to review mirror list support
  -

  ttereshc to file an issue about import/export
  -

  ipanova to reply to user on the pulp-list about upgrade issues from
  rc to the latest ga


Pulp 2:

   -

   2.21.2 is out
   -

  Except docs, travis issue


Open PRs:

   -

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


Triage:
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

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

  Core change
  -

  bmbouter to put a complete proposal
  -

   Release 3.3.1 is out, 3.3.2 is planned
   -

   Features
   -

  Estimate for mirroring metadata https://pulp.plan.io/issues/6353
  -

 Relative_path needs to be addressed to do this
 -

 Somewhere around 1-3 staff months/2 months.
 -

  Remaining features for Katello 4.0
  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=155
  -

 File task to skip drpms during sync
 -

 Daniel email amatej w/r to the drpm library support
 -

   Tests
   -

  Coverage
  -

 Hook and markdown form in WIP https://pulp.plan.io/issues/6706
 - RHEL repos
  -

 Users reporting problems only seen when consuming RHEL-CDN repos
 -

 Add debug-cert to secrets, have a nightly test against RHEL
 -

 Needs a test-specific/pulp-bot-owned cert-ticket opened
 -

 ttereshc takes AI to write up issue
 -

 dkliban takes AI to write up cert-getting ticket
 -

  Upgrade tests
  -

 Pulp_rpm_prerequisites CI tests upgrade, but it not test database
 migration (as it does not have data)
 -

 https://hackmd.io/Bz6cLGRCSMmnCLDvhnBWtg?both
 -

 Have upgrade tests with data in the db
 -

 Potentially run in CI for https://github.com/pulp/pulp-oci-images/
 -

 AI to write a task
 -

  SSL cert test https://pulp.plan.io/issues/6735
  -

 Needs “RHEL repos” above, to really have tests
 -

   Docs
   -

  RPM copy API documentation PR:
  https://github.com/pulp/pulp_rpm/pull/1706
  -

  REST API docs are out of date, don’t forget to push fresh api.json if
  you make any changes affecting it
  -

 (dalley) I’m doing this in the copy docs PR
 -

 (david) I am never going to remember to do this. Can we add
 https://pulp.plan.io/issues/5541 to next sprint?
 -

Discuss at open floor
-

   Priorities


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Release 3.3.1
   -

  Yes, the sooner the better, some critical bug fixes are merged
  -

   Features
   -

  Mirrorlist support
  -

 Needs review https://github.com/pulp/pulp_rpm/pull/1690
 -

  config.repo feature from @lieter
  -

 https://github.com/pulp/pulp_rpm/pull/1687
 -

 It seems like only one functional test left to be done
 -

   Tests
   -

  Ran into travis failure due to test importing directly from pulpcore
  -

 6682
 

 opened to update plugin-writers-guide to help avoid in the future
 -

  Coverage of features (internal doc at the moment)
  -

 Needs a “last revised” somewhere obvious
 -

 It would be nice to keep a list like this somewhere ‘public’
 -

Example: A markdown+1/rst doc in the project, with a list of
testcases and the use-case they are testing
-

Would get “out of sync” over time and need regular revisiting,
but would be a starting-point for a) tracking coverage, b)
publically/transparently
-

Automation to prompt (not require) dev to update test list when
test files are modified? (only if it would be simple, like
“touch any file
in this subdirectory, drop a comment) +1
-

   Kickstart issues
   -

  All known ones are filed
  -

 https://pulp.plan.io/issues/6629 - can’t remove a kickstart repo
 -

Need to check if it was the main repo or the sub repo which is
being removed
-

@dkliban to comment
-

 https://pulp.plan.io/issues/6683 - migrated kickstart repo missing
 treeinfo file after first sync by pulp 3
 -

   Docs
   -

  Copy API docs are close to be ready
  -

  They don’t block 3.3.1, docs can be published asynchronously
  -

   Priorities
   -

  Continue on tests and review of the feature PRs
  -

  Next sprint - start looking into major features for the Katello
  3.18/4.0 release
  -

 @ttereshc to prepare a list of features that needs to be done for ^


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] RPM plugin meeting notes

[Robin Chan]

>
>
>-
>
>From now on, add functional tests at the same time as features
>-
>
>   At least a happy path
>
> +1 - Let's start building this into feature delivery estimates and
commitments to stakeholders

Robin Chan

She/Her/Hers

Satellite Software Engineering Manager - Pulp

Red Hat 

IRC: rchan




On Thu, Apr 30, 2020 at 12:37 PM Tatiana Tereshchenko 
wrote:

> Pulp 3:
>
>-
>
>3.3.0 is released
>-
>
>From now on, add functional tests at the same time as features
>-
>
>   At least a happy path
>
> +1 - Let's start building this into feature delivery estimates and
commitments to stakeholders


>
>-
>
>List of RPM features to test and/or to ensure are present in the docs
>-
>
>   AI: Please review areas you are familiar with and which you think
>   deserve a happy-path test or a note in the docs
>   -
>
>Reminder: relative path problem still unsolved, another meeting on
>Monday to discuss
>-
>
>Features
>-
>
>   Mirrorlist support from @lmjachky
>   -
>
>  https://pulp.plan.io/issues/6225
>  -
>
>  In progress https://github.com/pulp/pulp_rpm/pull/1690
>  -
>
>   config.repo feature from @lieter
>   -
>
>  There is a problem with determining the name of the public key
>  file
>  -
>
> AI: dkliban will send a note to list about needing to
> strengthen the interface for signing services. Will for now 
> provide docs
> that recommend using a specific name for a public key.
>
>
> Pulp 2:
>
>-
>
>All 2.21.2 items are done.
>-
>
>   dalley is taking care of it instead of dkliban
>   -
>
>Need to reply to Katello
>-
>
>   CentOS 8 kickstarts  https://pulp.plan.io/issues/6470
>   -
>
>   can't be fixed in pulp2, will be fixed in pulp 3, dkliban to reach
>   out to Katello
>
>
> Open PRs:
>
>-
>
>https://github.com/pulp/pulp_rpm/pulls
>
>
> Triage:
>
>-
>
>Un-triaged bugs
>https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
>
>
>
> Sprint planning prep:
>
>-
>
>planned to be worked on during sprint and estimated time for each
>-
>
>   ppicka - tests planning/implementation (full time)
>   -
>
>   dkliban - kickstarts issues (1 day)
>   -
>
>   dalley - pulp 2 release (1 day)
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   3.3.0 is released
   -

   From now on, add functional tests at the same time as features
   -

  At least a happy path
  -

   List of RPM features to test and/or to ensure are present in the docs
   -

  AI: Please review areas you are familiar with and which you think
  deserve a happy-path test or a note in the docs
  -

   Reminder: relative path problem still unsolved, another meeting on
   Monday to discuss
   -

   Features
   -

  Mirrorlist support from @lmjachky
  -

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

 In progress https://github.com/pulp/pulp_rpm/pull/1690
 -

  config.repo feature from @lieter
  -

 There is a problem with determining the name of the public key file
 -

AI: dkliban will send a note to list about needing to
strengthen the interface for signing services. Will for
now provide docs
that recommend using a specific name for a public key.


Pulp 2:

   -

   All 2.21.2 items are done.
   -

  dalley is taking care of it instead of dkliban
  -

   Need to reply to Katello
   -

  CentOS 8 kickstarts  https://pulp.plan.io/issues/6470
  -

  can't be fixed in pulp2, will be fixed in pulp 3, dkliban to reach
  out to Katello


Open PRs:

   -

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


Triage:

   -

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



Sprint planning prep:

   -

   planned to be worked on during sprint and estimated time for each
   -

  ppicka - tests planning/implementation (full time)
  -

  dkliban - kickstarts issues (1 day)
  -

  dalley - pulp 2 release (1 day)
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   3.3.0 release is on the way (various issues along the way which didn’t
   let to release earlier)
   -

   Focus on bug fixes and tests
   -

   Features
   -

  Lubos started on mirrorlist support
  -

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

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

 Feedback is needed


   -

   Tests
   -

  Advisory tests
  -

  Plan to do some coverage report experiments
  -

   Need to move QueryModelResource to the plugin API
   -


  
https://github.com/pulp/pulpcore/blob/master/pulpcore/app/modelresource.py#L12
  -

  Will break plugins (ie pulp_file and pulp_rpm) when pulpcore 3.4
  releases since they are importing it from pulpcore.app
  -

  Our proposal: import it into the plugin API but leave it in core. ove
  it in a future release (3.5+).
  - Plugins get pinned to pulpcore<3.4 on release so we can just move
 the model to the plugin api.
  -

   Validating content in Stages
   -

  Validate content in the first stage? Should be ok for RPM
  -

  Follow up on pulp-dev mailing list to discuss with other plugins
  -

   pulp_rpm_prerequisites release process: Where to document?
   -

  Either add to main pulpcore (which describes plugins generically)
  doc, or create a separate doc prereqs roles.


Pulp 2:

   -

   ttereshc tries to finish today
   -

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

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

   next is applicability issue https://pulp.plan.io/issues/6387


Open PRs:

   -

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


Triage:

   -

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

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

 Needs to be resolved this or next sprint (3 weeks till Katello
 release)
 -

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

 Needs to be tested with real S3 and not minio to be sure that it’s
 not a minio specific issue.
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Query for the upcoming release
   -

  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149
  -

 Copy API docs
 -

Maybe we can publish them after the release? +1
-

 PR reviews
 -

   “Relative_path” problem
   -

  https://www.redhat.com/archives/pulp-dev/2020-April/msg0.html
  -

  Need to come back to it and bump the thread
  -

  Will be discussed at the pulpcore meeting
  -

   Import/export
   -

  Main path works, tech-preview in 3.3
  -

 pulp_file/pulp_rpm happy-path available
 -

  Docs in progress
  -

  Setting up handoff mtg w/katello next week
  -

 Public invite to list
 -

 Dennis volunteered to manage accepts
 -

 Invite QE folks
 -

   Katello timeline and deliverables
   -

  Ask if anything is unclear
  -

   3.3.0 release
   -

  Monday or Tuesday
  -

  Daniel to take care of the release
  -

   Testing publish task
   -

  Easy to test using the REST API:
  
https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/tests/functional/api/test_publish.py#L347
  -

  Problem: how to test publish task directly? How to emulate a synced
  repo? (Unit and Functional tests run on different places on CI)
  - Brian to write a proposal to solve this type of testing problems


Pulp 2:

   -

   Both items from last week needs to be taken care of
   -

  for the RPM migration to Pulp 3
  -

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

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

  CentOS directory KS structure is no longer RH compatible
  -

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

 the same problem in Pulp3
 - Dennis to test more and file an issue if needed


Open PRs:

   -

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


Triage:

   -

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


Tests:

   - Pulp 3 https://pulp.plan.io/projects/pulp_rpm/issues?query_id=153
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Query for items to be done for Katello release
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149
   -

  Priorities for Katello from the items which are not merged
  -

 Checksum type configuration for a publication
 - more tests added
- ready for review
 -

 Kickstart copy
 -

https://pulp.plan.io/issues/5207 - POST, awaiting review
-

 Issue with advisory checksum type
 -

https://github.com/pulp/pulp_rpm/pull/1667
-

proceed with the string representation
-

ready for review
-

   Import/export
   -

  On track for a first pass for pulpcore 3.3
  -

  Hope to have RPM integration by then or shortly thereafter
  -

  Need feedback about how to handle content dependencies
  -

 https://www.redhat.com/archives/pulp-dev/2020-April/msg00015.html
 -

   Features
   -

  Publish layout Packages + Opensuse support
  -

 Merged
 -

  Advisory version is considered at conflict resolution time
  -

 Advisory doesn't seem to be checked for conflicts at upload time
 (with repository specified)
 - ppicka to test thoroughly if it's the case
 -

  Mirror metadata discussion, aka "relative_path" problem
  -

 Bump email discussion next week


Pulp 2:

   -

for the RPM migration to Pulp 3
   -

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

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

  Need to fix it next week
  -

   CentOS directory KS structure is no longer RH compatible
   -

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

  need someone to look at it next week
  -

  potentially a problem with pulp2 only (hopefully)


Open PRs:

   -

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


Triage:

   -

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


Tests:

   - Pulp 3 https://pulp.plan.io/projects/pulp_rpm/issues?query_id=153
  - Opinions differ on how good the current test coverage is
  - Need to find a way to identify gaps, hopefully work on coverage
  report will be back on track soon
  - Focus on tests after 3.3, no capacity to look at it right now
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   “Relative_path” problem
   -

  https://www.redhat.com/archives/pulp-dev/2020-April/msg0.html
  -

  Doesn’t block critical work
  -

   Query for items to be done for Katello release
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149
   -

  Priorities for Katello from the items which are not merged
  -

 Checksum type configuration for a publication (needs review)
 -

 Kickstart copy (volunteer is needed)
 -

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

That issue could probably use some more detail
-

Start by writing a test
-

 OpenSUSE support (not blocked, needs review)
 -

   Import/export
   -

  Import PR up
  -

  Export-backend PR going up today
  -

   Other features
   -

  Copying a package group auto-copies packages that are members of it
  -

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

 Not a priority, but needs to be addressed eventually
 -

  Publish layout Packages/
  -

 Potentially  blocked by relative_path problem but it’s not a
 critical feature and can wait


Open PRs:

   -

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


Triage:

   -

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

  OOM kill for https://packages.microsoft.com/rhel/7/prod/

Tests:

   - Pulp 3 https://pulp.plan.io/projects/pulp_rpm/issues?query_id=153
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   A query for items to be done for Katello release
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149
   -

  Waiting on Katello to review and mark what is needed for the
  early-April release
  -

   DRPM support
   -

  Likely is needed for Katello 4.0/4.1
  -

   Import/export
   -

  ggainey filling out export backend
  -

  daviddavis working on importer/import
  -

  Take a look at 6329  and
  comment if you have thoughts
  -

  agreed on Master/Detail approach

  -

   Other features
   -

  Publish layout Packages/x
  -

 a/name.rpm and b/name.rpm situation
 -

 Consider storing relative_path outside of ContentArtifact or
 Package model
 -

 Mirror repository story - https://pulp.plan.io/issues/6353
 -

  Opensuse
  -

 Done but depends on publish layout above
 -

  Configuration of a checksum type for a publication
  -

 PR is up and needs review



   -

   Tests
   -

  Will try to focus on it after the features for the upcoming Katello
  release


Pulp 2:

   -

   Applicability issue
   -

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

   Reminder from last week
   -

  Needs to be fixed in pulp2, required for the RPM migration to Pulp 3
  -

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

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

 Will go into 2.21.z release


Open PRs:

   -

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


Triage:
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Copy
   -

  In 3.3.0 beta 1
  -

   Import/export
   -

  Initial CRUD for Exporter in progress.
  -

  PR should be ready for review today hopefully. Debugging an openapi
  issue.
  -

   Other features
   -

  Opensuse
  -

 Open issue against productmd
 -

ppicka and fao89 to discuss
-

 Same nevra packages issue (pulp-dev-mailing-list)
 -

One option is to have a separate type of a repository for SUSE
-

   AI: run by Katello
   -

nosrc is (should be) a valid arch
-

   AI: talk to #suse
   -

AI: gather user cases, email pulp-list and PMs
-

  Sync optimizations
  -

 Merged
 -

 Automating tests
 -

   Tests
   -

  Query: https://pulp.plan.io/projects/pulp_rpm/issues?query_id=153
  -

  Started with tests originated by bugs:
  
https://github.com/pulp/Pulp-2-Tests/search?q=selectors.bug_is_fixed_q=selectors.bug_is_fixed



Pulp 2:

   -

   Applicability performance, patches accepted from CEE
   -

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

   Needs to be fixed in pulp2, required for the RPM migration to Pulp 3
   -

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

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

  Will go into 2.21.z release


Open PRs:

   -

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

  Reviews are needed!
  -

 Opensuse kickstart support
 https://github.com/pulp/pulp_rpm/pull/1639
 -

 Modularity sync fix https://github.com/pulp/pulp_rpm/pull/1649


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Forgot to add for Pulp 3:

   - Metadata signing merged - https://pulp.plan.io/issues/4812


On Thu, Mar 12, 2020 at 5:43 PM Tatiana Tereshchenko 
wrote:

> Pulp 3:
>
>-
>
>Copy
>-
>
>   Merged, waiting on testing from Katello
>   -
>
>   Beta may be released ‘today’
>   -
>
>Tests
>-
>
>   conversion to bindings
>   -
>
>  S3 test has some issues, hte rest are done
>  -
>
>  Finish and get signoff today?
>  -
>
>Features
>-
>
>   Opensuse support
>   -
>
>  Some version issues, treeinfo parsing - otherwise working
>  -
>
>  Treeinfo is ‘productmd problem’ (with validations) - need to
>  work w/ productmd gang to figure out where fix needs to be
>  -
>
>  ppicka to submit WIP PR for review, reach out to productmd
>  -
>
>   Sync optimizations
>   -
>
>  In testing
>  -
>
>Import/export
>-
>
>   High-level stories are in redmine
>   -
>
>   Initial CRUD for Exporter in progress
>   -
>
>   AI: everyone, check out the pulp-dev e-mail and review the design
>
>
>
>-
>
>Pulp_rpm 3.3.0beta1 release today or tomorrow
>
>
> Pulp 2:
>
>-
>
>Applicability performance discussions
>-
>
>Some issues/bzs investigated, likely to close w/no change
>-
>
>   4524  - need to close loop w/paji
>   and then close WONTFIX
>   -
>
>   6327  - users can turn on
>   validate:true to fix their broken /var/lib/pulp directory (see also
>   1775154
>   ) -
>   prob close NOTABUG
>
>
> Open PRs:
>
>-
>
>https://github.com/pulp/pulp_rpm/pulls
>
>
> Triage:
>
>- Un-triaged bugs
>https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Copy
   -

  Merged, waiting on testing from Katello
  -

  Beta may be released ‘today’
  -

   Tests
   -

  conversion to bindings
  -

 S3 test has some issues, hte rest are done
 -

 Finish and get signoff today?
 -

   Features
   -

  Opensuse support
  -

 Some version issues, treeinfo parsing - otherwise working
 -

 Treeinfo is ‘productmd problem’ (with validations) - need to work
 w/ productmd gang to figure out where fix needs to be
 -

 ppicka to submit WIP PR for review, reach out to productmd
 -

  Sync optimizations
  -

 In testing
 -

   Import/export
   -

  High-level stories are in redmine
  -

  Initial CRUD for Exporter in progress
  -

  AI: everyone, check out the pulp-dev e-mail and review the design



   -

   Pulp_rpm 3.3.0beta1 release today or tomorrow


Pulp 2:

   -

   Applicability performance discussions
   -

   Some issues/bzs investigated, likely to close w/no change
   -

  4524  - need to close loop w/paji
  and then close WONTFIX
  -

  6327  - users can turn on
  validate:true to fix their broken /var/lib/pulp directory (see also
  1775154 )
  - prob close NOTABUG


Open PRs:

   -

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


Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Copy API Status (dalley out-of-office)
   -

  General API shape + implementation: done
  -

  Depsolving: done
  -

  Incremental update: done
  -

  Multi-repo-copy: almost done
  -

 just need to hook the backend to the API properly, no serious
 implementation effort required
 -

  Thorough functional tests: discussions taking place
  -

   When do we want Z release
   -

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

  ‘Now’ would be good
  -

   Tests conversion status (ppicka)
   -

  Hopefully today/tomorrow parity w/Pulp2
  -

   Features status (anyone working on features)
   -

  Opensuse support (ppicka)
  -

 started
 -

  Optimize sync (dawalker)
  -

 testing scenarios now
 -

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

 Looking for volunteer
 -

 pulpcore item driven by rpm needs
 -

   Need to test new createrepo_c which supports parsing of xml_snippets
   (needed for the migration plugin)
   -

   Whenever it’s released, we need to publish new version to PyPI



Pulp 2:

   -

   Check applicability and depsolving for modularity multicontext issues



Open PRs:

   -

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


Triage:

   -

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


Sprint planning prep:

   -

   Items planned to be worked on during sprint and estimated time for each
   -

  David
  -

 Copy: 1-2 days
 -

 Importers/exporters 3-4 days
 -

  Pavel
  -

 Opensuse support 1-3 days (hard to say with this one)
 -

 Finish modularity upload or higher prio
 -

  Dana
  -

 Checksum options work, 4 days?
 -

 Available for other work
 -

  Daniel (out today)
  -

 [ttereshc guess] Finishing up Copy work
 -

  Grant
  -

 Import/Export: 5 days
 -

 #4534  (if critical): 2 days
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Copy status
   -

  Depsolving: DONE
  -

  Incremental Update: Almost done
  -

  Multi-repo-copy: Almost done
  -

  API:
  -

 Need to check with Katello that their needs are met
 -

 Need to work out how to accept repositories OR repository versions
 as source, & support base_version on dest
 -

  Questions:
  -

 Do we need distribution tree copy for Katello?
 - Probably.
- We need to check with Katello and test how it works now.
- It's outside of the scope of copy API.
 -

 Do we need to copy Comps children (PackageGroup -> RPMs,
 PackageEnvironment -> PackageGroups, etc.) for Katello?
 -

 No

 -

  Tests: Not nearly enough of them



   -

   Import/export status
   -

  ggainey & daviddavis meeting every day/every-other to brainstorm
  -

  Design doc braindump in progress
  -

  Top-level epic - 6134  - also has
  thoughts
  -

   Tests
   -

   3.x (katello release)
   -

  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149
  -

  Deadlines:
  -

 Beginning of March - to have ability to integrate for major
 features like Copy API
 -

 End of March - GA with all the features complete (bugs can be
 fixed later in Z releases) +  tests
 -

 April - import/export work  (it’s the only exception which is not
 required to finish in March but we aim to finish it in March)
 -

   Bucket of prioritised items outside of any release
   -

  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=148
  -

  Don’t pick up this work unless you can’t contribute to the items
  aligned to a certain release
  -

  Items here are not groomed and descriptions might be outdated. If you
  are willing to work on it, reach out to the group and groom it first.
  -

   Modularity bug, a nasty one, should be fixed soon, on the sprint
   -

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



Pulp 2:

   - Couple of security requests closed, no issues identified


Open PRs:

   -

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


Triage:
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Reminder to mark bugfixes which needs to be cherry picked
   -

  PR author and reviewer should check that
  -

   Remaining features for katello 3.16 which have redmine tickets in new
   and not assigned
   -

  Copy
  -

  Importers/exporters
  -

  OpenSUSE support
  -

 Waiting on createrepo_c
 -

  Maybe we should add mirrorlist support?
  -

 maybe by October
 -

 bmbouter has PoC for it
 -

  Certguard - in progress, bmbouter is on it
  -

  AI: ttereshc to bring katello milestone in redmine up to date, to
  have a prioritised list of issues to work on
  -

   pulp_rpm_prerequisites
   -

  licensing question: PR #35
  , although
  tiny, was submitted before re-licensing. I rebased and amended the commit
  message #38 .
  Do we need the author’s relicense affirmation?
  -

 All good.
 -

  Not auto-importing  to galaxy since
  GHA migration, but I will work on the versioned release instead.



Pulp 2:

   -

   All blockers have been resolved.


Sprint planning prep:

   -

   Items planned to be worked on during sprint and estimated time for each
   -

  fao89 (1-2 days)
  -

 work on bindings problem
 -

 S3 test
 -

  ggainey
  -

 import/export - design/use-cases in progress, 3 days (??)
 -

 Errata-migration discussion(s), 1 day
 -

  daviddavis
  -

 copy: 1-2 days
 -

 importers/exporters: 3 days?
 -

  dawalker
  -

 Finishing optimize sync and optional checksum PRs through merging
 (6055, 4458): 3 days?
 -

 Open to work on whatever is needed the remainder of the sprint
 -

  dalley
  -

 Modulemd and modulemddefault depsolving: 3 days?
 -

 Child unit copy (errata-RPMs, packagegroup-RPMs): 2 days?
 -

 Multi-repo copy: 3 days?
 -

 Testing all of the above properly, including generating better
 fixtures: 5+ days?
 -

 Pre-built binary Python packages: any remaining free time
 -

  bmbouter
  -

 Certguard candlepin support and GA release 3-5 days
 -

  ppicka
  -

 TBD (ppicka was out today)


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Support repos with primary.xml only
   https://bugzilla.redhat.com/show_bug.cgi?id=1627372
   -

  Question is whether to support them or not?
  -

 Probably no, David will comment on the BZ and close in a week if
 there is no disagreement.
 -

 Old issue/discussion https://pulp.plan.io/issues/1287#note-9
 -

   Copy work
   -

  RPM-only depsolving now working
  -

  Libsolv packaged as Python package, querying if upstream is
  interested in the work at all
  -

  Next items:
  -

 Support module & module default depsolving <- Daniel
 -

 Support “standard” advanced copy w/ RPMs referenced by Errata,
 PackageGroups
 -

 Support multi-repo copy
 -

 Support copy by unit href <-David
 -

   pulp_rpm_prerequisites relicensing PR
   
   -

  semi-urgent because we want to publish an actual version to Galaxy
  
  -

  Only 1 author missing review or “I affirm” message: bmbouter (on PTO)
  -

  About half of people wrote “I affirm the re-licensing” or similar.
  -

  Plan to go to rchan after all reviews


Pulp 2:

   -

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

  Patch ready, needs to be tested
  -

  GA blocker


Open PRs:

   -

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

   good job on closing/merging PRs



Triage:
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Copy API work
   -

  No change since last meeting, David out, Daniel doing other work
  -

   Libsolv python 3 bindings (python3-libsolv subpackage RPM)
   -

  Also missing .egg-info / .dist-info
  -

  Probably possible to package as a Python package, not done yet, on
  backburner
  -

  To get RPM for py3-bindings need to file a BZ - should be able to get
  into next RHEL; until then, katello would need to carry
  - Everyone has issues to work on, no one is blocked


Pulp 2:

   -

   Dep solving bugs
   -

  Grant sent a doc with his evaluation of dep solving bugs
  -

  No blockers


Open PRs:

   -

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

   a lot of PRs, need review



Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

>From last week.


Pulp 3:

   -

   Distribution trees (main topic, Katello devs are joining this time)
   -

  Currently pulp implementation assumes that there is a main repo
  -

 It might not be correct because there can be multiple variants and
 no main repo
 -

 Repo path == “.” == remote url
 -

 (addon/variant) repo path == “.” is considered as main repo
 -

 (addon/variant) repo path != “.” is considered as sub repo
 -


 
https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/tasks/synchronizing.py#L125-L150
 -

 When publishing [general] repository == first variant ordered by
 uid
 
https://github.com/release-engineering/productmd/blob/f6d73c9822a6451ef4e3af98393bf3935102667a/productmd/treeinfo.py#L1009-L1015

 
https://github.com/release-engineering/productmd/blob/f6d73c9822a6451ef4e3af98393bf3935102667a/productmd/treeinfo.py#L358-L360

 
https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/kickstart/treeinfo.py#L150-L152

 -

  Main repo vs no main repo
  - keep implementation as is (aka have a main repo)
 - some repos don't have a dedicated kickstart repo, they just add
 .treeinfo to the existing repo.
  -

   Sync optimizations for Katello 3.16
   -

  Any optimization usually requires an option to switch it off
  -

 Goal: one switch to ‘turn off all optimizations’, only
 -

 AI: someone to test RHEL7 first/re-sync numbers
 -

 AI: figure out how best to optimize re-sync down to “less than 10
 seconds” if nothing to do
 -

 Treeinfo check and repomd.xml version. There are more things to
 think about (remote-url change? etc)
 - https://pulp.plan.io/issues/6055
 -

   Export
   -

  To filesystem
  -

  To dvd-iso
  -

  To dvd-blu-ray
  -

  incremental
  -

  Does katello need all 4 use-cases? Justin to share use cases.


Pulp 2:

   -

   Announced Z release schedule
   -

   dependency solving issues
   -

  Dalley investigating
  https://bugzilla.redhat.com/show_bug.cgi?id=1784165
  -

 Able to reproduce & bisected to a commit
 -

  Ggainey investigating
  https://bugzilla.redhat.com/show_bug.cgi?id=1725958
  -

 Specifically issue#5449 


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Applicability
   -

  Summary of the discussion w/ Katello about ownership of applicability
  feature
  -

  AI: [ggainey] check in with jsherrill RE moving applicability
  discussion to pulp-dev
  -

   Copy
   -

  https://hackmd.io/OIIpE4GUTXKYoQa8lRMgww?view
  -

  AI: meeting with Katello to finalize details

  -

   Review of the remaining (medium to small) RPM features


Pulp 2:

   -

   Z release
   -

  Fixes https://bit.ly/2RcWG56
  -

  Ina volunteered to be a release shepherd


Open PRs:

   -

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


Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Copy API discussion (continued)
   -

  Complex unified endpoint vs content-type specific endpoints +
  accumulative changes (repository versions created by many tasks
+ “commit”)
  -

  leaning towards the unified endpoint

  -

  Keep epic story up to date and collect feedback later
  -

  AI: figure out Katello-specific needs
  -

   Applicability
   -

  Draft design doc sent to pulp-list@
  https://hackmd.io/ydvHuzXNRA6T9eXx6cqy5A?view#Definitions
  -

  Discussions in progress w/jsherrill on refining katello use-cases
  -

  epic/subtasks created and being added to -
  https://pulp.plan.io/issues/5933
  -

  Initial code work spinning up this week
  -

   RPM planning, feature completeness for Katello


Pulp 2:

   - The is_modular flag issue is fixed
   https://github.com/pulp/pulp_rpm/pull/1579
  - Katello blocker


Open PRs:

   -

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


Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   1770940  - figured
   out why there’s a performance difference, now need to figure out what to do
   about it
   -

   Katello calls differ (no clone distributor is used), Pulp does publish
   in the same way

   -

   https://github.com/pulp/pulp_rpm/pull/1558 sync perf improvement ( from
   CDT)
   -

  Ipanova will follow up ( next year)

Pulp 3:

   -

   Copy API
   -

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

  discussed use cases, expect a follow-up email on pulp-dev list

  -

   Cherry picks next week
   -

  In the event of an emergency (eg Katello encounters a major blocker)
  is there someone who can cherry pick to the 3.0 branch? Or do we
just wait
  until Jan?
  -

  Yes, there will be pulp-committers available next week if needed
  -

   Release status
   -

  Will start after meeting
  -

   Applicability - draft design doc is out, feedback is needed
   -

   Is #5841  (Document how to install
   libcomps and dependencies) needed for GA?
   -

  https://github.com/pulp/pulp_rpm/pull/1570 - Needs cherry-pick
  -

   All 3 of Mike’s RPM-related Ansible installer issues are on QA/MODIFIED


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   Sat 6.6 publish performance issue bug(s) - investigating
   -

  1770940 
  -

  1773601 


Pulp 3:

   -

   Blockers https://pulp.plan.io/projects/pulp_rpm/issues?query_id=139
   -

  Performance
  -

 Increased batch-sizes has direct impact
 -

Configure per-plugin - maybe
-

Increase default in pulpcore stages api
-

 Fabricio found one more source of memory problem (pulpcore)

 
https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/repository.py#L473
 -

 Publish has similar pattern for the performance problem
 -

 Decrease worker-heartbeat writes to DB (~30% overhead?) (pulpcore)
 -

Might be an artifact of the sampling method. Would like to see
verification from cProfile before we change anything.
Heartbeat is in a
separate thread so if it’s waiting on IO, it doesn’t
really matter (dalley)
- UpdateRecord was saved one by one and not in batches, PR is
 posted
 -
  -

  Model level validation
  -

 Not sure full_clean is the correct solution
 -

 ttereshc will check how much plugin is currently affected
 - Comps publish issue
 - root cause not found yet
 - dawalker to send email with the current state of things for
 someone to pick up or collaborate on
  -

  Docs
  -

  Installer (libcomps)
  -

 On sprint, needs to be picked up - mikedep333 will take care of it
 -

 Current state - CentOS7 doesn’t install libcomps
 - Release
 - next RC when the code changes are ready
- optimistically - tomorrow, realistically - next week


   - Open PRs:
  - https://github.com/pulp/pulp_rpm/pulls


Triage:

Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   #5658  - modulemd_defaults and copy
   -

  Potential fix in hand, PR today or tomorrow
  -

   Dep solving performance concerns
   -

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


Pulp 3:

   -

   Blockers https://pulp.plan.io/projects/pulp_rpm/issues?query_id=139
   -

  Advisory merge should be done today,
  https://github.com/pulp/pulp_rpm/pull/1513
  -

  Modularity, add/remove consistency
  -

  Need to merge comps publish
  -

  Advisory upload
  -

   Publish issues
   -

   Branch date - probably tomorrow
   -

   Priorities after branching and before GA
   -

  Focus on docs
  -

  Performance
  -

  Bug fixes
  -

  Add pulp_smash tests for critical/sensitive areas
  - Python 3 bindings for libcomps, packaging discussion


Open PRs:

   -

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


Triage:

Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Hi Ales,

Thanks for confirmation!
I'll definitely file BZs when we analyze and figure out all the differences
and what is needed.
It was a quick pre-GA discussion about the path forward when we need to add
opensuse advisories.

Tanya
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

On Thu, Nov 7, 2019 at 10:04 PM Neal Gompa  wrote:

> On Thu, Nov 7, 2019 at 3:48 PM Tatiana Tereshchenko 
> wrote:
> >
> > Advisory
> >
> > Opensuse advisory
> >
> > some fields differs (reboot_suggested != restart_suggested)
> >
>
> These are not the same fields. The restart_suggested field indicates
> that the update tool should restart itself after this update is
> applied and continue onward. SUSE updateinfo uses both fields.
>
> Cf.
> https://en.opensuse.org/openSUSE:Standards_Rpm_Metadata_UpdateInfo#restart_suggested
>
> > AI: convince createrepo_c team to support suse fields :)
> >
>
> Is there something in createrepo_c that prevents the extra fields from
> working? This is the first time I'm hearing of it, as the SUSE guys
> have been using createrepo_c for a while now in their build system...
>
>
Hi Neal,
It depends how they use it. If they generate updateinfo.xml separately and
then just add it as yet another repodata, there is no limitation to what
one can add.
We are using createrepo_c library to parse/generate updateinfo.xml. I
believe the reporter hasn't checked yet, if certain fields are supported or
not, but a quick look into the code suggests that they are not.
E.g. here is the list of fields for the package in advisory package list
https://github.com/rpm-software-management/createrepo_c/blob/master/src/updateinfo.h#L38-L51
.

Tanya


>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] RPM plugin meeting notes

[Neal Gompa]

On Thu, Nov 7, 2019 at 3:48 PM Tatiana Tereshchenko  wrote:
>
> Advisory
>
> Opensuse advisory
>
> some fields differs (reboot_suggested != restart_suggested)
>

These are not the same fields. The restart_suggested field indicates
that the update tool should restart itself after this update is
applied and continue onward. SUSE updateinfo uses both fields.

Cf. 
https://en.opensuse.org/openSUSE:Standards_Rpm_Metadata_UpdateInfo#restart_suggested

> AI: convince createrepo_c team to support suse fields :)
>

Is there something in createrepo_c that prevents the extra fields from
working? This is the first time I'm hearing of it, as the SUSE guys
have been using createrepo_c for a while now in their build system...




--
真実はいつも一つ！/ Always, there's only one truth!

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   5359 /BZ#1744225 closed WONTFIX
   -

   Investigating 5658 


Pulp 3:

   -

   Blockers https://pulp.plan.io/projects/pulp_rpm/issues?query_id=139
   -

  All RPM endpoints, go/no-go
  https://paste.fedoraproject.org/paste/-qVUKlmvL6zwoAwdWGzNag
  -

 Make all content plural? See ^ +1 - AI: do it
 -

Modulemds
-

Packageenvironments
-

Packagecategories
-

Packagegroups
-

 Modulemd-defaults vs modulemd_defaults - AI: change to _
 -

 Copy /pulp/api/v3/rpm/copy/
 -

Need decision on https://pulp.plan.io/issues/5344
-

filter by type is useful feature and needed (not for GA)
tricky to introduce granular filtering for multiple types on
one endpoint

-

AI: remove the endpoint for GA, decide on API and functionality
later
-

 2-3 issues to do after completion of 3541 and decision on typed
 repos



   -

   Advisory
   -

  Opensuse advisory
  -

 some fields differs (reboot_suggested != restart_suggested)
 -

 *AI: convince createrepo_c team to **support suse fields **:)*
 - Reboot_suggested in advisory level (not in package) (e.g.
  
https://repos.fedorapeople.org/pulp/pulp/fixtures/rpm-erratum/erratum.json)
  (exists in RHEL advisories)
  -

 -

 AI: file issue for advisory level reboot_suggested (can be fixed
 after GA)
 -

   Comps.xml (dana)
   -

   publish is done
   libcomps seems to have a bug in xml generation, in progress



Open PRs:

   -

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

  All PRs (except the modularity upload one) need to be reviewed/merged
  before Tue, Nov 12.


Triage:

   -

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


Questions/thoughts for GA:

   -

   Do we have a release-lead? *ttereshc* will do it
   -

   We need a docs-lead, ttereshc will look for *a volunteer after dev
   freeze.*
   -

   Performance: can we get a sanity test/check pre-GA?
   -

  *AI: Fix travis tests for centos 8 publish,* the rest are fine
  -

   jsherrill and memory issue - publication of RHEL7 repo takes MUCH memory
   (9Gb box OOMs, 12Gb box does not) - issue to be filed. Compare Pulp2/3
   differences. Travis works w/7.5Gb. What’s katello doing ‘on top of’ what
   pulp3 is doing? Can we tune what/how many fields are prefetched?
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Blockers (aim is to close all by pulpcore dev freeze)
   -

  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=139
  -

 3-4 docs, can be done after dev freeze
 -

 Few refactors - soft blockers
 -

 The rest must be done before dev freeze
 -

  Centos publish fix - merged, thanks to Fabricio
  -

  Advisory listing fix - merged, thanks to Pavel
  -

  ttereshc to work on advisory merge - completion is blocked by
  https://pulp.plan.io/issues/3541
  -

  Modulemd removal from a repo version - blocked by
  https://pulp.plan.io/issues/3541
  -

  Modulemd copy/add to a repo version  - blocked by
  https://pulp.plan.io/issues/3541
  -

   David will schedule discussion of https://pulp.plan.io/issues/3541 for
   tomorrow


   -

   Comps.xml (dana)
   -

  Working on publish
  -

  Addressing updates to tests for sync, otherwise needs review


Open PRs:

   -

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

  Reviews are needed
  -

 Advisory upload
 -

 Comps.xml sync


Triage:

   -

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

  All triaged
  -

  More blockers added (but small ones)
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   MONGO_X509 auth PR in
   - discussions w/ewoud about impacts on Katello installation
  - not pulp_rpm specific


Pulp 3:

   -

   3.0.0b7 released
   -

   Blockers status
   -

  Couple are waiting on 3541 https://pulp.plan.io/issues/3541
  -

 If you have thoughts, share in issue or talk to
 daviddavis/bmbouter/ttereshc
 -

  ppicka is working on advisory upload
  -

   Comps.xml
   -

  Sync is under review
  -

  ttereshc needs to look at the error for epel repo
  https://paste.fedoraproject.org/paste/SbjF3DbRZT74qNUZ-LSsRw
  -

   ttereshc started working on RPM functional test audit with kersom
   -

  Need to identify critical gaps to put on the blocker list (GA, not
  feature freeze)
  -

   Performance tests should be merged today
   -

  Will help to investigate performance problems
  -

  Questions:
  -

 Resync-with-no-updates is the slow thing? -yes
 - fabricio will add a resync test
-

 Is first-time sync faster in empty db than ‘full’ db?
 -

 Is batchsize in stages api affecting us?
 -

 Look at sql-explain-plans for possibly missing useful indices
 - we need to find someone to work on it soon


Open PRs:

   -

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


Triage:

Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

   -

   Modularity update (ppicka)
   -

  PR for upload sent
  -

   Comps.xml (dana)
   -

  Sync PR was blocked by segfault bug in libcomps, using workaround
  -

  Github issue filed:
  https://github.com/rpm-software-management/libcomps/issues/54
  -

  Bugzilla bug filed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1757959
  -

   Pulp_rpm 3.0.0 GA Blockers list
   -

  Let’s go through it, some of them might not be important enough to be
  considered blockers - done
  -

  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=139
  -

   Some discussion still needed on the copy API (dalley)
   -

  https://pulp.plan.io/issues/5344
  - Decision needs to be reached for the core blocker
   https://pulp.plan.io/issues/3541
  - plugins depend on it and plugin work needs to be done after ^ is
  complete


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   Pulp 2.21.0 GA going out today (24 hr delay due to docs build issues)
   -

   https://pulp.plan.io/issues/5447 - should add this to 2.21.1
   - non-RPM specific


Pulp 3:

   -

   Modularity update (ppicka)
   -

  Sync and publish are merged
  -

   Comps.xml update (dana)
   -

  PR is up for sync: https://github.com/pulp/pulp_rpm/pull/1452
  -

  finishing bugfixing/tests passing before removing WIP tag and getting
  final reviews
  -

 Waiting on this PR to merge and fix some broken tests:
 https://github.com/pulp/pulp_rpm/pull/1450
 -

  Will start on publish immediately after
  -

   (dalley) Have we discussed testing the RPM plugin performance with the
   performance team?  Re: User report of 24 hour sync time for RHEL repo.
   -

  No, we should start to look into it ourselves first
  -

  AI: dalley to create an issue to write a test to sync CentOS 7 & 8
  repo
  -

  AI: ttereshc to try to sync RHEL7 repo with on_demand policy
  -

   Installation on rhel7 https://pulp.plan.io/issues/5496
   -

  Katello blocker
  - add to the sprint
  -

   3.0 GA
   -

  AI: ttereshc to update the plan to be inline with Katello releases
  -

  AI: ttereshc to create a 3.0 blockers list/milestone


Open PRs:

   -

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


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - only one item, discussed above
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

General:

   -

   Make the meeting optional? +1
   -

  Make sure to fill the agenda and updates at least the day before, so
  others will know whether they should attend or not
  -

  Don’t plan anything on purpose for this time, in case you’ll be
  needed for a discussion
  -


   
https://lists.fedorahosted.org/archives/list/koji-de...@lists.fedorahosted.org/thread/5FXCQJF2PRXTTSU5USBVYLOOML4J3P6H/
   -

  Dkliban and ggainey will join the list and reply


Pulp 2:

   -

   Signed8bit reported a copy problem (not recursive copy)
   -

  Dalley will investigate when he gets time
  -

  Dalley or signed8bit will file an issue
  -

   2.21.0 RC today


Pulp 3:

   -

   Kickstart update (david/fabricio)
   -

  Publish PR is merged
  -

  AI: check if the announcement has been sent for pulp_rpm beta 5
  -

   Modularity update (ppicka)
   - addressing sync PR review feedback
  -

  AI: create a checklist for PRs
  -

   Comps.xml update(dawalker)
   -

  Made changes to relations
  -

  Working closely w/ ttereshc on sync


   -

   Katello tentative plans for pulp3 rpm
   -

  add/enable rpm plugin in 1.26
  -

  pulp_rpm (nightlies) should be feature complete-ish by mid-March


Open PRs:

   -

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


Triage:

   -

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

  https://pulp.plan.io/issues/5448 If multiple source repos contain the
  same package, it can be chosen at random
  -

 WONTFIX
 -

  https://pulp.plan.io/issues/5449 Multiple source repos copy of errata
  produces different results
  -

 Ask katello on the impact
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Ina Panova]

Pulp 2:

   -

   Multi-repo copy update (dalley)
   -

  2 PRs, got approval from 1 reviewer, will be good to get a second
  reviewer
  -

  https://github.com/pulp/pulp/pull/3947
  -

  https://github.com/pulp/pulp_rpm/pull/1420
  -

  Daniel will continue to test edge cases with modular errata


   - closed out https://pulp.plan.io/issues/5187

Pulp 3:

   -

   Kickstart update (david/fabricio)
   -

  Models and sync PRs merged
  -

  Working on publishing (testing against virt-manager)
  -

   Comps.xml update (dawalker)
   -

  Models merged
  -

  Plans to start on sync
  - Need to created relations between packages/package
  groups/env/categories
  -

   Modularity update (ppicka)
   -

  Sync PR up. Needs review
  -

  Travis error: No module named 'gi'
  -

  Rebased one shot upload PR. Needs review

  


Open PRs:

   -

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


Triage:

   - No bugs this time



Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   Multi-repo copy update (dalley)
   -

  PRs ready for review
  -

  https://github.com/pulp/pulp_rpm/pull/1420/
  -

  https://github.com/pulp/pulp/pull/3947
  -

  Docs changes remain
  -

  Still no smash tests, will work with QE on this, they won’t have
  capacity until upcoming Wednesday
  -

  Need to clear simple copy changes with all stakeholders?  Katello is
  already +1


Pulp 3:

   -

   Kickstart update (david/fabricio)
   -

  Splitted in 3 PRs:
  -

 Models: https://github.com/pulp/pulp_rpm/pull/1418
 -

 Sync: https://github.com/pulp/pulp_rpm/pull/1427/
 


   -

 Publish: https://github.com/pulp/pulp_rpm/pull/1429
 -

  Tested sync on RHEL7/RHEL8 repos
  -

  Sync seems to be working, needing some feedback to improve it, and to
  understand publishing
  -

 Suggestions: add test of Centos7/8 repos, manual test of
 multi-variant KS from RHEL8 ContentISO, add testing of on-demand



   -

   Modularity update (ppicka)
   -

  Sync in progress
  -

  Changes to pipeline to handle artifacts without remote artifacts
  - check the pulp-dev thread and Matthias' approach
 -

 Discussion: modulemd always exists, because metadata is always
 downloaded even in the deferred-download scenario



   -

   Comps.xml update (dawalker/ttereshc)
   -

  Name collision - rpm_group, had to rename Group to PackageGroup, any
  other suggestions?
  -

 Rename other entities (eg PackageEnvironment) to be consistent?
 - or rename rpm_* fields in Package model?
 - AI: think
 -

  Do we want to have any relations like group->packages, group->
  categories, etc?
  -

 It seems like in pulp 2 we have a recursive copy for categories?
 
https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/importers/yum/associate.py#L112
 -

 Katello doesn’t need recursive copy for any comps.xml types
 -

 Discussion: implementing it is complicated, but not doing it could
 cause us way more grief later - consensus seems to be “get the model
 correct from the start”
 -

   copy API
   -

  suggestion: new endpoint that does recursive-copy and mark
  simple-copy as “you can, but probably shouldn’t”
  -

  take discussion to list


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pull
   
   - ppicka to rebase module upload PR


Triage:

   -

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

   Triage etherpad https://etherpad.net/p/rpm_triage_grooming
   -

  https://pulp.plan.io/issues/5367
  - new item requested by Katello (it's a pulp 2 feature but it was not
 requested before)
 -

 bmbouter to add details and convert to a story
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   Multi-repo copy update (dalley)
   -

  2 PRs
  -

  https://github.com/pulp/pulp/pull/3947
  -

  https://github.com/pulp/pulp_rpm/pull/1420
  -

  Still testing the 2nd one, not returning exactly the same results yet
  for the standard test cases


Pulp 3:

   -

   Status on Travis failures?
   -

  Waiting on container work
  -

   Kickstart update (david/fabricio)
   -

  Modeling PR open
  -

  Now working on syncing/parsing treeinfo file
  -

   Comps.xml update (dawalker)
   -

  https://github.com/pulp/pulp_rpm/pull/1424 models
  -

  Design/Refactor questions:
  -

 https://pulp.plan.io/issues/5325 +1 add to the sprint
 -

 https://pulp.plan.io/issues/5326 +1 add to the sprint
 -

 Re: langpacks, should we set a list to unique or calculate digest
 -

Calculate digest
-

 Anything to keep in mind for Pulp2->Pulp3 migration
 -

Requirements on Pulp 2 models (we either should not require
more than in Pulp 2 or if we need to - make a note to
tackle it in some way
at the migration time)
-

   Modularity update (ppicka)
   -

  https://github.com/pulp/pulp_rpm/pull/1403 upload for review
  -

  https://pulp.plan.io/issues/5330 - urlpatterns needs fix
  - we need to decide on copy/upload endpoints to be consistent
 - dalley to file a story
 - this issue can be solved together with the story
 -

  https://pulp.plan.io/issues/5305 - sync without updateinfo in repo
  fail +1 add to the sprint


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
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   -

   Dep solving
   -

  Finished the part which interacts with libsolv (the multi-repo copy
  feature is the last one left to close the dep solving features/bugs for
  pulp2)
  -

  No smash tests for the new stuff yet
  -

 *AI*: dalley will work with QE to assist if they need help (issues
 are mostly already written)
 -

   Multi-repo copy
   -

  Almost done, but there’s no tests for it and they are probably not
  written either


Pulp 3:

   -

   Kickstart update (david/fabricio)
   -

  Started working on modeling changes
  -

  Question 1: How do we identify kickstart repos?
  -

 Pulp 2: We check for a treeinfo file at sync time
 -

 Alternative: Create a specific remote (e.g.
 DistributionTreeRemote) that syncs down kickstarts
 -

 +1 to have one remote (and have a kickstart content as a part of
 RPM plugin) for now
 -

  Question 2: relationship between kickstarts and sets of RPMs
  -

 Create a join between DistributionTrees and repos (or rather repo
 versions)?
 -

Probably repos, since they need to be able to be managed
independently as well.
-

  Question 3: DistributionTree mutability?
  -

 No, immutable (upstream). Maybe within Pulp they should be mutable
 but only the related RPM repositories.

 -

   Spoke with QE and they are interested if we know of gaps in test coverage
   -

  *AI*: ttereshc to reach kersom and probably do an audit



   -

   Containers work update
   -

  it’s coming together, expected to be done in a week or two.


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
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

General:

   - Fabricio joined RPM mini-team. Welcome!


Pulp 2:

   -

   Dependency solving
   -

  3 PRs in progress
  -

 Address copying module-defaults with modules
 -

https://github.com/pulp/pulp_rpm/pull/1400
-

Blocked on crashes - sent dump of solver state to Igor, waiting
on feedback
-

Should be 100% functional and ready to merge once the crashes
are resolved
-

 Address multiple source/destination repos
 -

https://github.com/pulp/pulp_rpm/pull/1407
-

Initial implementation of just the depsolver portion of this
work complete -- pending necessary changes to backend
-

   A PR for multiple resource locking in pulp platform is under
   test and Grant will submit it either today or tomorrow. Awesome!


   -

 Address accidental copies of units that shouldn’t be copied
 -

https://github.com/pulp/pulp_rpm/pull/1408
-

Blocked on some patches to our version of libsolv
- https://pulp.plan.io/issues/5151
   -

   Also blocked on a question to Igor -- do we need to expose
   anything else through the libsolv bindings?
   - After all patches are ready and it's clear that we don't
   need anything else, we'll ask the build team to apply
patches and rebuild
   libsolv package that we carry. Zach has been notified
that it's coming.



   -

   Pulp 2 needs to create files with ‘apache:pulp’ ownership.
   https://pulp.plan.io/issues/5154
   - Just for information, no actions on RPM plugin side, the platform issue


Pulp 3:

   -

   Modularity
   -

  Does the _’ prefix in field names in plugins mean that it came from
  pulpcore?
  -

 The majority agreed that yes or at least we should try to avoid
 using it for user-facing items.
 -

  libmodulemd and travis
  -

 Pavel tried to make it work on ubuntu, ran into multiple issues
 -

Mike is very close to have containers to test on
- Decided not to spend more time on trying to make it work on
ubuntu
-

   Roadmap
   - Draft discussed
  - ttereshc to update it with provided feedback
  - ttereshc to wait till tomorrow if any RPM folks have more feedback
  and then share with a larger group


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls
   - AI for everyone: look at it every now and then and review PRs so they
  are not piling up


Triage:

   -

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

   Triage etherpad https://etherpad.net/p/rpm_triage_grooming
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   - Modularity dep solving
  - automatic module_default copy works!! but is buggy, *crashes* -
  under investigation
  - "too many packages/modules are copied" issue - clear what to do,
  just needs to be done
   - Multiple source/target repositories support for recursive copy
  - https://pulp.plan.io/issues/5067
  - for that we are adding multi-resource locking to the tasking system
 - https://pulp.plan.io/issues/5108
  - potential concern is resource utilization
  - need some katello input on sequence of calls for their workflows -
 sync/publish/applicability
 - concern is to end up with N-2 idle workers for some time
 - AI: dkliban to work w/katello(partha) on
 api-workflow/resource-utilization
 - to consider: instrument 'waiting for available worker' state (%
 calls run into, amount of time spent waiting)
 - to consider: ask field engineering about customer workflows, to
 make sure we're testing those.

Pulp 3:

   - Modularity (ppicka)
   - modulemd models PR open
  - simple upload PR open
 - can be used to test the models PR
 -  few prerequisities for ansible installer are added
  - todo: temporarily install ubuntu package for libmodulemd in travis
- to be able to test rpm plugin until containers work is done
and we can use Fedora/Centos there
- AI: dkliban to share relevant info with ppicka


   - Roadmap for RPM plugin
   - discussed LOE for major items
  - AI: ttereshc to put the discussed roadmap into the redmine
  - highlights:
 - prioritize tasks which might affect pulpcore, so we can change
 something before pulpcore goes GA, candidates:
 - kicktstarts
- sync option to verify content (files are corrupted or removed
from the FS, the DB is ok - there should be a way to fix it)
   - it's not RPM-specific, other plugins will benefit from it
   as well
   - AI: dkliban to write a story to start discussion
- before we start working on applicability, ggainey will demo
 and share his experience with VMaaS
 https://github.com/RedHatInsights/vmaas


   - https://pulp.plan.io/issues/5092 Files are not deleted when deleting
   uploads
  - not RPM-specific, core question
  - discussion is needed to figure out if any resource reservation is
  required for upload workflow, including the deletion of uploads.
  - the outcome of the discussion (whenever it happens) should be
  posted on the issue

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - all triaged
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

*June **2**7**, 2019*

Pulp 2:

   - Modularity dep solving
   - fixes are not in 2.20.0 for now
  - refactoring and future PR:
 - https://github.com/pulp/pulp_rpm/pull/1383
  - issue with dependencies being spread across multiple repos
  - discussion with Katello is planned this week


Pulp 3:

   - modularity testing
   - libmodulemd for ubuntu?
 - probably not worth time if a lot is required
 - temporary solution anyway
 - containers are weeks/month away
 - rpm plugin can wait few weeks
 - modularity support is not ready/merged yet


   - errata - "Pulp 3, same advisory - different pkglists" thread
   - no objections on the thread
 - potential concern around on_demand case, let's discuss a url
 change on a Remote
 - AI: ttereshc to write/update a story


   - url change on a Remote, on_demand
   - url should be changed for all content for that Remote
 - just new RemoteArtifact is created
 - RemoteArtifact has url field on it as well
 - why is it needed? one-time options like proxy settings should
not respect this field anyway
   - likely pass-through case (pulp_maven) uses it
   - dkliban to find a case when url on RemoteArtifact is
  required
  - how to combine repos with on_demand policy?
 - not with url-change approach
 - use 2 Remotes
 - we need to document it, it's important for errata case discussed
 above^


   - depsolving
  - Refactors in Pulp2 have/will make it much easier to port to Pulp 3,
  a lot of code will be able to be shared


   - kickstarts in pulp 3
  - no progress
  - daviddavis might have some time next week
 - ttereshc to share all the collected info and suggested approach

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   - Modularity bug updates https://pulp.plan.io/issues/4693
  - a lot of progress
  - smash test is written, thanks to bherring


Pulp 3:

   - JFYI, version for the master branch has been updated
  - master branch should always refer to .dev


   - more attention is needed for a thread about uniqueness within a repo
   version
  - https://www.redhat.com/archives/pulp-dev/2019-May/msg00061.html
  - no progress since last week
  - ttereshc to update issues with the proposal from the thread to
  trigger discussion there
  - RPM issue: https://pulp.plan.io/issues/4898
 - File issue: https://pulp.plan.io/issues/4028


   - modularity progress
  - models a re on the way
  - libmodulemd is a dependency now
 - installer needs to be updated
 - how to test rpm plugin
- fedora containers to test for now, maybe centos containers
can also be used later when centos8 is out
- dkliban to expand Travis pipeline to support running builds
inside containers


   - errata design proposal in Pulp 3
  - "Pulp 3, same advisory - different pkglists" thread
  - AI: provide feedback
  - ttereshc to ping Katello


   - items for upcoming sprint
  - no new items will be added, maybe some bug fixes during sprint
  - reason: other tasks have higher priority: pulpcore, migraiton tool,
  plugins which are integrating with Katello right now
  - areas continued to be worked on:
 - ppicka - pulp3 modularity
 - dalley - dep solving for pulp2 with the intention to reuse ot
 the extent possible in pulp3


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
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   - Modularity bug updates https://pulp.plan.io/issues/4693
  - investigation in progress
  - dalley planned to collaborate with QE


Pulp 3:

   - bindings
  - docs updated
  - announcement sent
  - bmbouter/dkliban gave overview of how bindings are generated and
  where bugs usually are - thank you


   - Problem: duplicates during upload
  - email thread
  https://www.redhat.com/archives/pulp-dev/2019-May/msg00061.html
  - AI stays the same: provide feedback


Open PRs:

   - https://github.com/pulp/pulp_rpm/pulls
  - no old PRs

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - no un-triaged items
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   - Modularity bug updates https://pulp.plan.io/issues/4693
  - As noted, erroneous behavior reproduced w/ modules in the Fedora
  modules repo
  - It seems like a lot of modules are copied correctly, but some
  aren't. Trying to figure out the pattern.
  - Refactoring PR, doesn't fix any issues
  https://github.com/pulp/pulp_rpm/pull/1367
 - ttereshc to review it
 - Added lots of docstrings so that less code reading and
  re-reading is necessary to figure out what functions do


   - https://pulp.plan.io/issues/4869  RPMTAG_MODULARITYLABEL
  - available on F30+
  - working with DNF team to make it available on Centos7


Pulp 3:

   - modularity updates
  - https://pulp.plan.io/issues/4873 groomed and on the sprint


   - need to improve pulplift - https://pulp.plan.io/issues/4770
  - dkliban to leave his thoughts, so whoever picks it has more ideas
  on how to complete this taskwhich potentially will be just a docs
  improvement


   - bindings
  - dkliban to publish them today
 - already done
 - https://rubygems.org/gems/pulp_rpm_client
 - https://pypi.org/project/pulp-rpm-client/
  - bmbouter to help with docs for it
  - announcement should go onto mailing list


   - start making changelog entries
  - best effort before it's required by travis


   - Problem: duplicates during upload
  - email thread
  https://www.redhat.com/archives/pulp-dev/2019-May/msg00061.html
  - AI: provide feedback, there are good suggestions and concerns from
  Simon


   - Did we ever check in migrations?
  - no, ttereshc forgot to include them into release last time
  - we should do it with the next release


   - Planning on next release
  - no need to wait for the next pulpcore RC if we have anything useful
  to release


   - pulp_rpm requires DB to be in utf8 format
  - great and it's a default in Django


Open PRs:

   - https://github.com/pulp/pulp_rpm/pulls
  - community Pulp 2 PR - cant reproduce the problem
 -  https://github.com/pulp/pulp_rpm/pull/1343
- no reply for quite a while, closed


   - black: https://github.com/pulp/pulp_rpm/pull/1355
- Holding off until pulp-dev discussion/PUP is resolved

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

*May **23**, 2019*

Pulp 2:

   - schedule for 2.20
  - dkliban and ttereshc discussed it the other day
  - ttereshc to put it together today


Pulp 3:

   - simple copy PR https://github.com/pulp/pulp_rpm/pull/1328
  - there were some merge conflicts but its fixed now and ready to merge
  - but I would like to merge this one first:
  https://github.com/pulp/pulp_rpm/pull/1354
 - decide whether we want user-facing name to be "errata" or
 "update"
- we'll call it an "advisory" since it's the most common term
which is used in the cli tools and the customer portal
- ttereshc to reach Katello to suggest this name for their UI
as well


   - kickstart trees updates
  - due to other priorities, no progress here


   - modularity updates
  - ppicka started writing a task for modelling
  https://pulp.plan.io/issues/4873
  - ppicka to schedule a meeting to discuss and polish the design and
  task descritpion


   - slow progress
  - pulp_rpm is currently not the highest priority
  - any available capacity?
 - maybe in a week or two there will be more
 - more focus on pulpcore, pulp_ansible, migration tool, travis
 improvements and so on


   - refactor to use primary key and not carry the whole object for tasks
  - bmbouter to file a refactor


   - consider to use black project
   - https://black.readthedocs.io/en/stable/
  - daviddavis to open a PR to try it out


   - Open PRs
   - https://github.com/pulp/pulp_rpm/pulls
 - community Pulp 2 PR still needs testing/review
- https://github.com/pulp/pulp_rpm/pull/1343
 - https://github.com/pulp/pulp_rpm/pull/1347 CDT is impacted
 - View module content with pulp-admin
 https://github.com/pulp/pulp_rpm/pull/1350
 - ttereshc to review


   - Triage:
  - Un-triaged bugs
  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
  - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   - Some old issues which are fixed are still at ON_QA. daviddavis will
   move it to CLOSED-CURRENTRELEASE
  - https://pulp.plan.io/issues/3047
  - https://pulp.plan.io/issues/3100
  - https://pulp.plan.io/issues/3115


   - 2.19.1 work
  - low participation, probably due to conference prep
  - it will be helpful if more people are involved in fixing pulp 2
  issues


   - https://pulp.plan.io/issues/4798  upload issue
  - seems to be a dupe of https://pulp.plan.io/issues/4059
  - #4059 should be reopen
  - link 4798 to 4059, ref both in any PRs - AI for ggainey to
  link/reopen
  - need to find issue about download catalog not being updated - AI
  for dkliban

Pulp 3:

   - simple copy PR https://github.com/pulp/pulp_rpm/pull/1328
  - bmbouter will review, docs mostly


   - kickstart trees updates
  - not much progress due to pulp2 work
  - got Katello feedback, no blockers
  - AI: ttereshc to update roadmap with use cases


   - modularity updates
  - use cases are done and reviewed by some stakeholders
  - https://etherpad.net/p/modularity_use_cases
  - AI: file tasks to model modularity content
  - AI: ttereshc to update roadmap with use cases


   - installer
  - no improvements needed in forklift
  - task is filed against pulplift https://pulp.plan.io/issues/4770


   - committing migrations
  - let's commit with the next release
  - still keep it as beta, not rc


   - Are we compatible with the latest pulpcore? When should we release?
  - yes, all the changes are made
 - thanks to ppicka for updating the distribution part
  - we'll release next beta right after pulpcore rc2


Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp2:

   - Dev freeze for 2.19.1 is May 14
  - Look for the pulp2 issues of the sprint, most of them should be
  fixed for 2.19.1
  - the nice-to-have ones have comments that they are not critical to
  go into 2.19.1 specifically.
  - dkliban set platform release for 2.19.1 issues
  - dalley to work on https://pulp.plan.io/issues/4693

Pulp3:

   - simple copy PR status
  - https://github.com/pulp/pulp_rpm/pull/1328/
  - ready for final review


   - dep solving updates
  - dalley started look into detail in pulp2 code and working out the
  API for pulp3
  - epic story to track the effort and to write down design when it's
  ready
 - https://pulp.plan.io/issues/4762


   - kickstart trees updates
  - bmbouter and ttereshc discussed some design ideas
  - getting feedback from some teams is postponed due to RH Summit.


   - modularity planning meetings
  - started today (ipanova, ppicka, ttereshc)
  - bringing ppicka up to speed
  - going through use cases
  - whenever the list is ready, we'll share it to get feedback
  - anyone is free to join design discussions (not started yet)
  - https://github.com/rpm-software-management/createrepo_c/issues/98
 - we need to see what kind of modularity support is available in
 createrepo_c


   - installer updates
   - issues using it with pulplift
 - dkliban to file an issue, for real this time :)
 - dkliban to file a forklift rfe as well - to add pre-steps


   - https://pulp.plan.io/issues/4010 As a user, I can view update records
   in the API
  - is it up to date?
  - what are the katello needs?
  - what are the benefits of merging or not merging
  - ttereshc to answer questions and to find specific examples of the
  same erratum in multiple variations in Pulp (updated erratum,
same erratum
  for different distros)

Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - nothing too old or worth special attention

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - only one, needed for 2.19.1


   - any sprint candidates?
  - https://pulp.plan.io/issues/4445 As a user, RPMs are published in
  Packages/ and sorted alphabetically
  - https://pulp.plan.io/issues/4413 As a user, I can specify one-time
  options during sync
  - not adding anything this time
 - some people are away
 - focus on pulp 2 issues for 2.19.1 is needed
 - there are enough pulp 2 issues on the sprint
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp2:

   - many Pulp 2 items are on the sprint, including publish dir race
   condition
  - any deadlines/priorities?
  - need them in 2.19.1 (tentatively by the end of May)


   - https://pulp.plan.io/issues/4534 Searching for modulemd_defaults
   without "profiles" field will crash: InvalidBSON
  - is a patch from the reporter expected? no
  - is it a priority for them? what are the deadlines?
 - ipanova asked
 - likely not a priority for 2.19.1

Pulp3:

   - https://pulp.plan.io/issues/4716 As a user, I have simple content copy
   between repositories
  - add filtering by type, currently RPM and Erratum
  - destination repo - repo href, no base_version choice
  - source repo - repo href or repo_version href, mutually exclusive,
  user decides which one to use


   - kickstart trees updates
  - gathering of info is close to completion
  - ttereshc needs to talk to Katello
  - experimenting with libraries, in progress


   - Should we remove RpmPublisher? +1
  - Or will we need it in the future - maybe


   - installer updates
  - done (last week)
  - issues with pulplift and rpm installer
 - dkliban to file an issue


   - dep solving
  - dalley to start working on it


Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - https://github.com/pulp/pulp_rpm/pull/1331  Add support for
  anonymous proxy
 - dkliban is on it? yes

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   - High priority issues?
  - publish race condition https://pulp.plan.io/issues/3098
 - not RPM specific but affects RPM plugin as well (mostly
 noticeable for the Docker plugin)
 - volunteer is needed
  - Pulp 2 RPM bugs, mass closing
  - AI: ttereshc/ipanova to go through a backlog for the past month to
  identify issues to re-open.


Pulp 3:

   - installer updates
  - ansible role is done (ppicka)
  - new repo for it is needed


   - distribution/kickstart tree updates
  - couple replies with use cases
  
https://community.theforeman.org/t/kickstart-tree-content-management-feedback/13527
  - last attempts to get official docs


   - docs updates
  - homepage now has features directly on it
  https://pulp-rpm.readthedocs.io/en/latest/
  - quickstart PR up, merging after installer is merged
 - https://github.com/pulp/pulp_rpm/pull/1316
  - New REST API docs!
  https://pulp-rpm.readthedocs.io/en/latest/restapi.html


   - Unit copy discussion - pulp-dev list
  - not many comments, but so far a design similar to one-shot upload
  seems preferred
  - AI: dalley will write story

Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - All good, nothing is there for too long

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - on-going ^
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

General:

   - ppicka joined RPM mini-team
  - welcome :)

Pulp 2:

   - dkliban to plan release of 2.19.1 soon to release the migration issue
   https://pulp.plan.io/issues/4617 and other bugfixes which will be
   completed in time for the release
   - https://pulp.plan.io/issues/4631 Pulp allows uploading RPM as SRPM
   - waiting for the feedback on priority and potential contribution from
  the reporter, ipanova is on it

Pulp 3:

   - challenges with distributing Pulp 3 RPM
   - https://github.com/rpm-software-management/createrepo_c/issues/145


   - complex copy use cases, including recursive copy
  - where do we plan to put copy functionality as far as the REST API
  goes?
  - has to happen before depsolving can happen, needed to integrate
  with Katello
  - repositories themselves are content agnostic, but we need to
  support content-specific options
  - do we create a "copier" object like remotes and publishers, and do
  something like /pulp/api/v3/copiers/rpm/package/ content_units=[...]
  source=.../repositories/... destination=...
 - dalley will start a mailing list discussion about unit copy


   - installer updates
  - discussion is ongoing https://pulp.plan.io/issues/4494#note-14
  - hopefully more progress next week


   - distribution/kickstart tree planning
  - reaching out to try to find official specs
  - reaching out to try to find use cases


   - demo candidates
  - dkliban to record demo of RPM on_demand sync of Centos 7 or EPEL 7

Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - https://github.com/pulp/pulp_rpm/pull/1311
 - needs review and maybe an issue? +1
 - ppicka to create an issue

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - issues triaged, some stories remain ungroomed, more info on the
  etherpad ^
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

General:

   - changes in Fedora 30
  - remaining items are being evaluated (see details in the previous
  e-mail)

Pulp2

   - there are few issues on the sprint, nothing urgent at the moment


Pulp3

   - installer updates
  - bmbouter plans to work with asmacdo in the upcoming days
   - ready to release beta 2 when pulpcore rc1 is out
   - next steps
  - improve docs https://pulp-rpm.readthedocs.io/en/latest/
 - refer to live docs
 - bmbouter will file a task with ideas to make docs more
 approachable
  - distribution/kickstart tree planning
 - high priority
- bmbouter/daviddavis - started investigation, no capacity to
continue
- ttereshc will take over, dalley is a backup
- bmbouter and daviddavis will schedule a knowledge transfer
session
 - performance improvements for sync and publish, small features
  like skip/retain-old-cout
  - bmbouter will ask for user's feedback over mailing list and twitter
 - large areas remaining untouched
 - dep solving
 - modularity
- blocked by createrepo_c not having support for modular errata
- they asked today if we can test their PR to see if it has
everything we need
https://github.com/rpm-software-management/createrepo_c/pull/116
- applicability

Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - None (apart from beta 2 prep)
  - Good job on quick reviews!

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - on-going on the etherpad ^ in the async way
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

General:

   - We should track changes in Fedora and evaluate impact on Pulp
  - https://fedoraproject.org/wiki/Releases/30/ChangeSet
  - any volunteers? - Daniel(@dalley)
  - Possibly relevant changes:
 - Zchunk Metadata
 https://fedoraproject.org/wiki/Changes/Zchunk_Metadata
- impact discussed/considered some time ago
 - Removing the Group Tag
 https://fedoraproject.org/wiki/Changes/Remove_Group_Tag
- needs checking/evaluation
 - Replace Comps Language Group with Langpacks
 
https://fedoraproject.org/wiki/Changes/Replace_Comps_Language_Group_With_Langpacks
- needs checking/evaluation
 - SWID tags
 https://fedoraproject.org/wiki/Changes/SWID_Tag_Enablement
- impact discussed/considered some time ago


Pulp2

   - No questions at the moment, except un-triaged bugs


Pulp3

   - #4505 slow sync is fixed. Great job, Daniel!
   - Beta plans
  - merge the publish fix and release, maybe today
  - publish fix needs review, see open PRs below
   - Any progress on the installer?
  - more discussion is needed
 - there are multiple options outlined in
 https://pulp.plan.io/issues/4494
 - the rpm specific issue is on the sprint
 https://pulp.plan.io/issues/4494
- should be worked on next, after critical issues are resolved
and merged and beta is released
 - ideas for our regular demo
  - One-shot upload? +1+1
 - ttereshc to check with ppicka the plans on demoing it
 - On-demand sync/publish of EPEL


Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - publish fix
  https://github.com/pulp/pulp_rpm/pull/1298#discussion_r265235083
 - feedback and review are still needed
- ugly solution but the question is if we need to change the
model for packages or not
   - if not, we can refactor it later, after RC
- test for publish is not failing
   https://github.com/pulp/pulp_rpm/pull/1299
  - dkliban will look into it

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - partially triaged
  - some follow-ups are needed, more info on the etherpad for triage ^
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp2

   - https://pulp.plan.io/issues/4477 modular errata publication issue
  - on the sprint
  - should it be considered as a blocker for upcoming 2.19.0
  - ttereshc will work on it


   - https://pulp.plan.io/issues/4541 packages are published twice, in
   different layouts
   - dkliban will check in with jsherrill and then triage
  - a potential blocker for 2.19.0

Pulp3

   - Sync is failing https://pulp.plan.io/issues/4505#note-2
  - dalley is working on it
  - a blocker for the pulp_rpm Beta since users can't sync EPEL repo
  with that issue
   - Should release new Beta after publish fix is merged and #4505 is fixed
   in the core
   - Sprint candidates identified last time are added to the sprint 50.
   Priority for them is lower than the core RC work and issues blocking any
   release.


Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - https://github.com/pulp/pulp_rpm/pull/1298#discussion_r265235083
 - feedback needed
 - ugly solution but the question is if we need to change the model
 for packages or not
- if not, we can refactor it later, after RC

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - everything is triaged except #4521 (mentioned earlier) which will
  be triaged shortly
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp2

   - https://pulp.plan.io/issues/4477 modular errata publication issue
  - needs to be worked on sooner rather than later, added to the sprint

Pulp3

   - Sync is failing https://pulp.plan.io/issues/4505#note-2
  - likely a problem in core but easy to reproduce with RPM plugin
  - should be brought up on the sprint planning tomorrow

Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - https://github.com/pulp/pulp_rpm/pull/1289 recursive copy docs
 - feedback on correctness of examples is needed
 - dkliban will take a look
  - https://github.com/pulp/pulp_rpm/pull/1291 Replace remaining usage
  of createrepo with createrepo_c
 - pulp2 is in maintenance mode
 - ipanova will ask the reporter to see how critical it is for this
 PR to be merged.
  - https://github.com/pulp/pulp_rpm/pull/1295 test updates due to
  changes in core
 - tests are failing
 - daviddavis will look at it
  - 2 more recent PRs which require review but not urgent

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
   - all issues filed at the time of the meeting were triaged


Sprint candidates discussed and identified:

   - Installer work https://pulp.plan.io/issues/4163
   - Stories for one-time option -> combine into one
  - ttereshc will combine stories to support various one-time options
  during sync
   - Errata duplicates elimination https://pulp.plan.io/issues/4295
   - RpmContentSaver stage refactor https://pulp.plan.io/issues/4117
   - Reporting story https://pulp.plan.io/issues/4503
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp2

   - recursive copy docs https://pulp.plan.io/issues/4371 , in progress
   - should be done today


   - new libsolv package, QE are blocked
  - if no news from the build team by the end of the week, bring up on
  Monday meeting

Pulp3

   - https://pulp.plan.io/issues/4424
  - Pulp will require primary, other and filelists
  - Descriptive error message should be shown to user
  - Document why repos without filelists/other are not supported


   - https://pulp.plan.io/issues/4458 custom checksum type story
  - feedback/discussion is needed
  - AI: Team think and comment on the issue
  - AI: Tanya will remind Katello to comment on the issue


   - Issue with publish in case of lazy sync
   https://pulp.plan.io/issues/4412, on the sprint
   - any other critical/noticeable issue left which blocks beta? No.


   - One-shot uploader: Kersom suggested allowing a base_version option to
   be used along with repository
  - opinion #1: it's not really necessary, you can already do it in 2
  steps and we don't need to duplicate the entire feature set of the normal
  workflow.
  - opinion #2: maybe it's not a bad idea if it will ease user's life
  and if there is no additional logic/changes happening to base_version
  option, just directly passing the parameter to a repo version
creation call.


   - Packaging of RPM plugin in Fedora
  - sounds reasonable if pulpcore and pulpcore-plugin will be in Fedora
  and also RPM plugin requires libraries which are available on RPM-based
  distributions only.

Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - well done, we are in a good shape, everything reviewed and merged
  except a couple of  test related PRs

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
  - done, Redmine updated
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp2:

   - https://github.com/pulp/pulp_rpm/pull/1269 approved, about to merge +1
   +1
  - AI: Ina to check with stakeholders if there is any required release
  date
 - checked, we can release according to our schedule

Pulp 3:

   - https://pulp.plan.io/issues/4424
  - How should pulp handle repos with missing metadata files?
  - AI: team think and comment


   - Let's identify/start discussing RPM specific Katello gaps
   - as a starting point Justin marked Katello items in our roadmap doc and
  he will add any missing ones if there are any.
  https://pulp.plan.io/projects/pulp/wiki/Pulp_RPM_Roadmap


   - question from Katello: where checksum type configuration will be on
   Publisher or not?
  - AI: Tanya will create a story
  - requires more planning, many details to this custom checksum type
  feature
  - potentially a one-time option


   - sometimes Travis fails after PRs are merged
  - Travis build history https://travis-ci.org/pulp/pulp_rpm/builds
  - Likely due to changes in depencdencies


   - Code owners for functional tests are added. Thank you, David!


Open PRs

   - https://github.com/pulp/pulp_rpm/pulls
  - https://github.com/pulp/pulp_rpm/pull/1191/
 - discussion will be continued

Triage:

   - Un-triaged bugs
   https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   - Triage etherpad https://etherpad.net/p/rpm_triage_grooming
   - No un-triaged bugs this time
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

General discussion:

   - The commit bit to pulp/pulp_rpm has been given to QE team.
   - Codeowners [0] for functional tests in pulp/pulp_rpm
  - Agreed to add
  - AI: David to open PR to add codeowners. Add some docs to wiki.

Pulp 2:

   - Potentially an issue with sync of Fedora 29 repo, expecting a bug
   report and steps to reproduce from a user.

Pulp 3:

   - Modularity considerations [1]
  - Due to RPM specific dependencies Pulp3 RPM plugin will be available
  on RH distros only or containerized
   - Sprint candidates [2][3][4]
   - will be considered after tomorrow's sprint planning, depend on number
  of pulpcore RC items and other priorities
  - Issue discussed: sync fails if there are same artifacts in
   different repos with different relative paths
  - repo1 has foo.rpm
  - repo2 has nested_dir/foo.rpm
  - paths are different, artifact is the same
  - right now only one relative path can be for content-artifact
  relation
  - Questions:

1. Is there a need to replicate directory structure from upstream without
configuring explicitly a path for publication?

   - Agreed that expectation is that upstream directory structure should be
preserved by default.


   - AI: Tanya will start a discussion on pulp-dev to hear from other
plugins and to discuss how to do it and where to introduce
the change

2. How to fix the issue for now?

   - use a filename as a relative_path for now
- directory structure of the upstream won't be preserved until
the question #1 is resolved


   - some functional tests don't seem to be isolated
  - AI: Tanya to check and follow up with QE to see if it was done on
  purpose or if it should be improved

[0] https://www.redhat.com/archives/pulp-dev/2019-February/msg00040.html
[1] https://pulp.plan.io/issues/4162
[2] https://pulp.plan.io/issues/4295 - ready to go on the sprint
[3] https://pulp.plan.io/issues/4412 - needs triaging
[4] https://pulp.plan.io/issues/4413 - needs grooming
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

General discussion:

   - We had a discussion about a commit bit to pulp/pulp_rpm for QE team.
   Everyone who was present is on board. Many team members were out today, so
   the final decision is deferred till they are back.

Pulp 2:

   - Modularity issues are solved and merged, thanks to Daniel (dalley)
   - Module dep solving issue [0]
  - in testing by devs, not complete due to other priorities (RC
  blockers)

Pulp 3:

   - Need volunteer to review one-shot uploader for RPM [1]
   - PackageManagerConsumeTestCase failure [2]
  - Travis doesn't run this test since it requires DNF
  - David got a failure when tried to run it locally but perhaps the
  content app is not set up correctly? (ie  no CONTENT_HOST configured)
  - Let's focus on improving ansible in this area, added relation to
  the #4302 [3]
   - Any update on kickstart tree progress?
  - no, pulpcore RC blockers take priority, probably get back to that
  work after pulpcore goes RC
   - pulplift and RPM plugin
  - RPM plugin has additional requirements to install packages
  - Maybe we should add a generalized mechanism to install packages in
  the installer itself, since some other plugin might need that as well.

[0] https://pulp.plan.io/issues/3740
[1] https://github.com/pulp/pulp_rpm/pull/1246
[2] https://pulp.plan.io/issues/4320
[3] https://pulp.plan.io/issues/4302
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 2:

   - modularity issues are on the sprint [0], dalley is working on them.


   - module dep solving story [1], dalley or jortel will take a look at the
   corresponding PR to see if it requires any adjustments

Pulp 3:

   - Agreement reached with the stakeholders that it's ok to publish errata
   without filtering its pkglist at publish time. The way errata content is
   designed in Pulp 3 allows to have errata with the same id but different
   pkglists in different repos without a problem.


   - Should we add errata duplicates story [2] to the Sprint?
  - Yes, if there are no concerns raised by the end of the day


   - kickstart trees
  - investigation is ongoing , various tools are being tested to be
  sure that all the required functionality can be provided.

[0] https://pulp.plan.io/issues?query_id=111
[1] https://pulp.plan.io/issues/3740
[2] https://pulp.plan.io/issues/4295
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev