Today, I am going to kick off an interesting series of blog posts on how to build own Private Cloud using Windows Azure Pack (WAP).
The series will be divided into the following five posts:
[Part-1]Private Cloud: Introduction and installation of pre-requisites
[Part-2]Private Cloud: Configure SCVMM and SPF
[Part-3]Private Cloud: Install and Configure WAP
[Part-4]Private Cloud: Demo of provisioning VM and SQL DB using Tenant portal.
[Part-5]Private Cloud: Some common issues and troubleshooting tips.
Let’s have a quick introduction to Windows Azure Pack (WAP) before you proceed further.
What is Windows Azure Pack (WAP)
Windows Azure Pack provides a multi-tenant, self-service cloud that works on top of your existing software and hardware investments. Built on the familiar foundation of Windows Server and System Center, Windows Azure Pack offers a flexible and familiar solution that your business can take advantage of, to deliver self-service provisioning and management of infrastructure — Infrastructure as a Service (IaaS), and application services — Platform as a Service (PaaS), such as Web Sites and Virtual Machines.
The Windows Azure Pack includes the Customer Portal, Admin Portal, and customer and admin services built on Windows Server and System Center.
Note: In this series, we will perform an express installation of WAP.
Hardware & Software Requirements
1. Physical Machine: Physical server with Hyper-V enabled.
Operating System: Windows Server 2008 or higher.
Memory: 32 GB
Storage: 1 TB
2. Virtual Machine (Virtual Machine to install all the require software)
Operating System: Windows Server 2012 R2
Memory: 8 GB
Storage: 512 GB
i. Windows Azure Pack (WAP) – It’s a collection of IIS websites and configuration databases that utilize a Virtual Machine Manager (VMM) through the Service Provider Foundation (SPF)
ii. SQL Server – This provides configuration databases for multiple components, but this can still be used to provide Database as a Service (DaaS)
iii. System Center SPF – Service to provide interface for VMM that is used by WAP
iv. System Center Virtual Machine Manager (SCVMM) – Service to automate configuration, management, and operation of a group of HV nodes
Installation of pre-requisite software
Install the following pre-requisite software. Keep in mind, services created by each of these require a service account that is a local administrator on the server where we want to install these software.
a. SQL Server
b. System Center Virtual Machine Manager (SCVMM)
c. Service Provider foundation (SPF)
Note: I am not going to cover the step-by-step instruction for installation of above software as they are pretty straight forward. I am going to mention a few important things to keep in mind while installing above ones. Configuration SCVMM and SPF will be covered, in detail, in rest of the series.
SQL Server Instance
SQL Server instance should be installed in the same domain with Mixed mode authentication (or you may configure it post-installation). In my case, I have installed SQL Server instance called myvmserver\AZUREPACK with mixed authentication
System Center Virtual machine manager (SCVMM) is the base of this cloud. It provides a capability to automate, manage and operation of multiple VMs on a host.
System Center requires the following pre-requisites:
i. Deployment Tools and Windows preinstallation Environment from Windows Assessment and Deployment Kit
ii. WCF Data Services 5.0
iii. ASP.Net MVC 4
iv. WCF Data Services 5.0
I followed this excellent blog post to install SCVMM http://blogs.technet.com/b/kevinholman/archive/2013/10/18/scvmm-2012-r2-quickstart-deployment-guide.aspx
Here is a screenshot from Database Configuration of SCVMM installation wizard.
Service provider foundation (SPF) is a very critical component in deploying WAP. SPF provides an interface to WAP using which it can interact with the VMM cluster, including provisioning, managing, and reporting on the clouds utilization. With the help of SPF, WAP provides an infrastructure allowing for customized and multi-tenant solutions by utilizing the underlying VMM.
SPF is a part of Orchestrator. Follow the instructions from this TechNet article to install SPF. https://technet.microsoft.com/en-us/library/dn266007.aspx
Here are couple of screenshots from my installation wizard.
Note: On the Configuration page, make sure you give the same SQL Server name and port number which you had provided during SCVMM setup.
Similar to SCVMM, you need to specify a different database name during SPF configuration to create necessary objects.
And there we go, we have all the pre-requisite software installed for our private cloud.
In the next blog post of this series, we are going to learn how to configure SCVMM and SPF.
Stay tuned for the next post on [Part-2]Private Cloud: Configure SCVMM and SPF
Happy building Private Cloud!