Bring deimos in line with the latest API for the External Containerizer

[tarnfeld]

There's a large refactor that's gone on with the EC which deimos needs updating to match. Here's a few notable changes that I can see (against the 0.19.0 EC release candidate).

• Different protobuf messages
• New containers method to return list of running container IDs
• New recover method for recovering internal state
• New update method for updating a containers resources
  • This is an interesting one... deimos needs to (at minimum) support changing CPU and memory limits, though ports would be a good one.

There might be some improvements that can be made to how deimos works (and manages state) due to the introduction of the new recover method.

Would be interested in your thoughts @solidsnack – is this something you've started work on?

[timothysc]

I think the whole community is a +1 on this one given dockercon.

[tarnfeld]

I agree, since I heard nothing back from the mesosphere guys I ended up bring my own containerizer back to life... but I do think it's very important to be able to demonstrate how mesos and docker can fit together transparently.

[solidsnack]

With 0.3.0 we have support for the new API.

[timothysc]

Many thanks Jason!