- Enhance plugin API documentation
https://github.com/docker/libnetwork/blob/master/docs/remote.md
- Implement Exec driver
The purpose of this driver is to implement Network plugin protocol & call exec calls to an external driver This is useful for those stateless drivers that doesn’t have a long running process
- Implement Wrapper plugin
Generic plugin/driver that implements the network plugin protocol and wraps an existing driver/plugin This is useful for those cases, were the user just wants to enhance a particular aspect of an existing driver instead of rewriting entirely new plugin
- Implement Native ipvlan driver
Start from https://github.com/gopher-net/ipvlan-docker-plugin)
- Implement Native macvlan driver
Start from https://github.com/gopher-net/macvlan-docker-plugin)
- Implement Native vlan driver
Associate a vlan per network and hook it to the vlan space on the host namespace
- SR-IOV plugin
A plugin to make use of SR-IOV capabilities
- Enhance libnetwork to enable plugin event replay/retry cases
There are cases in which libnetwork might provide events to a plugin that is either down or not provisioned yet. Hence a replay/retry will be very useful This is particularly true when saved configuration is replayed during docker daemon bootup
- Enhance plugin protocol with versioning
Plugin API/protocol as described in https://github.com/docker/libnetwork/blob/master/docs/remote.md doesn’t have versioning scheme. Its good to have version negotiation as part of the protocol to provide proper compatibility matrix.
- Enhance plugin protocol towards troubleshooting and debugging
Currently the plugin APIs are focused on plumbing. It would be awesome to enhance the API to provide more dataplane-level troubleshooting and debugging.
- help/wanted in https://github.com/docker/libnetwork/issues
In addition to these hack ideas, pls help libnetwork project by filtering the label (help wanted)