My experience installing Windows Azure Services for Windows Server using the PowerShell Deployment Toolkit (PDT)
If you are unfamiliar with PDT, please check out part 1 of my posts, and if you need additional information on setting up a home lab please read part 2 in my series. This post will expand on the deployment settings used on part 2.
Release 1005 of the PDT Workflow.xml adds support for installing Windows Azure Services for Windows Server. There are six roles added, all of which are required for Windows Azure Services. These roles can be installed on a single server or on multiple servers in any combination. The roles are:
- Windows Azure Services 2012 Database Server
- Windows Azure Services 2012 AdminAPI Server
- Windows Azure Services 2012 TenantAPI Server
- Windows Azure Services 2012 TenantPublicAPI Server
- Windows Azure Services 2012 AdminSite Server
- Windows Azure Services 2012 TenantSite Server
If Service Provider Foundation and Virtual Machine Manager are deployed with Windows Azure Services, the integration is automatically configured. I will add, if you have already deployed VMM and SPF using PDT, these integrations will be managed by the PDT perfectly.
If you download the current 1005 version of the workflow.xml, you will have to make a small modification to fix a slight bug in the validation for the VMM Integration. If you use the workflow.xml included with this article, I have made the modification for you.
In the validation for
Windows Azure Services 2012 System Center 2012 SP1 Virtual Machine Manager Integration, it incorrectly writes an out file called
WindowsAzureServices2012SystemCenter2012SP1VirtualMachineManagerClusterIntegration.role, notice that cluster was added, when there are not clusters in this implementation. I corrected this and everything showed green.
You will also need to update your variable.xml to include the new Windows Azure roles, this has also been done in the attached files.
In the <Roles> section of the variable.xml add the following:
<Role Name=”Windows Azure Services 2012 Database Server” Server=”SC18.contoso.com” Instance=”MSSQLSERVER”></Role>
<Role Name=”Windows Azure Services 2012 AdminAPI Server” Server=”SC18.contoso.com” ></Role>
<Role Name=”Windows Azure Services 2012 TenantAPI Server” Server=”SC18.contoso.com” ></Role>
<Role Name=”Windows Azure Services 2012 TenantPublicAPI Server” Server=”SC18.contoso.com” ></Role>
<Role Name=”Windows Azure Services 2012 AdminSite Server” Server=”SC18.contoso.com” ></Role>
<Role Name=”Windows Azure Services 2012 TenantSite Server” Server=”SC18.contoso.com” ></Role>
In the <SQL> section, add the following sql server definition:
<Server Server=”SC18.contoso.com” Version=”SQL Server 2012″></Server>
<Instance Server=”SC18.contoso.com” Instance=”MSSQLSERVER” Version=”SQL Server 2012″>
<Variable Name=”SQLAdmins” Value=”CONTOSO\SQLAdmins” />
In the VMs section increment the count of VM’s to 08:
Ran downloader.ps1 to download the Windows Azure Services and Prerequisites. Sixteen additional “installables” were downloaded and took only 3 minutes.
- VC2012 (x64 & x86)
Windows Azure Services Components
Set the memory of all my existing VM’s to 2048 Startup, 1024 Min and 4096 Max Memory and Snapped them.
Ran VMCreator.ps1 to create additional VM for Windows Azure Services roles. In a production environment, these roles should be split, as some roles should not be internet facing. Since all other VM’s already existed, only 1 additional VM was created, as was expected. It looks like these roles could be combined with Orchestrator and SPF, I’ll try this on another run, or separate the internet facing roles onto their own internet facing server and keep the internal roles on the Orchestrator/SPF role VM.
After SC18.contoso.com VM was built and domain joined I snapped it and then ran Installer.ps1.
Due to the bug in the workflow.xml, it was several runs before I discovered the issue. On the 3rd run, after fixing the workflow.xml, I made a successful run with all green status. The PDT will wait for all prerequisites, so it was easy to layer in the Windows Azure Services after using PDT to complete all the other System Center 2012 SP1 roles before it.
Here is a picture of the Admin Portal running on my own home lab private cloud. Time to get busy and add some services!
Once you have Windows Azure Services for Windows Server 2012 installed, please take a look at Cameron Fullers post on taking the next steps with WAS.