Project

Profile

Help

Story #3900

As a user, I can use Pulp3 on S3

Added by bmbouter about 1 year ago. Updated 6 months ago.

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

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 48

Description

Pulp users should be able to configure S3 as the storage backend for their Pulp data. The backend needs to be provided by the django-storages0 python package. This should be an optional dependency for pulpcore that will be installed by users that want to use S3 as the storage backend.

The content app needs to be updated to recognize when the storage backend is S3. In immediate download use cases, the content app needs to redirect requests to the S3 URL stored on the Artifact. In the 'on demand' use cases, the content app needs to stream the artifact to the client and then save the Artifact. The S3 storage backend should handle the uploading of the file to S3 as part of the save.

Documentation needs to be added to let users know how to configure S3 as the storage backend.

[0] https://django-storages.readthedocs.io/en/latest/backends/amazon-S3.html


Related issues

Related to Pulp - Test #4383: Test Pulp on S3 NEW Actions
Related to Pulp - Story #4438: As a user, I can use the pulp installer to configure pulp to use S3 NEW Actions
Related to Docker Support - Task #4456: Test out docker with S3 ASSIGNED Actions
Related to RPM Support - Test #4457: Test out S3 support NEW Actions

Associated revisions

History

#1 Updated by bmbouter 11 months ago

  • Tags Pulp 3 RC Blocker added

I think this is a release blocker we should at least consider. I'm adding this here so we will see it at the RC blocker roundup meeting.

#2 Updated by dkliban@redhat.com 9 months ago

  • Description updated (diff)

#3 Updated by bmbouter 9 months ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

This looks like what I expect from this story.

#4 Updated by bmbouter 9 months ago

  • Sprint set to Sprint 47

#5 Updated by daviddavis 9 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to daviddavis

#6 Updated by rchan 9 months ago

  • Sprint changed from Sprint 47 to Sprint 48

#7 Updated by daviddavis 8 months ago

  • Status changed from ASSIGNED to POST

#8 Updated by daviddavis 8 months ago

#9 Updated by daviddavis 8 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#10 Updated by daviddavis 8 months ago

  • Related to Story #4438: As a user, I can use the pulp installer to configure pulp to use S3 added

#11 Updated by daviddavis 8 months ago

  • Related to Task #4456: Test out docker with S3 added

#12 Updated by daviddavis 8 months ago

  • Related to Test #4457: Test out S3 support added

#13 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#14 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3, Pulp 3 RC Blocker)

Please register to edit this issue

Also available in: Atom PDF