Reactive Orchestration in Hurtle with Monasca

In a previous series of blog posts (123), we have discussed how to install Monasca to monitor OpenStack, how to create alarms based on specific events happening in the monitored system, and how to setup notifications when any of these alarms are triggered.

Going further, in the context of the Cloud Orchestration initiative and the Hurtle framework, we go further by using Monasca to detect events in orchestrated applications and perform callbacks to the orchestrator so it can react to events. The motivation behind this is provide hurtle with processes able to perform continuous health management of any orchestrated application.

While initially designed to monitor the Cloud itself, it is easy to install the monasca agent on any platform, making it simple to monitor deployed VMs behaviour. Continue reading

Cloud Incident Management Survey

We are conducting research in order to find out more about how companies handle Cloud Incident Management in their infrastructure (ICT / Cloud).

To this end, we would be grateful if you could fill in the following survey so we could get more information about how your company does it, what tools you use (if any) and other opinions you have on the matter. Filling in the survey will only take a few minutes of your precious time.

When there will be enough data to get good statistics, we will disseminate anonymized results of the survey.

How to install and setup Monasca (3/3)

In this final part of the tutorial we will verify that all things are working properly.

Because of the large number of moving components the norm is that things will go wrong. Code changes daily both in Monasca and in Openstack and quite often things need further adjusting.

As a general rule, in case a component is misbehaving, change logging from INFO to DEBUG in /etc/monasca and restart the component. The look at the logs in /var/log/monasca and see what is wrong. For Thresh / Storm, logs can be found in /opt/storm/current/logs

Continue reading

How to install and setup Monasca (1/3)

In my previous blog post I covered my initial impressions on Monasca. In the following trilogy I will cover its installation, setup, and testing. The installation will be performed for the Java version of Monasca, as some components have both Java and Python code available. For those which only need a quick local setup best would be to use the vagrant setup found here.

The installation will be performed on Ubuntu 14.04 and will be split into 3 posts. The first one (this one) will cover dependency installation and configuration, the next one will cover Monasca’s installation and configuration, and the final one will cover the testing of the whole setup.

Continue reading

Extended Call for Papers for International Workshop on Automated Incident Management in Cloud (AIMC’15)

===========================================================
CALL FOR PAPERS AND PARTICIPATION
===========================================================
International Workshop on Automated Incident Management in Cloud (AIMC’15)
April 21-24 2015, Bordeaux, France
http://aimc.io/

Held in conjunction with
European Conference on Computer Systems (EuroSys)
http://eurosys2015.labri.fr/ Continue reading

Monasca for Cloud Monitoring: Initial impressions

One of the focuses of the Cloud Incident Management research initiative are Monitoring as a Service solutions as they provide the building blocks for incident detection and resolution. As such, part of the work carried throughout the initiative was on identifying good, maintainable, monitoring solutions which can be easily adapted and integrated into a greater incident management architecture. The current blog post tries to cover Monasca showing the good, the bad and the ugly.

Monasca is a Monitoring as a Service solution which comes from HP and Rackspace: it focuses on providing a complete monitoring solution for Openstack. Monasca is an open source solution designed to be highly scalable, performant and fault-tolerant for a multi-tenant environment. It features a RESTful API though which one can interact with the system in order to query it or send metrics for processing.

The solution monitors both the Openstack Infrastructure as well as the VMs which run on it. Further, it can be easily integrated with Rackspace’s Stacktach which forwards all Openstack events coming from its different components to be processed by Monasca. Additionally, the primary authentication mechanism it uses as well as service catalog is Keystone.

Continue reading