Hi Muhammad, Sorry about this late reply – I was quite busy for release. We have tested Clearwater with Docker Compose as well as with Kubernete, and know for sure Clearwater works with them. The fact that you were able to enter the container also suggests that the deployment has been successfully created, and Docker Swarm isn’t what is causing the problem here. I would suggest you try to deploy it with Docker Compose, and
1. If it doesn’t work, I can help with the investigation more easily by comparing to how I did it 2. If it works, we can be sure it’s something to do with Docker Swarm and investigate in that direction Thanks, Ying From: Clearwater [mailto:[email protected]] On Behalf Of Muhammad Imran Sent: 27 November 2017 08:45 To: [email protected] Subject: [Project Clearwater] Clearwater Failing with Docker Swarm on Single/Multiple Machine(s) Hi, I am trying to deploy Clearwater project on Docker Swarm. However, it fails to start the services of Clearwater components inside the container. I tested it by deploying the services on a single machine as well as multiple machines. The issues are the same. Steps (on multiple machines): Executed the following on swarm leader machine. sudo docker swarm init (joined swarm on nodes and set node.labels.comp=<componentname> on each node so that each component must run on separate machine.) sudo docker network create -d overlay --subnet=10.254.0.0/16<http://10.254.0.0/16> clearwater_nw --attachable sudo docker service create --name etcd --constraint 'node.labels.comp==etcd' --mode=global --hostname etcd --network clearwater_nw -p 4001:4001 -p 2379:2379 -p 2380:2380 quay.io/coreos/etcd:v2.2.5<http://quay.io/coreos/etcd:v2.2.5> -name etcd0 -advertise-client-urls http://etcd:2379,http://etcd:4001 -listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 -initial-advertise-peer-urls http://etcd:2380 -listen-peer-urls http://0.0.0.0:2380 -initial-cluster etcd0=http://etcd:2380 -initial-cluster-state new sudo docker service create --name astaire --constraint 'node.labels.comp==astaire' --mode=global --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/astaire sudo docker service create --name cassandra --constraint 'node.labels.comp==cassandra' --mode=global --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/cassandra sudo docker service create --name chronos --constraint 'node.labels.comp==chronos' --mode=global --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/chronos sudo docker service create --name homestead --constraint 'node.labels.comp==homestead' --mode=global --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/homestead sudo docker service create --name homestead-prov --constraint 'node.labels.comp==homesteadprov' --mode=global --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/homestead-prov sudo docker service create --name homer --constraint 'node.labels.comp==homer' --mode=global --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/homer sudo docker service create --name ralf --constraint 'node.labels.comp==ralf' --mode=global --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/ralf sudo docker service create --name sprout --constraint 'node.labels.comp==sprout' --network name=clearwater_nw,alias=scscf.sprout,alias=icscf.sprout --mode=global -e ADDITIONAL_SHARED_CONFIG -p 22 clearwater/sprout sudo docker service create --name bono --constraint 'node.labels.comp==bono' --mode=global --env-file .env --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 -p 3478:3478 -p 3478:3478/udp -p 5060:5060 -p 5060:5060/udp -p 5062:5062 clearwater/bono sudo docker service create --name ellis --constraint 'node.labels.comp==ellis' --mode=globtachableal --network clearwater_nw -e ADDITIONAL_SHARED_CONFIG -p 22 -p 80:80 clearwater/ellis After that, when I enter inside the container, services of ellis, bono, sprout, and others are not started, so no logs are available. Environment: - I am using Openstack instances with ubuntu 16.04 (kernel version 4.10.0.28). - Clearwater docker project stable (also tried with latest and some older images available on docker hub) - Docker version 17.09.0-ce Steps (on a single machines): The commands are same as above, but no constraints and mode(by default replicated) are used. I tested Clearwater project without swarm on a single machine, and it's working fine and clearwater live tests are passing. My question is: Has the clearwater tested with Docker swarm? OR does it work with swarm for someone? OR am I doing something wrong? Please let me know if you need further clarifications from me. Thanks a lot! Best Regards, Muhammad Imran
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
