Here’s a fun talk I did with Matt Fischer, Eric Peterson, and Kris Lindgren at the Tokyo summit. This lightning round talk will present various operators horror stories on weird things needed to keep OpenStack running. Audience participation is almost assured as we share feats of strength and airing of grievances. Slides (PPT) Slides (Google Slides)
We have given a few “show and tell” talks at the last summits and operators’ meetups about the OpenStack architecture we’re running at Go Daddy. We thought we’d some more in-depth posts to dive into it further.
As mentioned previously we do some customizations in Neutron in order to support our layer 3 networking model. There are no tenant networks, tunneling or overlays.
After our first two posts detailing OpenStack architecture at Go Daddy, this third one in the series focuses on Nova.
We recently had a requirement to enforce selection of an availability zone* when booting instances in nova. There’s no way to do this in the stock API, we didn’t want to modify code, and a waffle seems like overkill. So I spent some time playing with policy.json config to see if we could enforce this there:
Read full post.