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.
"
