[Pulp-dev] Pulpcore team meeting notes

2021-03-17 Thread 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] Removing the pulp_deb docs from readthedocs

2021-03-17 Thread Quirin Pamp
With the pulp_deb 2.10.0 release all prominent links to pulp_deb documentation 
should now point at https://docs.pulpproject.org/pulp_deb/
Also, the old docs at https://pulp-deb.readthedocs.io/en/latest/ are now quite 
out of date.
As a result I think it would be best to take down the documentation on 
readthedocs (or replace it with a single URL to the new docs location).

If whoever has the relevant access rights to do this could do so, I would be 
much obliged.

Kind regards,
Quirin Pamp (quba42)
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev


[Pulp-dev] Katello/Pulp3 Integration meeting

2021-03-17 Thread Grant Gainey
March 17, 2021

Overview

   -

   Katello Schedule
   -

  3.18 November 2020
  -

 pulpcore 3.7
 -

  4.0 branching ~February 2021 (dry-run needed by end-of-Dec)
  -

 pulpcore 3.9
 -

  4.1 branching ~May 2021
  -

 pulpcore 3.10 (or newer)
 -

  4.2 branching ~August 2021
  -

  4.3 branching ~Nov 2021

Pulp

   -

   Pulpcore
   -

  3.7.4 released
  -

 Dynaconf fix
 -

  3.11 released!
  -

  3.12 “soon”
  -

 Will *not* be breaking-change
 -

 Jsherrill to review proposed 3.12 list
 -

https://pulp.plan.io/versions/182
-

   RPM
   -

  3.10 release in the next few days, will resolve many issues with
  errata handling
  -

  Distribution-tree fix (backported to 3.9.1)
  -

   Migration
   -

  0.9.0 and 0.9.1 released
  -

  Working with QE on issues
  -

  ttereshc is working on
  https://bugzilla.redhat.com/show_bug.cgi?id=1939090
  -

 revalidate re-migration-post-changes-in-pulp2 paths?
 -

   Ansible
   -

  Working on sync collection dependencies
  -

  Scoping AH/Satellite token support
  -

 Mtg next week to make sure we know which katello version needs this
 -

   Pulp CLI
   -

  0.7.0 released
  -

 Pulp-python and other fixes
 -


 
https://github.com/pulp/pulp-cli/blob/develop/CHANGES.rst#070-2021-03-15

 -

   pulp_container
   -

  Fixes backported to 3.7-compatible version (2.1)
  -

  How soon do we need 3.9-compatible backport release? (2.2)


Katello

   -

   Trying to ensure all the upstream stuff makes it downstream
   -

   Ansible poc finished
   -

   Correlation id support in review
   -

   User & dogfood-clone db testing
   -

  What’s the best way to fix the tasking-issue?
  -

  ggainey/dalley/bmbouter to see if we can learn anything about the
  tasking-issues
  -

 Look into logs?
 -

 What if postgres failed commits?
 -

   Work ongoing on nightly bindings testing


QE

   -

   Snap 17 > snap 16
   -

  No self patching needed
  -

   Migration + pulp3 testing continue
   -

  Lai to talk to team about re-migration test cases
  -

   Dogfood migration is still at 25% since yesterday, not sure if hanging
   -


  
https://dhcp-2-136.vms.sat.rdu2.redhat.com/foreman_tasks/tasks/9e0f7e77-5642-42c9-8b54-9139ff330438
  -

   BZs
   -

  “Migrated_pulp3_href NULL value” -
  https://bugzilla.redhat.com/show_bug.cgi?id=1939090
  -

 Tanya working on it
 -

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

  Couple of bz mistakenly put ON_QA
  -

  Verifying ON_QAs are still ongoing


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


[Pulp-dev] Pulp CLI Meeting Notes

2021-03-17 Thread Matthias Dellweg
## March 17, 2021

* Better classification of options
* I realized, we have three different types of options referring to
objects:
* filter options (used for list_command)
* lookup options (used for show, update, destroy)
* resource options (used in update, create, sync, ... to reference
other options)
* https://github.com/pulp/pulp-cli/pull/161
* I see some potential for each of them to make the actual command
definition even more descriptive than today.
* Easier command chaining/sequences
* Common workflows produce an href that needs to be manually copied to
be inspected or used in other commands. (publish, sync)
* Suggestion: have Pulp context store output of previous command and
have it be referencable through new resource language
* `pulp file publication create --repository foo`
* `pulp file distribution create --publication p:href ...`
* `pulp -b file repository sync --name foo`
* `pulp task show --href p:task`
* Reference language could use it's context features to have common
shorthands, aka p:pulp_href == p:href, p:latest_version_href == p:latest
* This would need a notion of a session
* Maybe we can implement a pulp-shell
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev