moby--moby/libnetwork
Madhu Venugopal dca35085f5 datastore support for Endpoint
Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-06-10 21:17:55 -07:00
..
Godeps Updating to latest Swarm dependancies 2015-06-10 21:17:55 -07:00
api Add restrictions for default drivers/bridge name 2015-06-08 08:32:08 -07:00
client Moved services to dnet top-level and removed experimental 2015-06-08 14:23:41 -07:00
cmd datastore support for Endpoint 2015-06-10 21:17:55 -07:00
config Libnetwork Host Discovery using Swarm Discovery pkg 2015-05-25 16:29:40 -07:00
datastore datastore support for Endpoint 2015-06-10 21:17:55 -07:00
docs Document the remote driver protocol 2015-06-05 12:18:50 +01:00
driverapi Allow drivers to supply static routes for interfaces 2015-05-25 19:25:30 -07:00
drivers Minor changes in bridge.go 2015-06-09 16:44:43 -07:00
etchosts Remove pkg directory 2015-05-16 16:12:13 -07:00
hostdiscovery Updating to new Swarm discovery and store APIs 2015-06-10 21:17:55 -07:00
ipallocator Simplify the code in the RegisterSubnet method of ipallocator. 2015-05-12 00:44:34 +00:00
iptables Provide interface to categorize errors 2015-05-20 22:29:29 -07:00
netlabel Remove pkg directory 2015-05-16 16:12:13 -07:00
netutils Make GenerateIfaceName generic 2015-06-08 09:49:17 -07:00
options Remove pkg directory 2015-05-16 16:12:13 -07:00
portallocator Do not warn in packages 2015-06-02 15:11:32 -07:00
portmapper Add dummy proxy on port map 2015-05-22 12:38:28 -07:00
resolvconf Remove pkg directory 2015-05-16 16:12:13 -07:00
sandbox Check GC loop is active/necessary before triggering GC 2015-06-10 16:43:31 -04:00
test/integration Initial bats based integration tests for testing daemon network configs 2015-04-25 07:33:48 -07:00
types Make GenerateIfaceName generic 2015-06-08 09:49:17 -07:00
.gitignore Create a build image to avoid install-deps every time 2015-05-11 21:17:12 +01:00
LICENSE Initial commit 2015-02-19 17:20:15 -08:00
MAINTAINERS Add Alessandro as a libnetwork maintainer 2015-05-29 18:46:33 +00:00
Makefile Moved services to dnet top-level and removed experimental 2015-06-08 14:23:41 -07:00
README.md Remove container data return value from Join 2015-05-29 20:11:02 +00:00
ROADMAP.md Updated Design Document 2015-05-06 13:38:16 -07:00
circle.yml Report Code Coverage and Add Status Badges 2015-04-14 16:19:55 +01:00
controller.go datastore support for Endpoint 2015-06-10 21:17:55 -07:00
drivers_freebsd.go make libnetwork compile on freebsd 2015-06-05 14:27:23 +03:00
drivers_linux.go Windows: Enable compile 2015-05-26 10:46:21 -07:00
drivers_windows.go Windows: Enable compile 2015-05-26 10:46:21 -07:00
endpoint.go datastore support for Endpoint 2015-06-10 21:17:55 -07:00
endpoint_info.go Fixing a few go-vet issues 2015-06-04 04:32:10 -07:00
error.go TOML based Configuration support for libnetwork 2015-05-25 16:29:40 -07:00
errors_test.go Provide interface to categorize errors 2015-05-20 22:29:29 -07:00
libnetwork_internal_test.go TOML based Configuration support for libnetwork 2015-05-25 16:29:40 -07:00
libnetwork_test.go Add restrictions for default drivers/bridge name 2015-06-08 08:32:08 -07:00
network.go datastore support for Endpoint 2015-06-10 21:17:55 -07:00
sandboxdata.go Refactor sandbox code to use interfaces 2015-06-08 10:17:56 -07:00
sandboxdata_test.go Add container join priority option to endpoint 2015-06-03 17:48:58 -07:00
store.go datastore support for Endpoint 2015-06-10 21:17:55 -07:00

README.md

libnetwork - networking for containers

Circle CI Coverage Status GoDoc

Libnetwork provides a native Go implementation for connecting containers

The goal of libnetwork is to deliver a robust Container Network Model that provides a consistent programming interface and the required network abstractions for applications.

NOTE: libnetwork project is under heavy development and is not ready for general use.

Design

Please refer to the design for more information.

Using libnetwork

There are many networking solutions available to suit a broad range of use-cases. libnetwork uses a driver / plugin model to support all of these solutions while abstracting the complexity of the driver implementations by exposing a simple and consistent Network Model to users.

        // Create a new controller instance
        controller := libnetwork.New("/etc/default/libnetwork.toml")

        // Select and configure the network driver
        networkType := "bridge"

        driverOptions := options.Generic{}
        genericOption := make(map[string]interface{})
        genericOption[netlabel.GenericData] = driverOptions
        err := controller.ConfigureNetworkDriver(networkType, genericOption)
        if err != nil {
                return
        }

        // Create a network for containers to join.
        // NewNetwork accepts Variadic optional arguments that libnetwork and Drivers can make of
        network, err := controller.NewNetwork(networkType, "network1")
        if err != nil {
                return
        }

        // For each new container: allocate IP and interfaces. The returned network
        // settings will be used for container infos (inspect and such), as well as
        // iptables rules for port publishing. This info is contained or accessible
        // from the returned endpoint.
        ep, err := network.CreateEndpoint("Endpoint1")
        if err != nil {
                return
        }

        // A container can join the endpoint by providing the container ID to the join
        // api.
        // Join acceps Variadic arguments which will be made use of by libnetwork and Drivers
        err = ep.Join("container1",
                libnetwork.JoinOptionHostname("test"),
                libnetwork.JoinOptionDomainname("docker.io"))
        if err != nil {
                return
        }

		// libentwork client can check the endpoint's operational data via the Info() API
		epInfo, err := ep.DriverInfo()
		mapData, ok := epInfo[netlabel.PortMap]
		if ok {
			portMapping, ok := mapData.([]netutils.PortBinding)
			if ok {
				fmt.Printf("Current port mapping for endpoint %s: %v", ep.Name(), portMapping)
			}
		}

Current Status

Please watch this space for updates on the progress.

Currently libnetwork is nothing more than an attempt to modularize the Docker platform's networking subsystem by moving it into libnetwork as a library.

Future

Please refer to roadmap for more information.

Contributing

Want to hack on libnetwork? Docker's contributions guidelines apply.

Code and documentation copyright 2015 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.