Fig speaks to the powerstrip HTTP api which in turn speaks to the weave adapter.
It would definitely be interesting to have some kind of cadvisor adapter (or equivalent) that was automatically feeding back metrics to some kind of scheduler.
The main point is to allow the vanilla docker client to interact with powerstrip and therefore by extension - all of the existing orchestration tools.
because powerstrip presents a standard docker HTTP api - it can certainly be used to interact with any other tool that talks standard docker HTTP.
For example - I put together a small run-through in powerstrip-weave where fig can be used to allocate weave IP addresses:
https://github.com/binocarlos/powerstrip-weave/tree/master/e...
Fig speaks to the powerstrip HTTP api which in turn speaks to the weave adapter.
It would definitely be interesting to have some kind of cadvisor adapter (or equivalent) that was automatically feeding back metrics to some kind of scheduler.
The main point is to allow the vanilla docker client to interact with powerstrip and therefore by extension - all of the existing orchestration tools.