Loading…
This event has ended. View the official site or create your own event + mobile app → Check it out
This event has ended. Create your own
View analytic
Wednesday, May 14 • 9:00am - 9:40am
Saved By the Bell: Alerting, Logging, and Monitoring OpenStack with Open Source Tools

Sign up or log in to save this event to your list and see who's attending!



If you are relatively new to OpenStack you will have discovered that it is a system that is designed to provide a very robust Infrastructure as a Service (IaaS) platform. Specifically this service is the abstraction, management, automation and orchestration of underlying infrastructure components – CPU, memory, disk and network.
You may have also noticed that it is (seemingly) lacking in other infrastructure support services, e.g. monitoring, backups, alerting, notifications, etc. It is intentionally myopic in this sense – dedicated to providing core IaaS functions without introducing complexity, bloat, points of failure and other risks for functions that are otherwise not germane to its primary purpose.
Its strength however lies in its design and development philosophy – a very open architecture, easy access to data and a powerful API. This allows for the dedicated IaaS functions to operate as efficiently as possible but also exposes the components required to provide other, typically “higher level”, infrastructure and support services. These data points and functions are often consumed by processes, applications and services outside of OpenStack, e.g. Ceilometer data pulled into an external chargeback or auditing tool, Nova or Cinder APIs polled to provide capacity or asset data to an enterprise CMDB, and so on.
These higher level" infrastructure support services are still required for a production environment however. Not every environment however has tier 1, enterprise class systems, with easy or readily available OpenStack integration so how do we provide these functions for our environment using standard open source tools?
In this session we are going to explore techniques to provide a basic level of infrastructure management services, e.g. monitoring, alerting, logging, reporting, etc., for your OpenStack environment using common and freely available open source tools, e.g. monit, collectd, syslog, etc.
If you are relatively new to OpenStack you will have discovered that it is a system that is designed to provide a very robust Infrastructure as a Service (IaaS) platform. Specifically this service is the abstraction, management, automation and orchestration of underlying infrastructure components – CPU, memory, disk and network.

You may have also noticed that it is (seemingly) lacking in other infrastructure support services, e.g. monitoring, backups, alerting, notifications, etc. It is intentionally myopic in this sense – dedicated to providing core IaaS functions without introducing complexity, bloat, points of failure and other risks for functions that are otherwise not germane to its primary purpose.

Its strength however lies in its design and development philosophy – a very open architecture, easy access to data and a powerful API. This allows for the dedicated IaaS functions to operate as efficiently as possible but also exposes the components required to provide other, typically “higher level”, infrastructure and support services. These data points and functions are often consumed by processes, applications and services outside of OpenStack, e.g. Ceilometer data pulled into an external chargeback or auditing tool, Nova or Cinder APIs polled to provide capacity or asset data to an enterprise CMDB, and so on.

These "higher level" infrastructure support services are still required for a production environment however. Not every environment however has tier 1, enterprise class systems, with easy or readily available OpenStack integration so how do we provide these functions for our environment using standard open source tools?

In this session we are going to explore techniques to provide a basic level of infrastructure management services, e.g. monitoring, alerting, logging, reporting, etc., for your OpenStack environment using common and freely available open source tools, e.g. monit, collectd, syslog, etc.
"
Speakers
avatar for Jason Grimm

Jason Grimm

Open Cloud Architect, Rackspace
I'm a 40 year old husband and father of 7. | I'm a native of downtown Atlanta, GA but have made the move from townie to farmer this year and now live about an hour north of the city on a sustainable farm. | I'm an avid reader, wannabe film critic, and indie music enthusiast; collector and restorer of antique guns; occasional gamer (a.k.a. bonding time with the kids); and always up for something new and interesting. | I've had a longish and interesting career - Naval Intelligence...
Read More →
avatar for James Thorne

James Thorne

Sales Engineer at Rackspace, Rackspace
James Thorne is a Sales Engineer at Rackspace focused on working with OpenStack. He is a Texas State University alumnus and former Platform Consultant at Red Hat. James has been working with Linux professionally for the past four years and in his free time even longer. He blogs at thornelabs.net and can be followed on Twitter @jameswthorne.

Wednesday May 14, 2014 9:00am - 9:40am
Room B101

Attendees (391)

Attendance numbers do not account for private attendees. Get there early!


Remove this from your schedule?
This session is full and you may not be able to get back in.
Remove
Cancel