A Blog of the ZHAW Zurich University of Applied Sciences
We presented at the Swiss Academic Cloud Computing Experience conference. Below are the slides as presented (or you can grab the PDF here). Schlagwörter: federation, foreman, icclab, interoperability, presentation, puppet
In the previous article we defined use cases for an OpenStack implementation according to the usage scenario in which the OpenStack environment is deployed. In this part of the Dependability Modeling article series we will show how these use cases relate to functions and services provided by the OpenStack environment and create a set of dependabilities between use cases, functions, services and system components. From this set we will draw the dependency graph and make the impact of component outages computable.
Following on from our 2nd meeting, the Swiss OpenStack user group met on 24th of April at the University of Bern.It was an excellent event with many attention grabbing presentations! A big thanks goes out to the sponsors…
Dependability Modeling is carried out in 4 steps: model the user intercations, model the system functions, model the system services and then model the system components which make system services available. In the first part we will define which interactions could be expected from end users of the OpenStack cloud platform and construct the first part of the dependability graph. Once the dependapility model is constructed, a Dependability Analysis will be performed and several OpenStack HA architectures will be rated according to their outage risk.
Researcher of the InIT Cloud Computing Lab. His research interests are related to the studies and implementations of Future Internet technologies including cloud services and infrastructures aspects for the Smart Cities. His solid background in the industry allows to have a broad vision of market impacts and needs for the research and education. He is […]
In a former article we spoke about testing High Availability in OpenStack with the Chaos Monkey. While the Chaos Monkey is a great tool to test what happens if some system components fail, it does not reveal anything about the general strengths and weaknesses of different system architectures. In order to determine if an architecture with 2 redundant controller nodes and 2 compute nodes offers a higher availability level than an architecture with 3 compute nodes and only 1 controller node, a framework for testing different architectures is required. The “Dependability Modeling Framework” seems to be a great opportunity to evaluate different system architectures on their ability to achieve availability levels required by end users.
Concord is a supporting action of the FI PPP programme having as main EC objective the harmonisation, dissemination, facilitation and content of the core platform (FI-WARE), the Cloud Infrastructure (XIFI) and Use Case Projects. From Phase 2 onward , one of the challenge of FI PPP, and therefore of Concord, is the deployment of the […]
The ICCLab presented at Ireland’s second national conference on cloud computing and commerce (NC4). Below is the presentation (PDF here) given on providing a guide on how to assess the openness of cloud standards. Schlagwörter: cdmi, cimi, cloud, occi, standards
Vagrant is a ruby framework that automates a lot of the boring, painful setup a developer needs to do to work with services. In the case of the ICCLab those services are generally OpenStack services. We use vagrant to create consistent reproducible setups of our testbed on local development machines.
As proposed in a former article different technologies must be evaluated in order to make the current MobileCloud environment suitable to High Availability (HA) requirements. The following article lists a basic evaluation of the different technologies that could be used. Basically there are four technologies which allow to build a reliable HA-infrastructure for OpenStack…