Once the basic WAP installation is completed, the various services need to be configured. In the post I will look at the VM Cloud Service configuration.
The VM Cloud Service requires some additional installations and configurations. The following three steps are required.
- Service Provider Foundation Installation and Configuration (SPF)
- System Center Virtual Machine Manager Installation and Configuration
- WAP VM Cloud Service Configuration
Service Provider Foundation Installation and Configuration
The Service Provider Foundation requires a SQL Server. So make sure you have one available where you can put the SPF database. Before you install SPF you need to enable some Windows features and you need to install two prerequisites. To enable the windows features use the following power shell command:
Install-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Http-Tracing, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Basic-Auth, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Scripting-Tools, NET-Framework-45-ASPNET, NET-WCF-HTTP-Activation45, ManagementOdata, WAS, WAS-Process-Model, WAS-Config-APIs
Then install the following software.
- ASP.NET MVC 4 (download here: http://www.asp.net/mvc/mvc4)
- WCF Data Services 5.0 for OData V3 (download here: http://www.microsoft.com/en-us/download/details.aspx?id=29306)
- System Center Virtual Machine Manager 2012 R2 Administrator Console
Additionally two users are required for the SPF installation:
- srv_spf_app (domain user account used for the SPF application pool)
- srv_spf (local user on SPF server used for the WAP connection)
Once this is all set up start with the SPF installation. SPF can be installed from the System Center 2012 R2 Orchestrator setup program. Select Service Provider Foundation under Service Management and follow the wizard. Use the srv_spf_app user account for all application pools. Apart from this, use the default values.
After the installation is completed, add the local srv_spf user account to the following local groups:
System Center Virtual Machine Manager Installation and Configuration
Now to the Virtual Machine Manager configuration. If you have not installed Virtual Machine Manager yet check out the Microsoft installation guild for that. For the configuration of VMM do the following:
- Add the domain srv_spf_app user account to the VMM administrator role using the VMM console.
- Create or have a VMM Cloud and do not select any of the Capability profile. Assign a logical network to the cloud. Assign a VMM Library to the cloud.
- Create or have a VM template. The OS image of the template must have the remote desktop connection enabled. The VM template must have a selected Guest OS Profile and no Capability profiles are selected.
WAP VM Cloud Service Configuration
The last thing to do is to configure the VM Cloud service in the Windows Azure Pack. Let’s start with the following:
- Log in to the WAP Admin portal
- In the VM Clouds Window select Register System Center Service Provider Foundation. Enter the URL of the SPF server, the local user account (srv_spf account on the SPF server) and it’s password.
- Once the SPF connection is successfully established, add the VMM server to the VM Cloud. In the Clouds tab click USE AN EXISTING VIRTUAL MACHINE CLOUD PROVIDER TO PROVISION VIRTUAL MACHINES and enter the name of the VMM server. After the connection is completed, you will see the VMM server and it’s clouds in the VM Cloud.
So far, we have configured the Windows Azure Pack to connect to the System Center Virtual Machine Manager. In the next post we will look at the creation of a Windows Azure Pack plan for VM Clouds. The plan will define what resources we what to provider to our WAP customers.
The Service Provider Foundation is a service that sits between the Windows Azure Pack and the System Center Virtual Machine Manager that allows the Windows Azure Pack to talk to Virtual Machine Manager. To make this happen we need a Service Provider Foundation service account that has administrator rights in Virtual Machine Manager and the Windows Azure Pack requires a local account on the SPF server to have access to the SPF service.