Where does a plugin sit in the CNM? about libnetwork

[mrjana]

@guru-shetty Most likely libnetwork will be running in docker daemon. Your understanding of where plugins will sit is correct. But all of these should be transparent to plugin provider as long as they conform to the Network plugin protocol (yet to be fully defined)

[dave-tucker]

Marking this as closed as I think @mrjana has answered the question

[squaremo]

Any future plugin will be between libnetwork and the drivers. i.e., if the plugin takes the form of a REST API, then this will make network.go (https://github.com/docker/libnetwork/blob/master/network.go) call REST APIs to the bridge driver to Create network, create endpoint etc.

The way we (weave) have been constructing a PoC plugin is as follows:

• when loaded, the plugin registers itself with libnetwork as a network driver
• the driver implementation it registers uses the "plugin transport" (currently RPC-over-HTTP-over-unix-socket) to talk to the plugin.

[shettyg]

@squaremo Thanks for the information. Do you have a semi-working PoC code yet, that I could look at?

[tomwilkie]

@shettyg Michael + I are working on it here:

https://github.com/tomwilkie/docker/tree/network_extensions_dev

Its very rough and ready! But it pretty much works (just ironing out the last problems now). You'll need my forks of libcontainer and libnetwork too; put them in docker's vendor dir.