If you would like to read the other parts in this article series please go to:
- Deploying Windows Azure Pack (Part 1)
- Deploying Windows Azure Pack (Part 2)
- Deploying Windows Azure Pack (Part 3)
- Deploying Windows Azure Pack (Part 4)
- Deploying Windows Azure Pack (Part 6)
Updated deployment scenario
Thus far in our proof of concept (PoC) walkthrough of deploying Windows Azure Pack we have deployed a simple lab setup that consists of two physical servers running Windows Server 2012 R2. These two servers are on the same subnet, have Internet connectivity, both have the Hyper-V role installed on them, and are named HOST30 and HOST40 as shown in Figure 1 below.
Figure 1: PoC lab setup for VMM 2012 R2
HOST 30 is hosting the virtualized infrastructure for Contoso Ltd which currently consists of three virtual machines:
- DC-150 This virtual machine is the domain controller for the contoso.com domain.
- SCVMM01 This virtual machine is a member server running System Center Virtual Machine Manager 2012 R2.
- DB01 This virtual machine is a member server running Microsoft SQL Server 2012 SP1 and hosts the VMM database.
In addition to applying all updates to these servers, the following configuration tasks have been performed in VMM to prepare the environment for deploying Windows Azure Pack:
- VMM storage and the VMM library have been configured.
- Host groups have been created and HOST40 has been added as a managed host.
- Logical networks, IP address pools, network sites, and virtual machine networks have been created.
- A new cloud has also been created but as Figure 2 shows this cloud does not yet have any virtual machines running in it.
Figure 2: Host groups and clouds in VMM.
Since we’re going to perform an express deployment of Windows Azure Pack, we’ll need to add one more virtual machine to our Contoso infrastructure. This new virtual machine is shown in Figure 3 and is named WAP01 and it has the minimum requirement of 8 GB of RAM allocated to it from HOST30.
Figure 3: Windows Azure Pack will be installed on virtual machine WAP01.
Installing Service Provider Foundation
Service Provider Foundation is part of System Center 2012 R2 Orchestrator and exposes a web service to VMM that enables service providers (either hosters or enterprises that want to provision services like hosters) to implement multi-tenant self-service portals for Infrastructure as a Service (IaaS) scenarios.
Service Provider Foundation must be installed first before you can install Windows Azure Pack in your environment, and since we’re doing an Express deployment we can install Service Provider Foundation on server WAP01 shown in Figure 3 above. The procedure for installing Service Provider Foundation is as follows:
- Start by installing the VMM console on your server. You’ll need your VMM installation media (ISO file) to do this. Launch the Setup.exe and select the option for installing only the VMM console as shown in Figure 4:
Figure 4: Installing the VMM console on WAP01 to prepare for installing Service Provider Foundation.
Once installation of the VMM console is complete, verify that you can use it to connect to your VMM management server which is SCVMM01 in this example.
- Open the Add Roles and Features Wizard from Server Manager on WAP01 and install the following:
- On the Server Roles page, select the Web Server (IIS) role with its associated features.
- On the Features page, under .NET Framework 4.5 Features, under WCF Services, select HTTP Activation and its associated features.
- Also on the Features page, select Management OData IIS Extension and its associated features.
- On the Web Server Role (IIS) Role Services page, add the following role services:
- Under Management tools, select IIS Management Scripts and Tools
- Under Security, select Basic Authentication and Windows Authentication
- Install WCF Data Services 5.0 which enables the creation and consumption of data services for the Web based on Open Data Protocol (OData) version 3 to facilitate data access and change via standard HTTP verbs. You can download this from the Microsoft Download Center.
- Install ASP.NET MVC 4 which provides a Model-View-Controller (MVC) framework for developing Web applications using Visual Studio. You can download this from the Microsoft Download Center.
- Go to Windows Update (actually Microsoft Update since you’ve installed VMM) and apply any necessary software updates for the components you just installed.
- Create a service account (a domain user account) and some security groups for Service Provider Foundation. The security groups are needed to control permissions on the virtual directories created by IIS for Service Provider Foundation. The service account and groups are shown later in this walkthrough.
- Install a web server certificate on IIS to enable Service Provider Foundation to use SSL for secure communications via the OData web service. This can be a certificate you purchased from a public certification authority, a certificate generated by your enterprise certification authority, or even a self-signed certificate for testing purposes. We’ll use a self-signed certificate and will generate one by using the Server Certificates item in the IIS section of the center pane of IIS Manager as shown in Figure 5:
Figure 5: Installing a server certificate using IIS Manager.
After opening Server Certificates, you click the Create Self-Signed Certificate option in the Actions pane and specify a friendly name for your certificate such as wap01.contoso.com in this example. Then you can export the certificate from IIS Manager and use the MMC Certificates snap-in to add the self-signed certificate to the Certificates folder under Trusted Root Certification Authorities in the local computer store for testing purposes.
- At this point you are now ready to install Service Provider Foundation. You will you need your System Center 2012 R2 Orchestrator installation media (ISO file) for this purpose. Begin by launching Setup.exe to display the initial splash screen:
Figure 6: Step 1 of installing Service Provider Foundation.
Click Service Provider Foundation under Standalone Installation on the above screen. This opens the splash screen for Service Provider Foundation:
Figure 7: Step 2 of installing Service Provider Foundation.
Click Install to start the installation. Make sure that the prerequisites check passes in everything:
Figure 8: Step 3 of installing Service Provider Foundation.
On the first Configuration page, specify DB01 as the name of your database server. You might need to log on to DB01 at this point and add an inbound rule to allow traffic on TCP port 1433 as this will be needed for connecting to Service Provider Foundation on WAP01.
Figure 9: Step 4 of installing Service Provider Foundation.
On the next page select the self-signed certificate you previously generated:
Figure 10: Step 5 of installing Service Provider Foundation.
On the next page, specify the security group you created for the Admin web service and also the service account you created for Service Provider Foundation:
Figure 11: Step 6 of installing Service Provider Foundation.
On the next page, specify the security group you created for the Provider web service and also the service account you created for Service Provider Foundation:
Figure 12: Step 7 of installing Service Provider Foundation.
On the next page, specify the security group you created for the VMM web service and also the service account you created for Service Provider Foundation:
Figure 13: Step 8 of installing Service Provider Foundation.
On the next page, specify the security group you created for the Usage web service and also the service account you created for Service Provider Foundation:
Figure 14: Step 9 of installing Service Provider Foundation.
Finish the wizard to install Service Provider Foundation on WAP01.
Figure 15: Service Provider Foundation has been installed on WAP01.
- We’re not quite done yet. Add the Service Provider Foundation service account to the Service Provider Foundation security groups so it becomes a member of these groups.
- Open the VMM Console on WAP01 and select the Settings workspace at the bottom right. Then expand Security in the console tree and select User Roles to display the Administrator role:
Figure 16: Select the Administrator user role in VMM.
Double-click on the Administrator user role and select the Members tab, then click Add and add the Service Provider Foundation service account you created to the Administrator user role for VMM:
Figure 17: Adding the Service Provider Foundation service account to the Administrator user role for VMM
- Log on to DB01 and open SQL Server Management Studio. Expand Logins under Security and right-click on the Service Provider Foundation service account and select Properties:
Figure 18: Configuring the Service Provider Foundation service account using SQL Server Management Studio.
Select the Server Roles page and then select the checkbox for sysadmin to assign the Sysadmin role for SQL Server to the service account:
Figure 19: Assigning the Sysadmin role for SQL Server to the Service Provider Foundation service account.
You’ve now completed installing Service Provider Foundation and are ready for the final step of installing Windows Azure Pack. We’ll cover that in the last article of this series.
If you would like to read the other parts in this article series please go to: