ICCLab & Swiss Informatics Society – Cloud Computing Special Interest Group

We, the ICCLab, are proud to announce that the past Presidential Conference of the Swiss Informatics Society accepted our proposal (slides) for setting up a Special Interest Group in Cloud Computing. The SIG is currently being formed. If you wish to participate and influence the future of Swiss Cloud Computing in this context please don’t hesitate to contact us. […]



How to Test your OpenStack Deployment?

Like us in the ICCLab, you have likely spent lots of time researching the best means to deploy OpenStack and you’ve decided upon a particular method (at the ICCLab we use foreman and puppet). You’ve implemented OpenStack with your chosen deployment plan and technologies and you now have an operational OpenStack cluster. The question you now have to ask is: “How do I test that all functionality is operating correctly?”


How Do You Organise Your OpenStack Deployment?

So you have a new shiny OpenStack installation! Within that installation you may have differing classes of hardware and so you wish to be able to organise those classes

To organise your OpenStack deployment there are two concepts currently available: Availability Zones (AZs) and Cells. These allow you categorise your resources within an OpenStack deployment and organise those resources as you see fit. These is a very useful feature in order to offer different types of the same service. For example you might want to offer a compute service that runs on SSDs or plain spinning disks.

In this article we’ll describe OpenStack Availability Zones (AZs) and OpenStack Cells. We’ll also show how each differ.