windows azure pack - installing and configuring · windows azure pack – infrastructure as a...

Windows Azure Pack – Infrastructure as a Service (IaaS) Setup and Configuration

Windows Server

2012 R2

Hands-on lab

Windows System Center 2012 R2 Virtual Machine Manager, in

conjunction with the Service Provide Framework (SPF),

provides the underlying Infrastructure as a Service (IaaS)

capabilities available in Windows Azure Pack, In this lab, you

will learn how to setup and configure Infrastructure as a

Service in Windows Azure Pack (WAP). You will first setup and

configure objects in VMM that are required to enable IaaS in

WAP. You will then set up and configure IaaS in WAP so that

users of the WAP tenant portal can deploy a flexible

infrastructure that is based on the objects that configured and

defined both in VMM and in the WAP administration portal.

Produced by HynesITe, Inc

Version 1.0

1/7/2014

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial

release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in

this document. Information in this document, including URL and other Internet Web site references, is subject to change without

notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the

companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein

are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or

event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without

limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or

transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without

the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter

in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document

does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Copyright 2014 © Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Hyper-V, Internet Explorer, SQL Server, System Center, Windows, Windows Azure, and Windows Server

2012 are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.


Lab created by HynesITe, Inc. For questions or comments, send an e-mail message to [email protected] Page | 3

Introduction

Estimated time to complete this lab

60 minutes

Objectives

After completing this lab, you will be able to:

Install the Windows Azure Pack roles.

Perform Windows Azure Pack initial configuration.

Create cloud objects including tenants and users.

Create subscriptions and create cloud resources.

Prerequisites

Before working on this lab, you must have:

An understanding of cloud technologies especially Windows Azure.

An understanding of basic database and website creation concepts.

Overview of the lab

Windows System Center 2012 R2 Virtual Machine Manager, in conjunction with the Service Provide

Framework (SPF), provides the underlying Infrastructure as a Service (IaaS) capabilities available in

Windows Azure Pack, In this lab, you will learn how to setup and configure Infrastructure as a Service in

Windows Azure Pack (WAP). You will first setup and configure objects in VMM that are required to enable

IaaS in WAP. You will then set up and configure IaaS in WAP so that users of the WAP tenant portal can

deploy a flexible infrastructure that is based on the objects that configured and defined both in VMM and

in the WAP administration portal.

Virtual machine technology

This lab is completed using virtual machines that run on Windows Server 2012 Hyper-V technology. To

log on to the virtual machines, press CTRL+ALT+END and enter your logon credentials.

Computers in this lab

This lab uses computers as described in the following table. Before you begin the lab, you must ensure

that the virtual machines are started and then log on to the computers.

Virtual Machine Role

WAPSQL SQL Server database and Active Directory domain controller for WAP.Local

domain

WAPPortal Express installation of Windows Azure Pack Portal and Web App Gallery.

Configured as an access point for service and tenant admin websites.

WAPSMA Service Management Automation and Service Bus

WAPSPF Service Provider Foundation

WAPVMM System Center Virtual Machine Manager 2012 R2 server

WAPHVS Hyper-V server (virtualized), file server, and MySQL server

mailto:[email protected]



Virtual Machine Role

SitesCN Web Sites Controller

SitesFE Web Sites Front End

SitesMN Web Sites Management

SitesPB Web Sites Publisher

SitesWWR Web Sites Reserved

SitesWWS Web Sites Shared

All user accounts in this lab use the password Passw0rd!

Navigation

Windows Azure Pack uses icons instead of labeled buttons for many tasks. While most are obvious, this

document refers to them by action names. Below is a quick reference of action names and corresponding

icons.

Done or Finished – Check Mark

Next – Right Arrow

Previous – Left Arrow

Close or Exit – X

Note regarding pre-release software

Portions of this lab may include software that is not yet released, and as such may still contain active or

known issues. While every effort has been made to ensure this lab functions as written, unknown or

unanticipated results may be encountered as a result of using pre-release software.

Note regarding user account control

Some steps in this lab may be subject to user account control. User account control is a technology which

provides additional security to computers by requesting that users confirm actions that require

administrative rights. Tasks that generate a user account control confirmation are denoted using a shield

icon. If you encounter a shield icon, confirm your action by selecting the appropriate button in the dialog

box that is presented.

Note on activation

The virtual machines for these labs may have been built by using software that has not been activated.

This is by design in the lab to prevent the redistribution of activated software. The unactivated state of

software has been taken into account in the design of the lab. Consequently, the lab is in no way affected

by this state. For operating systems other than Windows 8, please press Cancel or Close if prompted by an

activation dialog box. If you are prompted by an Activate screen for Windows 8.1, press the Windows key

to display the Start screen.




Exercise 1: Understanding Windows Azure Pack

Components and Architecture

In this exercise, you will not perform any tasks. You will be provided with an overview of the Windows

Azure Pack and how it is deployed in this lab environment. Understanding this environment and

deployment is the key to understanding the steps preformed in the lab exercises.

Important: If you already have a good understanding of the Windows Azure Pack and this environment,

proceed to Exercise 2.

This lab initially configures the following components:

Web Sites

Infrastructure as a Service (IaaS)

Service Bus

Automation

Databases

Windows Azure Pack components: Web Sites

The Windows Azure Pack: Web Sites service uses a minimum of 6 server roles: Controller, Management

Server, Front End, Web Worker, File Server, and Publisher. Also required is a server running SQL Server for

the Web Sites runtime database. These roles are separate from, and in addition to, the servers that form

an express or distributed installation of the Service Management API. The roles can be installed on

physical servers or virtual machines.

1. Web Sites Controller - The controller provisions and manages the other Web Sites roles. This

role is installed first. This role is installed on the SitesCN virtual machine.

2. Management Server - This server exposes a REST endpoint that handles management traffic to

the Windows Azure Pack Web Sites Management API. This role is installed on the SitesMN virtual

machine.

3. Web Workers - These are web servers that process client web requests. Web workers are either

Shared or Reserved (at minimum, one of each is required) to provide differentiated levels of

service to customers. Reserved workers are categorized into small, medium, and large sizes. The

SitesWWR is the reserved worker server, and SitesWWS is the shared worker server.

Important: Because web workers run customer code, they represent a potential risk to the Web Sites

infrastructure. After installation, you should configure IP filtering from the Management Portal for

Administrators to reduce the risk. For more information, see Configure IP filtering.




4. Front End - Accepts web requests from clients, routes requests to web workers, and returns web

worker responses to clients. Front end servers are responsible for load balancing and SSL

termination. This role is provided by the SitesFE server.

5. File Server - Provides file services for hosting web site content. The file server houses all of the

application files for every web site that runs on the Web Sites cloud. The file server in this

environment is WAPHVS. This is a general purpose server that provides several roles.

6. Publisher - Provides content publishing to the Web Sites farm for FTP clients, Visual Studio, and

WebMatrix through the Web Deploy and FTP protocols. The publishing server is SitesPB.

In addition, up to three database servers are required. Note that in this environment, all SQL Server

databases are located on WAPSQL. There is also a MySQL database instance on WAPHVS.

1. Service Management API database - The core installation of the Windows Azure Pack Service

Management API uses a SQL Server server to store its configuration data. This database is

configured as part of the overall Windows Azure Pack installation and is not specific to web sites.

2. Web Sites runtime database - Prior to installing Windows Azure Pack: Web Sites, you will need

to prepare a SQL Server server to contain the runtime database that Web Sites uses for its

operations.

3. Application databases - If your usage scenario includes providing database functionality for the

tenant web sites, you will need to install separate SQL server and/or MySQL databases to provide

this service.

Windows Azure Pack components: Virtual Machines

Virtual Machines leverage several components to provide tenant based access to virtual machines hosted

in a System Center Virtual Machine Manager (VMM) infrastructure.

1. Service Provider Foundation - Service Provider Foundation is provided with

System Center 2012 R2 Orchestrator (and System Center 2012 SP1 - Orchestrator). Service

Provider Foundation exposes an extensible OData web service that interacts with Virtual Machine

Manager (VMM). This enables service providers and hosters to design and implement multi-

tenant self-service portals that integrate IaaS capabilities available on System Center 2012 R2.

Service Provider Foundation is installed on WAPSPF.

2. Virtual Machine Manager – VMM-specific objects such as clouds, virtual machine templates,

hardware profiles, networks, and gallery items are exposed as artifacts which can be used to




create virtual machine services. In this environment VMM is deployed on WAPVMM and the VMM

environment has been populated with objects.

Windows Azure Pack components: Databases

You can add one or more Microsoft SQL Server or MySQL server instances for tenants to deploy and use.

Tenants also use these databases with the Web Sites service.

Microsoft SQL Server databases can range from simple stand-alone databases to highly available, always-

on databases. You should rely on your SQL Server database administrator to install and configure SQL

Server for you, ensuing that both Windows and SQL Server authentication are available.

In this environment, SQL Server is deployed on WAPSQL. MySQL is deployed on WAPHVS. Both are very

simple installations. The complexity of the SQL implementation is hidden by Windows Azure Pack, so you

manage all types the same way, regardless of the underlying infrastructure.

Windows Azure Pack components: Service Bus

Service Bus for Windows Server is a set of installable components that provides the messaging capabilities

of Windows Azure Service Bus on Windows Server. Service Bus for Windows Server enables you to build,

test, and run loosely-coupled, message-driven applications in self-managed environments and on

developer computers.

The purpose of Service Bus for Windows Server is to provide similar capabilities across Windows Azure

and Windows Server, and to enable flexibility in developing and deploying applications. It is built on the

same architecture as the Service Bus cloud service and provides scale and resiliency capabilities. The

programming model, Visual Studio support, and APIs exposed for developing applications are symmetric

to that for the cloud service making it easier to develop applications for either, and switch between the

two. Going forward, the experience for managing entities on the Windows Azure Management Portal will

be consistent across the on-premises and cloud versions.

Service Bus is installed on WAPSPF.

Windows Azure Pack components: Service Management Automation

Service Management Automation is a workflow management solution for Windows Azure Pack for

Windows Server. It enables you to automate the creation, monitoring, and deployment of resources in

your environment.

Service Management Automation can be used to leverage existing System Center infrastructure and

automation, including System Center Orchestrator runbooks.

Service Management Automation is installed on WAPSMA.




Exercise 2: Configure System Center 2012 R2 Virtual

Machine Manager

In this exercise, you will set up the objects in Virtual Machine Manager that comprise a set of the required

components to implement and deploy IaaS in Windows Azure Pack. The focus of this exercise is from the

point of view of a Service Admin who needs to ensure that the required objects are configured and

available in a pre-existing deployment of VMM that already has an underlying storage and VMM logical

network configuration. In the case of the lab environment, we are using a simple local storage

configuration, although for WAP, SMB or other-network based storage can also be used. Also, the lab

environment contains a single logical network.

You will use this existing configuration as the starting point to configure an internal network for Network

Virtualization and a public network. You will then create two clouds that will offer two different levels of

resources to WAP tenant portal users, the consumers of IaaS. Finally, you will set up and configure the

reusable objects and artifacts that will be consumed by the tenant portal users. These include VMM library

objects, such as hardware profiles, Virtual Machine Templates. You will also set up Virtual Machine Role

templates for role-based IaaS VMs

Create and configure networks for WAP portal users

In this task, you will create and configure Virtual Machine networks that will be made available to WAP

portal users. You will first create a private isolated VM network and then create a public VM network.

Begin this task logged on to WAPVMM as WAP\Administrator using the password Passw0rd!

1. On the desktop of WAPVMM, double-click Virtual Machine Manager.

2. In the Connect to Server dialog box, click Connect.

3. In the navigation pane, click the VMs and Services workspace.

4. Under VMs and Services, click VM Networks.

5. Right-click VM Networks, and then click Create VM Network.

6. On the Specify a name and description for the VM network page, in Name, type Tenant WAP

Private Network.

NOTE: You are going to bind the VM network to the pre-existing logical network, Tenant Virtual

Machines, that was pre-configured as part of the lab set up. Logical networks are an abstraction of the

underlying physical network and are used to organize and simplify the network assignments for hosts,

virtual machines, and services. Virtual machines connect to Virtual Machine Networks, which are

assigned to Logical Networks.

7. In description, type Isolated private VM network for WAP IaaS, and then click Next.

8. On the Select the isolation for this VM network page, ensure Isolate using Hyper-V network

virtualization is selected, and click Next.




NOTE: Isolation allows multiple tenants to share the same logical network without being aware of each

other

9. On the Specify VM Subnets page, click Add.

10. In Name, type Tenant WAP Private Subnet.

11. In Subnet, type 192.168.1.0/24, and click Next.

12. On the Connectivity page, click Next.

13. On the Confirm the settings page, click Finish.

NOTE: The Jobs window will appear.

14. Wait for the Jobs to complete and then close the Jobs window.

15. In the Virtual Machine Manager console, right-click Tenant WAP Private Network, and then click

Create IP Pool.

NOTE: IP address pools provide the ability to assign IP address to bare metal hosts that are converted

to Hyper-V hosts and to virtual machines that are created within the VMM environment.

16. On Specify the IP address pool name and VM subnet page, in Name, type Tenant WAP Private

IP Pool, and click Next.

17. On the IP address range page, in Starting IP address, enter 192.168.1.100.

18. In Ending IP address, enter 192.168.1.150, and click Next.

19. Click Next on the remaining pages.


21. When the job completes, close the Jobs window.

22. In the VMs and Services workspace, right-click VM Networks and click Create VM Network.

23. On the Specify a name and description for the VM Network, in Name, type Tenant WAP Public

Network, and click Next.

24. On the Select the isolation for this VM network page, select No isolation, and click Next.

NOTE: This means that the VM network is the same as the logical network on which it is configured.


26. Wait for the job to complete, and then close the Jobs window.

Create and configure clouds

In System Center 2012 R2 Virtual Machine Manager, clouds provide the means to organize delegated

resources that can be scoped to meet administrative or business requirements. These resources can be

provided to consumers as service, with available resources scoped to meet their present needs. Because




cloud resources can be enlarged or shrunk at any time, they can also meet future needs, as demands

change over time.

In this task, you will configure two clouds: a premium cloud that provides access to resources without

limitations and a standard cloud that limits resource availability.


1. In the VMM console, in the VMs and Services workspace, right-click Clouds, and then click Create

Cloud.

2. On the Specify a name and optional description for the private cloud page, in Name, type

Premium Cloud, and then click Next.

3. On the Select the resources for this cloud, check All Hosts, and then click Next.

4. On the Select the logical networks for this cloud, check Tenant Virtual Machines, and click Next.

5. On the Add load balancers for this cloud page, check Microsoft Network Load Balancing (NLB),

and click Next.

6. On the Select the VIP templates for this cloud page, click Next.

7. On the Port Classifications page, check Tenant Port Classification, and click Next.

NOTE: This classification was configured as part of the lab set up.

8. On the Storage page, check Local Storage, and click Next.

NOTE: In this lab environment, you are using the pre-configured local storage. However, SMB or other

network-based storage can be used.

9. On the Specify stored VM path and read-only library shares page, click Add.

10. In the Add Library Shares dialog box, check MSSCVMM Library, and click OK.

11. Click Next.

12. On the Set the capacity for this cloud page, leave the default settings selected, and click Next.

13. On the Add virtual machines capability profiles for this cloud page, click Next without making any

selections.


15. Wait for the job to complete, and then close the Jobs window.

16. In the VMM console, in the VMs and Services workspace, right-click Clouds, and then click Create

Cloud.

17. On the Specify a name and optional description for the private cloud page, in Name, type

Standard Cloud, and then click Next.

NOTE: In the next steps, you are creating a second cloud that limits the resources available to self-

service users.




18. On the Select the resources for this cloud, check All Hosts, and then click Next.

19. On the Select the logical networks for this cloud, check Tenant Virtual Machines, and click Next.

20. On the Add load balancers for this cloud page, check Microsoft Network Load Balancing (NLB),

and click Next.

21. On the Select the VIP templates for this cloud page, click Next.

22. On the Port Classifications page, check Tenant Port Classification, and click Next.

23. On the Storage page, check Local Storage, and click Next.

24. On the Specify stored VM path and read-only library shares page, click Add.

25. In the Add Library Shares dialog box, check MSSCVMM Library, and click OK.

26. Click Next.

27. On the Set the capacity for this cloud page, clear the Virtual CPUs check box, and in Assigned

Capacity, enter 500.

28. Repeat the previous step for Memory (GB), Storage (GB) and Virtual machines categories,

modifying the Assigned Capacity as follows:

Memory (GB): 2000

Storage (GB): 2000

Virtual machines: 250

29. Click Next.

30. On the Add virtual machines capability profiles for this cloud page, click Next without making any

selections.


32. When the job completes, click the Jobs windows.

Create and configure hardware profile

In System Center 2012 R2 Virtual Machine manager, hardware profiles are reusable objects that are stored

in a VMM library and provide the hardware settings that we want applied to guest VMs that are deployed

using the profile. Profiles also simplify the creation of templates. In this task, you examine create an

additional hardware profile that will be used in a later lab exercise.


1. In the VMM console, select the Library workspace.

NOTE: The VMM library is a catalog of reusable file-based resources, such as VHDs, scripts, and

application package that reside on library servers and non-filed base resources such as VM templates,

service templates, and hardware profiles that reside in the VMM database.




2. In the Library workspace, expand Profiles, and then click Hardware Profiles.

NOTE: In the details pane, you see three previously configured hardware profiles.

3. Right-click Hardware Profiles, and Create Hardware Profile.

4. In the Hardware Profile dialog box, in Name, type X-Large (8 Core, 32 GB Memory).

5. Click the Hardware Profile tab.

6. In the Hardware Profile tab, click Processor, and then in Number of processors, enter 8.

7. Click Memory, and in Virtual machine memory, enter 32768.

8. In the New Hardware Profile dialog box, click OK.

Create and configure a virtual machine template

In System Center 2012 R2 Virtual Machine manager, a virtual machine template provides a means for

implementing virtual machines that have consistent settings and configuration across deployments.

Templates can also be used to restrict configurations of virtual machines to self-service users. In this task,

you will create a VM template that will be used for deploying a standalone virtual machine.



2. In the Library workspace, under Templates, click VM Templates.

NOTE: In the details pane, you see three previously configured VM templates.

3. Right-click VM Templates, and then click Create VM Template.

4. On the Select a source for the new VM template page, click Browse.

5. In the Select VM Template Source dialog box, select WS 2012 R2.vhd, and click OK.

6. Back on the Select a source for the new VM template page, click Next.

7. On the VM Template Identity page, in Name, type Windows Server 2012 R2 Datacenter, and

click Next.

8. On the Configure Hardware page, accept the default settings and click Next.

NOTE: This page provides the option to use a pre-configured hardware profile.

9. On the Configure Operating System page, ensure that Windows Server 2012 R2 Datacenter is

selected, and then click Next.

10. On the Application configuration page, check Windows Server 2012 R2 Datacenter, and then

click Next.

IMPORTANT: You may have to scroll down to see the check box.

11. On the SQL Server configuration page, click Next.




12. On the Before you create the new VM template, review the settings that you chose page, click

Create.

13. When the jobs complete, close the Jobs window.

Create virtual machine role templates using VMM and Windows Azure Pack

Virtual machine role templates allow WAP portal users (tenants) to create virtual machines that have

specific operating systems and applications pre-installed and configured in a manner that is reproducible

and scalable. Virtual machine role templates cannot be created solely with VMM. To create a virtual

machine role template, you must use System Center 2012 R2 with Windows Azure Pack.

To create a virtual machine role template, it is necessary to import a gallery item into VMM and WAP.

In this task, you will view the relevant settings of a pre-existing SQL virtual machine role that contains a

sysprepped image of Windows Server 2012 R2 and SQL Server 2012. You will then prepare and install the

virtual machine role template into VMM.



2. In the Library workspace, expand Library Servers/WAPVMM.WAP.local/MSSCVMMLibrary,

and click VHDs.

NOTE: Among the file-based resources stored on the Library Server are VHD files.

3. In the details pane, double-click SQL 2012-WS 2012 R2.vhd.

4. In the SQL2012-WS 2012 R2.vhd Properties dialog box, examine the settings, paying particular

attention to the Family and Release, and Operating System values.

NOTE: The properties of the VHD in the library must include values in these fields as a requirement for

implementing virtual machine role templates.

NOTE: The values in these fields must match specific formats. For example, Version must be in this

form: n.n.n.n.

5. Click OK.

6. On the ribbon of the VMM console, click the Home tab.

7. On the ribbon, click PowerShell.

8. At the Windows PowerShell prompt, type the following command and then press ENTER.

↪ Get-SCVirtualHardDisk –Name ‘SQL 2012-WS 2012 R2.vhd’ | Select Name,

FamilyName, OperatingSystem, Version, Tag

NOTE: In WAP, tags are used to provide a list of VHDs that could potentially be used for a given

application. That is, they can be used for loosely coupling applications to various operating systems. For




example, SQL 2012 can run on more than one OS. Tags, among other things, allow tenants to select an

OS for an application that meets their licensing or other requirements, for example, Standard vs

Datacenter SKU.

9. On the taskbar, right-click the PowerShell icon, and then click Windows PowerShell ISE.

10. Click File, and then click Open.

11. In the Open dialog box, select Gallery Import, and then click Open.

12. In Windows PowerShell ISE, locate and identify the path in the second line of the script.

13. In the second line of the script, replace the string “My-VMRole-Pkg\MyVMRole.resextpkg”, with

SQL_Server_2012_VMRole_Pkg\SQLServer2012.resextpkg.

14. Press F5.

15. In the Windows PowerShell ISE dialog box, click OK to acknowledge the script will be saved.

NOTE: A gallery item contains three files: a readme file, a resource extension package that is imported

into VMM, and a resource definition package that needs to be imported in WAP. Gallery items are

downloadable from Microsoft and can be customized to meet requirements. In this step, we are

importing the resource extension package into VMM.




Exercise 3: Configure Windows Azure Pack for IaaS

Integration of Windows Azure Pack with VMM occurs via the Service Provider Foundation (SPF), as shown

in the following high-level architectural diagram.

In this exercise, you will complete the set up and configuration of IaaS. You will use the WAP admin portal

to add a Virtual Machine Manager provider to enable integration of VMM with WAP via SPF. You will then

import the resource definition package from the Gallery Item into WAP. Finally, you will make the Gallery

Item available to the tenant to deploy as a VM role by scoping the Gallery Item to a plan that has an

associated subscription.

Add a new VMM provider

In this task, you will add a new VMM provider to enable integration of VMM with WAP.

Begin this task on WAPPortal logged on as WAP\Administrator using the password Passw0rd!

1. On the desktop, double-click WAP-Admin.

2. Click Continue to this website (not recommended).

NOTE: You see this error because the lab environment is using self-signed certificates.

NOTE: After a few moments, you will be prompted with another message about a certificate error.


NOTE: A Windows Security dialog box appears.

4. In the Windows Security dialog box, enter Administrator for the user name and Passw0rd! for

the password, and click OK.

NOTE: Wait until all the labels on the left-hand navigation resolve.

NOTE: You may see an alert on the Automation node. You can safely ignore this alert. It will not have an

effect on the lab exercise.

5. In the left-hand navigation, click VM CLOUDS.




6. Under vm clouds, click the small cloud icon to the left of CLOUDS.

NOTE: The Service Provider Foundation is currently registered.

7. Click CLOUDS.

8. Click USE AN EXISTING VIRTUAL CLOUD PROVIDER TO PROVISION VIRTUAL MACHINES.

9. In VIRTUAL MACHINE MANAGER SERVER FQDN, type wapvmm.wap.local.

NOTE: The REMOTE DESKTOP GATEWAY FQDN (OPTIONAL) field allows you to enter the fqdn of a

remote desktop gateway. This field is one of items you configure to enable remote console access for

tenants to the VMs they provision, regardless of whether the VMs are RDP capable. Tenants can

establish a console session to Linux VMs or even VMs that do not have an operation system installed.

The lab environment is not configured to demonstrate this functionality.

10. Click Done (check mark).

NOTE: After a few moments, WAPVMM.WAP.LOCAL appears in the list of cloud providers.

11. Expand WAPVMM.WAP.LOCAL.

NOTE: The clouds you configured in Exercise 2 are visible.

12. Click Standard Cloud.

NOTE: The resulting page provides an overview of the usage of the resources available in the cloud.

13. Click Back (left arrow).

14. Click VIRTUAL MACHINES.

NOTE: No virtual machines have been provisioned for tenants, and an empty list is displayed. This is

expected.

15. Click NETWORKS.

NOTE: No virtual networks have been provisioned for tenants, and an empty list is displayed. This is

expected.

16. Click GALLERY.

NOTE: A catalog of pre-installed Gallery Items is displayed. Any of these Gallery Items can be made

scoped to a plan with an attached subscription.

17. Leave the Admin Portal open for the next task.

Import a Gallery Item

In this task, you will import a Gallery Item and then make it public so that it can be made available to WAP

plans.





1. Still on the vm clouds page you left open in the last task, click GALLERY, if it is not already

selected.

2. On the portal taskbar, click IMPORT.

NOTE: You will be importing a resource definition file into WAP. In the previous exercise, you imported

the associated resource extension package file into VMM.

3. Click BROWSE FOR FILE.

4. In the Choose File to Upload dialog box, navigate to

\\wapvmm\c$\GalleryResources\SQL_Server_2012_VMRole_Pkg.

5. Select SQLServer2012Workgroup.resdefpkg, and click Open.

6. On the Upload gallery item resource definition file page, click Done (check mark).

NOTE: It will take a few moments to import the definition. Once the resource definition is imported, you

will see the new Gallery Item, Microsoft SQL Server 2012 - Workgroup.

7. In GALLERY, click Microsoft SQL Server 2012 – Workgroup.

NOTE: The information on the DASHBOARD included the version number. WAP supports versioning.

8. On the portal taskbar, click MAKE PUBLIC, and then click Yes (check mark).

NOTE: To make a plan available to a subscription, it needs to be made Public.

9. Click Back (left arrow).

10. Leave the WAP Admin portal open for the next task.

Create a plan

In this task, you will create a plan through which you make the IaaS environment available to an

associated subscription.


1. In the left navigation pane, click PLANS.

2. Click CREATE A NEW HOSTING PLAN.

3. In PLEASE SELECT A FRIENDLY NAME FOR YOUR PLAN field, type Fabrikam IaaS, and then click

Next (right arrow).

4. On the Select services for a Hosting Plan, check VIRTUAL MACHINE CLOUDS, and click Next.

NOTE: You also have the option to deploy Platform as a Service, for example web servers, in addition to

IaaS.

5. On the Select add-ons for the plan page, click Done.

NOTE: The lab environment is not configured to support high availability.




NOTE: After a few moments, the plan is created. Note that the status of the plan is private. As with the

Gallery Item, you configured earlier, you need to make the plan public to make it available to tenants.

However, before you can make the plan public, you will need to perform additional configuration. In

particular, you need to associate virtual machine cloud with the plan.

6. Click Fabrikam IaaS.

7. On the DASHBOARD page, under plan services, click Virtual Machine Clouds.

8. On the virtual machine clouds page, click the VMM MANAGEMENT SERVER box, and select

WAPVMM.WAP.LOCAL.

9. Click the VIRTUAL MACHINE CLOUD box, and select Premium Cloud.

10. Under usage limit, deselect the VIRTUAL MACHINES check box, and enter 500 as the USAGE

LIMIT.

11. Repeat the previous step for CORES, RAM, and STORAGE as follows:

CORES: 1000

STORAGE: 4000

RAM: 4000

NOTE: The portal admin can further restrict and define settings established by the VMM cloud

administrator.

12. Scroll down, and under networks, click Add networks.

NOTE: You see the VM networks that you created earlier.

13. On the Select networks to add to this plan page, check SELECT ALL, and then click Done.

14. Under hardware profiles, click Add hardware profiles.

NOTE: You see the hardware profiles that were pre-configured for this lab environment, as well as the

one you created earlier.

15. On the Select hardware profiles to add to this plan page, check SELECT ALL, and then click Done.

16. Under templates, click Add templates.

17. On the Select templates to add to this plan page, check SELECT ALL, and then click Done.

18. Under gallery, click Add gallery items.

19. On the Select gallery items to add to this plan page, check SELECT ALL, and then click Done.

NOTE: Gallery Items can be filtered for individual plans, as can template, hardware profiles, and

networks.

20. Under additional settings, select all the check boxes, and then click SAVE.

21. Click Back.

22. On the fabrikam iaas page, on the portal taskbar, click CHANGE ACCESS, and then click Public.




23. Click Yes.

24. Once the plan is updated, click Back.

25. Leave the portal open for the next task.

Create user account

In this task, you will create a user account and provide it access to the plan you just created.


1. In the left navigation pane, click USER ACCOUNTS.

2. Click CREATE A NEW USER.

3. In ENTER EMAIL ADDRESS, type [email protected].

4. In ENTER PASSWORD and CONFIRM PASSWORD, type Passw0rd!

5. NOTE: The Fabrikam Iass (public) plan is already selected.

6. Click CREATE.

7. Wait until the user is created, and then click [email protected].

8. On the [email protected] page, note that a subscription is associated with the Fabrikam IaaS

plan.

9. Click Back, and leave the WAP Admin portal open for the next exercise.




Exercise 4: Deploy Infrastructure

Now that you have configured WAP to provide IaaS to tenants and configured a user account, tenants can

now log in to the tenant portal and deploy virtual machines. In this exercise, you will log on the WAP

portal as a tenant, explore the options for deploying a standalone virtual machine, deploy a virtual

machine role that you made available through the Fabrikam Iaas plan you created in the previous

exercise, and then create a custom network.

Deploy a standalone virtual machine

In this task, you will log on to the WAP tenant portal and look at the options for deploying a standalone

virtual machine. You will cancel out of the wizard before deploying the virtual machine.


1. In Internet Explorer, open a new tab.

IMPORTANT: Leave the WAP Admin portal open. Do not open the WAP tenant portal on the same tab

as the Admin portal.

2. In the new tab, on the favorites bar, click WAP – Tenant.


4. Click Continue to this website (not recommended) again.

5. On the LOGIN page, enter [email protected] as the username and Passw0rd! as the password,

and then click submit.

6. On the Welcome! page, click Next.

7. Read each page, and then click Next until you reach the end.

8. NOTE: After you click the last page in the tutorial, the NEW page appears. If it doesn’t, click NEW

from the portal taskbar.

9. On the NEW page, click STANDALONE VIRTUAL MACHINE.

10. Click FROM GALLERY.

11. On the Virtual Machine configuration page, select WS 2012 R2.vhd, and click Next.

12. On the Provide virtual machine hardware information, click the NETWORK box and note the

choices.

NOTE: You see the VM networks you created earlier.

13. Click the X in the upper-right hand corner to cancel out of the wizard.

14. Leave both WAP Admin and WAP Tenant portals open.




Deploy a virtual machine role

In this task, you will deploy the virtual machine role that you configured in the previous exercise.

IMPORTANT: The lab configuration uses nested virtualization (Hyper-V installed on a Hyper-V guest).

Although this configuration allows you to create VMs and configure Hyper-V related settings, you

cannot start these VMs. Consequently, the deployment will fail at the end of this task.


1. In the WAP – Tenant portal, click NEW.

2. On the NEW page, select VIRTUAL MACHINE ROLE, and click FROM GALLERY.

3. On the Virtual Machine Role configuration page, select Microsoft SQL Server 2012 –

Workgroup, and then click Next.

NOTE: This is the Gallery Item you imported into VMM and WAP in the previous exercise.

4. Click Next.

5. On the Provide Virtual Machine Role Settings page, in NAME, type SQL-Workgroup.

NOTE: If available, you can select different versions of the virtual machine roles. These version may

contain updates or configuration changes that preferable for your configuration.

6. Click Next.

7. On the VM SETTINGS page, click the COMPUTER SIZE box, and select Small (1 Core(s), 1792

MB).

NOTE: Although only one operating system is available in the virtual machine role, it is possible through

the use of Tags, to make other choices available. This provides tenants with a great of flexibility to

choose operating system SKU that meet their business or licensing requirements.

8. In PASSWORD and CONFIRM, type Passw0rd!

9. In COMPUTE NAME PATTERN, enter SQL-WG-###.

10. NOTE: The name pattern is used to create unique computer names when the guest VMs are

provisioned.

11. Click NETWORK REFERENCE, note the choices, and select Tenant WAP Private Network.

12. In WORKGROUP NAME, type SQLWG, and click Next.

13. On the SQL SERVER PROPERTIES page, note the checkboxes to enable or disable named pipes

and TCP/IP client protocols.

14. In SQL SERVER 2012 PRODUCT KEY, enter 1234.

15. Click the SQL SERVER AUTHENTICATION box, note the choices, and then select SQL Server and

Windows Authentication mode.




16. In INITIAL SQL SERVER SYSADMIN, type SA.

17. In SQL SERVER SA PASSWORD and CONFIRM, type Passw0rd!

IMPORTANT: Do NOT click Done at this time. In the next steps, you will switch to WAPVMM and open

the Jobs window so that you can see the progress of the VM creation, even though the VM creation will

ultimately fail.

18. Switch to WAPVMM.

19. In the VMM console, select Jobs.

20. In the Jobs workspace, click Running.

21. Switch to WAPPortal.

NOTE: Before executing the next step, be prepared to switch quickly to WAPVMM.

22. On the SQL SERVER PROPERTIES page, click Done.

23. As quickly as possible, switch to WAPVMM to watch the progress of the jobs.

24. In Jobs, expand Add VM Role resource.

NOTE: You can view the various tasks and their progress that VMM executes to deploy the virtual

machine role. When the job fails, it will disappear from the running jobs. If you did not switch to

WAPVMM in time to see the running job, you can click History, and click on the failed Add VM Role

resource job to view the details.

25. Switch to WAPortal.

26. In the WAP – Tenant portal, in VIRTUAL MACHINES, click SQL-Workgroup.

27. On the sql-workgroup page, click DASHBOARD, and scroll down the dashboard page, if

necessary to see all the items.

NOTE: The dashboard shows us the details of the deployment.

28. On the taskbar, click UPDATE.

NOTE: If other versions were available, you could update the deployment.

29. Click SCALE.

NOTE: If this deployment had been successful, you would be able add additional instances, up to the

resource limitations defined by either the VMM cloud or the WAP admin.

30. Click Back.

31. Leave the WAP Admin and WAP Tenant portals open for the next task.

Deploy virtual networks.

In this task, you will deploy a new virtual network.





1. In the WAP – Tenant portal, click NEW.

2. On the NEW page, click VIRTUAL NETWORK.

3. Click CUSTOM CREATE.

4. On the Virtual Network Details page, in NAME, type IaaS VM network, and click Next.

5. On the DNS Servers and Connectivity page, check Configure site-to-site VPN, and note the

configuration options.

6. Clear the Configure site-to-site VPN check box, and click Next.

7. On Address Space, in STARTING IP, type 10.7.211.0.

8. In CIDR (ADDRESS COUNT), click the drop down, and select /25 (125), and click Done.

9. Leave the WAP Admin portal open for the next task.

Verify virtual deployments in the WAP Admin portal.

In this task, you will verify that the networks and virtual machines appear in the WAP admin portal..


1. In Internet Explorer, select the tab that is logged on to the WAP Admin portal.

2. In the WAP Admin portal, in the left navigation, click VM CLOUDS.

3. Click VIRTUAL MACHINES.

4. Click Search (check mark).

NOTE: The output shows the failed deployment from an earlier task.

5. Click NETWORKS.

6. Click Search (check mark).

NOTE: The output shows the Virtual Machine network we created in the previous task.

This is the end of the lab.


windows azure pack - installing and configuring · windows azure pack – infrastructure as a...

Documents