On 26/01/16 08:17, David Halls wrote:
A couple of other side points:
- Docker themselves use The Update Framework in their tools. They had to
port it to Go because they're a Go shop. Also, they have a separate server
for storing all the TUF metadata called Notary. It does the job of doing
all the crypto stuff so that instead of doing distributed 'web of trust'
(passing public keys around), everything's done the under the auspices of
your Docker account.
Silly question (with a -- I hope -- silly answer): why not use the Go
version?
- Just to be clear, the Docker tools aren't needed here on the client and
just the hypervisor is used to run the Node binary. This is off-topic but
what I want to do is then orchestrate the hypervisors using a tool like
Saltstack.
I think that subject is extremely on topic for the list ... and at the
same time extremely off-topic. As many know, I believe (because
software development is all about religion) that drivers and
Orchestrating Systems should be separate. This project can't split
itself into the orchestrating layer anymore, we're already too split
into a billion different directions. Any data that someone else can
provide on if orchestrating system X works with Rumprun (or some other
way of applying rump kernels) and what we can do to better support X is
of great value. I look forward to hearing about your experiments.
