Implementation of Private Cloud for Hyper-V in WebsitePanel

WebsitePanel offers two types of Hyper-V configurations:

1. Non-Clustered

2. Clustered

Hyper-V/Failover Cluster Configuration

A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service.

It is recommended deploying a failover cluster on Windows Server 2008 R2 Enterprise or Datacenter editions.

Note that each Hyper-V host cluster can have up to 16 nodes (Host Servers); with each node typically running 10-20 Hyper-V based Virtual Machines (actual number may vary based on host capacity). Note that in LAB environment, a minimal of 2 Node Hyper-V host clusters is required to enable high availability and failover.

To deploy a Hyper-V cluster on Windows Server 2008 R2, please follow the steps outlined below:

1) Review “Failover Cluster Step-by-Step Guide: Validating Hardware for a Failover Cluster” online at TechNet: http://technet.microsoft.com/en-us/library/cc732035(v=WS.10).aspx;

2) Review “Using Cluster Shared Volumes in a Failover Cluster in Windows Server 2008 R2” online at TechNet: http://technet.microsoft.com/en-us/library/ff182346(v=WS.10).aspx;

3) Review “Understanding Requirements for Failover Clusters” online at TechNet: http://technet.microsoft.com/en-us/library/cc771404.aspx;

4) Follow steps described in “Hyper-V: Using Hyper-V and Failover Clustering” online at TechNet to get a Hyper-V failover cluster up and running: http://technet.microsoft.com/en-us/library/cc732181.aspx;

5) Ensure you successfully went through Steps 9 and 10 as it is a crucial part of the deployment to confirm the environment and failover clustering feature is configured and functioning as appropriate;

Pre-Requisites for Cluster Configurations

System Center Virtual Machine Manager 2008 R2 Deployment

Virtual Machine Manager provides scalable infrastructure for managing virtual machines. It integrates with System Center Operations Manager 2007 to enable performance and resource optimization.

We recommend you to use System Center Virtual Machine Manager Configuration Analyzer before starting installation of System Center Virtual Machine Manager to ensure the server’s configuration matches the software requirements. Please use the following link to download the analyzer: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=02d83950-c03d-454e-803b-96d1c1d5be24&displaylang=en. After you installed the analyzer, please go ahead and validate the server configuration. The following is a screenshot of sample scan results on the server to ensure the configuration is appropriate and no configuration issues have been found:

clip_image002

Once the analyzer reported that the server carries all the pre-requisites to install System Center Virtual Machine Manager 2008 R2, please follow the steps outlined below:

1) Review Supported Configurations for Virtual Machine Manager 2008 R2 online at TechNet: http://technet.microsoft.com/en-us/library/cc764231.aspx;

2) Review the latest system and software pre-requisites for deploying Virtual Machine Manager 2008 R2 online at TechNet: http://technet.microsoft.com/library/cc764328.aspx;

3) Provision a physical or virtual machine to install the Virtual Machine Manager 2008 R2;

4) Install necessary pre-requisites, including any service packs, and any dependent software such as Microsoft SQL Server 2005 w/SP3. Refer to TechNet documentation for installing System Center Virtual Machine Manager 2008 R2 on single server at: http://technet.microsoft.com/en-us/library/cc764289.aspx;

5) Install Virtual Machine Virtual Machine Manager per TechNet documentation and “New Installation of VMM” at http://technet.microsoft.com/en-us/library/cc793149.aspx;

Once Virtual Machine Manager 2008 R2 is installed, perform the following post-installation tasks to ensure the software is fully operational:

1) Ensure that you can launch the VMM 2008 console as shown in the picture below;

2) Create one or more Host Server Groups;

3) Register either cluster or single Hyper-V host(s) deployed within the environment;

4) Ensure that you can see the virtual machines that are provisioned in the Hyper-V host(s) or cluster registered;

5) Create and configure the library server;

6) Add any VHD’s and ISO images to the library;

7) Create hardware/software templates;

8) Set/configure high availability options for virtual machines;

clip_image004

System Center Operations Manager 2007 R2 Deployment

Operations Manager 2007 R2 is a component of System Center Enterprise, and provides end-to-end service management of applications and IT services running across data center fabric, providing greater control and insight into health and performance of Microsoft, UNIX, and Linux servers, and the workloads running on them. For an overview of Systems Center Operations Manager 2007, please refer to the site: http://www.microsoft.com/systemcenter/en/us/default.aspx.

To install System Center Operations Manager 2007 R2 in DDC Environment, please proceed with the following steps:

1) Review “Getting Started with Operations Manager 2007 R2” online at TechNet: http://technet.microsoft.com/en-us/library/dd887701.aspx;

2) Review “Operations Manager 2007 R2 Design Guide” online at TechNet: http://technet.microsoft.com/en-us/library/dd789005.aspx;

3) Review Infrastructure Planning and Deployment (IPD) guide online at TechNet: http://technet.microsoft.com/library/ee354213.aspx;

4) Determine the specific deployment scenario for installing Operations Manager 2007 R2 by reviewing the TechNet article “Operations Manager 2007 Deployment Scenarios” found at: http://technet.microsoft.com/en-us/library/bb432145.aspx;

5) Review the pre-requisites for deploying Operations Manager 2007 R2 online at TechNet: http://technet.microsoft.com/en-us/library/bb432131.aspx;

6) If needed, provision a physical or virtual machine needed for installing the Operations Manager 2007 R2 (for instance, DDC-SC-OM01);

7) Install necessary Operations Manager 2007 R2 pre-requisites, including any service packs, and any dependent software such as Microsoft SQL Server 2005 w/SP3, and SQL Reporting Services. Refer to TechNet documentation “Deploying the Single Server, Single Management Server Scenario” at http://technet.microsoft.com/en-us/library/bb432146.aspx;

8) Once System Center Operations Manager 2007 R2 is installed, verify that you can launch the Administrative Console as shown in the picture below;

9) Follow post-installation configuration steps as detailed below;

clip_image006

Dynamic Data Center Toolkit 3.0 Components Deployment

The Dynamic Data Center Toolkit consists of software (web services) and a sample control panel application. The DDC Toolkit also contains documents outlining best practices for the creation and configuration of Dynamic Data Centers to meet the needs of the provider’s customers using proven technology and repeatable, documented process.

Note that all sample code is located at http://code.msdn.microsoft.com/ddc

The figure below illustrates how the DDC Toolkit exposes management functionality by providing a layer on top of the Microsoft Platform.

clip_image007

We recommend installing each service component from Dynamic Data Center Toolkit on a server that is running corresponding software either System Center Virtual Machine Manager 2008 R2 or System Center Operations Manager 2007 R2.

The following are pre-requisites for installing the services layer:

1) Installed IIS 6.0 Compatibility feature on IIS 7/7.5;

2) Enabled WCF Activation feature;

3) Installed Microsoft .NET Framework 4.0 Full distributive;

4) Created an IIS Application Pool for each WCF Service.

5) Created a domain account for running each service with all necessary privileges granted to each of these accounts (please follow carefully corresponding guidelines).

6) Admin rights on the server to install the service.

7) Once the services are installed, verify that each of the services is running by invoking the corresponding WSDL in web browser: http://<SCVMM Service>/

Please find below description of all pre-deployment steps required to configure corresponding service accounts and permissions to run SCVMMService and SCOMService (MonitoringWebService) web applications from DDTK, as well as the corresponding guidelines for an every step.

Attachments

1. Implementation of Private Cloud for Hyper-V in WebsitePanel

2. SCVMM download(.msi file)

3. SCOM download(.msi file)

[Note: The newest versions of the above software are available at http://code.msdn.microsoft.com/ddc. Kindly ensure that you have the latest versions installed.]

4. DDC_FastStart_Getting_Started_v3.2

5. DDC Lab Environment Diagram