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

README: clarify what CNI is #186

Merged
merged 1 commit into from
Apr 21, 2016
Merged

README: clarify what CNI is #186

merged 1 commit into from
Apr 21, 2016

Conversation

steveej
Copy link
Member

@steveej steveej commented Apr 20, 2016

The word "standard" does not represent what CNI is actually trying to
be.

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 for configuring network interfaces for Linux application containers.
Copy link
Member

Choose a reason for hiding this comment

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

How about something like "CNI [...] is a specification for container networking plugins. It defines how a plugin is invoked by an application to configure a network namespace. This repository also contains a Go library implementing the specification on both sides (the application, and the plugin)."

The word "standard" does not represent what CNI is actually trying to
be.
@squaremo squaremo merged commit 8bb41b9 into containernetworking:master Apr 21, 2016
@squaremo
Copy link
Member

Yes, good to remove "standard", and emphasise "specification". Thanks @steveej

@steveej steveej deleted the project-clarification branch April 21, 2016 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants