From ef251cc6cececcc0ee9b11a0f2ac2ecd9b2d183f Mon Sep 17 00:00:00 2001 From: Stefan Junker Date: Wed, 20 Apr 2016 17:54:12 +0200 Subject: [PATCH] README: clarify what CNI is The word "standard" does not represent what CNI is actually trying to be. --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index ccc6aea4..c96526f3 100644 --- a/README.md +++ b/README.md @@ -5,13 +5,15 @@ ## What is CNI? -CNI, the _Container Network Interface_, is a proposed standard for configuring network interfaces for Linux application containers. -The standard consists of a simple specification for how executable plugins can be used to configure network namespaces; this repository also contains a go library implementing that specification. - +CNI, the _Container Network Interface_, is a project to help configure network interfaces for Linux application containers. CNI concerns itself with setting up network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus CNI has a wide range of support and the specification is simple to implement. -The specification itself is contained in [SPEC.md](SPEC.md). +The project repository contains a [simple specification](SPEC.md) for how executable plugins can be used to configure network namespaces, and a number of plugins, libraries and utilities written in Go that can be used to get started with CNI. + +The specification and the plugin architecture form a template system with perfectly clear interfaces. +This allows developers to integrate their existing container networking solutions with a thin CNI wrapper plugin. +It also gives a good framework to create new container networking solutions from scratch. ## Why develop CNI?