question Re: Storage layer of Cloudbreak's docker containers - how the elasticity/bursting works as containers are added/removed from scaling in Archives of Support Questions (Read Only)

Storage layer of Cloudbreak's docker containers - how the elasticity/bursting works as containers are added/removed from scaling

RyanCicak — Wed, 11 May 2016 23:43:59 GMT

Is there any documentation on the storage layer of Cloudbreak docker containers - how the elasticity/bursting works as containers are added/removed from scaling?

Re: Storage layer of Cloudbreak's docker containers - how the elasticity/bursting works as containers are added/removed from scaling

rdoktorics — Thu, 12 May 2016 03:11:32 GMT

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.

Re: Storage layer of Cloudbreak's docker containers - how the elasticity/bursting works as containers are added/removed from scaling

tbihari — Thu, 12 May 2016 14:34:23 GMT

Here you can find the Cloudbreak docs and this part is describe the architecture of Cloudbreak Deployer and Cloudbreak it self: http://sequenceiq.com/cloudbreak-docs/latest/architecture/