Category: Community (page 1 of 4)

FIWARE Acceleration – SMEs get their apps into gear with €80 million boost

Original Source:

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

Continue reading

ICCLab vBrownBag Tech Talks @ OpenStack Summit

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!

Continue reading

Swiss FIWARE Acceleration Conference – 5 December 2014

cabecera_fiware3 fi-ware_accelerators






Register free HERE

1st SWISS FI-WARE acceleration Conference 5-Dec 2014
Zurich University of Applied Sciences ICCLab
Technikumstrasse 9, 8400 – Winterthur CH – Room: TL201 (chemistry building)

FIWARE, in collaboration with FI-PPP projects, join forces to host a series of events in several cities, bringing an excellent opportunity to receive training and coaching on FIWARE enablers and open calls.

The event offers, to SWISS Small Enterprises and WEB entrepreneurs, the opportunity to introduce project ideas to the professional A16 accelerators.
They will guide you through the difficult time of developing your application and building your business with their expertise.

you2Get your funding up to 150.000 Euro (100% of your costs) !

09:00-10:00 Registration and Welcome
10:00 Overview of the Future Internet PPP- European Commission, Ragnar Bergström
10:30 FIWARE project and ecosystem – ZHAW ICCLab, Thomas Michael Bohnert MB
11:00 Swiss industry representative: Equinix
11:30 A16 Speedup! Europe Open Calls – Olaf-Gerd Gemein
12:00 Break
12:15 A16 SOUL-FI Open Calls, Nuno Varandas

12:45 Networking Lunch – A16 face to face meetings

13:30 Guide for the applicants
14:00 Wrap-up and Closing


Sponsors :


CSfi-ppp concord_logo_bigger

Attending the Swiss Informatics Society Green IT Special Interest Group

The Green IT Special Interest Group (SIG) of the Swiss Informatics Society met yesterday (29/10/14) in Zurich. ZKB kindly hosted the event. A full meeting report will probably appear on the group’s website, but here we just capture some of our reflections on the group’s work.

This was our second time to attend the group meetings. It attracts a very interesting cross-section of folks who have an interest in both making IT systems more energy efficient as well as some folks who want to use IT systems to make other vertical more energy efficient.

The group is led by the very active and engaging Klaus Meyer who does a fantastic job of defining the strategy and direction of the group, representing the group to interested parties, running the group meetings and generally banging the Green IT drum.

The meeting is attended by a diverse mix of folks including Data Centre folks who are interested in increasing energy efficiency in Data Centres – these include folks from some of the financial and insurance sector in Switzerland. There are also academics who are interested in energy efficiency from different perspectives. There are also consultants and small companies who are active in the space. All in all, the group has a very interesting and healthy mix of interesting perspectives which leads to interesting discussions.

At this week’s meeting the host ZKB gave a presentation on how energy efficiency is very important in their IT systems and they talked about how they have managed to achieve very significant savings in their operations by using advanced DC design, largely focused on cooling and airflow issues. This was followed by a very interesting presentation by the guys from Born Green Technologies on a system they are working on which supports understanding of the energy consumption of the IT systems within an organization, mostly focused on the equipment on people’s desks – phones, computers, monitors etc. – and described a case study they performed with a mid-size client in which they were able to obtain 25% savings on their energy bill.

The group is receiving increasing interest – there is a so-called Antenna group being formed in La Suisse Romande – and we’re sure it will go from strength to strength in the coming years. From our point of view, we’re very happy to be associated with it and will continue to contribute as it grows.

icclab@ Nagios World Conference 2014

Benz explains the OpenStack Nagios integration to the interested audience.

ICCLab Cloud HA initiative Leader Konstantin Benz explains the OpenStack Nagios integration to the interested audience.

The icclab participated on the Nagios World Conference 2014 which took place Oct 13th-16th, 2014 in St. Paul, MN, USA. Icclab’s Cloud High Availability-initiative leader Konstantin Benz presented an approach on how to use Nagios Core to monitor utilization of OpenStack resources. The key point he mentioned was that Nagios has to be reconfigured elastically in order to monitor virtual machines in an OpenStack environment. Depending on implementation requirements, it can be useful to exploit configuration management tools like Puppet or Chef to automatically reconfigure the Nagios server as soon as new VMs are commissioned or decommissioned by cloud users. Another approach could be to exploit OpenStack’s Ceilometer component though an integration of Nagios with Ceilometer could lead to data duplication which can be problematic for some systems, said Benz. Besides the Nagios-Ceilometer plugin Benz was able to show how elastic Nagios reconfiguration could work with Python fabric and the Cuisine library. This approach seems to be a lightweight solution to monitor VM utilization in OpenStack with Nagios. Benz also discussed a similar approach which has been chosen in the XIFI-project. The eXtensible Infrastructures for Future Internet cloud project uses Nagios as main monitoring tool to monitor OpenStack instances and resources provided by OpenStack.

Nagios Founder Ethan galstad presents Nagios Log Server to the audience.

Nagios Founder Ethan Galstad presents Nagios Log Server to the audience.

A highlight of the Nagios conference was a demo presentation of Nagios Log Server which was announced by Nagios Founder Ethan Galstad. Nagios Log Server allows for scalable and fast querying of log files – fully replacing “ELK”-Stack (ElasticSearch, LogStash, Kibana) solutions. Nagios Log Server is available under a perpetual licence that costs $995. Compared to commercial solutions this is a very modest price. In contrast to ELK-Stack solutions, Nagios Log Server offers user authentication to protect sensitive data in logfiles to be viewable by unauthorized website visitors. Another advantage are customizable visual dashboards that show log file findings. Visualization makes the task of reporting incidents to higher management a lot easier and allows for better monitoring.

8th Swiss OpenStack and Docker User Group meeting – announcement

docker-logo-loggedout         chosug  icclab-logo

OpenStack User Group – Meeting, 16 Oct. at ICCLab Winterthur

Co-located with docker CH meeting

Goals: Analysis of OpenStack  Solutions, deployments and container solutions.


ZHAW Zurich University of Applied Science
Technikumstrasse 9, 8401 Winterthur
Data: 16.10.2013 –   18:00 – 21:00

Agenda  start: 18.00 –  ROOM TL203  (Chemistry Building)

(order of speakers may change)

– Intro & Welcome 5 mins (Florian & Antonio)
– Peter Mumenthaler – Puzzle ITC – “Docker, blessing or curse? (15m)
– Marco Kueding and Rolf Schaerer (Cisco CH) – “Intercloud and Cisco OpenStack strategy.  (35 m)
– Michael Erne, ZHAW ICCLab – “Manage Docker at scale with Kubernetes” (15m)

Drink break

– Jesper Kuhl, Nuage Networks & Alcatel Lucent  “VSP – Virtualized Services Platform” (25m)
– Srikanta Patanjali, ZHAW ICCLab – ” Updates on CYCLOPS – A Charging platform for OPenStack Clouds” (20m)
– Alexander Gabert, Cynthia, “Network Virtualization” (20m)

– Common Wrap up and apero

Looking forward to seeing you all!
Snacks and Drinks kindly offered by ZHAWMirantis

Announcing 2nd CloudFoundry UserGroup DACH Meetup

link to meetup

Join us at the second CloudFoundry User Group DACH Meetup on September 22nd in Zürich.

This time the focus is on CloudFoundry in general. Learn about the basic functionality in the CloudFoundry 101 session and pick up some lessons learned from Klimpr, a startup which switched its Application from Heroku to CloudFoundry.

Date & Time
Monday, September 22nd 2014, 18:00 CEST

ZHAW School of Engineering, Lagerstrasse 41, 8021 Zürich,
Room ZL O6.10 (6th floor)

18:00 – 18:15 > Welcome
18:15 – 19:15 > CloudFoundry 101
19:15 – 19:30 > Lessons learned from Klimpr
19:30 – 21:00 > Q&A with drink and sandwiches/pizza

Please register here

ICCLab News – July 2014 Issue no.2

news header july

ZHAW Service Engineering ICCLab periodically sends Newsletters with short information about latest activities of the lab and relevant events. This is the newsletter for July 2014.

Continue reading

Most suitable language for SDK development for SDN?

We at ICCLab are embarking upon an exciting project to make a software development kit to enable SDN researchers develop exciting products and innovative protocols overcoming the challenges and drawbacks of decades old network protocols in use today. We had a huge debate internally to decide which programming language to use for this development. Since, internally we had quite strong and vocal supporters of both Java and Python, it led to stalemate. So how did we resolve it?

Continue reading

Introduction to MuleSoft

Being part of the Service Prototyping lab, the ICCLab teaches the Service Engineering course at ZHAW. As part of that course was a lecture on MuleSoft, a tool that facilitates the data exchange between applications following the service-oriented architecture (SOA) methodology. It was developed to take the donkey-work out of the integration process, allowing developers to connect anything, anywhere. Because it “carries the heavy development load” of connecting systems, it is also sometimes referenced as a Swiss army knife. Mule differs from the typical web application servers by specializing in integration between different applications, databases and cloud services, as opposed to integration with just the end users. Mule applications are also stateless and event-driven.

MuleSoft is an integration platform that consists of CloudHub and Mule ESB. CloudHub is an integration platform as a service (iPaaS) that connects SaaS and on-premise application. It allows cloud to cloud integration as well as cloud to enterprise integration. MuleESB on the other hand, is Java-based enterprise service bus for building and running integration applications and web services. It offers service meditation by separating business logic from protocols and message formats, message routing and data transformation. Most importantly, it provides service creation and service orchestration. It allows the functionalities in any endpoint to be exposed as a service and existing services to be hosted as a lightweight service containers.

To facilitate the access to MuleESB’s functionalities, there is Mule Studio, an Eclipse-based integration development environment that can be used as either a visual, drag-and-drop editor or just a simple XML editor. Because Mule is also based on the concept of event-driven architecture, you can use MuleStudio to create an application that processes messages by forming a flow. The Mule flow is actually a sequence of message-processing events constructed by combining several building blocks which are pre-packed units of business logic. Each building block in the flow evaluates or process the message until it has passed through all the building blocks in the flow. Mule receives the message through a request-response inbound endpoint, transforms the content into a new format and process the business logic before returning a response via the message source.

The Mule flow typically consists of a message source, message processors and some global elements. The message source accepts a message from an external source, thus triggering the execution of the flow itself. The message processors transform, filter and enrich the message, while the global elements are reusable pieces of code that can be invoked by multiple elements in any flow within the application. The Mule message is the data that passes through the application via one or more flows. It consists of a message header that is the meta data about the message, and message payload, the actual data content that is being transported through the Mule application. Mule uses the Mule Expression language (MEL) to facilitate the transport of the Mule message. In the final stages, a response is returned to the original sender or the results of the processing are logged to a database or send to a third party.

For example, lets say that a company has a shipping and a billing service which now need to connect to an inventory system. Writing the code manually may work for the time being, but suppose we want to make a few changes in the future. Or connect to a third party SaaS app. We will then have to update every connection. Instead, Mule can transform the different data formats and act as a translator between them.

To sum up, what Mule basically does is enabling the integration between the SaaS and on-premise applications, eliminating point-to-point connections and taking out the need to worry about the different data formats.

« Older posts