moby--moby/libnetwork/drivers_windows.go

package libnetwork

import (
	"github.com/docker/libnetwork/drivers/null"
	"github.com/docker/libnetwork/drivers/remote"
	"github.com/docker/libnetwork/drivers/windows"
	"github.com/docker/libnetwork/drivers/windows/overlay"
)

func getInitializers(experimental bool) []initializer {
	return []initializer{
		{null.Init, "null"},
		{overlay.Init, "overlay"},
		{remote.Init, "remote"},
		{windows.GetInit("transparent"), "transparent"},
		{windows.GetInit("l2bridge"), "l2bridge"},
		{windows.GetInit("l2tunnel"), "l2tunnel"},
		{windows.GetInit("nat"), "nat"},
		{windows.GetInit("internal"), "internal"},
		{windows.GetInit("private"), "private"},
		{windows.GetInit("ics"), "ics"},
	}
}
Rename strategy to driver Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com> 2015-02-19 20:37:53 -05:00			`package libnetwork`

Windows HNS integration Signed-off-by: msabansal <sabansal@microsoft.com> 2016-01-29 20:08:11 -05:00			`import (`
			`"github.com/docker/libnetwork/drivers/null"`
Register remote network driver on Windows. Without this change, specifying a remote network driver on Windows results in "could not resolve driver X in registry" error. Signed-off-by: Michal Kostrzewa <kostrzewa.michal@o2.pl> 2016-11-02 11:18:12 -04:00			`"github.com/docker/libnetwork/drivers/remote"`
Windows HNS integration Signed-off-by: msabansal <sabansal@microsoft.com> 2016-01-29 20:08:11 -05:00			`"github.com/docker/libnetwork/drivers/windows"`
Windows overlay driver support 1. Base work was done by msabansal and nwoodmsft from : https://github.com/msabansal/docker/tree/overlay 2. reorganized under drivers/windows/overlay and rebased to libnetwork master 3. Porting overlay common fixes to windows driver * 46f525c * ba8714e * 6368406 4. Windows Service Discovery changes for swarm-mode 5. renaming default windows ipam drivers as "windows" Signed-off-by: Madhu Venugopal <madhu@docker.com> Signed-off-by: msabansal <sabansal@microsoft.com> Signed-off-by: nwoodmsft <Nicholas.Wood@microsoft.com> 2016-10-12 19:55:20 -04:00			`"github.com/docker/libnetwork/drivers/windows/overlay"`
Windows HNS integration Signed-off-by: msabansal <sabansal@microsoft.com> 2016-01-29 20:08:11 -05:00			`)`
Rename strategy to driver Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com> 2015-02-19 20:37:53 -05:00
Handling the new experimental daemon flag related to https://github.com/docker/docker/issues/29368 Signed-off-by: Madhu Venugopal <madhu@docker.com> 2016-12-13 16:22:55 -05:00			`func getInitializers(experimental bool) []initializer {`
Push driver config during `Init` Currently the driver configuration is pushed through a separate api. This makes driver configuration possible at any arbitrary time. This unncessarily complicates the driver implementation. More importantly the driver does not get access to it's configuration before it can do the handshake with libnetwork. This make the internal drivers a little bit different to external plugins which can get their configuration before the handshake with libnetwork. This PR attempts to fix that mismatch between internal drivers and external plugins. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com> 2015-09-18 17:00:36 -04:00			`return []initializer{`
Windows HNS integration Signed-off-by: msabansal <sabansal@microsoft.com> 2016-01-29 20:08:11 -05:00			`{null.Init, "null"},`
Windows overlay driver support 1. Base work was done by msabansal and nwoodmsft from : https://github.com/msabansal/docker/tree/overlay 2. reorganized under drivers/windows/overlay and rebased to libnetwork master 3. Porting overlay common fixes to windows driver * 46f525c * ba8714e * 6368406 4. Windows Service Discovery changes for swarm-mode 5. renaming default windows ipam drivers as "windows" Signed-off-by: Madhu Venugopal <madhu@docker.com> Signed-off-by: msabansal <sabansal@microsoft.com> Signed-off-by: nwoodmsft <Nicholas.Wood@microsoft.com> 2016-10-12 19:55:20 -04:00			`{overlay.Init, "overlay"},`
Register remote network driver on Windows. Without this change, specifying a remote network driver on Windows results in "could not resolve driver X in registry" error. Signed-off-by: Michal Kostrzewa <kostrzewa.michal@o2.pl> 2016-11-02 11:18:12 -04:00			`{remote.Init, "remote"},`
Renaming driver name to lower case for usability and allowing portmapping to surface Signed-off-by: msabansal <sabansal@microsoft.com> 2016-02-25 18:06:16 -05:00			`{windows.GetInit("transparent"), "transparent"},`
			`{windows.GetInit("l2bridge"), "l2bridge"},`
			`{windows.GetInit("l2tunnel"), "l2tunnel"},`
			`{windows.GetInit("nat"), "nat"},`
Add support for Internal and Private network types on windows Signed-off-by: Sandeep Bansal <sabansal@microsoft.com> 2018-07-12 00:49:46 -04:00			`{windows.GetInit("internal"), "internal"},`
			`{windows.GetInit("private"), "private"},`
Changes to support ICS network on windows Signed-off-by: Sandeep Bansal <sabansal@microsoft.com> 2017-05-18 16:38:04 -04:00			`{windows.GetInit("ics"), "ics"},`
Generic options model Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com> 2015-02-20 01:21:05 -05:00			`}`
Generic argument passing to drivers Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com> 2015-02-20 12:12:29 -05:00			`}`