design: remove distribution GRPC service

Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
This commit is contained in:
Akihiro Suda 2017-09-22 17:47:58 +00:00
parent df896c92e7
commit 3a88be3831

View File

@ -28,7 +28,6 @@ thought behind the design.
External users interact with services, made available via a GRPC API. External users interact with services, made available via a GRPC API.
- __*Distribution*__: The distribution service supports pulling images.
- __*Bundle*__: The bundle service allows the user to extract and pack bundles - __*Bundle*__: The bundle service allows the user to extract and pack bundles
from disk images. from disk images.
- __*Runtime*__: The runtime service supports the execution of _bundles_, - __*Runtime*__: The runtime service supports the execution of _bundles_,
@ -62,6 +61,12 @@ components:
- __*Metrics*__: Each components will export several metrics, accessible via - __*Metrics*__: Each components will export several metrics, accessible via
the metrics API. (We may want to promote this to a subsystem. the metrics API. (We may want to promote this to a subsystem.
## Client-side components
Some components are implemented on the client side for flexibility:
- __*Distribution*__: Functions for pulling and pushing images
## Data Flow ## Data Flow
As discussed above, the concept of a _bundle_ is central to containerd. Below As discussed above, the concept of a _bundle_ is central to containerd. Below