Many services, nodes, configuration files, log files - due to this complexity it can be cumbersome to uniquely identify the root cause for problems in a timely manner. We’re going to look at common problems in OpenStack environments, their root cause, and options for efficient operation.
OpenStack maintenance - Finding the needle in the haystack
OpenStack has come to stay for good. Many companies leverage the advantages of having a private cloud: fewer costs, more control, no vendor lock-in. In addition, you get a better understanding of how cloud platforms work. However, you also need to take care of operations and maintenance. OpenStack troubleshooting is a nontrivial task and takes a lot time, knowledge, and experience. Hundreds of log files are written by numerous services with several configuration files to countless virtual and physical machines - the possibilities for errors seem endless. Manual root cause analysis is like looking for the needle in the haystack. We’re going to look at common problems in OpenStack environments, analyze their root cause, and discuss options for effective and efficient operation and troubleshooting.
Participants of this session will learn
- Basically, OpenStack is a micro-service application and therefore also needs to be monitored
- Insight into what is important to monitor in an OpenStack environment – Resource utilization of physical and virtual machines – Health of supporting services (MySQL, RabbitMQ, Memcached) – OpenStack service availability – Response times of OpenStack services – Lead times of common OpenStack operations
- A brief overview of monitoring tools for OpenStack
- Common error patterns in OpenStack environments and how to identify and fix them
