Closed
Description
Currently, the implementation of uploads uses the local file system to store state. This was done to move the implementation along before setting too many details in stone and to validate the API.
This is terrible and must be fixed before releasing a serious implementation of the registry.
There are two options for implementing state storage:
- Store state in the
Locationheader of upload-related requests. Something like<host>/v2/<name>/blobs/uploads/<uuid>?_state=<hmac + urlbase64 encoded:{UUID: <uuid>, Name: <name>, Offset: 0}>would be appropriate, given that these are opaque to the client. This is desirable in that we remove the need for shared state, allowing the registry to scale better. - Store the upload state in redis. This will support more sophisticated coordination at the cost of scalability.
I'm in favor of 1, but we may implement both in the future. We should compare and contrast the benefits of each approach.