CALL FOR PAPERS AND PARTICIPATION
International Workshop on Automated Incident Management in Cloud (AIMC’15)
April 21-24 2015, Bordeaux, France
On the 20th of November, the third SDN-workshop of the Software Defined Networking group of Switzerland took place in ZHAW in Winterthur. For a full day arround 25 people discussed SDN/NFV, OpenSource vs OpenSystems, impressions about (open) standards and recommendations from SDOs such as ETSI/SDNRG and other SDN related issues.
As someone new to SDN, it was a great opportunity to see exciting research going on with this technology. All the talks were very interesting, but I especially liked the presentation about Service chaining using SDN by David Hausheer from the TU Darmstadt. He showed us how they used SDN and OpenFlow technology to make it easier to set up rules for complex network configurations. Basically with the system they developed you can drag and drop services (eg a firewall or a proxy) into a Service chain and for the different users appropriate rules will be inserted into the OpenFlow Switches to realize this compound service. It was very interesting to see how SDN is currently used and the possibility to support networking processes with this technology. Overall it was also great to meet these SDN specialists and the activities they are carrying out in the area of Software Defined Networking with strong ideas.
The SDN community in Switzerland is growing and we are looking forward to the next workshop which will be held sometime in Q1 of 2015. So if you are interested in it, join the Linkedin group or contact one of the chairs directly (Kurt Baumann or Thomas Michael Bohnert).
In our previous blog post we showed a web application to monitor and understand energy consumption in an Openstack cluster; the main goal of this tool is to understand how energy consumption relates to activity on the cloud resources. In general, this can be quite complex as there are many resources to take in account and Ceilometer doesn’t report all the information required at this time. In this blog post we describe one task we needed to perform in this work: we needed to retrieve from Ceilometer the set of VMs running on a given physical server together with their CPU utilization over some period of time. We can envisage other contexts in which it might be useful to do this, so we present the solution here. (Note that it is of course possible to obtain the set of VMs that are currently running on a given physical host using Nova, but this does not offer the historical perspective).
Hurray! We have finally deployed QEMU 2.1.5 with post-copy live migration support on our servers! But before we get to that, a little bit of context… in our previous blog posts we focused on performance analysis of pre-copy live migration in Openstack. So far all of our experiments were done using QEMU version 1.2 with KVM acceleration. As we were keen to do some experimentation with post-copy live migration, we had to upgrade to the very new QEMU 2.1.5 which provides post-copy live migration support in one of its branches. (More generally, there have been significant enhancements in QEMU since version 1.2 – of November 2012 – and hence we expected better performance and reliability in pre-copy as well). This blog post focuses on our first hands-on experience with post-copy live migration in QEMU.
ZHAW Service Engineering ICCLab periodically sends Newsletters with information about latest activities of the lab and relevant events. This is the newsletter for November 2014 and the last for the year 2014.
(03/11/2014) In September, the European Commission announced the launch of its FIWARE Accelerator Programme, an €80 million booster shot for SMEs, startups and web entrepreneurs using Future Internet platforms and technology.
The new programme will help FIWARE expand its already significant network of Public-Private Partners and entrepreneurs helping to create a thriving startup environment for Future Internet developments in Europe.
Understanding how innovation works continues to be a significant agenda item for many researchers. Innovation, however, is generally recognised to be a complex and multi-dimensional phenomenon. Classificatory approaches have been used to provide conceptual frameworks for descriptive purposes and to help better understand innovation. Furthermore, classificatory approaches also attempt to elevate theorising from the specific and contextual to something more abstract and generalisable. In last decades, researchers have sought to explain variance in innovation activities and outcomes in terms of these different ‘types’ of innovation. The innovations are targeted to invent, or increment as we will see, new solutions that will be introduced in the market. Therefore in the methods for classifying the innovations are often utilized or customized to classify the products to specific market momentum or to classify the simply the markets. In the next sections, this part-1 blog introduces at high level the Gartner Market clock classification (for the products) and the innovation cube approach for the classification of the innovations. The second one is mainly a method to identify winning innovation strategies for the market and for the industries.
The part-2 of this blog will be dedicated to practical example to classify the ICT innovation and in particular the ecosystem of products dealing with virtualization an cloud computing.
ICCLab had the privilege to talk about our latest research activities in “Rating, Charging & Billing” & “Performance analysis of live migrations in OpenStack” at the #vBrownBag Tech talks which were held as part of OpenStack summit in Paris. Here we provide a short summary of each talk and include the captured video for your viewing pleasure!
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.