All technology fails. There is no getting around this point. The part that we can influence out of that statement is what happens when the technology fails. OpenStack in all its marvelous modular glory can be a bear when you encounter the service failure creep. You know that think which occurs when one service fails and then causes another service to fail...then on and on.
Imagine if you could configure your OpenStack services to automatically recovery. Yes, I know you are going to say I can do that with a cron job or something alike. For a second think of the impact if you could link your monitoring system to another one that will trigger automated recovery processes to restore your OpenStack services without human intervention.
This workshop will walk attendees thru the process of linking a monitoring system such as Nagios to an automated recovery system such as StackStorm to produce auto-recovery OpenStack cloud actions.
Please note: session attendance does have a maximum capacity. All admittance will be on a first come, first served basis. Thank you for your understanding.
- Attendees will learn a bit about what services should be monitored with Nagios
- Learn some baseline threshold you can set for your monitoring events
- Become familar with StackStorm, an open source triggered auto-remediation tool
- Explore how you can link the two tools together to setup auto-recovery for your OpenStack services
