Project

Profile

Help

Story #1884

closed

Pulp - Story #3693: Lazy for Pulp3

As a user, I can lazily sync python packages

Added by amacdona@redhat.com almost 8 years ago. Updated about 3 years ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
3.0.0
Target Release - Python:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 51
Quarter:

Description

With the previous work done in for python packages, it is now possible to create objects using only the metadata provided by the json API of PyPI. This metadata is also now provided by pulp publish.

Completion of this story should allow the user to set the download policy to on_demand and background.


Related issues

Related to Pulp - Story #4209: As a plugin writer, I can implement lazy sync for plugins with multiple metadata filesCLOSED - CURRENTRELEASEmdellweg

Actions
Related to Python Support - Test #4706: Add a test for lazy syncing contentCLOSED - COMPLETEActions
Blocked by Python Support - Story #1882: Rebuild model to support all package typesCLOSED - CURRENTRELEASEamacdona@redhat.com

Actions
Blocked by Python Support - Story #1883: As a user, I can sync and publish all package typesCLOSED - CURRENTRELEASEamacdona@redhat.com

Actions
Actions #1

Updated by amacdona@redhat.com almost 8 years ago

  • Blocked by Story #1882: Rebuild model to support all package types added
Actions #2

Updated by amacdona@redhat.com almost 8 years ago

  • Blocked by Story #1883: As a user, I can sync and publish all package types added
Actions #3

Updated by amacdona@redhat.com almost 8 years ago

  • Blocked by Issue #1183: As a developer, I can close this ticket as a duplicate of 1884 :) added
Actions #4

Updated by mhrivnak almost 8 years ago

I think this should be a story instead of an issue.

The description dives right into how to do this, but skips over what the goal is. :) "Lazy integration" is perhaps obvious to some, but it's helpful to have a more full description. Start with the desired behavior: we want the ability to set the download policy to on_demand or background. Describe the workflow of specifying that setting, accessing content, having it retrieved on-demand, etc. What will QE do to verify this?

The checklist is a good place for implementation details, including: add catalog entries during sync, document new importer settings, make new importer settings available in pulp-admin, add release notes, etc.

The "downloaded" boolean is already on FileContentUnit in platform, so you'll get that for free.

I'm not sure about the idea of updating the unit in the DB after download. Pulp's job is a LOT easier when units are immutable. Do we really need to update it for some reason?

Actions #5

Updated by dkliban@redhat.com almost 8 years ago

  • Triaged changed from No to Yes
Actions #6

Updated by dkliban@redhat.com almost 8 years ago

  • Triaged changed from Yes to No
Actions #7

Updated by amacdona@redhat.com almost 8 years ago

  • Tracker changed from Issue to Story
  • Subject changed from Lazy integration to As a user, I can lazily sync python packages
  • Groomed set to No
  • Sprint Candidate set to No
Actions #8

Updated by amacdona@redhat.com almost 8 years ago

  • Sprint Candidate changed from No to Yes
Actions #9

Updated by mhrivnak almost 8 years ago

  • Sprint/Milestone set to 21
  • Groomed changed from No to Yes
Actions #10

Updated by amacdona@redhat.com almost 8 years ago

  • Sprint/Milestone deleted (21)
Actions #11

Updated by amacdona@redhat.com almost 8 years ago

  • Description updated (diff)
Actions #12

Updated by mhrivnak almost 8 years ago

  • Sprint/Milestone set to 22
Actions #13

Updated by mhrivnak over 7 years ago

  • Sprint/Milestone deleted (22)
Actions #14

Updated by mhrivnak over 7 years ago

  • Sprint Candidate changed from Yes to No
Actions #15

Updated by bizhang almost 6 years ago

  • Tags Pulp 3 added
Actions #16

Updated by amacdona@redhat.com over 5 years ago

  • Blocked by deleted (Issue #1183: As a developer, I can close this ticket as a duplicate of 1884 :))
Actions #17

Updated by amacdona@redhat.com over 5 years ago

  • Blocked by Refactor #4132: Metadata is not downloaded in parallel added
Actions #18

Updated by dalley over 5 years ago

  • Parent issue set to #3693
Actions #19

Updated by dalley over 5 years ago

  • Related to Story #4209: As a plugin writer, I can implement lazy sync for plugins with multiple metadata files added
Actions #20

Updated by amacdona@redhat.com almost 5 years ago

  • Blocked by deleted (Refactor #4132: Metadata is not downloaded in parallel)
Actions #21

Updated by CodeHeeler almost 5 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to CodeHeeler
Actions #22

Updated by CodeHeeler almost 5 years ago

  • Sprint set to Sprint 51

Added by CodeHeeler almost 5 years ago

Revision 66e8a02a | View on GitHub

Add ability to lazy sync python packages

Add lazy support using DeclarativeVersion by specifying deferred_download which will check policy on remote.

fixes #1884 https://pulp.plan.io/issues/1884

Actions #24

Updated by CodeHeeler almost 5 years ago

  • Status changed from ASSIGNED to POST
Actions #25

Updated by amacdona@redhat.com almost 5 years ago

  • Sprint/Milestone set to 3.0 GA
Actions #26

Updated by CodeHeeler almost 5 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #27

Updated by bmbouter almost 5 years ago

  • Tags deleted (Pulp 3)
Actions #28

Updated by CodeHeeler almost 5 years ago

  • Related to Test #4706: Add a test for lazy syncing content added
Actions #29

Updated by dalley about 3 years ago

  • Platform Release set to 3.0.0

Also available in: Atom PDF