It turns out that our support dump logic is *really* fast and compact.
Even on a large node (hundreds of containers and thousands of images)
it runs in ~10 seconds and weighs in at a few hundred K. Since we're
running all the dumps in parallel, there's really no need for the added
complexity of saving them to a DB.
This change revamps and simplifies the support dump API. Now you simply
POST to the API endpoint, and it will stream the full zip file containing
all the nodes payloads within. If a node is unreachable, times out,
or has some other catastrophic problem, the contents for that node will
be an error message instead of the normal tar.gz bundle.
I've tested this with a swarm of multiple nodes, confirmed the dumps
match up to the hosts, and the system handles offline nodes, reporting
an error message within the bundle. (it does take a long time in the
failure cases due to a bug in swarm that's slated to be fixed in 1.9,
but curl doesn't give up so this still works fine.)
We might want to take the time to make this work via compose, but that
will require some custom bootstrap scripts, so for now, lets just use
manual cut-and-paste for anyone who needs a "real" cert setup in dev mode.
