Picking up the pieces

Independent of which use case your future OpenStack deployment will start with, mastering the art of its ecosystem is a vital step before investigating any further design and architecture options. OpenStack covers more than 1 million lines of Python code! At this stage, there is no need to worry about learning how the code works: far more important is to take a reverse engineering approach: understanding the ecosystem interactions. Simply understanding the interrelation of core services gives you the keys to the kingdom of the art of design. Starting with the basics, the foundational components will open more doors to the next ones if we master the core ones correctly. So far, we have revisited core services of OpenStack that exist with each release and had a brief scan of the incubated projects, particularly within the latest releases. Next, we will select a common workflow that illustrates the different steps and pieces to spawn a VM. This type of workflow will...