kotovalexarian-likes-github
/
moby--moby
mirror of https://github.com/moby/moby.git
1
0
Fork 0
Code Releases Activity

Merge pull request #62 from marun/patch-1 

Minor language cleanup in ROADMAP.md
This commit is contained in:
Jana Radhakrishnan 2015-04-17 18:38:32 -07:00
parent 3debfb30b6 0957eed04b
commit 91eef607d0
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
libnetwork/ROADMAP.md
View File

@ -13,11 +13,10 @@ To suggest changes to the roadmap, including additions, please write the change
1. Sandbox: An isolated environment. This is more or less a standard docker container.
2. Endpoint: An addressable endpoint used for communication over a specific network. Endpoints join exactly one network and are expected to create a method of network communication for a container. Endpoints are garbage collected when they no longer belong to any Sandboxes. Example : veth pair
3. Network: A collection of endpoints that are able to communicate to each other. These networks are intended to be isolated from each other and do not cross communicate. Networks house endpoints which can communicate with each other.
3. Network: A collection of endpoints that are able to communicate to each other. Networks are intended to be isolated from each other and to not cross communicate.
#### axioms
The container network model is a few axioms about how libnetwork wishes to supply
interoperation between networks and containers.
The container network model assumes the following axioms about how libnetwork provides network connectivity to containers:
1. All containers on a specific network can communicate with each other freely.
2. Multiple networks are the way to segment traffic between containers and should be supported by all drivers.
@ -25,10 +24,10 @@ interoperation between networks and containers.
4. An endpoint is added to a sandbox to provide it with network connectivity.
## Bridge Driver using CNM
Existing native networking functionality of Docker will be implemented as a Bridge Driver using the above CNM. In order to prove the effectiveness of the Bridge Driver, we will make necessary modifications to Docker Daemon and LibContainer to replace the existing networking functionality with libnetwork & Bridge Driver.
Existing native networking functionality of Docker will be implemented as a Bridge Driver using the above CNM. In order to prove the effectiveness of the Bridge Driver, we will make the necessary modifications to Docker Daemon and LibContainer to replace the existing networking functionality with libnetwork & Bridge Driver.
## Plugin support
The Driver model provides a modular way to allow different networking solutions to be used as the backend. But they are static in nature.
Plugins solves that problem by supporting dynamic pluggable networking backend for libnetwork.
There are other community efforts in developing Plugin support on the Docker platform.libnetwork project will also make use of it when available.
The Driver model provides a modular way to allow different networking solutions to be used as the backend, but is static in nature.
Plugins promise to allow dynamic pluggable networking backends for libnetwork.
There are other community efforts implementing Plugin support for the Docker platform, and the libnetwork project intends to make use of such support when it becomes available.