Temporary files are an inefficient use of cloud storage
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Version
All
Describe the bug
Pulp uses temporary files and puts them on the same storage backend as everything else (AFAIK) - storage backends like S3 or Azure require you to pay for usage, so using those services for short lived and often small files is not an efficient use of resources.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by tracing how temporary files are created and which storage backend they use, then compare that behavior with the S3 and Azure cost concern described here. Done would require a clearly scoped approach and evidence that short-lived files no longer use inefficient cloud storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100