vbatts
/
cri-o
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

adding current roadmap 

Signed-off-by: Vishnu kannan <vishnuk@google.com>
This commit is contained in:
Vishnu kannan 2016-09-23 12:59:50 -07:00
parent 053c022623
commit 7ffc6fb787
1 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -1,9 +1,11 @@
ocid - OCI-based implementation of Kubernetes Container Runtime Interface [![Build Status](https://travis-ci.org/kubernetes-incubator/ocid.svg?branch=master)](https://travis-ci.org/kubernetes-incubator/ocid)
OCID - OCI-based implementation of Kubernetes Container Runtime Interface [![Build Status](https://travis-ci.org/kubernetes-incubator/ocid.svg?branch=master)](https://travis-ci.org/kubernetes-incubator/ocid)
=
### Status: pre-alpha
# What is the scope of this project?
ocid is meant to provide an integration path between OCI conformant runtimes and the kubelet.
OCID is meant to provide an integration path between OCI conformant runtimes and the kubelet.
Specifically, it implements the Kubelet Container Runtime Interface (CRI) using OCI conformant runtimes.
The scope of OCID is tied to the scope of the CRI.
@ -11,19 +13,16 @@ At a high level, we expect the scope of OCID to be restricted to the following f
* Support multiple image formats including the existing Docker image format
* Support for multiple means to download images including trust & image verification
* Container Image management (managing image layers, overlay filesystems, etc)
* Container image management (managing image layers, overlay filesystems, etc)
* Container process lifecycle management
* Monitoring and logging required to satisfy the CRI
* Resource isolation as required by the CRI
# What is not in scope for this project?
* Building, signing and pushing images to various image storages
* A CLI utility for interacting with OCID. Any CLIs built as part of this project are only meant for testing this project and there will be no guarantees on the backwards compatibility with it.
### Status: pre-alpha
This is an implementation of the Kubernetes Container Runtime Interface (CRI) that will allow Kubernetes to directly launch and manage Open Container Initiative (OCI) containers.
The plan is to use OCI projects and best of breed libraries for different aspects:
@ -32,5 +31,13 @@ The plan is to use OCI projects and best of breed libraries for different aspect
- Storage: Storage and management of image layers using [containers/storage](https://github.com/containers/storage)
- Networking: Networking support through use of [CNI](https://github.com/containernetworking/cni)
It is currently in active development in the Kubernetes community through the [design proposal](https://github.com/kubernetes/kubernetes/pull/26788). Questions and issues should be raised in the Kubernetes [sig-node Slack channel](https://kubernetes.slack.com/archives/sig-node).
## Current Roadmap
1. Basic pod/container lifecycle, basic image pull (already works)
1. Support for tty handling and state management
1. Basic integration with kubelet once client side changes are ready
1. Support for log management, networking integration using CNI, pluggable image/storage management
1. Support for exec/attach
1. Target fully automated kubernetes testing without failures