{"version":"1.0","provider_name":"Service  Engineering (ICCLab &amp; SPLab)","provider_url":"https:\/\/blog.zhaw.ch\/icclab","author_name":"Andy Edmonds","author_url":"https:\/\/blog.zhaw.ch\/icclab\/author\/edmo\/","title":"How Do You Organise Your OpenStack Deployment?","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"JUNNQKSaOL\"><a href=\"https:\/\/blog.zhaw.ch\/icclab\/how-do-you-organise-your-openstack-deployment\/\">How Do You Organise Your OpenStack Deployment?<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/blog.zhaw.ch\/icclab\/how-do-you-organise-your-openstack-deployment\/embed\/#?secret=JUNNQKSaOL\" width=\"600\" height=\"338\" title=\"&#8220;How Do You Organise Your OpenStack Deployment?&#8221; &#8212; Service  Engineering (ICCLab &amp; SPLab)\" data-secret=\"JUNNQKSaOL\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script>\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/\/# sourceURL=https:\/\/blog.zhaw.ch\/icclab\/wp-includes\/js\/wp-embed.min.js\n<\/script>\n","description":"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.","thumbnail_url":"http:\/\/blog.zhaw.ch\/icclab\/files\/2013\/02\/AZs.png"}