WIP libnetwork - Add support for /networks and /services API endpoints

[abronan]

Tested with docker experimental.

The API is going to change (with the sandbox entity: see moby/libnetwork#365), but I open the PR to keep track of the evolution on both sides.

TODO items:

• Add error scheme for all methods
• Move the networks and services endpoints in their own file (networks.go/services.go?)
• Include new sandbox entity
• Refactor and split tests

Signed-off-by: Alexandre Beslic abronan@docker.com

[abronan]

Also, it's now probably time to cleanup the client a little bit... And split in multiple files (containers.go/images.go/networks.go/services.go, etc.)

[mavenugo]

@aboch can you please take a look ?

[abronan]

/cc @aluzzardi @vieux @chanwit @jimmyxian (cc'ing just so you can follow the discussion here ;)

[chanwit]

👍

[jimmyxian]

Cool, split in multiple files is pretty good.

[aluzzardi]

Awesome :)

But ... aren't we going to blindly proxy the calls to the engine anyway ? :)

[jimmyxian]

@aluzzardi
In Swarm, I think proxy the calls to the engine is a good way to keep api fresh.

[aboch]

We support only one query parameter for these endpoints in libentworks, either name or partial-id
I think this should be: uri += "?name=" +name and uri += "?partial-id=" + partialId below.

[abronan]

@aluzzardi Most of them yes ;)

@aboch Thanks! Will revisit and fix when your PR will be merged on libnetwork's side.

[abronan]

replaced by #169 that supports the new networking UX