Is there any documentation on the storage layer of Cloudbreak docker containers - how the elasticity/bursting works as containers are added/removed from scaling?
Cloudbreak using overlayfs on the machines. More details about overlayfs here: https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/
The containers running net=host so every machine contains one ambari container which is an ambari-agent or an ambari-server.
If you scaling up the cluster then the new container will not start on an existing machine but create a new machine and they will running there.
View solution in original post
Here you can find the Cloudbreak docs and this part is describe the architecture of Cloudbreak Deployer and Cloudbreak it self: