Adventures of a Small Time OpenStack Sysadmin Chapter 011 - Installing the OpenStack Environment

Adventures of a Small Time OpenStack Sysadmin relate the experience of converting a small VMware cluster into two small OpenStack clusters, and the adventures and friends I made along the way.

Adventures of a Small Time OpenStack Sysadmin Chapter 011 - Installing the OpenStack Environment.

The relevant chapter from The OpenStack Install Guide:

https://docs.openstack.org/install-guide/environment.html

Most of this was installed one time, by hand, by me, then I added it to my Ansible 

and let Ansible take care of the other hosts in the cluster. Life is too short to configure by hand, let Ansible take care of it. I created for myself kind of a low-budget homemade Kolla-Ansible, and it worked pretty well.

As a checklist and commentary of each step in the process:

Ansible takes care of the apt repo.

Ansible installs SQL packages, but have to restart and finalize manually.

Ansible installs message queue, but have to add user and permissions manually.

Ansible installs memcached, but have to restart manually if config changes.

Ansible installs etcd and config file, but have to enable and restart manually. Note the human readable name is default, not controller as per docs. That seems to work?

As a side note, Openstack docs should emphasize testing MTU on networks as OS behaves very weirdly during MTU mismatch situations. MySQL, especially goes insane if you set up for a 9000 byte MTU but its actually only 1500 or even worse, 1450 bytes later on. Old timers who've run into MTU mismatch problems recognize and fix it pretty easily, but sysadmins whom have not run into MTU problems always struggle on their first. I'd almost suggest new sysadmins intentionally set up MTU settings wrong to gain the experience.

Stay tuned for the next chapter!