Try   HackMD

Pulpcore 2021 Archive

December 14th, 2021

December 7, 2021

  • [ipanova] Are we going to participate in the upcoming conferences? Devconf and Fosdem. Do we plan any booths or just talks/workshops
    • dkliban will submit a talk to FOSDEM on using the single container
  • [ipanova] https://pulp.plan.io/issues/9603 reclaim disk space for whole pulp, katello would benefit from this
    • The proposed solution looks good
  • [bmbouter] interested in adding an additional commiter
  • [bmbouter] forming telemetry working group in Jan
  • [mdellweg] Do we want to make 3.20 a remove deprecations only release?
    • let's see what happens
    • probably not

November 30, 2021

November 23, 2021

November 16, 2021

November 2, 2021

October 26, 2021

  • 3.17 relese date - before or after Pulpcon?Nov 4 or Nov 16?
    • Let's release on Nov 16th
  • Docs day. November 3rd? https://pulp.plan.io/issues?query_id=174
    • Yes!
  • Feedback on Patchback proposal
    • we need to move to github issues before we focus on automating the backports

October 19, 2021

October 12, 2021

  • Removing mirror parameter from pulpcore RepositorySyncURLSerializer
    • Doesn't make sense for all plugins
    • Not flexible enough for some plugins
    • Proposal: Remove from pulpcore, have plugins provide it for API backwards compatibility
      • Deprecate + add to plugins in 3.17, remove in 3.18
    • Some discussion here:
  • David - anything before I leave?
    • Will give up commit bit

October 5, 2021

  • https://pulp.plan.io/issues/9289#note-5
    • Will move to a separate repository and will try to simply tag it without releasing to PyPI
  • 3.14 tagged all-in-one container image (was) a month old, should we trigger / automate them more frequently?
  • 3.16.0 release
    • ACS prs are merged
    • plugins will check on compatibility during Open Floor today

September 28, 2021

  • Proposal: Redis should be optional by default
  • Supported auth in url format?
  • Check-in on Roles progress
    • models are finished
    • permissions are being checked.
    • some helper functions for queryset filtering and checking permissions
    • creation_hooks (formerly known as permissions_assignment) with hooks for roles
    • roles are part of the access policy
      • may change due to concerns
        • want to allow admins to modify roles, but not the rest of access policy
      • options
        • keep it that way
        • move default roles as a class attribute in the viewset; post migrate signal; add REST for roles +1
        • add REST for roles, ship default as a migration
    • rewritten access policy for tasks as an example
    • Still need API views for listing Roles, to assign roles, and to remove roles

September 21, 2021

September 14, 2021

September 7, 2021

Action items

August 31, 2021

Action items

  • [dkliban] to reach out to newswangerd/osapryki to get the list of proposed projects for token auth support and check with security teams

August 24, 2021

  • 3.14.z release
    • waiting on the last item to be investigated (encoding issue observed in rpm but potentially a pulpcore problem)
    • dalley to finish cherry-picks
    • ttereshc to release
    • fao89 to release installer
  • Move docs day to next week? +1
  • 3.15 release on Thursday (tentative)
    • everything needs to be merged by tomorrow EOB

August 17, 2021

  • 3.15 release is postponed till next week
    • refactor code to stop running async code inside a transaction, dkliban is on it
    • mdellweg to release next week
  • Issues with gunicorn
    • concurrent chunk upload, with concurrency 25+, e.g. docker push
    • gunicorn prematurely closes the connection
    • need a lead, might become urgent
  • Docs day query https://tinyurl.com/uc59aa5k

August 10, 2021

  • 3.15 pulpcore workers use 10 times as many connections to the DB during sync as they did in 3.14
    • in 3.14 - 1 extra db connection during file repo sync
    • in future 3.15, without the wrapper - extra 9 connections
    • in future 3.15 with the wrapper - extra 12 connections (but overall number of connections can be limited)
  • Full Django 3 support will possibly require a few new patches in core areas to address the connection issue
    • Technically they might not fit the backport policy upstream
    • We can always apply them downstream-only, but also..
    • Without the model changes (using the new JSONField) there will be a tremendous number of deprecation warnings logged on startup
    • Should we find a way to hide the warnings and proceed with backports or should we make 3.15 the minimum recommended version for supporting Django 3?
      • No backports, 3.15 only for official support
  • [osapryki] State of Token Authentication support in pulpcore.
    • no progress, won't be in 3.15
    • need to create a new plugin
    • [osapryki] drf auth token has security concerns, encourage not to use it
    • needs to be in 3.16
  • pulp_file release with pulpcore 3.15 compatibility?
    • let's wait for now, there are might be changes required for 3.15 compatibility
  • many duplicate key errors in postresql logs
  • 3.14.4
    • cherry picks are done
    • dralley to release

Action items

  • [osapryki and dkliban] to get the list of proposed projects for token auth support and check with security teams

August 3, 2021

Action items

  • [dkliban] to close @dannysauer PRs
  • [ipanova] to schedule docs day and prep a query for the next meeting

July 27, 2021

Action Items

  • [ttereshc] to file a task to automate more cherry-picking process
  • [fao + dkliban] follow up with bin about upgrade issue

July 20, 2021

  • Backport to 3.14? https://github.com/pulp/pulpcore/pull/1484
    • outcome: it's backported
  • pulp_ci_centos image has Python 3.8 now
    • Release branches use this, will be running against 3.8
    • Is that a problem? We can make a 3.6 base image
    • outcome: Don't pursue this for release branches
  • https://github.com/pulp/pulp_file/pull/538
    • Backport to pulp_file 1.8?
    • outcome: yes to backport @daviddavis to do so
  • django 3.2 - https://github.com/pulp/pulpcore/pull/1464
    • outcome: merged
  • Investigating how to backport migrations
  • RBAC work update
    • bmbouter to try to make
      • assign_role(role, user_or_group, obj=None)
      • remove_role(role, user_or_group, obj=None)

Action Items

July 13, 2021

Action items

July 6, 2021

  • Rotate the release engineering role
    • outcome: done, dkliban is 3.15 release lead
  • how to allow users to have more control over the routes included in urls
  • katello indicated they would not recommend investing additional effort in the old tasking system
    • Except insofar as it impacts katello 3.18
    • what to do with the old epic? CLOSE - WONTFIX?
    • outcome: will close WONTFIX and invite anyone to reopen, also recommend users upgrade
  • Sync pipeline race condition when syncing repos w/ identical content
    • https://pulp.plan.io/issues/8967
    • I distinctly remember being able to reproduce this, and it's coming up in HTB, but I can't reproduce any more? Maybe just not enough attempts? But I don't remember this being explicitly fixed
    • outcome: @dalley will try to reproduce some if he has time, not an official AI

Action Items

  • [dkliban] pick tentative 3.15 date and schedule first go/no-go meeting

June 29 2021

Action Items

  • [bmbouter] to ask katello if they want pulp to continue investigating old-style tasking system

June 22 2021

Topics

  • Making new-style tasking system the default with 3.14?
  • content app is shown as online for quite a while (~20 sec) after being stopped
  • Confused by https://pulp.plan.io/versions/242
    • I thought we were using milestones for releases?

Action Items

  • [ttereshc] file an issue to support graceful shutdown for content app
  • [mdellweg] switch new-style tasking to be enabled by default and improve docs on how to switch between
  • [ipanova] delete milestone https://pulp.plan.io/versions/242 and move onto 3.15
  • [mdellweg] plan a deep dive for the new tasking system

June 15 2021

Topics

Action Items

  • [dkliban] to continue working with @dannysauer and help with their PRs
  • [ttereshc] come up with a proposal for plugin removal
  • [mdellweg and bmbouter] continue old tasking system investigation
  • [dkliban] update and move release guide to GH community repo's wiki. email pulp-dev with link to new guide.
  • [bmbouter] to file issue on how to generically load urls into pulp

June 8 2021

Topics

Action Items

  • [bmbouter & dalley] add tasking env var to django 3.2 epic (https://pulp.plan.io/issues/8488)
  • [dkliban] to continue working with @dannysauer and help with their PRs
  • [ttereshc] come up with a proposal for plugin removal
  • [dalley and bmbouter] to review tasking system PR from @x9c4
  • [dkliban and daviddavis] use new release automation to release pulp_file 1.8.0
  • [mdellweg] setup a meeting for tasking issues

June 1 2021

Topics

Action Items

  • [bmbouter & dalley] add tasking env var to django 3.2 epic
  • [dkliban] to engage contributor @dannysauer and help with their PRs
  • [dkliban] file issue to update CI to use python 3.7 and the single container to use python 3.7
  • [ipanova] set up a RBAC meeting
  • [ipanova] reach out to Melanie and ask for a meeting to address Danny's feedback + team prefers survey
  • [ttereshc] come up with a proposal for plugin removal
  • [dalley and bmbouter] to review tasking system PR from @x9c4

May 25, 2021

Topics

Action Items

  • [dkliban] to engage contributor @dannysauer and help with their PRs
  • [bmbouter & dalley] add tasking env var to django 3.2 epic
  • [david] email asking users about python 3.6 and django 3.2
  • [dkliban] file issue to update CI to use python 3.7 and the single container to use python 3.7
  • [ipanova] reach out to Melanie w/r to Danny's feedback so we prepare it in a format that can be shared/discussed with a wide group/community

May 18, 2021

Topics

Action Items

  • [ipanova] to invite pulp docs day since we identified issues
  • [dkliban] to engage contributor @dannysauer and help with their PRs
  • [dalley] to move back the 3.13 release to may 24th
  • [bmbouter, dalley, gerrod] to help round up 3.13 bocking Prs
  • [dkliban] to review upgrade test docs in plugin_template and merge if good
  • [x9c4] to review what plugins need releases prior to 3.13 release and bring up at open floor today
  • [ttereshc] to file upstream logging bug related to BZ and invite discussion about how to handle

May 11, 2021

Topics

  • Hold https://pulp.plan.io/issues/8386 for 3.14
    • could potentially break plugins (pulp_rpm) that want 3.13
  • Possible scheme to "backport idempotent data migrations"
    • We cannot backport migrations, but we could wrap the migrating code into a post_migrate action on the backport only.
    • This can only work for pure data migrations( no schema change).
    • Being on the dot releases, the post_migrate code may be run arbitrarily often before the real migration (coming with the minor release) will run once. Therefore the code must be idempotent.
    • The post_migrate code should not appear on master ever, because it may be incompatible with later database schemas.
  • Response to checksum migration
    • https://github.com/pulp/pulpcore/pull/1313#issuecomment-838075001
    • considered 3 options:
      • option (1): make it a no-op
      • option (2): make it continue even if there are errors
      • option (3): leave it as is
      • question: should the migration also download content
        • overall folks believe no, mostly because the common case is reducing the number of checksums not adding them
    • decision: go with option (2) @daviddavis to update his PR and reply to the concern
  • Docs Backlog ( let's time box it 20mins)
  • Idea/quesiton: should we add DRF token authentication to pulpcore, can pulp-container use it?
  • Backports for django CVE fix
    • 3.9 - 3.12 for pulp_deb
    • katello & galaxy_ng need: 3.7, 3.9, 3.11
    • bmbouter to release backports

Action Items

[fao] write a report about upgrade tests and send on pulp-dev mailing list

May 4, 2021

Topics

Action Items

April 27, 2021

Topics

  • Migration issue on galaxy
  • 3.13 - https://pulp.plan.io/versions/188
    • Revisit next week
  • Move from gnupg to pretty-bad-protocol?
  • 3.12.2/3.7.6 to release
    • Investigating another potential issue
  • Katello hits this 75% of the time on el8 runs
  • Testing the waters on removing RemoteArtifact
    • TL;DR what if we just use "Artifact" + a small table for remote sources, validated by constraints rather than a separate table schema.
      • https://github.com/pulp/pulpcore/compare/master…dralley:delete-remoteartifact#diff-81f6a78175bb93934b6beff952646d3ca1ef3731f1ff14492d4ec77bfc3fdf82R224-R241
      • Fixes https://pulp.plan.io/issues/8305
      • Simplifies working w/ artifacts
        • can filter Artifact by whether it's on_demand or not
        • update artifacts in-place when files are downloaded
        • delete "RemoteArtifactSaver" stage and _needed_remote_artifacts()
    • I have a prototype that works for sync, should I invest more time in it?
  • Review old quarter open issues

Action Items

April 20, 2021

Topics

  • Demo videos?
    • Was asked about a demo video for a feature
    • I guess we're not doing these anymore?
    • Fail to record anything due to capacity and commitments
    • Record demos ad hoc?
      • Ask feature writer to record demo when stakeholder asks for one
  • Releasing https://pulp.plan.io/issues/8578
    • Problem: BaseDistribution is deprecated but plugin api is missing RepositoryVersionRelatedField
    • 3.12.1 or early/small 3.13.0?
      • bumping minor release would cause extra churn
  • 3.13 - https://pulp.plan.io/versions/188
    • Needs date and release lead (rotation on lines 10-11)
  • make distribution update synchronous https://pulp.plan.io/issues/7762
    • rhui would like to dev freeze by may
  • Pulp 2 to Pulp 3 enablement session for Satellite
    • [fao] I need some onboarding
  • Streamed endpoints
  • Review old quarter open issues

Action Items

April 13, 2021

Topics

Action Items

April 6, 2021

Topics

Action Items

March 30, 2021

Previous AIs

Topics

Actions Items

March 23, 2021

Previous AIs

Topics

Action Items

March 16, 2021

Previous AIs

[mdellweg] summarize "safety in deletion" of remotes feature onto https://pulp.plan.io/issues/8305 [done]

Topics

  • deleting and rejecting, timeline and scheduling?
    • https://pulp.plan.io/issues/7659 run orphan clean up in parallel
    • ask for deleting artifact but keeping the content
      • keeping the record but freeing diskspace;
      • delete collection-1.2.3 tarball and never allow collection-1.2.3 to be uploaded again
      • version consistency + free disk space
  • retain N repository versions, request for comment
  • improving how users can identify orphans, request for comment
  • should this merge? https://github.com/pulp/pulp/pull/4020/
    • may simplify satellite carrying downstream patch if they only need to patch pulp_rpm. low-risk, small patch.
    • Yes, merge it
  • 3 month planning

Action Items

March 9, 2021

Previous AIs

  • [mdellweg] look for any docs issues that we might need for 3.11
    • don't have time to complete for 3.11, so we skip and will revisit for 3.12
  • [dalley] get more info about what happens remote gets deleted to revisit next week
    • deleting a remote, then recreating the remote, then resyncing it, everything is fixed

Topics

Action Items

[mdellweg] summarize "safety in deletion" of remotes feature onto https://pulp.plan.io/issues/8305 [done]

March 2, 2021

Previous AIs

  • [mdellweg] ping quba42 about pulp_deb CI; Done

Topics

  • docs day for 3.11. Does it makes sense to schedule it this time? I don't think anyone(?) has made any docs PR for 3.10 docs day due to the workload[ipanova]
    • Skip but mdellweg will check for any docs issues that we might need for 3.11
  • Deleting a remote breaks content artifacts: https://pulp.plan.io/issues/8305
    • Get more info (eg does recreating the remote fix everything?)
    • Revisit next week
  • should Pulp sync handle 429?
    • It should currently
  • removal of tech preview label .doc or .feature?
    • We should be consistent. ttereshc demanded we use ".doc"
    • Maybe introduce tech preview section in the future?
  • https://github.com/pulp/pulpcore/pull/1086#issuecomment-788176427
    • Checking remote artifacts for publications
    • Pulpcore team to review PRs. Set up follow up discussion.
  • worker timeouts
    • HDD environments have WAL lock issues
  • Removal (or not) of tech-preview labels in 3.11 and beyond!

Action items

  • [mdellweg] look for any docs issues that we might need for 3.11
  • [dalley] get more info about what happens remote gets deleted to revisit next week

February 23, 2021

Previous action items

Topics

Action items

[mdellweg] ping quba42 about pulp_deb CI; Done

February 16, 2021

Previous action items

Topics

Action items

  • [david] Close out https://pulp.plan.io/issues/5510 with comment directing them to labels
  • [david] file/update issues about checks
  • [bmbouter] add galaxy tag to track galaxy requests

February 9, 2021

Previous action items

None

Topics

Action items

February 2, 2021

Previous action items

Topics

  • Status API app name changing (bugfix, but backwards incompatible)
    • https://github.com/pulp/pulpcore/pull/1102
    • 4 options
      • do nothing - things update and changed
      • use the name attribute and strip off ".app" - this would get you back to the original
        * have plugins change their label as part of 3.10 compatibility release
      • defer??
    • Decision: use labels
  • Encrypting data at rest issue FYI ( get into pulpcore 3.12)
  • Revisiting returning secrets in the API for authorized users
  • rbac for artifacts

Action items

None

January 27, 2021

Previous action items

Topics

Action items

  • [fao89] will port fr the rate limit code to pulpcore - david + brian will review
  • [brian and matthias] will meet to talk about security scanners
  • [bmbouter] to file story for adding proxy_username and proxy_password and add to 3.11

January 19, 2021

Previous action items

  • [bmbouter] to ask Satellite if they require this and when https://pulp.plan.io/issues/7683
    • Satellite PM doesn't need. David to check with support.
  • [ipanova] open story to add write api for users
    • Done.
  • [daviddavis] schedule fips check in meeting
    • Done. Next meeting is Jan 28.

Topics

Action Items

January 12, 2021

Previous action items

Topics

Action Items

  • [bmbouter] to ask Satellite if they require this and when https://pulp.plan.io/issues/7683
  • [ipanova] open story to add write api for users
  • [daviddavis] schedule fips check in meeting

January 5, 2021

Previous action items

Topics

Action Items

tags: pulpcore
Last changed by 
 
Pulp
Design/Discussion/Meeting minutes for https://pulpproject.org/
0
735

Read more

Pulpcore team meeting

Core SME List

Apr 29, 2025
Pulpcore/katello/pulp_deb integration meeting

See also: https://discourse.pulpproject.org/t/katello-pulp-community-integration-meeting-minutes/39

Apr 16, 2025
CLI Team

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

Apr 9, 2025
RPM meeting

discuss adopting zero-downtime-migration strategy

Mar 6, 2025
Read more from Pulp
Published on HackMD