|
|
|
|
|
|
by rossf7
3895 days ago
|
|
|
We're working on a container scaling solution that runs on top of the scheduler. It will scale containers based on current demand. There is overlap with the Swarm strategies but we're focused on auto scaling. So for example we'll use the scheduler to provide fault tolerance. The demo tool we've released today is single node and uses the Docker Remote API. We've also built demos that integrate with the ECS and Marathon schedulers. Force12 will be platform agnostic. So we plan to integrate with more schedulers and Swarm is definitely on that list. |
|
|
Services are typically clustered across multiple hosts to alleviate pain associated with the availability constraints of a single host (e.g. physical resources, redundancy). "Scaling" containers across just a single host is:
1) an misunderstanding on the part of the operator, or
2) a very inefficient way of maximising the availability of a service on a single host.
In the case of 2), if you need to run multiple instances of your web service because one container doesn't maximise the resources of your host, then you're solving the problem in the wrong way. You should be making your service, in a single container, capable of maximising the resources of that host. Otherwise you're going to be wasting your physical resources taken up by the running of unnecessary containers.
Running multiple containers of the same image on the same host should be limited to testing of clustered services on a local host, admittedly with a few exceptions. I'd welcome any arguments to the contrary.