opencontainers / opencontainers/distribution-spec

Wrapper around s3 multipart upload protocol

Open
#210 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.1k
Forks
260
Avg merge
3d 23h
Merged PRs (30d)
1

Description

Has anyone given thought for how OCI could (easily? with some work?) be implemented to work alongside an s3 multipart upload compatible storage? For example, Minio is a good testing ground https://github.com/minio/minio/issues/10813. The creation of the request is fairly straight forward, but then the request to upload a part (akin to the PATCH for a chunk) is quite different. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/upload-part.html. I was thinking that it would be really useful to be able to implement the distribution spec alongside this one, but the challenge of course are the differences. The server could act as some receiver of the requests, parsing them and forwarding then to Minio (or the s3 compatible storage) but this is problematic in that it puts huge load on that server, which we don't want to do.

Does anyone have experience with allowing for this kind of support, or is the distribution spec really different enough that it's never going to be a thing?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files or tests are identified. Start by comparing the distribution specification's upload behavior with the AWS S3 UploadPart reference and the Minio issue linked in the discussion. Done would require a decided, documented approach for supporting S3 multipart-compatible storage without placing the upload load on the server.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.