Pulp

05/17/2019

• 
  daviddavis RPM Support

  06:39 PM · Commented on issue

  I looked at the code and it seems that publishing a repo is just a shorthand for publishing its latest repository version since publish tasks are currently locking on a repository version. I suppose if we wanted to make this change, we'd... Issue #4793: Locking does not work as expected with Publications

  Expected behavior: A publication can be created immediately after kicking off a sync task, because it will wait for the prior task to complete, at which point there will be a repository version to use.
  Actual behavior:...
• 
  daviddavis Pulp

  05:32 PM · Commented on issue

  If we did the rename in pulp 2, would we have to provide some sort of migration? Issue #4834: File directories between pulp 2 and pulp 3 conflict

  This is a problem for users (eg Katello) running both Pulp 2 and Pulp 3 side-by-side but also potentially in place upgrades too. Both pulp 2 and pulp 3 save files to /var/lib/pulp and /var/lib/pulp/published. It's possible to change this...
• 
  daviddavis Published artifacts. See:
  https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/storage.py#L131-L147

  05:13 PM · Commented on issue
• 
  daviddavis @bmbouter pulp 3 stores stuff in /var/lib/pulp/published as well as pulp 2.

  05:09 PM · Commented on issue
• 
  daviddavis Pulp

  05:28 PM · Commented on issue

  @asmacdo, I think your point makes sense. Let me give another example though: a user uploaded a package with sensitive information like customer info or a password. Even git lets you rewrite history to remove stuff. It's painful but poss... Story #4832: As a user, I can filter all repo versions by content unit

  If you want to delete a content unit, there's no way to check which repo versions it belongs to. This means that deleting content is virtually impossible.
  We need to give users a way to filter repo versions by content. The problem is ...
• 
  daviddavis Pulp

  05:00 PM · Closed issue

  We decided that we'll allow users to create distributions without distributing anything. This could be to reserve a path namespace, take a publication offline quickly without having to delete the distribution, etc
  Issue #4840 (CLOSED - WONTFIX): Prevent users from creating publication distributions without a ...

  ...
• 
  daviddavis Pulp

  04:58 PM · Closed issue

  We decided that we'll allow users to create distributions without distributing anything. This could be to reserve a path namespace, take a repo/repo version offline quickly without having to delete the distribution, etc Issue #4837 (CLOSED - WONTFIX): Prevent users from creating repo version distributions without re...

  The RepositoryVersionDistributionSerializer should check that either repo or repo version is being passed:...
• 
  daviddavis File Support

  04:13 PM · Commented on issue

  Talked to Katello and they said this is a P1. Story #4827: Add artifact sha details to the content API

  It would be helpful to see artifact sha details on the content details/list results to avoid an additional call to artifacts API to fetch sha details.
  

05/16/2019

• 
  daviddavis Ansible Plugin

  10:38 PM · Commented on issue

  De-prioritizing this. Task #3789: As a user, I can sync Roles from one Pulp server to another
• 
  daviddavis Ansible Plugin

  10:37 PM · Edited issue

  Applied in changeset commit:pulp_ansible|3107cb600a8bb339758ca19b41e93bdf1b9ff847. Issue #4820 (MODIFIED): Update pulp_ansible to use RepositoryVersionDistribution

  Distributions have been replaced by PublicationDistributions and RepositoryVersionDistributions. We need to update pulp_ansible to use the latter.