If you read the previous posts of this little series (hopefully it was interesting) you might be interested in this last post as well because it will conclude this series. I’ll focus on the main aspects we had to consider when the actual migration was about to happen. The pacemaker cluster was up and running as were all the required services.
We’re approaching the finale of this little blog series. In the previous post I described how to make Galera, RabbitMQ and Memcached highly available. This article will be about the HA configuration of the OpenStack services, this blog series will then conclude with the migration process itself and what to be aware of in the last part (V).
The previous post in this little series was about environment preparation to install the latest operating system and OpenStack version but preserve the database in order to migrate an existing Cloud environment to a newer platform. I mainly focused on the database as the most critical component.
This post will be about Galera, RabbitMQ and Memcached to continue the environment preparation. The next article will describe the high availability setup of the OpenStack services and then I’ll conclude with a last article dealing with the required steps for the actual migration.
