Hi Leonardo, We also provide an example of a multinode Memcached deployment, using Docker Swarm, here<http://cloudsuite.ch/swarm/>. It should be easy to follow the same process for Web Serving.
Regards, Alex On Feb 29, 2016, at 7:32 PM, Nooshin Mirzadeh <[email protected]<mailto:[email protected]>> wrote: Dear Leonardo, Thank you very much for your email, and the fixes. I have applied the changes, and we will push them to the master branch soon. The warnings are fine. There is no problem. You can run them on different machines by using the host network (instead of using my_network that is created). Also, you can take a look at Docker Swarm<https://docs.docker.com/swarm/overview/> which is for multi-node networking. It enables you to create cluster of containers over multiple nodes and creates an abstraction for you. In the future version of CloudSuite, we may consider it, as well. Regards, Nooshin On Sat, Feb 27, 2016 at 9:33 AM, Leonardo Piga <[email protected]<mailto:[email protected]>> wrote: Hi all, I was following the instructions to get the new Web Serving benchmark from here: http://cloudsuite.ch/webserving/ As a CloudSuite user since version 1, I appreciate the effort of using Dockers to make the users' life easier. However, when things do not work properly, it is very painful to debug without properly instruction. I used some of my past experience to track the following issues down. I don't know if you guys never tested the Web Serving Dockers or if you changed something after testing and broke things (most probably). After some hours reverse engineering the Dockers and installations, I finally manage to make it work. Here is the list of things that need to be fixed: 1) The web server docker should be named php_server, otherwise many things will break.I figured out that the db_server docker is still using php_server to refer to the front-end. This causes many problems with redirectiong. In the instructions, change $ docker run -d -t --net=my_net --privileged=true --name=web_server cloudsuite/web-serving:web_server /etc/bootstrap.sh to $ docker run -d -t --net=my_net --privileged=true --name=php_server cloudsuite/web-serving:web_server /etc/bootstrap.sh 2) Fix the run.sh script to look for php_server instead of web_server. Change docker exec faban_client sh -c "cd /web20_benchmark/build && java -jar Usergen.jar http://$(docker inspect --format '{{ .NetworkSettings.Networks.my_net.IPAddress }}' web_server):8080" to docker exec faban_client sh -c "cd /web20_benchmark/build && java -jar Usergen.jar http://$(docker inspect --format '{{ .NetworkSettings.Networks.my_net.IPAddress }}' php_server):8080" run.sh is pretty inconsistent, first half uses web_server and other half uses php_server. 3) There is a nasty bug in the file /usr/share/nginx/html/elgg/engine/setting.php in the web server docker that prevents memcache to work properly. In this file change $CONFIG->memcache_servers = array ( // array('server1', 11211), // array('10.22.17.71', 11211) array('memcache_server, 11211') ); to $CONFIG->memcache_servers = array ( // array('server1', 11211), // array('10.22.17.71', 11211) array('memcache_server', 11211) ); With these changes I was able to run faban_client. However, I still get many warnings. Please find attached the output of the run.sh. Do you think I should worry about these warnings? Also, do you have any suggestion to run the different servers and the clients on different machines? Perhaps using docker-machines? Let me know if you are planning to provide instructions in this lines. Regards, -- Leonardo
