what does it mean by different docker-compose.yml file after cluster creation? How does it internally communicate ? how can I see docker-compose file in other nodes ?

[#1]

Hi All,

what does it mean by different docker-compose.yml file after cluster creation? How does it internally communicate ? how can I see docker-compose file in other nodes ?

from where can I get all information internal architecture of docker communication between nodes ? now I know the architeture but does not how exactly it communicate in technical way.

Thanks,

Ram

docker.jpg

[#2 · Accepted solution]

Hi @Rambabu Gupta,

Docker compose file is part of Cloudbreak installation. It contains services which used by Cloudbreak. On the other hand Cloudbreak could provision clusters in cloud. Cloudbreak doesn't share any internal architecture stuff, so docker-compose.ym doesn't appear in other nodes.

What communication are you interested in?

- Cloudbreak internal, how containers work together

- Cloudbreak with the provisioned cluster?

- How cloud instances "communicate"?

[#3]

Hi @Rambabu Gupta This compose files only for cloudbreak deployer and not for the nodes. This lot of files are just backup because every times when you say 'cbd regenerate' then cloudbreak deployer make a backup from your actual compose file.

[#4]

Ok thanks for clarification.. yes how cloud instances communicate ? and also how containers work together.. if i understand correctly , docker would be installed on every machine but i could not able to see container in nodes..

[#5]

By default we are not using docker in cluster anymore. Docker only used for the cloudbreak containers (for example for the database).

[#6]

Ok.. I have seen architecture in which its shown that docker will be present in every nodes .. Please find the attached.. docker1.jpgso why swarm is used for ?

[#7]

This picture represent an older architecture. We are not using docker on the cluster machines anymore. Swarm is also not used anymore.

[#8]

Ok thanks for info 🙂