2014-11-18 00:29:42 +00:00
|
|
|
package storage
|
|
|
|
|
|
|
|
import (
|
2014-12-24 00:01:38 +00:00
|
|
|
"github.com/docker/distribution/digest"
|
2015-01-02 21:21:29 +00:00
|
|
|
"github.com/docker/distribution/manifest"
|
2014-12-24 00:01:38 +00:00
|
|
|
"github.com/docker/distribution/storagedriver"
|
2014-11-18 00:29:42 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
// Services provides various services with application-level operations for
|
|
|
|
// use across backend storage drivers.
|
|
|
|
type Services struct {
|
Spool layer uploads to remote storage
To smooth initial implementation, uploads were spooled to local file storage,
validated, then pushed to remote storage. That approach was flawed in that it
present easy clustering of registry services that share a remote storage
backend. The original plan was to implement resumable hashes then implement
remote upload storage. After some thought, it was found to be better to get
remote spooling working, then optimize with resumable hashes.
Moving to this approach has tradeoffs: after storing the complete upload
remotely, the node must fetch the content and validate it before moving it to
the final location. This can double bandwidth usage to the remote backend.
Modifying the verification and upload code to store intermediate hashes should
be trivial once the layer digest format has settled.
The largest changes for users of the storage package (mostly the registry app)
are the LayerService interface and the LayerUpload interface. The LayerService
now takes qualified repository names to start and resume uploads. In corallry,
the concept of LayerUploadState has been complete removed, exposing all aspects
of that state as part of the LayerUpload object. The LayerUpload object has
been modified to work as an io.WriteSeeker and includes a StartedAt time, to
allow for upload timeout policies. Finish now only requires a digest, eliding
the requirement for a size parameter.
Resource cleanup has taken a turn for the better. Resources are cleaned up
after successful uploads and during a cancel call. Admittedly, this is probably
not completely where we want to be. It's recommend that we bolster this with a
periodic driver utility script that scans for partial uploads and deletes the
underlying data. As a small benefit, we can leave these around to better
understand how and why these uploads are failing, at the cost of some extra
disk space.
Many other changes follow from the changes above. The webapp needs to be
updated to meet the new interface requirements.
Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-01-08 22:24:02 +00:00
|
|
|
driver storagedriver.StorageDriver
|
|
|
|
pathMapper *pathMapper
|
2014-11-18 00:29:42 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// NewServices creates a new Services object to access docker objects stored
|
|
|
|
// in the underlying driver.
|
|
|
|
func NewServices(driver storagedriver.StorageDriver) *Services {
|
|
|
|
|
|
|
|
return &Services{
|
|
|
|
driver: driver,
|
2015-01-09 00:55:40 +00:00
|
|
|
// TODO(sday): This should be configurable.
|
Spool layer uploads to remote storage
To smooth initial implementation, uploads were spooled to local file storage,
validated, then pushed to remote storage. That approach was flawed in that it
present easy clustering of registry services that share a remote storage
backend. The original plan was to implement resumable hashes then implement
remote upload storage. After some thought, it was found to be better to get
remote spooling working, then optimize with resumable hashes.
Moving to this approach has tradeoffs: after storing the complete upload
remotely, the node must fetch the content and validate it before moving it to
the final location. This can double bandwidth usage to the remote backend.
Modifying the verification and upload code to store intermediate hashes should
be trivial once the layer digest format has settled.
The largest changes for users of the storage package (mostly the registry app)
are the LayerService interface and the LayerUpload interface. The LayerService
now takes qualified repository names to start and resume uploads. In corallry,
the concept of LayerUploadState has been complete removed, exposing all aspects
of that state as part of the LayerUpload object. The LayerUpload object has
been modified to work as an io.WriteSeeker and includes a StartedAt time, to
allow for upload timeout policies. Finish now only requires a digest, eliding
the requirement for a size parameter.
Resource cleanup has taken a turn for the better. Resources are cleaned up
after successful uploads and during a cancel call. Admittedly, this is probably
not completely where we want to be. It's recommend that we bolster this with a
periodic driver utility script that scans for partial uploads and deletes the
underlying data. As a small benefit, we can leave these around to better
understand how and why these uploads are failing, at the cost of some extra
disk space.
Many other changes follow from the changes above. The webapp needs to be
updated to meet the new interface requirements.
Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-01-08 22:24:02 +00:00
|
|
|
pathMapper: defaultPathMapper,
|
2014-11-18 00:29:42 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Layers returns an instance of the LayerService. Instantiation is cheap and
|
|
|
|
// may be context sensitive in the future. The instance should be used similar
|
|
|
|
// to a request local.
|
|
|
|
func (ss *Services) Layers() LayerService {
|
2015-01-14 20:02:43 +00:00
|
|
|
return &layerStore{
|
|
|
|
driver: ss.driver,
|
|
|
|
blobStore: &blobStore{
|
|
|
|
driver: ss.driver,
|
|
|
|
pm: ss.pathMapper,
|
|
|
|
},
|
|
|
|
pathMapper: ss.pathMapper,
|
|
|
|
}
|
2014-11-18 00:29:42 +00:00
|
|
|
}
|
2014-11-22 03:39:52 +00:00
|
|
|
|
|
|
|
// Manifests returns an instance of ManifestService. Instantiation is cheap and
|
|
|
|
// may be context sensitive in the future. The instance should be used similar
|
|
|
|
// to a request local.
|
|
|
|
func (ss *Services) Manifests() ManifestService {
|
2015-01-14 20:02:43 +00:00
|
|
|
// TODO(stevvooe): Lose this kludge. An intermediary object is clearly
|
|
|
|
// missing here. This initialization is a mess.
|
|
|
|
bs := &blobStore{
|
|
|
|
driver: ss.driver,
|
|
|
|
pm: ss.pathMapper,
|
|
|
|
}
|
|
|
|
|
|
|
|
return &manifestStore{
|
|
|
|
driver: ss.driver,
|
|
|
|
pathMapper: ss.pathMapper,
|
|
|
|
revisionStore: &revisionStore{
|
|
|
|
driver: ss.driver,
|
|
|
|
pathMapper: ss.pathMapper,
|
|
|
|
blobStore: bs,
|
|
|
|
},
|
|
|
|
tagStore: &tagStore{
|
|
|
|
driver: ss.driver,
|
|
|
|
blobStore: bs,
|
|
|
|
pathMapper: ss.pathMapper,
|
|
|
|
},
|
|
|
|
blobStore: bs,
|
|
|
|
layerService: ss.Layers()}
|
2014-11-22 03:39:52 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
// ManifestService provides operations on image manifests.
|
|
|
|
type ManifestService interface {
|
2014-12-09 19:06:51 +00:00
|
|
|
// Tags lists the tags under the named repository.
|
|
|
|
Tags(name string) ([]string, error)
|
|
|
|
|
2015-01-14 20:02:43 +00:00
|
|
|
// Exists returns true if the manifest exists.
|
2014-11-22 03:39:52 +00:00
|
|
|
Exists(name, tag string) (bool, error)
|
|
|
|
|
|
|
|
// Get retrieves the named manifest, if it exists.
|
2015-01-02 21:21:29 +00:00
|
|
|
Get(name, tag string) (*manifest.SignedManifest, error)
|
2014-11-22 03:39:52 +00:00
|
|
|
|
|
|
|
// Put creates or updates the named manifest.
|
2015-01-02 21:21:29 +00:00
|
|
|
Put(name, tag string, manifest *manifest.SignedManifest) error
|
2014-11-22 03:39:52 +00:00
|
|
|
|
|
|
|
// Delete removes the named manifest, if it exists.
|
|
|
|
Delete(name, tag string) error
|
|
|
|
}
|
|
|
|
|
|
|
|
// LayerService provides operations on layer files in a backend storage.
|
|
|
|
type LayerService interface {
|
|
|
|
// Exists returns true if the layer exists.
|
|
|
|
Exists(name string, digest digest.Digest) (bool, error)
|
|
|
|
|
|
|
|
// Fetch the layer identifed by TarSum.
|
|
|
|
Fetch(name string, digest digest.Digest) (Layer, error)
|
|
|
|
|
|
|
|
// Upload begins a layer upload to repository identified by name,
|
|
|
|
// returning a handle.
|
|
|
|
Upload(name string) (LayerUpload, error)
|
|
|
|
|
Spool layer uploads to remote storage
To smooth initial implementation, uploads were spooled to local file storage,
validated, then pushed to remote storage. That approach was flawed in that it
present easy clustering of registry services that share a remote storage
backend. The original plan was to implement resumable hashes then implement
remote upload storage. After some thought, it was found to be better to get
remote spooling working, then optimize with resumable hashes.
Moving to this approach has tradeoffs: after storing the complete upload
remotely, the node must fetch the content and validate it before moving it to
the final location. This can double bandwidth usage to the remote backend.
Modifying the verification and upload code to store intermediate hashes should
be trivial once the layer digest format has settled.
The largest changes for users of the storage package (mostly the registry app)
are the LayerService interface and the LayerUpload interface. The LayerService
now takes qualified repository names to start and resume uploads. In corallry,
the concept of LayerUploadState has been complete removed, exposing all aspects
of that state as part of the LayerUpload object. The LayerUpload object has
been modified to work as an io.WriteSeeker and includes a StartedAt time, to
allow for upload timeout policies. Finish now only requires a digest, eliding
the requirement for a size parameter.
Resource cleanup has taken a turn for the better. Resources are cleaned up
after successful uploads and during a cancel call. Admittedly, this is probably
not completely where we want to be. It's recommend that we bolster this with a
periodic driver utility script that scans for partial uploads and deletes the
underlying data. As a small benefit, we can leave these around to better
understand how and why these uploads are failing, at the cost of some extra
disk space.
Many other changes follow from the changes above. The webapp needs to be
updated to meet the new interface requirements.
Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-01-08 22:24:02 +00:00
|
|
|
// Resume continues an in progress layer upload, returning a handle to the
|
|
|
|
// upload. The caller should seek to the latest desired upload location
|
|
|
|
// before proceeding.
|
|
|
|
Resume(name, uuid string) (LayerUpload, error)
|
2014-11-22 03:39:52 +00:00
|
|
|
}
|