Re: [Pulp-dev] pulpcore team meeting notes - May 25, 2021

[Neal Gompa]

Brian,

That's awesome! I'll also note that a variation of this workflow would
be desired for mirrors too, such as mirroring distributions or
prominent third-party repos (EPEL, Packman, COPRs, OBS repos, etc.).

On Thu, Jun 3, 2021 at 11:11 AM Brian Bouterse  wrote:
>
> Thank you for sharing this use case outline with me. I am hoping we can 
> prioritize rbac work like this. It's very important.
>
> On Wed, Jun 2, 2021 at 11:35 AM Neal Gompa  wrote:
>>
>> Hey Brian,
>>
>> Yes, for sure! I'm basically looking into using RBAC to support a
>> workflow like so:
>>
>> * Automation via a service account imports RPMs and DEBs into a pool
>> * Automation via another service account selects those packages to
>> publish into various staging repos
>> * Select users/groups can promote those packages to their assigned
>> "stable" repos
>>
>> The idea is that I can partition ACLs for various functions of Pulp to
>> prevent unwanted actions.
>>
>>
>> On Wed, Jun 2, 2021 at 10:56 AM Brian Bouterse  wrote:
>> >
>> > Hi Neal,
>> >
>> > Apologies for the late reply. We've added the RBAC to various endpoints in 
>> > pulpcore and some plugins, but what I think would be helpful is if we had 
>> > a way to more clearly identify what has RBAC and what doesn't across 
>> > pulpcore and plugins. Would that be helpful?
>> >
>> > Thank you,
>> > Brian
>> >
>> >
>> > On Tue, May 25, 2021 at 11:46 AM Neal Gompa  wrote:
>> >>
>> >> On Tue, May 25, 2021 at 11:23 AM Brian Bouterse  
>> >> wrote:
>> >> >
>> >> > * Making top-level Authentication page in docs
>> >> > * https://pulp.plan.io/issues/8799
>> >>
>> >> The docs currently mention that RBAC stuff is planned, is there
>> >> something that shows the status of that? This is something that I'd
>> >> love to see in Pulp sooner rather than later...
>> >>
>> >>
>> >> --
>> >> 真実はいつも一つ！/ Always, there's only one truth!
>> >>
>>
>>
>> --
>> 真実はいつも一つ！/ Always, there's only one truth!
>>


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


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

Re: [Pulp-dev] pulpcore team meeting notes - May 25, 2021

[Neal Gompa]

Hey Brian,

Yes, for sure! I'm basically looking into using RBAC to support a
workflow like so:

* Automation via a service account imports RPMs and DEBs into a pool
* Automation via another service account selects those packages to
publish into various staging repos
* Select users/groups can promote those packages to their assigned
"stable" repos

The idea is that I can partition ACLs for various functions of Pulp to
prevent unwanted actions.


On Wed, Jun 2, 2021 at 10:56 AM Brian Bouterse  wrote:
>
> Hi Neal,
>
> Apologies for the late reply. We've added the RBAC to various endpoints in 
> pulpcore and some plugins, but what I think would be helpful is if we had a 
> way to more clearly identify what has RBAC and what doesn't across pulpcore 
> and plugins. Would that be helpful?
>
> Thank you,
> Brian
>
>
> On Tue, May 25, 2021 at 11:46 AM Neal Gompa  wrote:
>>
>> On Tue, May 25, 2021 at 11:23 AM Brian Bouterse  wrote:
>> >
>> > * Making top-level Authentication page in docs
>> > * https://pulp.plan.io/issues/8799
>>
>> The docs currently mention that RBAC stuff is planned, is there
>> something that shows the status of that? This is something that I'd
>> love to see in Pulp sooner rather than later...
>>
>>
>> --
>> 真実はいつも一つ！/ Always, there's only one truth!
>>


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


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

Re: [Pulp-dev] pulpcore team meeting notes - May 25, 2021

[Brian Bouterse]

Hi Neal,

Apologies for the late reply. We've added the RBAC to various endpoints in
pulpcore and some plugins, but what I think would be helpful is if we had a
way to more clearly identify what has RBAC and what doesn't across pulpcore
and plugins. Would that be helpful?

Thank you,
Brian


On Tue, May 25, 2021 at 11:46 AM Neal Gompa  wrote:

> On Tue, May 25, 2021 at 11:23 AM Brian Bouterse 
> wrote:
> >
> > * Making top-level Authentication page in docs
> > * https://pulp.plan.io/issues/8799
>
> The docs currently mention that RBAC stuff is planned, is there
> something that shows the status of that? This is something that I'd
> love to see in Pulp sooner rather than later...
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] pulpcore team meeting notes - May 25, 2021

[Neal Gompa]

On Tue, May 25, 2021 at 11:23 AM Brian Bouterse  wrote:
>
> * Making top-level Authentication page in docs
> * https://pulp.plan.io/issues/8799

The docs currently mention that RBAC stuff is planned, is there
something that shows the status of that? This is something that I'd
love to see in Pulp sooner rather than later...


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


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

[Pulp-dev] pulpcore team meeting notes - May 25, 2021

[Brian Bouterse]

## Topics
* Is this a bug or intentional?
* https://pulp.plan.io/issues/8798
* [outcome] probably not intentional
* we cache these results to avoid recalculating them constantly
* Non-blocking orphan cleanup https://pulp.plan.io/issues/7659
* Plugin code needs to update timestamp
* [proposal] add `timestamp_of_interest` via migration in 3.14, then in
3.15 have orphan_cleanup become non-blocking and use `timestamp_of_interest`
* Django upgrade to 3.2
* https://pulp.plan.io/issues/8488
* django-guardian now resolved
*
https://github.com/pulp/pulpcore/pull/1352#pullrequestreview-667076933
* PR resolves pulp's issues
* https://github.com/pulp/pulpcore/pull/1116
* [goal] attempt to switch to Django 3.2 soon, maybe with 3.14
* Challenges with Python 3.6
* dependencies are dropping support
* Making top-level Authentication page in docs
* https://pulp.plan.io/issues/8799
* Relate backport requests to the original issue
*
https://docs.pulpproject.org/pulpcore/bugs-features.html#for-backport-requests
* will we benefit from automation here?
* Danny's feedback

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

[Pulp-dev] pulpcore team meeting notes - May 18, 2021

[Brian Bouterse]

## Topics
* Docs Backlog ( let's time box it 20mins)
* https://tinyurl.com/36hc2c9h
* 3.13.0 release moved to Monday May 24
* single container requires plugins to be compatible
*
https://github.com/pulp/pulp-oci-images/blob/latest/pulp/Containerfile#L14-L22
* 3.11.2 in-progress
* Logging suggestion/concern
* https://bugzilla.redhat.com/show_bug.cgi?id=1961508

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

[Pulp-dev] pulpcore team meeting notes - May 11, 2021

[Brian Bouterse]

## 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)
* https://tinyurl.com/36hc2c9h
* Idea/question: 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
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# May 4, 2021

## Topics
* New pulpcore meeting lead?
  * New lead rotation
* BaseDistribution drop migration problem
* https://pulp.plan.io/issues/8386#note-5
* Problem: using `run_before` prevents new plugins from being installed
* David to confirm that `run_before` won't work
* pulpcore meeting x open floor
* Goal: be more mindful of which topics can be discussed at open floor
* 3.13 - https://pulp.plan.io/versions/188
* dalley to release (bmbouter if release gets delayed past may 17)
* https://pulp.plan.io/issues/8656
* Django 2.2.21 introduced a change which breaks any workflows which use
stages API
* filename validation for file field fails
* https://docs.djangoproject.com/en/2.2/releases/2.2.21/
* individual orphan removal needs grooming
* https://pulp.plan.io/issues/8658
* prep for Docs day
* Installer release
* https://github.com/pulp/pulp_installer/pull/568
* Lately installer has been released by pulpcore team members
* Feedback from pulpcore people are welcome!

## Action Items
* [david] test out run_before for https://pulp.plan.io/issues/8386#note-5

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

[Pulp-dev] Pulpcore team meeting

[David Davis]

# April 27, 2021

## Topics
* Migration issue on galaxy
* https://github.com/pulp/pulpcore/pull/1174
* During migration it went out of memory
* Worries about migration breaking in the future when model(s) change
* Need better testing around upgrades
* 3.13 - https://pulp.plan.io/versions/188
* Revisit next week
* Move from `gnupg` to `pretty-bad-protocol`?
  * https://github.com/isislovecruft/python-gnupg
* 3.12.2/3.7.6 to release
* Investigating another potential issue
* Katello hits this 75% of the time on el8 runs
*  https://pulp.plan.io/issues/8603
*  daviddavis will look into it
* 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
  * https://tinyurl.com/pulpq12021

## Action Items
* [fao89] look at upgrade testing
* [fao89] find timeline for https://pulp.plan.io/issues/8192

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# April 13, 2021

## Topics

* Orphan endpoint
* As a user I want to see my orphaned content --> generic endpoint
* As a user I want to purge individual orphaned content
* As a user I want to purge orphaned content by type
* Whilst collection v1.2.3 is considered an orphan another v1.2.3 of
the same collection can NOT be published into any repo in Automation Hub
* can it enabled in the galaxy viewsets by comparing digest of the
uploaded binary data with the digest of the orphaned content ---> if
matches, reject upload?
* Orphan cleanup proposal https://pulp.plan.io/issues/7659
* Have orphan cleanup also consider longest running task?
* Use timestamp_of_interest or longest running task(LRT) start time
(whichever is greater)
* Leave out for now but recommend users don't set threshold above
LRT
* pulp_file release for pulpcore 3.12/3.13 https://pulp.plan.io/issues/8547
* Need to fix deprecations
* reclaim disk space story https://pulp.plan.io/issues/8459
* ROSI announcement
* pulp-smash removal from PyPI
*
https://github.com/pulp/Pulp-2-Tests/blob/013dffb728e4da5611b4b64e5310fe9cf1851479/setup.py#L43
*  Dynaconf or configuration issue?
https://bugzilla.redhat.com/show_bug.cgi?id=1937024#c11

## Action Items
* [david] update orphan cleanup proposal - https://pulp.plan.io/issues/7659
* [all] Look at ROSI announcement
* [all] Look at reclaim story https://pulp.plan.io/issues/8459
* [david] release pulp_file 1.7.0
* [david] ping ggainey about Pulp-2-Test's usage (of pulp-smash).

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# March 30, 2021

## Previous AIs
* [bmbouter] to close https://github.com/pulp/pulpcore/pull/1122 based on
the recent convo at pulp_ansible meeting
* [ttereshc] to review https://github.com/pulp/pulpcore/pull/1194
* Done, merged

## Topics
* another go/no-go meeting? thursday
* MasterModel distribution work update
* daviddavis to take over the completion of the work
* https://github.com/pulp/pulpcore/pull/1198/
* https://github.com/pulp/pulp_file/pull/484/
* bmbouter and mdellweg updating worker redesign PoC
* https://hackmd.io/Y0l9nBm9SFmPiIBXBz8lwQ
* pulp_file 1.6.1
* Going out today

## Actions Items
* [bmbouter] to close https://github.com/pulp/pulpcore/pull/1122 based on
the recent convo at pulp_ansible meeting

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

[Pulp-dev] Pulpcore team meeting notes

[Tanya Tereshchenko]

# March 23, 2021

## Previous AIs
* [ipanova] to set up meeting about content management (removal, rejecting,
etc) [done]
* [bmbouter] to merge https://github.com/pulp/pulp/pull/4020/ and reply to
thread [done]

## Topics
* Do we need a pulp_file release for pulpcore 3.11?
* we have 1.6.0 which allows 3.11
* we need to release pulp_file before 3.12 is out (April 6 is the
current tentative release date).
* Files are not being deleted from storage when calling the method delete()
* https://pulp.plan.io/issues/7316
* 3.12 or not?
* not a blocker, it's not a new problem or regression
* Repository version retention PR https://github.com/pulp/pulpcore/pull/1204
* Any thoughts/objections to only cleaning up repo versions on
`__exit__`?
* And NOT when the repo is updated
* https://pulp.plan.io/issues/8368#note-7
* opinions split whether to trim versions on the repository
update or not
* continue conversation on the PR and on the upcoming meeting
for content cleanup improvements
* https://github.com/pulp/pulpcore/pull/1204#discussion_r599518868

## Action Items
* [bmbouter] to close https://github.com/pulp/pulpcore/pull/1122 based on
the recent convo at pulp_ansible meeting
* [ttereshc] to review https://github.com/pulp/pulpcore/pull/1194
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# 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
* https://pulp.plan.io/issues/8368
* improving how users can identify orphans, request for comment
* https://pulp.plan.io/issues/8372
* 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
* [ipanova] to set up meeting about content management (removal, rejecting,
etc)
* [bmbouter] to merge https://github.com/pulp/pulp/pull/4020/ and reply to
thread

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

[Pulp-dev] Pulpcore team meeting notes

[Brian Bouterse]

# 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
* Deleting a remote breaks content artifacts:
https://pulp.plan.io/issues/8305
* add a validation for remote removal 1)check whether it is used in any
of the RA or 2) linked to any repo 3) add the force flag for force removal
* deleting and rejecting
* https://pulp.plan.io/issues/7659 run orphan clean up in parallel
* retain N repository versions
* https://pulp.plan.io/issues/8368

## Action Items
[mdellweg] summarize "safety in deletion" of remotes feature onto
https://pulp.plan.io/issues/8305 [done]
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# 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!
* https://pulp.plan.io/versions/174
* Discuss at go/no-go meeting

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# February 16, 2021

## Previous action items
* [bmbouter] to revise https://pulp.plan.io/issues/8202 and
https://pulp.plan.io/issues/8167
* Done
* [bmbouter] update working dir changes issue to include docs section about
tempfile https://pulp.plan.io/issues/8231
* Done
* [fao] contribute back to drf_spectacular to simplify our code

## Topics
* Close out this issue? https://pulp.plan.io/issues/5510
* System checks
* https://github.com/pulp/pulpcore/blob/master/pulpcore/app/checks.py
* https://git.io/JtX46
* Migration plugin support
* Pulpcore broke migration plugin?
* How long do we support migration plugin?
* For the foreseeable future
* Review items on the sprint
* https://pulp.plan.io/projects/pulp/issues?query_id=124
* Removed items we don't think we'll get to in near future

## 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 in plan.io to track galaxy requests

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# February 9, 2021

## Previous action items
None

## Topics
* https://pulp.plan.io/issues/8202
* Which fields need to be write_only?
* 3.11 release date? volunteer?
* March 2
* ipanova to release
* Discuss rotating the role
* working directory changes
* https://pulp.plan.io/issues/8231
* drf_spectacular
* https://pulp.plan.io/issues/8209
* how to avoid copy code to customize? Is it ok to contribute back to
drf_spectacular?
* Content app performance
* https://pulp.plan.io/issues/8180
* At minimum, we need to tune some parameters, optimize codepaths
* We may want to investigate other means of serving content (or caching)
* RHUI and others want this anyway https://pulp.plan.io/issues/7810
Next steps:
* bring up at the katello integration meeting
* involve perf team to extend existing test plans
* start hackmd + schedule a meeting

## Action items
* [bmbouter] to revise https://pulp.plan.io/issues/8202 and
https://pulp.plan.io/issues/8167
* update working dir changes issue to include docs section about tempfile
https://pulp.plan.io/issues/8231
* [fao] contribute back to drf_spectacular to simplify our code

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# 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
* FIPS estimate for pulpcore work
* https://tinyurl.com/pulpcorefips
* Estimate: 2.5 FTE
* Release automation - https://pulp.plan.io/issues/8093
* Added task to automate the pre-release steps
https://pulp.plan.io/issues/8119
* Proposal: start using github discussions
* https://github.com/orgs/pulp/teams/core
* let's not use it for now, let's instead explore using github issues
as planned fall 2020

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

[Pulp-dev] Pulpcore team meeting

[David Davis]

# January 12, 2021

## Previous action items
* [dkliban] to close out pulp_file 1.5.0
* Done
* [ttereshc] start discussion about LTS versions of pulp
* https://www.redhat.com/archives/pulp-dev/2021-January/msg3.html
* Done

## Topics
* Download and verify - https://pulp.plan.io/issues/7683
* Needs to be implemented in pulpcore
* bmbouter to ask for deadline
* Deadline for https://pulp.plan.io/issues/7659?
* Would like to fix by march/april
* write api for users
* All agreed to proceed - AI open a story
* Restrict default permissions to admin users
* https://github.com/pulp/pulpcore/pull/1064

## Action Items
* [bmbouter] to ask find out if/when this is needed
https://pulp.plan.io/issues/7683
* [ipanova] open story to add write api for users
* [daviddavis] schedule fips check in meeting

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

[Pulp-dev] Pulpcore team meeting

[David Davis]

# January 5, 2021

## Previous action items
* [dkliban] to release pulp_file 1.5.0
* [ttereshc] work on https://pulp.plan.io/issues/7869
* done https://github.com/pulp/plugin_template/pull/325
* [x9c4] write a task to have a test that searches for log messages with
deprecation warnings
* https://pulp.plan.io/issues/7997 [Done]
* [x9c4] start a pulp-dev thread about RBAC - objects that do not have
access policy are accesible by default
* Done
* https://github.com/pulp/pulpcore/pull/1064
* [dklban] to look at https://github.com/pulp/pulpcore/pull/799
* Done. Needs some installer changes.
* [ttereshc] update the release guide and plugin templates in plan.io
clarify when to bump plugin's Y release.
* done
https://pulp.plan.io/projects/pulp/wiki/Pulp3_Release_Guide#Criteria-to-have-the-Y-release-for-plugins
* needs feedback
https://www.redhat.com/archives/pulp-dev/2020-December/msg00032.html

## Topics
* Move off Travis https://pulp.plan.io/issues/7859
* need a volunteer for the remaining task to publish docs on every push
* Backports https://pulp.plan.io/issues/7950 and
https://pulp.plan.io/issues/7951
* on hold till the fixes are merged
* galaxy requirement: pulpcore>=3.7,<3.9 (backport will be needed in
3.7 and 3.8) https://github.com/ansible/galaxy_ng/blob/4.2.0/setup.py#L60
* Object labels https://pulp.plan.io/issues/7127
 * Need a volunteer to deliver in pulpcore 3.10
 * daviddavis: started on this
* Can we make the users, groups and permissions resources manageble by the
rest-api?
* enables us to add cli commands for them
* Sounds good. Check with bmbouter.
* https://pulp.plan.io/issues/8010
* Should backports be backported to every (minor) version between the fix
and the requested version
* We need an LTS, 3.7 is defacto an LTS version.
* Mailing list discussion
* new idna (sub-dependency) releases break pulp installation
* https://pulp.plan.io/issues/6169
* Follow up at installer meeting to ensure users are using the newest
version of pip (has newest dependency solver)
* Signing service SMEs?
* matthias and dkliban

## Action Items
* [dkliban] to close out pulp_file 1.5.0
* [ttereshc] start discussion about LTS versions of pulp

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

[Pulp-dev] Pulpcore team meeting notes

[Tanya Tereshchenko]

Previous action items

   - [dkliban] to schedule backlog grooming meeting
  - done
   - [dkliban] to email plugins about and close out
   https://pulp.plan.io/issues/7895
  - email sent, the issue will be closed today
   - [bmbouter] release pulp_file 1.5.0
  - dkliban will do it today

Topics

   - Move off Travis https://pulp.plan.io/issues/7859
  - Wrap up remaining issues?
 - ttereshc to pick up the cherrypick processor removal
 - need a volunteer for the remaining task to publish docs on every
 push
  - pulp_file 1.5.0 https://pulp.plan.io/issues/7953
  - Looks like brian was able to fix the deprecation
  https://github.com/pulp/pulp_file/pull/451
  - Still needs release and a volunteer - dkliban
   - Object labels https://pulp.plan.io/issues/7127
  - Updated issue with the design
  - Hoping someone can move this forward to deliver in pulpcore 3.10
   - Backports https://pulp.plan.io/issues/7950 and
   https://pulp.plan.io/issues/7951
  - on hold till the fixes are merged
  - galaxy requirement: pulpcore>=3.7,<3.9 (backport will be needed in
  3.7 and 3.8)
  https://github.com/ansible/galaxy_ng/blob/4.2.0/setup.py#L60
   - Is it ok that user can’t see any checksum for on_demand content?
   https://paste.ofcode.org/nXQBX7zVQWaxRbCFx2zrFw
  - I wonder if it matters for the FIPS reporting case
  - probably ok to have it as is, not much added value but a hassle to
  make the remote checksum available
   - RBAC - objects that do not have access policy are accessible by default
  - should we change for the opposite behaviour?
  - discuss on pulp-dev [x9c4]
   - bump of the plugin version during the pulpcore compatibility release
  - what is the reason to bump Y version if no major changes have been
  in the plugin?
 - the change of the floor version of pulpcore dependency
  - should we document this somewhere? It might be helpful to have a
  guide that will tell when to bump plugin version and pulpcore version in
  the plugin release process
 - update the release guide and plugin templates in plan.io
  - Can we make the users, groups and permissions resources manageble
   by the rest-api?
  - enables us to add cli commands for them
   - Can we add a test that searches for log messages with deprecation
   warnings?
  - it would be nice, but where?
 - plugin-from-pypi? probably too late
  - [x9c4] write a task
   - Should backports be backported to every (minor) version between the
   fix and the requested version
  - we need an LTS, 3.7 is de facto an LTS version.

Action Items

   - [dkliban] to release 1.5.0
   - [ttereshc] work on https://pulp.plan.io/issues/7869
   - [x9c4] write a task to have a test that searches for log messages with
   deprecation warnings
   - [x9c4] start a pulp-dev thread about RBAC - objects that do not have
   access policy are accessible by default
   - [dklban] to look at https://github.com/pulp/pulpcore/pull/799
   - [ttereshc] update the release guide and plugin templates in plan.io to
   clarify when to bump plugin’s Y release.
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# December 8, 2020

## Previous action items
* [ttereshc] to file a task to implement plugin removal
* Done https://pulp.plan.io/issues/7822
* [fao89] to figure out the use case for this fix
https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
* DRF raises 400/500 instead of 409
* https://issues.redhat.com/browse/AAH-152
* https://issues.redhat.com/browse/AAH-132
* https://httpstatusdogs.com/409-conflict
* https://http.cat/409
* Wait for user to report this. We need a reproducer

## Topics
* Backlog grooming
* pulp_file 1.5.0 release
* bmbouter to fix plugin config version and release
* Object label proposal
* https://hackmd.io/N4WFhHGWQtib7D1JIKzCDQ
* pulp_file docs
* Looks like the 1.4.0post1 release build succeeded? Docs still say 1.3
* [dkliban] fix in progress
* Task to take down read the docs for pulp_file:
https://pulp.plan.io/issues/7932
* Move off Travis check in
* https://pulp.plan.io/issues/7859
* Meet on Dec 15 & 22?
* Cancel Dec 22

## Action items
* [dkliban] to schedule backlog grooming meeting
* [dkliban] to email plugins about and close out
https://pulp.plan.io/issues/7895
* [bmbouter] release pulp_file 1.5.0

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

# December 1, 2020

### Previous action items
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions,
updating template config, etc)
* https://pulp.plan.io/issues/7817 (needs grooming, please provide
feedback)
* https://pulp.plan.io/issues/7818 (~~needs grooming~~)
* Done for now, focus is on moving off Travis for the short term.
* Defer until after 3.9 GA
* [ttereshc] to file a task to implement plugin removal
* [fao89] to figure out the use case for this fix
https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
* [david] updates on tagging planning https://pulp.plan.io/issues/7127
* Design is in progress. Will email out this week.

### Topics
* pulp_file 1.4.0
* ttereshc can be voluntold to do that
* dkliban to work on this this week
* alternate content sources design review
* https://pulp.plan.io/issues/7832

### Action items
* [ttereshc] to file a task to implement plugin removal
* [fao89] to figure out the use case for this fix
https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

## November 3, 2020

### Previous action items
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* [david] schedule pulpcore FIPS meeting with bmbouter for later in November
* Done.
* [dkliban] file a task for running tests for multiple plugins in one fips
environment in the installer nightly
* [fao89] look at driving forward release automation
* [x9c4] to backport https://pulp.plan.io/issues/7737 and release 3.6.z
* In progress
* [dkliban] cherry-pick 'request' commit to 3.8 branch
* Abandoned since change is a feature
* [ipanova] open a doc bug re:don't use settings in the models fields
   *  done https://pulp.plan.io/issues/7776
* [daniel] revert data corruption issue
* done. also have PR for repair all repos api endpoint.

### Topics
* FIPS epic for pulpcore - https://pulp.plan.io/issues/3778
* Closed out, new issues to be filed as needed
* Release automation next steps
* Post-release steps (branching, bumping to dev versions, updating
template config, etc)
* Need a Pulp query that shows issues for pulpcore (filters out
installer, operator, etc)
* Have automation open all PRs at once? Makes it easy to have a
reviewer review everything together
* Installation of our fips patch to Django is not working reliably in pypi
and source installation
* ask mikedep333 to take a look
* docs day
* nov 23
* go/no-go meetings?
* when do plugins bump requirement when they need a pulpcore feature
* Bump the floor version when you merge the change that requires
pulpcore feature
* If you require a change in pulpcore master, bump the floor to dev
version
* Remove dev from pulpcore version when releasing a plugin

### Action Items
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* [dkliban] file a task for running tests for multiple plugins in one fips
environment in the installer nightly
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions,
updating template config, etc)
* [david] a Pulp query that shows issues for pulpcore (filters out
installer, operator, etc)
* [david] move django fips repo to pulp
* [david] schedule go/no-go for nov 24
* [x9c4] to follow up on mailing list with proposal for setting pulpcore
requirements for plugins

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

Re: [Pulp-dev] Pulpcore team meeting notes

[David Davis]

What sort of topics are you hoping to follow/discuss? Asking because we run
an open floor discussion on Tuesdays/Fridays that's intended to discuss
topics of interest for the general Pulp community and not just a specific
team. More information:

https://pulpproject.org/get_involved/#meetings

David


On Tue, Oct 27, 2020 at 11:41 AM Calvin Spealman 
wrote:

> How does one get these meetings on their calendar and participate?
>
> On Tue, Oct 27, 2020 at 10:45 AM David Davis 
> wrote:
>
>> ## October 27, 2020
>>
>> ### Previous action items
>> * [ttereshc] follow up on relative_path problem on mailing list
>> * Done
>> * [david] To send out last call for feedback before merging
>> https://github.com/pulp/pulp-ci/pull/737
>> * [dkliban] to follow up with bmbouters about fips checks
>> * [ipanova] send an email to archive PUPS repository and file docs task
>> * Done
>> https://www.redhat.com/archives/pulp-dev/2020-October/msg00050.html
>> * [dkliban] file a task for running tests for multiple plugins in one
>> fips environment in the installer nightly
>>
>> ### Topics
>> * Tasking system improvements
>> * orhpan cleanup running in parallel
>> * bmbouter and ipanova collab on the design
>> * moved back a week
>> * resource manager bottleneck
>> * next step is to do an evaluation of tasking system performance
>> * Enforce funtional tests in pulp_file
>> * Add a check in Travis
>> * filed issue https://pulp.plan.io/issues/7748 potentially consider
>> adding option "enforce_tests" to the template instead?
>> * Commit bit for mdellweg
>> * 2 required reviews affects release process
>> * Should we pre-agree that 2 specific people are available for
>> reviews?
>> * Would excluding release branches from 2 ack be a solution?
>> * Go back to 1 required review, but opt into asking for 2 reviews for
>> any significant change?
>> * pulpbot to approve release PRs?
>> * For now, decrease # of required ACKs for release branches,
>> designate reviewers, and improve automation
>> * pulpcore version in plugin api
>> * https://pulp.plan.io/issues/7624
>> * https://pulp.plan.io/issues/6671
>> * need a volunteer to backport a fix to 3.6 and release it
>> * https://pulp.plan.io/issues/7737
>> * pulpcore 3.8.1 - can in include a backwards compatible change to the
>> plugin API?
>> *
>> https://github.com/pulp/pulpcore/commit/4063c346b4b75ffe74d2b0a95d650732dfb5ed8e
>> * settings should not be used in the models fields
>> *
>> https://github.com/pulp/pulp_container/pull/170/files#diff-1707426fbe1933a12da3490e42f0dbceea79e47f7c883708c0b0cb49755b1d94L383
>> *
>> https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/upload.py#L23
>> *  proposal - add to the plugin writers docs to not use settings in
>> the models but rather 'hardcode' those values
>> *  Silent data corruption bug
>> *  https://pulp.plan.io/issues/7676#note-8
>> *  revert the commit
>> *  cp to 3.7 and 3.8
>> *  open a new issue to repair the damage done
>> *  3.9.0 planned date?
>> *  daviddavis to release (tentatively November 30)
>> * When pulpcore is released and master branch version is bumped, the
>> nightly job for plugins will start failing.
>> *  Release pulp_file?
>>
>> ### Action items
>> * [david] To send out last call for feedback before merging
>> https://github.com/pulp/pulp-ci/pull/737
>> * [david] schedule pulpcore FIPS meeting with bmbouter for later in
>> November
>> * [dkliban] file a task for running tests for multiple plugins in one
>> fips environment in the installer nightly
>> * [fao89] look at driving forward release automation
>> * [x9c4] to backport https://pulp.plan.io/issues/7737 and release 3.6.z
>> * [dkliban] cherry-pick 'request' commit to 3.8 branch
>> * [ipanova] open a doc bug re:don't use settings in the models fields
>> * [daniel] revert data corruption issue
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>
>
> --
>
> CALVIN SPEALMAN
>
> SENIOR QUALITY ENGINEER
>
> cspea...@redhat.com  M: +1.336.210.5107
> [image: https://red.ht/sig] 
> TRIED. TESTED. TRUSTED. 
> ___
> 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

Re: [Pulp-dev] Pulpcore team meeting notes

[Calvin Spealman]

How does one get these meetings on their calendar and participate?

On Tue, Oct 27, 2020 at 10:45 AM David Davis  wrote:

> ## October 27, 2020
>
> ### Previous action items
> * [ttereshc] follow up on relative_path problem on mailing list
> * Done
> * [david] To send out last call for feedback before merging
> https://github.com/pulp/pulp-ci/pull/737
> * [dkliban] to follow up with bmbouters about fips checks
> * [ipanova] send an email to archive PUPS repository and file docs task
> * Done
> https://www.redhat.com/archives/pulp-dev/2020-October/msg00050.html
> * [dkliban] file a task for running tests for multiple plugins in one fips
> environment in the installer nightly
>
> ### Topics
> * Tasking system improvements
> * orhpan cleanup running in parallel
> * bmbouter and ipanova collab on the design
> * moved back a week
> * resource manager bottleneck
> * next step is to do an evaluation of tasking system performance
> * Enforce funtional tests in pulp_file
> * Add a check in Travis
> * filed issue https://pulp.plan.io/issues/7748 potentially consider
> adding option "enforce_tests" to the template instead?
> * Commit bit for mdellweg
> * 2 required reviews affects release process
> * Should we pre-agree that 2 specific people are available for reviews?
> * Would excluding release branches from 2 ack be a solution?
> * Go back to 1 required review, but opt into asking for 2 reviews for
> any significant change?
> * pulpbot to approve release PRs?
> * For now, decrease # of required ACKs for release branches, designate
> reviewers, and improve automation
> * pulpcore version in plugin api
> * https://pulp.plan.io/issues/7624
> * https://pulp.plan.io/issues/6671
> * need a volunteer to backport a fix to 3.6 and release it
> * https://pulp.plan.io/issues/7737
> * pulpcore 3.8.1 - can in include a backwards compatible change to the
> plugin API?
> *
> https://github.com/pulp/pulpcore/commit/4063c346b4b75ffe74d2b0a95d650732dfb5ed8e
> * settings should not be used in the models fields
> *
> https://github.com/pulp/pulp_container/pull/170/files#diff-1707426fbe1933a12da3490e42f0dbceea79e47f7c883708c0b0cb49755b1d94L383
> *
> https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/upload.py#L23
> *  proposal - add to the plugin writers docs to not use settings in
> the models but rather 'hardcode' those values
> *  Silent data corruption bug
> *  https://pulp.plan.io/issues/7676#note-8
> *  revert the commit
> *  cp to 3.7 and 3.8
> *  open a new issue to repair the damage done
> *  3.9.0 planned date?
> *  daviddavis to release (tentatively November 30)
> * When pulpcore is released and master branch version is bumped, the
> nightly job for plugins will start failing.
> *  Release pulp_file?
>
> ### Action items
> * [david] To send out last call for feedback before merging
> https://github.com/pulp/pulp-ci/pull/737
> * [david] schedule pulpcore FIPS meeting with bmbouter for later in
> November
> * [dkliban] file a task for running tests for multiple plugins in one fips
> environment in the installer nightly
> * [fao89] look at driving forward release automation
> * [x9c4] to backport https://pulp.plan.io/issues/7737 and release 3.6.z
> * [dkliban] cherry-pick 'request' commit to 3.8 branch
> * [ipanova] open a doc bug re:don't use settings in the models fields
> * [daniel] revert data corruption issue
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>


-- 

CALVIN SPEALMAN

SENIOR QUALITY ENGINEER

cspea...@redhat.com  M: +1.336.210.5107
[image: https://red.ht/sig] 
TRIED. TESTED. TRUSTED. 
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

## October 27, 2020

### Previous action items
* [ttereshc] follow up on relative_path problem on mailing list
* Done
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* [dkliban] to follow up with bmbouters about fips checks
* [ipanova] send an email to archive PUPS repository and file docs task
* Done
https://www.redhat.com/archives/pulp-dev/2020-October/msg00050.html
* [dkliban] file a task for running tests for multiple plugins in one fips
environment in the installer nightly

### Topics
* Tasking system improvements
* orhpan cleanup running in parallel
* bmbouter and ipanova collab on the design
* moved back a week
* resource manager bottleneck
* next step is to do an evaluation of tasking system performance
* Enforce funtional tests in pulp_file
* Add a check in Travis
* filed issue https://pulp.plan.io/issues/7748 potentially consider
adding option "enforce_tests" to the template instead?
* Commit bit for mdellweg
* 2 required reviews affects release process
* Should we pre-agree that 2 specific people are available for reviews?
* Would excluding release branches from 2 ack be a solution?
* Go back to 1 required review, but opt into asking for 2 reviews for
any significant change?
* pulpbot to approve release PRs?
* For now, decrease # of required ACKs for release branches, designate
reviewers, and improve automation
* pulpcore version in plugin api
* https://pulp.plan.io/issues/7624
* https://pulp.plan.io/issues/6671
* need a volunteer to backport a fix to 3.6 and release it
* https://pulp.plan.io/issues/7737
* pulpcore 3.8.1 - can in include a backwards compatible change to the
plugin API?
*
https://github.com/pulp/pulpcore/commit/4063c346b4b75ffe74d2b0a95d650732dfb5ed8e
* settings should not be used in the models fields
*
https://github.com/pulp/pulp_container/pull/170/files#diff-1707426fbe1933a12da3490e42f0dbceea79e47f7c883708c0b0cb49755b1d94L383
*
https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/upload.py#L23
*  proposal - add to the plugin writers docs to not use settings in the
models but rather 'hardcode' those values
*  Silent data corruption bug
*  https://pulp.plan.io/issues/7676#note-8
*  revert the commit
*  cp to 3.7 and 3.8
*  open a new issue to repair the damage done
*  3.9.0 planned date?
*  daviddavis to release (tentatively November 30)
* When pulpcore is released and master branch version is bumped, the
nightly job for plugins will start failing.
*  Release pulp_file?

### Action items
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* [david] schedule pulpcore FIPS meeting with bmbouter for later in November
* [dkliban] file a task for running tests for multiple plugins in one fips
environment in the installer nightly
* [fao89] look at driving forward release automation
* [x9c4] to backport https://pulp.plan.io/issues/7737 and release 3.6.z
* [dkliban] cherry-pick 'request' commit to 3.8 branch
* [ipanova] open a doc bug re:don't use settings in the models fields
* [daniel] revert data corruption issue
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

## October 20, 2020

### Previous action items
* [david] to update https://github.com/pulp/pulp-ci/pull/737
* ~~When PR is ready, email about the PR and ask for feedback~~
* ~~Done. Date set to Oct 23, 2020~~
* Will send an announcement and plugin information once merged
* ~~[ina] to file redmine issue about demo video requirement~~
* ~~done https://pulp.plan.io/issues/7703 and
https://pulp.plan.io/issues/7704~~
* ~~[david] to make meeting one hour~~
* ~~Done!~~
* [ttereshc] follow up on relative_path problem on mailing list, in progress

### Topics
* SigningService changes (on sprint, fyi really)
* https://pulp.plan.io/issues/7700
* https://pulp.plan.io/issues/7701
* Improvements to FIPS checks
* https://pulp.plan.io/issues/7696
* need one on checking for "future checksum use" e.g. during publish
time
* We no longer use PUPS, do we? we should update docs
*
https://docs.pulpproject.org/pulpcore/contributing/index.html#suggesting-changes-to-the-pulp-development-process
* maybe also mark repo a deprecated?
* how and where should we propose process improvement suggestions?
* [bmbouter] I can't attend so leaving comment here, +1 to
archiving this repo and announcing the process as no longer used. We should
try to move the relavent parts to the docs somehow (maybe file tickets). I
don't expect to replace this process with a formal process.
* Enforce funtional tests in pulp_file
* Add a check in Travis
* docs style guide question: newlines after each sentence or no?
* https://pulp.plan.io/issues/7570
* [bmbouter] my concern with having newlines instead of paragraphs was
that the docs unrendered become difficult to read (even though the blame
log does get easier).
* Backport to 3.7
* https://pulp.plan.io/issues/7702
* Should we regularly review redmine issues filed in between pulpcore
meetings? All except the "issue" type, since it's covered at triage.
* https://bit.ly/3m1e3nr
* running functional tests for all FIPS compliant plugins
* re-prioritize https://pulp.plan.io/issues/4832
* +1

### Action items
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* [ttereshc] follow up on relative_path problem on mailing list
* [dkliban] to follow up with bmbouters about fips checks
* [ipanova] send an email to archive PUPS repository and file docs task
* [dkliban] file a task for running tests for multiple plugins in one fips
environment in the installer nightly

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

## September 22, 2020

### Previous action items
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659
* Done!

### Topics

* Keeping the plugin API's call interface official (aka no private or
semi-private interfaces)
* Agreed, document as part of a greater push for better plugin writer
docs
* Pulpcore grooming on Friday
* David will be at DevConf.us
* dkliban to drive
* Signing reboot, next steps
* https://pulp.plan.io/issues/6926
* 3.7.0 release is happening today
* https://pulp.plan.io/issues/7463

### Action Items

* https://pulp.plan.io/issues/7487 is breaking pclean
* [daviddavis] revert and revisit for 3.8
* [bmbouter] to coordinate planning on https://pulp.plan.io/issues/6926

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

[Pulp-dev] Pulpcore team meeting

[Brian Bouterse]

## September 8, 2020

### Previous action items
* [dkliban] file a story to allow auto-publish and distribute
* Done. https://pulp.plan.io/issues/7469
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659
* not done, moved forward to next week

### Topics

* 3.7.0 is scheduled for Sept 22
* https://pulp.plan.io/issues/7463
* Go/No-Go: Tuesday Sept 15th, 12pm - 12:30pm EDT.
https://everytimezone.com/s/68f4535a
* Pulp UI project accepted by UMAss Lowell. Professors have started
recruiting students to take on the project.

### Action Items
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659

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

[Pulp-dev] Pulpcore team meeting

[David Davis]

## September 1, 2020

### Previous action items
* [dkliban] file a story to allow auto-publish and distribute
* [daviddavis] announce possible black PR merge date
* Done. Will merge tomorrow.
* [dkliban] call for release 3.6.1 tomorrow at open floor
* Going out today
* https://pulp.plan.io/issues/7429

### Topics
* PRs without any activity in the past month. Can we move them forward or
close them?
* https://github.com/pulp/pulpcore/pull/659
* https://github.com/pulp/pulpcore/pull/610
* https://github.com/pulp/pulpcore/pull/657
* Need a host for the next meeting September 8
* David has training, ttereshc and ipanova are on pto
* Roll out deprecations to plugins?
* https://github.com/pulp/plugin_template/pull/257
* Plugins can customize this.
* New plugins will have deprecations by default.
* Existing plugins can decide and roll it out themselves.

### Action Items
* [dkliban] file a story to allow auto-publish and distribute
* [bmbouter] to respond and close https://github.com/pulp/pulpcore/pull/659

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

## August 18, 2020

### Previous action items
* None

### Topics
* Grooming the backlog?
* https://pulp.plan.io/projects/pulp/issues?status_id=1
* Remove pulpcore items from sprint?
* https://pulp.plan.io/projects/pulp/issues?query_id=150
* How should the UI update a Distribution associated with a repository?
Right now we don't have a relationship between distributions and
repositories. So there is no way to schedule a task to update a
distribution before a publication finishes being created.
* Semi-related, similar problem with publications and repo-verisions
unless using "auto-publish" https://pulp.plan.io/issues/4793
* RBAC for UI endpoints being added in 3.7
* Proposal: functional test required for each feature and bug fix for
pulpcore and pulp_file
* pulp_rpm has this convention already

### Action items
* [daviddavis] to add a 2-hour backlog grooming meeting to focus on
pulpcore backlog
* [dkliban] file a story to allow auto-distribution of publications

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

## July 28, 2020

### Previous action items
* [bmbouter and daviddavis] to look into merging
https://github.com/pulp/pulpcore/pull/763
* merged!
* [bmbouter] aggregate tags/labels feedback on the issue
* [ipanova] mostly waiting on CDT to ack.

### Topics
* The same two declarative content units in one batch which differ only in
a remote they refer to
* https://pulp.plan.io/issues/7147
* is it too unexpected use case?
* should it be fixed in the pulpcore (or is it too special case and
better be fixed in the plugin)?
* Yes, let's fix it in pulpcore. Talk about implementation later.
* adjusting default download concurrency?
* https://hackmd.io/@ggainey/pulp3_sync_concurrency
* Discuss more at triage open floor
* Pulpcore cherry pick processor
* retiring the cherry pick processor for pulpcore and pulp_file
* cherry picks will be done on an as-needed basis by hand

### Action items
* [daviddavis] disable cherry pick processor for pulpcore and pulp_file
* Close out open PRs
* Delete "Needs Cherry Pick" label

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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

June 30, 2020

Previous Action Items

   -

   [dkliban] to ping alikins about https://github.com/pulp/pulpcore/pull/694
   -

   [bmbouter] to groom https://pulp.plan.io/issues/7015


Topic

   -

   RBAC changes in pulpcore
   -

  https://github.com/pulp/pulpcore/compare/master...bmbouter:rbac-PoC
  -

  Will not merge for 3.5 - plugins can develop against master after
  merge
  -

  Django admin will be tagged with tech-preview label
  -

   Relative path problem https://hackmd.io/02KBjCD3Q0WP7p4ALwzhJw


Action Items

   -

   [dkliban] to ping alikins and close out
   https://github.com/pulp/pulpcore/pull/694
   -

   [daviddavis] to follow up on https://github.com/pulp/pulpcore/pull/763
   - [bmbouter and dkliban] to look at
   https://github.com/pulp/pulpcore/pull/727


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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

June 23, 2020

Previous Action Items

   -

   [dkliban] to ping alikins about https://github.com/pulp/pulpcore/pull/694
   -

   [dkliban] to make https://pulp.plan.io/issues/6965 a plugin writer docs
   issue
   -

   [bmbouter] remove “Target Release - File” field


Topic

   -

   Linking remotes to repos https://pulp.plan.io/issues/7015
   -

  Feedback addressed. Needs someone to groom.
  -

   Problem: can’t make backwards incompatible changes while sticking to
   semver. We become locked into supported deprecations for years.
   -

  Adopt something like django’s model
  -

 Deprecations are removed after N y-releases
 -

  Release x-releases more often than every 7-8 years
  -

 Maybe yearly? Every 18 months? 2 years?
 -

  More discussion. Possible PulpCon topic.
  -

   More discussion about django admin ui.


Action Items

   -

   [dkliban] to ping alikins about https://github.com/pulp/pulpcore/pull/694
   - [bmbouter] to groom https://pulp.plan.io/issues/7015


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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

June 5, 2020

Previous Action Items

   -

   [bmbouter] to respond to PR 630
    and PR 659
   
   -

  We might use Django Admin pending RBAC
  -

  Meeting scheduled for PR 659 next week
  -

   [daviddavis] to groom https://pulp.plan.io/issues/6844
   -

   [daviddavis] AI to merge dependabot PRs
   -

   [dkliban] to look at https://github.com/pulp/pulpcore/pull/694
   -

   [bmbouter] schedule signing service meeting


Topic

   -

   Moving the pulp-fixtures location from /fixtures to /
   -

  https://github.com/pulp/pulp-fixtures/pull/160
  -

  Several PRs open against pulpcore, pulp_file, etc


Action Items

   -

   [daviddavis] to groom https://pulp.plan.io/issues/6844
   -

   [dkliban] to look at https://github.com/pulp/pulpcore/pull/694
   -

   [daviddavis] to file issue for django-filter 2.3.0
   https://github.com/pulp/pulpcore/pull/744


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

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

Topics

   -

   [bmbouter] Stages with duplicate content call _post_save() twice?
   -

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

  Accept issue but not work on it right now
  -

   [dkliban] https://pulp.plan.io/issues/6570 - new content handler
   interfaces
   -

  Will try to look. Needs go ahead or no go ahead
  -

   [bmbouter] https://pulp.plan.io/issues/5927 - validating content in
   stages API
   -

  Bmbouter to email pulp-dev calling out
  -

 No changes in stages API
 -

 5927 to be rewritten to be docs for plugin writer
 -

   [david/dellweg] merging of https://github.com/pulp/pulpcore/pull/663


Previous Action Items

   -

   [bmbouter and dkliban] - Review https://github.com/pulp/pulpcore/pull/577
   -

   [dkliban] - write up task for testing syncing using client certs
   -

   [bmbouter] to discuss on django-admin UI on pulp-dev
   -

   [daviddavis] discuss bumping pulp_file to 1.0
   -

   [daviddavis] send email to pulp-dev about modified issues after release
   -

   [dalley] discussion for relative_path problem
   -

   [dkliban] to summarize decision on write_only fields to pulp-dev


Open PRs

   -

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

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


Action Items

   -

   [bmbouter and dkliban] - Review https://github.com/pulp/pulpcore/pull/577
   -

   [bmbouter] - Rewrite and send out https://pulp.plan.io/issues/5927
   -

   [mdellweg] - email merge April 29 EOB for
   https://github.com/pulp/pulpcore/pull/663
   -

   [daviddavis] - make sure we have black documented
   -

   [dkliban] - write up task for testing syncing using client certs
   -

   [bmbouter] to discuss on django-admin UI on pulp-dev
   -

   [dalley] create a meeting for relative_path problem, send a link to
   Quirin Pamp
   -

   [bmbouter] champion the prometheus PR
   https://github.com/pulp/pulpcore/pull/518


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