November 6-8, 2017

Event Details

Don't Repeat Our Mistakes! Lessons Learned from Running Go Daddy's Private Cloud

After years of running one of the largest OpenStack clouds, we've learned a thing or two.  Early architectural decisions about networking, storage, and scaling have real and lasting consequences.  We'll walk through some of these early decisions, some which turned out to be good, but many turned out to be bad.  Also included are some strategies for thinking through the long term impacts, to help you avoid similar pitfalls for your cloud.

What can I expect to learn?

Details on Go Daddy's cloud architecture (the good and the bad) and the reasoning behind those decisions.  Tips and strategies for avoiding architecture decisions that might have long lasting harmful consequences for your cloud.

Tuesday, November 7, 3:20pm-4:00pm
Difficulty Level: Intermediate
SendGrid, DevOps Engineer
Now with SendGrid, Mike formerly was a senior systems engineer at Go Daddy, building and managing OpenStack cloud infrastructure and supporting systems.  He thrives on enabling others to work faster and better by using the cloud.  Mike lives in Colorado with his wife and five children, and enjoys hiking (summer), skiing and snowshoeing (winter.)  Follow Mike on Twitter... FULL PROFILE
Go Daddy
Kris Lindgren is an operator of Go Daddy's public and private cloud.  He has been using openstack in a production capactiy since Havana.  He loves enabling others to work faster and better by using the cloud and other self-service portals.  He is also a core dev on the anvil project ( ), which allows deployers to package upstream openstack... FULL PROFILE