moby/libnetwork
Jana Radhakrishnan 800029abb6 Remove container data return value from Join
Now that Endpoint interface has the Info method there is no
need to return container data as a return value in the Join
method. Removed the return value and fixed all the callers.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
2015-05-29 20:11:02 +00:00
..
api Remove container data return value from Join 2015-05-29 20:11:02 +00:00
client Bridge driver to support multiple networks 2015-05-24 07:59:34 -07:00
cmd Remove container data return value from Join 2015-05-29 20:11:02 +00:00
config Libnetwork Host Discovery using Swarm Discovery pkg 2015-05-25 16:29:40 -07:00
datastore Libnetwork Host Discovery using Swarm Discovery pkg 2015-05-25 16:29:40 -07:00
docs Orthographic corrections 2015-05-22 20:19:34 +02:00
driverapi Allow drivers to supply static routes for interfaces 2015-05-25 19:25:30 -07:00
drivers Allow drivers to supply static routes for interfaces 2015-05-25 19:25:30 -07:00
etchosts Remove pkg directory 2015-05-16 16:12:13 -07:00
Godeps Updating Godep to pull in Set functionality 2015-05-25 16:29:40 -07:00
hostdiscovery Libnetwork Host Discovery using Swarm Discovery pkg 2015-05-25 16:29:40 -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 Move network types to types package 2015-05-20 20:28:46 +00:00
options Remove pkg directory 2015-05-16 16:12:13 -07:00
portallocator Remove pkg directory 2015-05-16 16:12:13 -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 Allow drivers to supply static routes for interfaces 2015-05-25 19:25:30 -07:00
test/integration Initial bats based integration tests for testing daemon network configs 2015-04-25 07:33:48 -07:00
types Allow drivers to supply static routes for interfaces 2015-05-25 19:25:30 -07:00
.gitignore Create a build image to avoid install-deps every time 2015-05-11 21:17:12 +01:00
circle.yml Report Code Coverage and Add Status Badges 2015-04-14 16:19:55 +01:00
controller.go Remove container data return value from Join 2015-05-29 20:11:02 +00:00
drivers.go Make driver packages register themselves via DriverCallback 2015-05-11 19:00:06 +01:00
endpoint.go Remove container data return value from Join 2015-05-29 20:11:02 +00:00
endpoint_info.go Allow drivers to supply static routes for interfaces 2015-05-25 19:25:30 -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 Remove container data return value from Join 2015-05-29 20:11:02 +00:00
LICENSE Initial commit 2015-02-19 17:20:15 -08:00
MAINTAINERS Add MAINTAINERS 2015-04-01 14:43:06 +01:00
Makefile Moved all the service commands under experimental build tag 2015-05-23 13:05:48 -07:00
network.go Libnetwork Host Discovery using Swarm Discovery pkg 2015-05-25 16:29:40 -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
system.go Remove golint warnings 2015-03-04 13:29:28 -08:00

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.