moby--moby/libnetwork
Jana Radhakrishnan 84abbcefa8 Fix a couple of edge cases in service discovery
The first issue is an ordering problem where sandbox
attached version of endpoint object should be pushed
to the watch database first so that any other create endpoint
which is in progress can make use of it immediately to update
the container hosts file. And only after that the current
container should try to retrieve the service records from the
service data base and upate it's hosts file. With the previous
order there is a small time window, when another endpoint create
will find this endpoint but it doesn't have the sandbox context
while the svc record population from svc db has already happened
so that container will totally miss to populate the service record
of the newly created endpoint.

The second issue is trying to rebuild the /etc/hosts file from scratch
during endpoint join and this may sometimes happen after the service
record add for another endpoint  has happened on the container
file. Obviously this rebuilding will wipe out that service record which
was just added. Removed the rebuilding of /etc/hosts file during
endpoint join. The initial population of /etc/hosts file should only
happen during sandbox creation time. In the endpoint join just added
the backward-compatible self ip -> hostname entry as just another
record.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
2015-11-25 15:25:56 -08:00
..
Godeps godeps: update coreos/go-systemd to v4 and godbus/dbus to v3 2015-11-20 00:19:47 +01:00
api
bitseq
client
cmd Add IT case for external connectivity 2015-10-28 19:10:38 -07:00
config
datastore Format the code 2015-10-27 00:45:48 +08:00
docs Tidy up the IPAM driver doc 2015-10-26 12:47:05 +00:00
driverapi
drivers Merge pull request #591 from WeiZhang555/iptables-clean 2015-11-25 09:12:10 -08:00
etchosts
hostdiscovery
idm
ipam Fix bug in getAddressRange() in default ipam driver 2015-11-08 11:30:57 -08:00
ipamapi
ipams
ipamutils
iptables Merge pull request #591 from WeiZhang555/iptables-clean 2015-11-25 09:12:10 -08:00
netlabel
netutils Multi-Arch Support 2015-11-25 22:47:41 +00:00
ns
options
osl
portallocator
portmapper
resolvconf
test/integration Multi-Arch Support 2015-11-25 22:47:41 +00:00
testutils
types
.dockerignore Multi-Arch Support 2015-11-25 22:47:41 +00:00
.gitignore Multi-Arch Support 2015-11-25 22:47:41 +00:00
Dockerfile.build Multi-Arch Support 2015-11-25 22:47:41 +00:00
LICENSE
MAINTAINERS
Makefile Multi-Arch Support 2015-11-25 22:47:41 +00:00
README.md
ROADMAP.md
Vagrantfile
circle.yml Multi-Arch Support 2015-11-25 22:47:41 +00:00
controller.go Clean unused variables and fix typo 2015-11-06 11:38:33 +08:00
default_gateway.go Default Gateway endpoints must be annonymous 2015-10-23 16:52:11 -07:00
default_gateway_freebsd.go
default_gateway_linux.go
default_gateway_windows.go
drivers.go
drivers_freebsd.go
drivers_linux.go
drivers_windows.go
endpoint.go Fix a couple of edge cases in service discovery 2015-11-25 15:25:56 -08:00
endpoint_cnt.go Some functions' logic cleanup 2015-10-27 11:08:42 -07:00
endpoint_info.go Fix in endpoint Info() method 2015-11-22 21:44:06 -08:00
error.go
errors_test.go
libnetwork_internal_test.go
libnetwork_test.go Allow IPv6 allocation post endpoint create 2015-11-10 14:53:19 -08:00
network.go libnetwork to honor explicit mac-address 2015-11-14 13:17:43 -08:00
sandbox.go Fix a couple of edge cases in service discovery 2015-11-25 15:25:56 -08:00
sandbox_externalkey.go
sandbox_store.go Skip non-persistent endpoints in sandbox store 2015-11-02 08:09:49 -08:00
sandbox_test.go
store.go Remove redundant assignment to ep.network 2015-11-12 10:38:41 -08:00
store_test.go Add customer_prefix to the store URL for integration test 2015-10-26 17:48:52 +08:00
wrapmake.sh

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.

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

	// Create a new controller instance
	driverOptions := options.Generic{}
	genericOption := make(map[string]interface{})
	genericOption[netlabel.GenericData] = driverOptions
	controller, err := libnetwork.New(config.OptionDriverConfig(networkType, genericOption))
	if err != nil {
		return
	}

	// Create a network for containers to join.
	// NewNetwork accepts Variadic optional arguments that libnetwork and Drivers can use.
	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
	}

	// Create the sandbox for the container.
	// NewSandbox accepts Variadic optional arguments which libnetwork can use.
	sbx, err := controller.NewSandbox("container1",
		libnetwork.OptionHostname("test"),
		libnetwork.OptionDomainname("docker.io"))

	// A sandbox can join the endpoint via the join api.
	err = ep.Join(sbx)
	if err != nil {
		return
	}

	// libnetwork 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.([]types.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.