 Hi, I'm Stefano Maffulli. I work at Dreamhost as director of community and marketing. And I'm Caleb Boylan and I do developer advocate work at Dreamhost. We had a super fun morning at this summit where we had a very long table introduced on stage with 16 different representatives, 16 people representing different clouds, public clouds and private clouds running on different regions around the world and we all run the same script to deploy a WordPress workload on multiple nodes. It was a lot of fun. Everybody tried to make it not look like a race to finish and in fact we all won the same award at the end even though some of us were bragging about it behind the scenes for sure. It was a lot of fun. So the demo used an Ansible Playbook. Ansible when talking to OpenStack uses a Python module called Shade which sort of abstracts away the OpenStack API for Python developers so you can launch instances and do all sorts of other OpenStack stuff. Then the Playbook launches four VMs, a HA proxy balancer, two web servers and then a MySQL database and an NFS server on the same node. The HA proxy just points at the two web servers. The web servers were just running Apache with a WordPress install and then the WordPress install was shared across NFS and used the same MySQL database for both nodes. It was interesting to see before we got to the stage how all of us participants from DREAMost, Canonical, Suze, Dojo Telecom, OVH, Rackspace, Cisco, Red Hat, Fujitsu, Huawei and I'm probably missing someone else but you know there's going to be I'm sure some more info below here that we were all an IBM. How could I forget? We were all running the same identical script and the only thing that changed was the configuration files where we put our username and passwords and the URL for the API calls. Everything else of the Playbook was exactly the same, the very hard things to deploy. They were using the same stuff, whether it was running on a private cloud in Japan or a public cloud in West Virginia. It was super fun and we're going to take it to the next level. We actually had our very first chat about what we're going to do next because now that we set the bar so high with the length of the table we're going to have to find something else to do next.