Michael Bridgen

Support port mapping

1

I think the plugin will get told the port mapping; so it's possible we could support port mapping, and remove the need for adding a container to the bridge network.

We should set the veth MAC address to be the same as that we report back to libnetwork.

Register endpoints(?) with weaveDNS

2

At present the driver is not told either of the containerID or the hostname, so it is more or less impossible in remote driver terms to register containers with weaveDNS....

Make containers use WeaveDNS as resolver

8

Harder than it sounds. There are two requirements: 1. The plugin has to be able to put `nameserver x.x.x.x` in the container's `/etc/resolv.conf` 2. The container has to be able...

Make agents and listeners resilient to etcd being unavailable

2

At the minute, the various listeners (agent, balagent, balancer) will crash if they cannot establish or lose a connection to etcd. This makes some problems for both starting the infrastructure...

Expose outcome of select operations

1

When you use `fluxctl select`, it is typically not obvious whether it succeeded or failed; and if it failed, why it failed. This is information we report in logs, so...

We need to think of the most useful output for the CLI operations (those that aren't queries, anyway). Informational messages should go to stderr.

`amberctl service` streamlining

1

- [x] supply the service address as ip:port - [ ] allocate an address (and port?) if not given one, and return it

While writing the README for amberctl, it occurred to me that it would be better to generate the documentation -- or rather, that what I was writing belonged in a...