1
{"id":34672,"date":"2015-11-30T22:16:09","date_gmt":"2015-11-30T20:16:09","guid":{"rendered":"https:\/\/cloudbase.it\/?p=34672"},"modified":"2016-01-11T17:24:06","modified_gmt":"2016-01-11T15:24:06","slug":"hyper-c-part-2","status":"publish","type":"post","link":"https:\/\/cloudbase.it\/hyper-c-part-2\/","title":{"rendered":"Hyper-Converged OpenStack on Windows Nano Server &#8211; Part 2"},"content":{"rendered":"<h4>In the <a href=\"https:\/\/cloudbase.it\/hyper-c\/\">previous article<\/a> in this series we gave you a quick overview of why OpenStack and Windows Nano Server provide\u00a0some of the most exciting elements in\u00a0the current Windows ecosystem. In this article we are going to expand on those elements, and also give you the tools you need to deploy your own Hyper-Converged cloud using our <a href=\"https:\/\/cloudbase.it\/openstack-hyperv-driver\/\" target=\"_blank\">OpenStack Windows\u00a0Liberty components<\/a> along with Ubuntu&#8217;s OpenStack Linux ones!<\/h4>\n<p>&nbsp;<\/p>\n<h2>Why is everyone so excited about Windows Nano Server?<\/h2>\n<p>Nano Server is a new installation option for Windows Server 2016, reducing the overall footprint to just a few hundreds MB of disk space. The resulting deployed OS is thus way faster to deploy and to boot, reducing drastically also the overall amount of updates and reboots required during daily management. In short, it&#8217;s an OS built for a cloud age and huge leap forward compared to traditional GUI based Windows deployments.<\/p>\n<p>Nano images are\u00a0designed to be purpose built for each deployment. That means that if you want a Windows Server that is just a hypervisor, you can build the image just with that role installed and nothing else. In this article we are going to focus on three main roles:<\/p>\n<ul>\n<li>Compute (Cloudbase OpenStack components and Hyper-V)<\/li>\n<li>Clustering<\/li>\n<li>Storage (Storage Spaces Direct)<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Storage Spaces Direct (S2D)<\/h2>\n<p>Aside from Nano itself, this is one of the features I am most excited about and a key element in allowing a hyper-converged scenario on Windows Server. Storage Spaces Direct is an evolution of Storage Spaces introduced in Windows Server 2012, with one important difference &#8211; it allows you to use locally attached storage. This means that you can use commodity hardware to build you own scale out storage at a fraction of the cost of a normal enterprise storage solution. This also means that we can create a hyper-converged setup where all Hyper-V compute nodes are clustered together and become bricks in a scale-out storage system.<\/p>\n<p>&nbsp;<\/p>\n<p><a class=\"dt-single-image\" href=\"https:\/\/i0.wp.com\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d.png?ssl=1\" data-dt-img-description=\"\"><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-34507\" src=\"https:\/\/i0.wp.com\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d.png?resize=1200%2C683&#038;ssl=1\" alt=\"hyper-c-gfx\" width=\"1200\" height=\"683\" \/><\/a><\/p>\n<h2>Ok, Ok&#8230; lets deploy already!<\/h2>\n<p>Before we begin, a word of warning. Windows Nano Server is in Technical Preview (it will be released as part of\u00a0Windows Server 2016). The following deployment instructions have been tested and validated on the current Technical Preview 4 and subject to possible changes in the upcoming\u00a0releases.<\/p>\n<p>&nbsp;<\/p>\n<h2>Prerequisites<\/h2>\n<p>We want to deploy an OpenStack cloud on bare metal. We will use Juju for orchestration and\u00a0MAAS (Metal as a Service) as a\u00a0bare metal provider. Here&#8217;s our requirements list. We kept the number of resources to the bare minimum, which means that some features, like full components redundancy are left for one of the\u00a0next blog posts:<\/p>\n<ul>\n<li>MAAS install<\/li>\n<li><a href=\"https:\/\/www.microsoft.com\/en-us\/evalcenter\/evaluate-windows-server-technical-preview\">Windows Server 2016 TP4 ISO<\/a><\/li>\n<li>A Windows 10 or Windows Server 2016 installation. You will need this to build MAAS images.<\/li>\n<li>One host to be used for MAAS and controller related services\n<ul>\n<li>Should\u00a0have at least three\u00a0NICs (management, data, external)<\/li>\n<\/ul>\n<\/li>\n<li>At least 4 hosts\u00a0that will be used as Hyper-V compute nodes\n<ul>\n<li>Each compute node <strong>must<\/strong> have at least two disks<\/li>\n<li>Each compute node should\u00a0have at least two NICs (management and data)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>As an example, our typical lab environment uses Intel NUC servers. They are great for testing and have been our trusty companions throughout many demos and OpenStack summits. These are the <a href=\"http:\/\/www.intel.com\/content\/www\/us\/en\/nuc\/nuc-kit-nuc5i5myhe-board-nuc5i5mybe.html\">new NUCs<\/a> that have one mSATA port and an one M.2 port. We will use the M.2 disk as part of the storage spaces direct storage pool. Each NUC has one extra USB 3 ethernet NIC that acts as a data port.<\/p>\n<p>&nbsp;<\/p>\n<p>Here\u2019s a detailed\u00a0list of the nodes configuration:<\/p>\n<blockquote class=\"text-big shortcode-blockquote\"><table class=\"cbsl-table\" style=\"font-weight: normal;\">\n<colgroup>\n<col \/>\n<col \/><\/colgroup>\n<tbody>\n<tr>\n<th class=\"tg-yw4l\" colspan=\"2\">Node 1<\/th>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\" colspan=\"2\">Ubuntu 14.04 LTS MAAS on bare metal with 4 VMs running on KVM.<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\" rowspan=\"3\">3 NICs, each one attached to a standard linux bridge.<\/td>\n<td class=\"tg-yw4l\"><strong>eth0<\/strong> (attached to br0) is the MAAS publicly accessible NIC. It will be used by neutron as an external NIC.<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\"><strong>eth1<\/strong> (attached to br1) is connected to an isolated physical switch. This will be the management port for nodes deployed using MAAS.<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\"><strong>eth2<\/strong> (attached to br2) is connected to an isolated physical switch. This will be the data port used for tenant traffic.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/blockquote><br \/>\nThis node also hosts 4 virtual machines:<\/p>\n<blockquote class=\"text-big shortcode-blockquote\"><table class=\"cbsl-table\" style=\"font-weight: normal;\">\n<tbody>\n<tr>\n<th class=\"tg-yw4l\">Name<\/th>\n<th class=\"tg-yw4l\">Tags<\/th>\n<th class=\"tg-yw4l\">Purpose<\/th>\n<th class=\"tg-yw4l\">NICs<\/th>\n<th class=\"tg-yw4l\">vCPU<\/th>\n<th class=\"tg-yw4l\">RAM<\/th>\n<th class=\"tg-yw4l\">Disk<\/th>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\">VM01<\/td>\n<td class=\"tg-yw4l\"><strong>state<\/strong><\/td>\n<td class=\"tg-yw4l\">Juju state machine<\/td>\n<td class=\"tg-yw4l\">eth0 attached to br1<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap; text-align: center;\">2<\/td>\n<td class=\"tg-yw4l\">2 GB<\/td>\n<td class=\"tg-yw4l\">20 GB<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\">VM02<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap;\"><strong>s2d-proxy<\/strong><\/td>\n<td class=\"tg-yw4l\">Manages the Nano Server S2D cluster.<\/td>\n<td class=\"tg-yw4l\">eth0 attached to br1<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap; text-align: center;\">2<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap;\">2 GB<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap;\">20 GB<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\">VM03<\/td>\n<td class=\"tg-yw4l\"><strong>services<\/strong><\/td>\n<td class=\"tg-yw4l\">OpenStack controller<\/td>\n<td class=\"tg-yw4l\">eth0 attached to br1 (maas management)<br \/>\neth1 attached to br2 (isolated data port)<br \/>\neth3 attached to br0 (external network)<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap; text-align: center;\">4<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap;\">8 GB<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap;\">80 GB<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\">VM04<\/td>\n<td class=\"tg-yw4l\"><strong>addc<\/strong><\/td>\n<td class=\"tg-yw4l\">Active Directory Controller<\/td>\n<td class=\"tg-yw4l\">eth0 attached to br1<\/td>\n<td class=\"tg-yw4l\" style=\"white-space: nowrap; text-align: center;\">2<\/td>\n<td class=\"tg-yw4l\">2 GB<\/td>\n<td class=\"tg-yw4l\">20 GB<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/blockquote>\n<p>&nbsp;<\/p>\n<p>The rest of the nodes look like this:<\/p>\n<blockquote class=\"text-big shortcode-blockquote\"><table class=\"cbsl-table\">\n<colgroup>\n<col \/>\n<col \/><\/colgroup>\n<tbody>\n<tr>\n<th class=\"tg-yw4l\" colspan=\"2\">Node 2, 3, 4, 5<\/th>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\" colspan=\"2\">Nano Server Hyper-V compute nodes with Cloudbase OpenStack components<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\" colspan=\"2\">Tag: <b>nano<\/b><\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\" rowspan=\"2\">2 NICs<\/td>\n<td class=\"tg-yw4l\">one NIC attached to the MAAS management switch (PXE booting must be enabled and set as first boot option)<\/td>\n<\/tr>\n<tr>\n<td class=\"tg-yw4l\">one NIC attached to the isolated data switch<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/blockquote>\n<p>&nbsp;<\/p>\n<h2>Install MAAS<\/h2>\n<p>We are not going to go into too much detail over this as the installation process has been very well documented in the <a href=\"https:\/\/maas.ubuntu.com\/docs\/install.html\">official documentation.<\/a>\u00a0Just follow this article, it&#8217;s very simple and straightforward. Make sure to configure your management network for both DHCP and DNS.\u00a0After installing MAAS, it&#8217;s time to register your nodes in MAAS. You can do so by simply powering them on once. MAAS will automatically enlist them.<\/p>\n<p>You can log in the very simple and intuitive MAAS web UI available at <strong>http:\/\/&lt;MAAS&gt;\/MAAS<\/strong>\u00a0and check that you nodes are properly enlisted.<\/p>\n<p>&nbsp;<\/p>\n<h2>Assign tags to your MAAS nodes<\/h2>\n<p>Tags allow Juju to request hardware with specific requirements to MAAS for specific charms. For example the Nano Server nodes will have a &#8220;nano&#8221; tag. This is not necessary if your hardware is completely homogenous. We listed the tags in the prerequisite section.<\/p>\n<p>This can be done either with the UI by editing each individual node or with the following Linux CLI instructions.<br \/>\n<a name=\"register-tag\"><\/a><br \/>\nRegister a tag with MAAS:<\/p>\n<pre class=\"lang:sh decode:true\">maas root tags new name='state'<\/pre>\n<p><a name=\"assign-tag\"><\/a><br \/>\nAnd assign it to a node:<\/p>\n<pre class=\"lang:sh decode:true \"># &lt;system_id&gt; is the node's system ID. You can fetch it from MAAS\r\n# using:\r\n# maas root nodes list\r\n# and usually has the form of:\r\n# node-2e8f4d32-7859-11e5-8ee5-b8aeed71df42\r\n# You can also get the ID of the node from the MAAS web ui by clicking on the node.\r\n# The ID will be displayed in the browsers URL bar.\r\nmaas root tag update-nodes state add=\"&lt;system_id&gt;\"<\/pre>\n<p>&nbsp;<\/p>\n<h2>Build Windows images<\/h2>\n<p>After you have installed MAAS, we need to build Windows images. For this purpose, we have a set of PowerShell CmdLets\u00a0that will aid you in building the images. Log into your Windows 10 \/ Windows Server 2016 machine and open an elevated\u00a0PowerShell\u00a0prompt.<br \/>\n<a name=\"required-packages\"><\/a><br \/>\n&nbsp;<br \/>\nFirst lets download some required packages:<\/p>\n<pre class=\"lang:ps decode:true\"># install Chocolatey package provider\r\nGet-PackageProvider -Name chocolatey -ForceBootstrap\r\nSet-PackageSource -Name Chocolatey -Trusted:$true\r\n\r\n# Install Git\r\nInstall-Package -Source Chocolatey git\r\n\r\n# Install Notepad++ (optional). Any other good editor will do as well.\r\nInstall-Package -Source Chocolatey notepadplusplus\r\n\r\n# Add git to your path\r\n$env:PATH +=  \";${env:ProgramFiles}\\Git\\cmd\"\r\n\r\n# check that git works\r\ngit --version\r\n\r\n# If you wish to make the change to your $env:PATH permanent\r\n# you can run:\r\n# setx PATH $env:PATH<\/pre>\n<p><a name=\"required-resources\"><\/a><br \/>\nDownload the required resources:<\/p>\n<pre class=\"lang:ps decode:true \" title=\"Fetch scripts\">$ErrorActionPreference = \"Stop\"\r\nmkdir $HOME\\hyper-c -ErrorAction SilentlyContinue\r\ncd $HOME\\hyper-c\r\n\r\n# Fetch scripts and commandlets\r\nInvoke-WebRequest https:\/\/bit.ly\/FastWebRequest -OutFile FastWebRequest.psm1\r\nImport-Module .\\FastWebRequest.psm1\r\n\r\nInvoke-FastWebRequest -Uri \"https:\/\/the.earth.li\/~sgtatham\/putty\/latest\/x86\/pscp.exe\"\r\nInvoke-FastWebRequest -Uri \"https:\/\/the.earth.li\/~sgtatham\/putty\/latest\/x86\/putty.exe\"\r\n\r\n# Fetch nano image tools\r\ngit clone https:\/\/github.com\/cloudbase\/cloudbase-init-offline-install.git nano-image-tools\r\npushd nano-image-tools\r\ngit checkout nano-server-support\r\ngit submodule init\r\ngit submodule update\r\npopd\r\n\r\n# Fetch Windows imaging tools\r\ngit clone https:\/\/github.com\/cloudbase\/windows-openstack-imaging-tools.git windows-imaging-tools\r\npushd windows-imaging-tools\r\ngit checkout experimental\r\npopd\r\n\r\n\r\n<\/pre>\n<p>You should now have two extra folders in your home folder:<\/p>\n<ul>\n<li>generate-nano-image<\/li>\n<li>windows-openstack-imaging-tools-experimental<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>Generate the Nano image<\/h3>\n<p><a name=\"generate-nano-image\"><\/a><br \/>\nLets generate the Nano image first:<\/p>\n<pre class=\"lang:sh decode:true\">cd $HOME\\hyper-c\\nano-image-tools\r\n\r\n# Change this to your actual ISO location\r\n$isoPath = \"$HOME\\Downloads\\Windows_Server_2016_Technical_Preview_4.ISO\"\r\n# This will be your default administrator password. Change this to whatever you prefer\r\n$password = ConvertTo-SecureString -AsPlaintext -Force \"P@ssw0rd\"\r\n# This is the path of your Nano baremetal image \r\n$targetPath = \"$HOME\\DiskImages\\Nano.raw.tgz\"\r\n\r\n# If your hardware needs extra drivers for NIC or storage, you can add it by\r\n# passing the -ExtraDriversPaths option to the script.\r\n.\\NewNanoServerImage.ps1 -IsoPath $isoPath -TargetPath $targetPath `\r\n-AdministratorPassword $password -Platform BareMetal `\r\n-Compute -Storage -Clustering -MaxSize 1500MB `\r\n-AddCloudbaseInit -AddMAASHooks\r\n\r\ncd ..\r\n\r\n# Change to match you MAAS host address\r\n$MAAS_HOST = \"192.168.200.10\"\r\n\r\n# Copy the Nano image to the MAAS host, change the credentials accordingly\r\n.\\pscp.exe \"$targetPath\" \"cloudbase@${MAAS_HOST}:\"\r\n<\/pre>\n<p>Now, SSH into your MAAS node and\u00a0upload the image in MAAS using the following commands:<\/p>\n<pre class=\"lang:sh decode:true \"># Get your user's MAAS API key from the following URL: http:\/\/${MAAS_HOST}\/MAAS\/account\/prefs\/ \r\n# Note: the following assumes that your MAAS user is named \"root\", replace it as needed \r\nmaas login root http:\/\/${MAAS_HOST}\/MAAS \r\n# Upload image to MAAS\r\n# At the time of this writing, MAAS was version 1.8 in the stable ppa\r\n# Windows Server 2016 and Windows Nano support has been added in the next stable release.\r\n# as such, the images we are uploading, will be \"custom\" images in MAAS. With version &gt;= 1.9\r\n# of MAAS, the name of the image will change from win2016nano to windows\/win2016nano\r\n# and the title will no longer be necessary\r\nmaas root boot-resources create name=win2016nano title=\"Windows Nano server\" architecture=amd64\/generic filetype=ddtgz content@=$HOME\/Nano.raw.tgz<\/pre>\n<p>The name is important. It <strong>must<\/strong> be win2016nano. This is what juju expects when requesting the image from MAAS for deployment.<\/p>\n<p>&nbsp;<\/p>\n<h3>Generate a Windows Server 2016 image<\/h3>\n<p><a name=\"generate-windows-image\"><\/a><br \/>\nThis will generate a MAAS compatible image starting from a Windows ISO, it requires Hyper-V:<\/p>\n<pre class=\"lang:ps decode:true\">cd $HOME\\hyper-c\\windows-imaging-tools\r\n\r\n# Mount Windows Server 2016 TP4 ISO\r\n# Change path to actual ISO\r\n$isoPath = $HOME\\Downloads\\WindowsServer2016TP4.iso\r\n\r\n# Mount the ISO\r\n$driveLetter = (Mount-DiskImage $isoPath -PassThru | Get-Volume).DriveLetter \r\n$wimFilePath = \"${driveLetter}:\\sources\\install.wim\"\r\n \r\nImport-Module .\\WinImageBuilder.psm1 \r\n \r\n# Check what images are supported in this Windows ISO\r\n$images = Get-WimFileImagesInfo -WimFilePath $wimFilePath\r\n \r\n# Get the Windows images available in the ISO \r\n$images | select ImageName \r\n \r\n# Select the first one. Note: this will generate an image of Server Core.\r\n# If you want a full GUI, or another image, choose from the list above\r\n$image = $images[0]\r\n \r\n$targetPath = \"$HOME\\DiskImages\\Win2016.raw.tgz\" \r\n \r\n# Generate a Windows Server 2016 image, this will take some time!\r\n# This requires Hyper-V for running the instance and installing Windows updates\r\n# If your hardware needs extra drivers for NIC or storage, you can add it by\r\n# passing the -ExtraDriversPath option to the script.\r\n# You also have the option to install Windows Updates by passing in the -InstallUpdates option\r\nNew-MAASImage -WimFilePath $wimFilePath -ImageName $image.ImageName `\r\n-MAASImagePath $targetPath -SizeBytes 20GB -Memory 2GB `\r\n-CpuCores 2\r\n\r\ncd ..\r\n\r\n# Copy the Nano image to the MAAS host\r\n.\\pscp.exe \"$targetPath\" \"cloudbase@${MAAS_HOST}:\"<\/pre>\n<p>Upload the image to MAAS:<\/p>\n<pre class=\"lang:sh decode:true\"># upload image to MAAS\r\n# At the time of this writing, MAAS was version 1.8 in the stable ppa\r\n# Windows Server 2016 and Windows Nano support has been added in the next stable release.\r\n# as such, the images we are uploading, will be \"custom\" images in MAAS. With version &gt;= 1.9\r\n# of MAAS, the name of the image will change from win2016 to windows\/win2016\r\n# and the title will no longer be necessary\r\nmaas root boot-resources create name=win2016 title=\"Windows 2016 server\" architecture=amd64\/generic filetype=ddtgz content@=$HOME\/Win2016.raw.tgz\r\n<\/pre>\n<p>As with the Nano image, the name is important. It <strong>must<\/strong> be win2016.<\/p>\n<p>&nbsp;<\/p>\n<h2>Setting up Juju<\/h2>\n<p>Now the fun stuff begins. We need to fetch the OpenStack Juju charms and juju-core binaries, and bootstrap the juju state machine. This process is a bit more involved, because it requires that you copy the agent tools on a web server (any will do). A simple solution is to just copy the tools to &#8220;`\/var\/www\/html&#8220;` on your MAAS node, but you can use any web server at your disposal .<\/p>\n<p>For the juju deployment you will need to use an Ubuntu machine. We generally use the MAAS node directly in our demo setup, but if you are running Ubuntu already, you can use your local machine.<\/p>\n<p>&nbsp;<\/p>\n<h3>Fetch the charms and tools<\/h3>\n<p>For your convenience we have compiled a modified version of the agent tools and client binaries that you need to run on Nano Server. This is currently necessary as we&#8217;re still submitting upstream the patches for Nano Server support, so this step won&#8217;t be needed by the time Windows Server 2016 is released.<\/p>\n<p>From your Ubuntu machine:<\/p>\n<pre class=\"lang:sh decode:true\"># install some dependencies\r\n# add the juju stable ppa. We need this to get juju-deployer\r\nsudo apt-add-repository -y ppa:juju\/stable\r\n# install packages\r\nsudo apt-get update\r\nsudo apt-get -y install unzip git juju-deployer\r\n\r\nmkdir -p $HOME\/hyper-c\r\ncd $HOME\/hyper-c\r\n\r\n# Download juju-core with Nano support and the Hyper-C charms\r\ngit clone https:\/\/github.com\/cloudbase\/hyper-c.git hyper-c-master\r\nwget \"https:\/\/github.com\/cloudbase\/hyper-c\/releases\/download\/hyper-c\/juju-core.zip\"\r\nunzip juju-core.zip\r\n\r\n# Add the client folder to the $PATH. You can make this change permanend\r\n# for the current user by adding:\r\n# export PATH=\"$HOME\/hyper-c\/juju-core\/client:$PATH\"\r\n# to $HOME\/.bashrc\r\nexport PATH=\"$HOME\/hyper-c\/juju-core\/client:$PATH\"\r\n# test that the juju client is in your path\r\njuju version\r\n<\/pre>\n<p>If everything worked as expected, the last command should give you the Juju version.<\/p>\n<p>&nbsp;<\/p>\n<h3>Configuring the Juju environment<\/h3>\n<p>If you look inside &#8220;`$HOME\/hyper-c\/juju-core&#8220;` you will see a folder called &#8220;`tools&#8220;`. You need to copy that folder to the web server of your choice. It will be used to bootstrap the state machine. Lets copy it to the MAAS node:<\/p>\n<pre class=\"lang:ps decode:true \"># NOTE: If you are following this article directly on your MAAS node,\r\n# you can skip these steps\r\ncd $HOME\/hyper-c\r\nscp -r $HOME\/hyper-c\/juju-core\/tools cloudbase@$MAAS_HOST:~\/<\/pre>\n<p>Now, ssh into your MAAS node and copy these files in a web accessible location:<\/p>\n<pre class=\"lang:sh decode:true\">sudo cp -a $HOME\/hyper-c\/juju-core\/tools \/var\/www\/html\/\r\nsudo chmod 755 -R  \/var\/www\/html\/tools<\/pre>\n<p>Back on your client machine, create the juju environments boilerplate:<\/p>\n<pre class=\"lang:ps decode:true\">juju init<\/pre>\n<p>This will create a folder &#8220;`$HOME\/.juju&#8220;`. Inside it you will have a file called &#8220;`environments.yaml&#8220;` that we need to edit.<\/p>\n<p>Edit the environments file:<\/p>\n<pre class=\"lang:ps decode:true \">nano $HOME\/.juju\/environments.yaml<\/pre>\n<p>We only care about the MAAS provider. You will need to navigate over to your MAAS server under &#8220;`<strong>http:\/\/${MAAS_HOST}\/MAAS\/account\/prefs\/<\/strong>&#8220;` and retrieve the MAAS API key like you did before.<\/p>\n<p>Replace your &#8220;`environments.yaml&#8220;` to make it look like the following:<\/p>\n<pre class=\"lang:yaml decode:true \">default: maas\r\n\r\nenvironments:\r\n    maas:\r\n        type: maas\r\n        # this is your MAAS node. Replace \"MAAS_IP\" with the actual hostname or IP\r\n        maas-server: 'http:\/\/MAAS_IP\/MAAS\/'\r\n        # This is where you uploaded the tools in the previous step. Replace \"MAAS_IP\" with actual hostname or IP\r\n        agent-metadata-url: \"http:\/\/MAAS_IP\/tools\"\r\n        agent-stream: \"released\"\r\n        maas-oauth: 'maas_API_key'\r\n        # This will become you juju administrative user password\r\n        # you may use this password to log into the juju GUI\r\n        admin-secret: 'your_secret_here'\r\n        disable-network-management: false\r\n        bootstrap-timeout: 1800<\/pre>\n<p>Before you bootstrap the environment, it&#8217;s important to know if the newly bootstrapped state machine will be reachable from your client machine. For example, If you have a lab environment where all your nodes are in a private network behind MAAS, where MAAS is also the router for the network it manages, you will need to do two things:<\/p>\n<ul>\n<li>enable NAT and ip_forward on your MAAS node<\/li>\n<li>create a static route entry on your client machine that uses the MAAS node as a gateway for the network you configured in MAAS for your cluster<\/li>\n<\/ul>\n<p>Enable NAT on MAAS:<\/p>\n<pre class=\"lang:sh decode:true \"># enable MASQUARADE\r\n# br0 publicly accessible interface\r\n# br1 MAAS management interface (PXE for nodes)\r\n\/sbin\/iptables -t nat -A POSTROUTING -o br0 -j MASQUERADE\r\n\/sbin\/iptables -A FORWARD -i br0 -o br1 -m state --state RELATED,ESTABLISHED -j ACCEPT\r\n\/sbin\/iptables -A FORWARD -i br1 -o br0 -j ACCEPT\r\n\r\n# enable ip_forward\r\necho 'net.ipv4.ip_forward=1' &gt;&gt; \/etc\/sysctl.conf\r\nsysctl -p\r\n\r\n<\/pre>\n<p>Add a static route on your client:<\/p>\n<pre class=\"lang:ps decode:true\"># $MAAS_HOST was defined above in the sections regarding image generation\r\n# NOTE: this is not needed if you are running the juju client directly on your MAAS node\r\nroute add -net 192.168.2.0 255.255.255.0 gw $MAAS_HOST<\/pre>\n<p>You are now ready to bootstrap your environment:<\/p>\n<pre class=\"lang:ps decode:true\"># Adapt the tags constraint to your environment\r\njuju bootstrap --debug --show-log --constraints tags=state<\/pre>\n<p>&nbsp;<\/p>\n<h3>Deploy the charms<\/h3>\n<p>You should now have a fully functional juju environment with Windows Nano Server support. Time to deploy the charms!<\/p>\n<p>This is the last step in the deployment process. For your convenience, we have made a bundle file available inside the repository. You can find it in:<\/p>\n<pre class=\"lang:ps decode:true\">$HOME\/hyper-c\/hyper-c-master\/openstack.yaml<\/pre>\n<p>Make sure you edit the file and set whatever options applies to your environment. For example, the bundle file expects to find nodes with certain tags. Here is an example:<\/p>\n<pre class=\"lang:yaml decode:true\">s2d-proxy:\r\n  num_units: 1\r\n  charm: local:win2016\/s2d-proxy\r\n  branch: lp:cloudbaseit\/s2d-proxy\r\n  options:\r\n    # Change this to an IP address that matches your environment.\r\n    # This IP address should be in the same network as the IP addresses\r\n    # you configured your MAAS cluster to assign to your nodes. Make sure\r\n    # that this IP cannot be allocated to any other node. This can be done\r\n    # by leaving a few IP addresses out of the static and dynamic ranges MAAS\r\n    # allocates from.\r\n    # For example: 192.168.2.10-192.168.2.100 where 192.168.2.0-192.168.2.9\r\n    # are left for you to decide where to allocate them.\r\n    static-address: 192.168.2.9\r\n  # change this tag to match a node you want to target\r\n  constraints: \"tags=s2d-proxy\"\r\nnova-hyperv:\r\n  num_units: 4\r\n  charm: local:win2016nano\/nova-hyperv\r\n  branch: lp:cloudbaseit\/nova-hyperv\r\n  options:\r\n    use-bonding: false\r\n    # These are all the MAC addresses from all the nodes that are supposed to be\r\n    # used as data ports. You can find these ports in MAAS under node details\r\n    # Make sure you change this to match your environment.\r\n    data-port: \"3c:18:a0:05:cd:1c 3c:18:a0:05:cd:07 3c:18:a0:05:cd:22 3c:18:a0:05:cd:1e\"\r\n    network-type: \"hyperv\"\r\n    openstack-version: \"liberty\"\r\n  constraints: \"tags=nano\"<\/pre>\n<p>Pay close attention to every definition in this file. It should precisely mirror your environment (tags, MAC addresses, IP addresses, etc). A misconfiguration will yield unpredictable results.<\/p>\n<p>Use &#8220;`juju-deployer&#8220;` to deploy everything with just one command:<\/p>\n<pre class=\"lang:ps decode:true \">cd $HOME\/hyper-c\/hyper-c-master\r\njuju-deployer -L -S -c openstack.yaml<\/pre>\n<p>It will take a while for everything to run, so sit back and relax while your environment deploys. There is one more thing worth mentioning. Juju has a gorgeous web GUI. Its not resource intensive, so you can deploy it to your state machine. Simply:<\/p>\n<pre class=\"lang:sh decode:true \">juju deploy juju-gui --to 0<\/pre>\n<p>You will be able to access it using the IP of the state machine. To get the ip simply do:<\/p>\n<pre class=\"lang:sh decode:true\">juju status --format tabular<\/pre>\n<p>The user name will be &#8220;`admin&#8220;` and the password will be the value you set for &#8220;`admin-secret&#8220;`, set in\u00a0juju&#8217;s environments.yaml.<\/p>\n<p>At the end of this you will have the following setup:<\/p>\n<ul>\n<li>Liberty OpenStack cloud (with Ubuntu and Cloudbase components)<\/li>\n<li>Active Directory controller<\/li>\n<li>Hyper-V compute nodes<\/li>\n<li>Storage Spaces Direct<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h3>Access your OpenStack environment<\/h3>\n<p>Get the IP of your Keystone endpoint<\/p>\n<pre class=\"lang:sh decode:true\">juju status --format tabular | grep keystone<\/pre>\n<p>Export the required OS_* variables (you can also put them in your <em>.bashrc<\/em>):<\/p>\n<pre class=\"lang:sh decode:true \">export OS_USERNAME=cbsdemo\r\nexport OS_PASSWORD=Passw0rd\r\nexport OS_TENANT_NAME=admin\r\nexport OS_AUTH_URL=http:\/\/&lt;keystone_ip&gt;:35357\/v2.0\/\r\n\r\n# Let's list the Nova services, including the four Nano Server compute nodes\r\nsudo apt-get install python-novaclient -y\r\nnova service-list<\/pre>\n<p>You can access also Horizon by fetching its IP from Juju and open it in your web browser:<\/p>\n<pre class=\"lang:sh decode:true \">juju status --format tabular | grep openstack-dashboard<\/pre>\n<p>&nbsp;<\/p>\n<h3>What if something went wrong?<\/h3>\n<p>The great thing in automated deployments is that you can always destroy them and start over!<\/p>\n<pre class=\"lang:sh decode:true\">juju-deployer -TT -c openstack.yaml<\/pre>\n<p>Form here you can run again:<\/p>\n<pre class=\"lang:sh decode:true\">juju-deployer -L -S -c openstack.yaml\r\n<\/pre>\n<p>&nbsp;<\/p>\n<h2>Video<\/h2>\n<p>You can also watch the whole deployment process in <a href=\"https:\/\/www.youtube.com\/watch?v=jgApGS7pH5M\">this video<\/a>.<br \/>\n<iframe loading=\"lazy\" width=\"560\" height=\"315\" src=\"https:\/\/www.youtube.com\/embed\/jgApGS7pH5M\" frameborder=\"0\" allowfullscreen><\/iframe><br \/>\n&nbsp;<\/p>\n<h2>What&#8217;s next?<\/h2>\n<p>Stay tuned, in the next posts, we&#8217;ll show how to add Cinder volume on top of Storage Spaces Direct and how to easily add fault tolerance to your controller node (the Nano Server nodes are already fault tolerant).<\/p>\n<p>You can also start deploying some great guest workload on top of your OpenStack cloud, like SQL Server, Active Directory, SharePoint, Exchange etc using our <a href=\"https:\/\/cloudbase.it\/juju\/\" target=\"_blank\">Juju charms<\/a>!<\/p>\n<p>I know this has been a long post, so if you managed to get this far, congratulations and thank you! We are curious to hear how you will use Nano Server and storage spaces direct!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Nano Server is a new installation option for Windows Server 2016, reducing the overall footprint to just a few hundreds MB of disk space. The resulting deployed OS is thus way faster to deploy and to boot, reducing drastically also the overall amount of updates and reboots required during daily management. In short, it\u2019s an OS built for a cloud age and huge leap forward compared to traditional GUI based Windows deployments.<\/p>\n","protected":false},"author":18,"featured_media":34842,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_jetpack_memberships_contains_paid_content":false},"categories":[9,43,44,92,83,90,1,40],"tags":[108,84,51,50,106,7,107],"class_list":["post-34672","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hyper-v","category-juju","category-maas","category-nano-server","category-openstack","category-ubuntu","category-uncategorized","category-windows","tag-hyper-converged","tag-hyper-v","tag-juju-2","tag-maas-2","tag-nano","tag-openstack","tag-s2d","category-9","category-43","category-44","category-92","category-83","category-90","category-1","category-40","description-off"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.6 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Hyper-Converged OpenStack on Windows Nano Server - Part 2 - Cloudbase Solutions<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cloudbase.it\/hyper-c-part-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Hyper-Converged OpenStack on Windows Nano Server - Part 2 - Cloudbase Solutions\" \/>\n<meta property=\"og:description\" content=\"Nano Server is a new installation option for Windows Server 2016, reducing the overall footprint to just a few hundreds MB of disk space. The resulting deployed OS is thus way faster to deploy and to boot, reducing drastically also the overall amount of updates and reboots required during daily management. In short, it\u2019s an OS built for a cloud age and huge leap forward compared to traditional GUI based Windows deployments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cloudbase.it\/hyper-c-part-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Cloudbase Solutions\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/facebook.com\/cloudbasesolutions\" \/>\n<meta property=\"article:published_time\" content=\"2015-11-30T20:16:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2016-01-11T15:24:06+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1152\" \/>\n\t<meta property=\"og:image:height\" content=\"672\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Gabriel Samfira\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@cloudbaseit\" \/>\n<meta name=\"twitter:site\" content=\"@cloudbaseit\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Gabriel Samfira\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/\"},\"author\":{\"name\":\"Gabriel Samfira\",\"@id\":\"https:\/\/cloudbase.it\/#\/schema\/person\/9c948465f7f5ad60e7478f34c4d5bc0b\"},\"headline\":\"Hyper-Converged OpenStack on Windows Nano Server &#8211; Part 2\",\"datePublished\":\"2015-11-30T20:16:09+00:00\",\"dateModified\":\"2016-01-11T15:24:06+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/\"},\"wordCount\":2046,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\/\/cloudbase.it\/#organization\"},\"image\":{\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png\",\"keywords\":[\"hyper-converged\",\"Hyper-V\",\"juju\",\"maas\",\"nano\",\"OpenStack\",\"s2d\"],\"articleSection\":{\"0\":\"Hyper-V\",\"1\":\"Juju\",\"2\":\"MaaS\",\"3\":\"Nano Server\",\"4\":\"OpenStack\",\"5\":\"Ubuntu\",\"7\":\"Windows\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/cloudbase.it\/hyper-c-part-2\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/\",\"url\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/\",\"name\":\"Hyper-Converged OpenStack on Windows Nano Server - Part 2 - Cloudbase Solutions\",\"isPartOf\":{\"@id\":\"https:\/\/cloudbase.it\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png\",\"datePublished\":\"2015-11-30T20:16:09+00:00\",\"dateModified\":\"2016-01-11T15:24:06+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cloudbase.it\/hyper-c-part-2\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage\",\"url\":\"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png\",\"contentUrl\":\"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png\",\"width\":1152,\"height\":672},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cloudbase.it\/hyper-c-part-2\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/cloudbase.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Hyper-Converged OpenStack on Windows Nano Server &#8211; Part 2\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/cloudbase.it\/#website\",\"url\":\"https:\/\/cloudbase.it\/\",\"name\":\"Cloudbase Solutions\",\"description\":\"Cloud Interoperability\",\"publisher\":{\"@id\":\"https:\/\/cloudbase.it\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/cloudbase.it\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/cloudbase.it\/#organization\",\"name\":\"Cloudbase Solutions\",\"url\":\"https:\/\/cloudbase.it\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/cloudbase.it\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/cloudbase.it\/wp-content\/uploads\/2017\/03\/CBSL-Logo-2017-Black.png\",\"contentUrl\":\"https:\/\/cloudbase.it\/wp-content\/uploads\/2017\/03\/CBSL-Logo-2017-Black.png\",\"width\":583,\"height\":143,\"caption\":\"Cloudbase Solutions\"},\"image\":{\"@id\":\"https:\/\/cloudbase.it\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"http:\/\/facebook.com\/cloudbasesolutions\",\"https:\/\/x.com\/cloudbaseit\",\"https:\/\/www.linkedin.com\/company-beta\/3139764\",\"https:\/\/www.youtube.com\/channel\/UCBgH5RqPL4lgxA8gn3rIAFw\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/cloudbase.it\/#\/schema\/person\/9c948465f7f5ad60e7478f34c4d5bc0b\",\"name\":\"Gabriel Samfira\",\"description\":\"Senior Cloud Engineer\",\"sameAs\":[\"https:\/\/cloudbase.it\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Hyper-Converged OpenStack on Windows Nano Server - Part 2 - Cloudbase Solutions","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cloudbase.it\/hyper-c-part-2\/","og_locale":"en_US","og_type":"article","og_title":"Hyper-Converged OpenStack on Windows Nano Server - Part 2 - Cloudbase Solutions","og_description":"Nano Server is a new installation option for Windows Server 2016, reducing the overall footprint to just a few hundreds MB of disk space. The resulting deployed OS is thus way faster to deploy and to boot, reducing drastically also the overall amount of updates and reboots required during daily management. In short, it\u2019s an OS built for a cloud age and huge leap forward compared to traditional GUI based Windows deployments.","og_url":"https:\/\/cloudbase.it\/hyper-c-part-2\/","og_site_name":"Cloudbase Solutions","article_publisher":"http:\/\/facebook.com\/cloudbasesolutions","article_published_time":"2015-11-30T20:16:09+00:00","article_modified_time":"2016-01-11T15:24:06+00:00","og_image":[{"width":1152,"height":672,"url":"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png","type":"image\/png"}],"author":"Gabriel Samfira","twitter_card":"summary_large_image","twitter_creator":"@cloudbaseit","twitter_site":"@cloudbaseit","twitter_misc":{"Written by":"Gabriel Samfira","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/#article","isPartOf":{"@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/"},"author":{"name":"Gabriel Samfira","@id":"https:\/\/cloudbase.it\/#\/schema\/person\/9c948465f7f5ad60e7478f34c4d5bc0b"},"headline":"Hyper-Converged OpenStack on Windows Nano Server &#8211; Part 2","datePublished":"2015-11-30T20:16:09+00:00","dateModified":"2016-01-11T15:24:06+00:00","mainEntityOfPage":{"@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/"},"wordCount":2046,"commentCount":2,"publisher":{"@id":"https:\/\/cloudbase.it\/#organization"},"image":{"@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png","keywords":["hyper-converged","Hyper-V","juju","maas","nano","OpenStack","s2d"],"articleSection":{"0":"Hyper-V","1":"Juju","2":"MaaS","3":"Nano Server","4":"OpenStack","5":"Ubuntu","7":"Windows"},"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cloudbase.it\/hyper-c-part-2\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/","url":"https:\/\/cloudbase.it\/hyper-c-part-2\/","name":"Hyper-Converged OpenStack on Windows Nano Server - Part 2 - Cloudbase Solutions","isPartOf":{"@id":"https:\/\/cloudbase.it\/#website"},"primaryImageOfPage":{"@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage"},"image":{"@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png","datePublished":"2015-11-30T20:16:09+00:00","dateModified":"2016-01-11T15:24:06+00:00","breadcrumb":{"@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cloudbase.it\/hyper-c-part-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/#primaryimage","url":"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png","contentUrl":"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png","width":1152,"height":672},{"@type":"BreadcrumbList","@id":"https:\/\/cloudbase.it\/hyper-c-part-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cloudbase.it\/"},{"@type":"ListItem","position":2,"name":"Hyper-Converged OpenStack on Windows Nano Server &#8211; Part 2"}]},{"@type":"WebSite","@id":"https:\/\/cloudbase.it\/#website","url":"https:\/\/cloudbase.it\/","name":"Cloudbase Solutions","description":"Cloud Interoperability","publisher":{"@id":"https:\/\/cloudbase.it\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cloudbase.it\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/cloudbase.it\/#organization","name":"Cloudbase Solutions","url":"https:\/\/cloudbase.it\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cloudbase.it\/#\/schema\/logo\/image\/","url":"https:\/\/cloudbase.it\/wp-content\/uploads\/2017\/03\/CBSL-Logo-2017-Black.png","contentUrl":"https:\/\/cloudbase.it\/wp-content\/uploads\/2017\/03\/CBSL-Logo-2017-Black.png","width":583,"height":143,"caption":"Cloudbase Solutions"},"image":{"@id":"https:\/\/cloudbase.it\/#\/schema\/logo\/image\/"},"sameAs":["http:\/\/facebook.com\/cloudbasesolutions","https:\/\/x.com\/cloudbaseit","https:\/\/www.linkedin.com\/company-beta\/3139764","https:\/\/www.youtube.com\/channel\/UCBgH5RqPL4lgxA8gn3rIAFw"]},{"@type":"Person","@id":"https:\/\/cloudbase.it\/#\/schema\/person\/9c948465f7f5ad60e7478f34c4d5bc0b","name":"Gabriel Samfira","description":"Senior Cloud Engineer","sameAs":["https:\/\/cloudbase.it"]}]}},"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/cloudbase.it\/wp-content\/uploads\/2015\/11\/hyper-c-s2d-feat.png","_links":{"self":[{"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/posts\/34672"}],"collection":[{"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/comments?post=34672"}],"version-history":[{"count":93,"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/posts\/34672\/revisions"}],"predecessor-version":[{"id":34902,"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/posts\/34672\/revisions\/34902"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/media\/34842"}],"wp:attachment":[{"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/media?parent=34672"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/categories?post=34672"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudbase.it\/wp-json\/wp\/v2\/tags?post=34672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}