Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move client implementations for content store and snapshotter #2341

Merged
merged 4 commits into from May 25, 2018

Conversation

dmcgowan
Copy link
Member

The client implementations for content store and snapshotters are just proxy implementations of the interface. Move these next to the other implementations. These could be used for any proxy implementation.

Signed-off-by: Derek McGowan <derek@mcgstyle.net>
Signed-off-by: Derek McGowan <derek@mcgstyle.net>
Signed-off-by: Derek McGowan <derek@mcgstyle.net>
Signed-off-by: Derek McGowan <derek@mcgstyle.net>
@Random-Liu
Copy link
Member

Will docker use this for all filesystem? Or only filesystem which containerd doesn't support today?

@dmcgowan
Copy link
Member Author

Will docker use this for all filesystem? Or only filesystem which containerd doesn't support today?

The proposed snapshot proxy would only be used for snapshotters based on Docker graph drivers, which are not supported today. The proxy drivers could also be used to provided other implementations which all clients could end up using transparently, such as P2P content stores.

@Random-Liu
Copy link
Member

Random-Liu commented May 15, 2018

@dmcgowan I see. Thanks! I'm just curious whether Docker will partially use containerd image management, and partially use graph driver. Or Docker will only use graph drivers for a long time.

@Random-Liu
Copy link
Member

Random-Liu commented May 15, 2018

Sorry, I don't quite understand this PR. Why the package is called "proxy"?

Will Docker replace the grpc service implementation or the interface implementation?

@dmcgowan
Copy link
Member Author

I'm just curious whether Docker will partially use containerd image management, and partially use graph driver. Or Docker will only use graph drivers for a long time.

The goal is to move Docker over in stages, ultimately completely using the image management and only graph drivers to support upgrade or graph drivers which do not have a snapshotter equivalent.

Why the package is called "proxy"?

These implementations of the content store and snapshotter just proxy over GRPC, there is no concrete implementation. I used the term "proxy" here because the caller is not intended to distinguish between using the proxy or directly using a concrete snapshotter.

@codecov-io
Copy link

Codecov Report

Merging #2341 into master will increase coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2341      +/-   ##
==========================================
+ Coverage   44.98%   44.99%   +<.01%     
==========================================
  Files          92       92              
  Lines        9340     9350      +10     
==========================================
+ Hits         4202     4207       +5     
- Misses       4459     4461       +2     
- Partials      679      682       +3
Flag Coverage Δ
#linux 49.28% <ø> (ø) ⬆️
#windows 41.25% <ø> (ø) ⬆️
Impacted Files Coverage Δ
oci/spec.go 28.57% <0%> (-11.43%) ⬇️
metadata/buckets.go 56.79% <0%> (+2.12%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b511c39...7c80d0a. Read the comment docs.

@crosbymichael
Copy link
Member

LGTM

Copy link
Member

@estesp estesp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@estesp estesp merged commit e9434a1 into containerd:master May 25, 2018
@dmcgowan dmcgowan deleted the move-client-content-snapshot branch June 5, 2018 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants