Jana Radhakrishnan c0162f53a6 Add overlay manager driver ... Because overlay is a builtin driver and global allocation of overlay resources is probably going to happen in a different node (a single node) and the actual plumbing of the network is probably going to happen in all nodes, it makes sense to split the functionality of allocation into two different packages. The central component(this package) only implements the NetworkAllocate/Free apis while the distributed component(the existing overlay driver) implements the rest of the driver api. This way we can reduce the memory footprint overall. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2016-04-14 10:37:42 -07:00
..
drvregistry.go	Create driver registry package	2016-04-09 09:43:43 -07:00
drvregistry_test.go	Add overlay manager driver	2016-04-14 10:37:42 -07:00