May 2018
Intermediate to advanced
256 pages
7h 6m
English
When we design a highly available OpenStack control plane, we're looking to mitigate two different scenarios. The first is failure. When a physical piece of hardware dies, we want to make sure that we recover without human interaction and continue to provide service to our users. The second and perhaps more important scenario is success.
Software systems always work as designed and tested until humans start using them. While our automated test suites will try to launch a reasonable number of virtual objects, humans are guaranteed to attempt to launch an unreasonable number. Also, many of the OpenStack projects we've worked on have grown far past their expected size and need to be expanded on the fly.
There are a ...
Read now
Unlock full access