Private cloud virtual reality to reality a partner story daniel mar_technicom

25 March 2011

Singapore

Slide 1

Microsoft Cloud Summit

Private Cloud: Virtual Reality to Reality a

partners’ story

Daniel Mar [[email protected]] Technical Services Manager – TechniCom IT Solutions

PRIVATE CLOUD: MAKING IT REAL

• Where and how to start with building a private cloud

within your organisation

• Server Virtualisation – Hosts and Storage selection

• Tips and Tricks for virtualising server workloads

• Real Life Customer Scenarios – share their story and

lessons learnt

• System Center Management

• Self Service Portal

Slide 2

PRIVATE CLOUD: STEPS TO MAKE IT HAPPEN

Slide 3

Virtualise

Create a

Virtual

Infrastructure

Add

Management

Add Self

Service Portal

+ +

• What to look at when selecting server hardware for a Host

HOST SERVER HARDWARE SELECTION

Slide 4

- CPU Speed

- No of Cores

- x64 bit

- Supports

Hardware

assisted

Virtualisation

(AMD-V/Intel-VT)

- More RAM the

better

- NUMA – check

RAM module

install sequence

- Dynamic Memory

in SP1

- Use SAS not SATA

- Higher RPM

Speeds better

- Local/Shared

Storage

- More NIC ports

the better

- 1Gb/10Gb

- VLAN support

- TOE/VMQ

- Storage access

- FC HBAs

- 10Gb NICs

- SSD are faster

and are more

reliable

HOST SERVER HARDWARE SELECTION

• Should I create my private cloud on Blade or Rack servers?

Slide 5

Depends what fits your requirements better!

Rack Servers • Supports a higher density of Network and

Fibre ports

• Greater number of RAM slots available

• Greater number of local disk options

• Can be easily moved to another site or rack

• Power consumed maybe slightly more than

Blade servers

Blade Servers • Smaller physical footprint

• Highly reliant on Blade enclosure – backplane

could be single point of failure, high

availability also requires two enclosures

• Server has limited expansion/upgrade options

• High density means more heat generated in a

single area – cooling considerations

• Shared storage is critical in supporting a Highly Available

virtual infrastructure.

• What features do I look for in storage • Support for FC or iSCSI or both [FC – 2/4/8Gbps and iSCSI 1/10Gb]

• De-duplication

• Fast cloning

• Snapshots

• Thin Provisioning

• Data Replication to support DR

• Storage sizing – Plan for current

and future requirements

• Most important remove all single

points of failure – Multiple

paths to the storage should

be implemented in production.

STORAGE HARDWARE SELECTION

Slide 6

Flexible Volumes

(2TB Provisioned)

Aggregate Physical Storage

(1TB Total)

RAID Groups

1TB

300

GB

200

GB

200

GB

50 GB

150 GB

100 GB

File system and LUNs stored in Dynamic Flexible Volumes

NetApp FAS SANs

• Supports FC and iSCSI out of the box

• RAID-DP disk protection

• Thin Provisioning, Deduplication, Fast

Clone

• Data Replication and Snapshots

STORAGE HARDWARE SELECTION

• So many storage vendors out there - how do you choose?

• Firstly leverage off your existing storage vendor

• Analysis of two storage vendors solutions we have

deployed in the past

Slide 7

HP Lefthand SANs

• iSCSI based SAN only

• Unique feature - Network RAID

• Virtual SAN Appliance available

• Start small, grow seamlessly

TIPS & TRICKS: HOST SETUP

Biggest Tip for 2011: Install Windows 2008 R2 SP1 to get

access to features like Dynamic Memory and Remote FX.

Slide 8

Installing Antivirus on the host – exclude

selected files and folders

Network connections

• More NICs the better when

configuring hosts – ensure

correct binding order

• Enable new network

features – Jumbo Frames,

VMQ

Storage connections

• Fibre Channel – ensure multi-path enabled.

• iSCSI – Windows does not support NIC

bonding for iSCSI, hence use separate NICs

with multi-path enabled.

Full or Core Installation

Host

TIPS & TRICKS: WORKLOAD MIGRATION • Your environment is probably running many different types of OS

• Check with software vendor on supportability

• Check resource requirements for the workload – MAPS Tool

• Migrate Test/Dev servers first

• P2V or New – depends but Domain Controllers always new

Slide 9

OS Type Notes

Windows NT Will run on Hyper-V – not

supported by MS

Windows 2000 – 1 vCPU only,

max 4 disks

Was officially supported until

13th July 2010

Windows 2003 / 2003 R2 – up

to 2 vCPUs

Windows 2008 / 2008 R2 – up

to 4 vCPUs

R2 no need to install

integration components

Linux Distributions – now up

to 4 vCPUs

Official support for SUSE 10 +

and RHL 5.2 +

TIPS & TRICKS: COM AND USB PORT ATTACHED DEVICES

• Do you think that all workloads can be virtualised?

• What about devices attached to the…

SOLUTION: Make the devices IP enabled over the network.

Slide 10

COM Port

USB Port

www.moxa.com

www.seh.de

SEH myUTN-80

MOXA NPort 6150

SEH myUTN-50

CUSTOMER SCENARIO: BASIC VIRTUALISATION

• Start with 2 hosts and connect them to shared storage

• Install Windows 2008 R2 OS [Full Installation]

• Enable the Hyper-V Role

• Enable the Failover Clustering Feature and create a

Hyper-V cluster

• Migrate workloads – P2V or Build New VMs

Slide 11

VM VM VM VM

• Need min two for failover cluster

• Though need to reserve 50% of the RAM on each host Why start with 2 hosts?

• Adding another host enables more workloads to be hosted.

• 3 hosts the RAM needed to be reserved is 33% on each host

What happened when we add

another host?

VM VM

• Customer had legacy

application server running

Windows 2000 SP4

• Not officially supported by

Microsoft – before 13th July

2010 was supported on Hyper-

V with 1 vCPU, and IDE

attached disks.

• Migration Method: Mostly P2V

using an offline mode.

Fortunately Windows 2000 is a

plug and play OS so can

recognise the new VM

hardware

• Customer has a Windows 2003

domain and is running

Windows 2003 Domain

Controllers

• Windows 2003 SP2 is officially

supported by Microsoft with

max 2 vCPUs

• Migration Method: Domain

Controllers should never be

P2V migrated, it is always a

build New VM process. Also

remember to uncheck Time

Sync with the host.

• Customer has a number of

Windows 2003 application

servers

• Windows 2003 SP2 is officially

supported by Microsoft with

max 2 vCPUs

• Migration Method: Mostly P2V

using an online mode.

Windows 2003 has a VSS writer

so data is made crash

consistent before migration.

P2V Wizard from SCVMM

used.

• Customer has a Windows 2008

x86 file server

• Windows 2008 R2 has new file

server features such as Branch

Cache, Enhanced Backup and

DFS improvements

• Migration Method: Build new

VM running Windows 2008 R2,

migrate shares and sync data

using a robocopy process.

Cutover is a simple as changing

login scripts and GPOs.

• Customer has a Linux Red Hat

5.4 Server running a SMTP

server

• Linux Red Hat 5.4 is officially

supported on Hyper-V with up

to 4vCPUs

• Integration components exist

for Linux

• Migration Method: Build new

VM process. P2V process for

Linux not supported by any

tools available from Microsoft

CUSTOMER SCENARIO: WORKLOAD MIGRATION

• Customer had the

following workloads to

migrate

1. WinNT with SQL 6.5 DB

2. Windows 2000

application servers

3. Windows 2003 Domain

Controllers

4. Windows 2003

application Servers

5. Windows 2008 File Server

6. Linux Red Hat 5.4 Server

7. Debian Server

Slide 12

• Customer had legacy server

running WinNT with SQL 6.5

database

• Not officially supported by

Microsoft

• Migration Method: P2V will

not work because WinNT4 is

not a plug and play OS. Build

new VM running WinNT and

SQL 6.5 and migrate the

database.

• Alternative Migration

Method: Use a commercial

paid migration tool.

• Customer has a Debian Server

running some monitoring

software

• Debian is not officially

supported by Microsoft on

Hyper-V. However, it should

still run.

• Integration components exist

for Linux which could be

installed.

• Migration Method: Build new

VM process. P2V process for

Linux not supported by any

tools available from Microsoft

CUSTOMER SCENARIO: VIRTUALISATION ON BLADE SERVERS

• Customer has purchased a number of blade servers and a single blade enclosure

• Server specification is 4 sockets - 6 core, 128GB RAM, Local disk for OS and NetApp attached shared storage, 4 NICs.

• Customer had configured 4 VMs with 30GB RAM each on each host

• VMs and VHDs were stored on a single LUN from NetApp attached exclusively to one host.

• Patching requirements reduced – power, network, fibre channel

• Reconfigured NetApp storage to support a Hyper-V cluster

• Reconfigured and reinstalled hosts and created single Hyper-V cluster

• Features such as live migration and high availability enabled by cluster

• New project requirements now raise the consolidation ratio to 10:1

• Windows 2008 R2 Datacenter edition and Server Management Suite – Datacenter purchased

• SC Virtual Machine Manager and SC Operation Manager deployed

Slide 13

+

CUSTOMER SCENARIO: MS EXCHANGE VIRTUALISED

• Virtualising Exchange – Supported on Hyper-V?

• Check out Microsoft Support Policies • Exchange 2003/2007 - http://technet.microsoft.com/en-us/library/cc794548(EXCHG.80).aspx

• Exchange 2010 - http://technet.microsoft.com/en-us/library/aa996719.aspx

• “Microsoft doesn't support combining Exchange high availability

solutions (DAGs) with hypervisor-based clustering, high

availability, or migration solutions …”

• How to implement on Hyper-V? • Exchange standalone - OK to go on Hyper-V cluster

• Exchange HA solution (DAG) – Need to go on standalone Hyper-V hosts

Slide 14

Exchange 2003 Exchange 2007 Exchange 2010

DAG VM VM

ADD MANAGEMENT WITH SYSTEM CENTER

Deploy in the following sequence:

1. SCVMM to manage the virtual infrastructure

2. SCOM to monitor and mange

3. SCCM to patch, configure and deploy

4. SCDPM to backup and recover

5. SCSM to deal with service management

6. Opalis for process automation

CUSTOMER SCENARIO: CITRIX INFRASTRUCTURE VIRTUALIZED AND MONITORED

• Customer is deploying Citrix XenApp and Citrix XenDesktop

• Created a highly available virtual infrastructure running on

Hyper-V

• Deployed System Center components – SCVMM + SCOM

• Single management console to monitor and mange virtual

infrastructure and also Citrix infrastructure.

• Highly scalable solution together with comprehensive

management.

• Future requirements for SCDPM and SCCM

Slide 16

ADD SELF SERVICE WITH SSP 2.0

• Benefits • Allocates datacenter resources

• Simplifies business unit on boarding

• Helps to validate and provision infrastructure

• Enables Self service provisioning

• Allow partners to extend functionality

• Using the SCVMMSSP2.0

• How to Deploy to SCVMMSSP2.0? • Install as a VM, configure to existing SCVMM server and deploy SSP2.0

dashboard on a SharePoint server for reporting and chargeback views

Slide 17

Partner-extensible solution that enables datacenters to pool, allocate, and manage resources to enable IT as a service.

VISION

Step 1

• Configuration

and

Extensibility

Step 2

• Onboarding /

Infrastructure

Request

Step 3

• Approval /

Provisioning

Step 4

• Self Service VM

Provisioning

START YOUR JOURNEY TO THE PRIVATE CLOUD

Slide 18

Step 1: Analyse and assess current workloads to

identify those to be virtualised

Step 2: Design a HA virtual infrastructure to

support current and future requirements

Step 3: Build the HA virtual infrastructure

Step 4: Migrate workloads or build new

workloads

Step 5: Add management with System Center

Step 6: Add self service with Self Service Portal

2.0

WHERE DO I START? • Private Cloud is not for everyone…

… it depends on where you are in terms of IT Maturity

• Enter the Microsoft Infrastructure Optimisation Model

Slide 19

Virtualise today – start

with your Test/Dev

servers, web servers

Ready for the Self

Service Portal

Move between

private and public

cloud

OUR SERVICE OFFERINGS • Server Virtualisation offerings

• Server Virtualisation Pre-Assessments

• Business Case and ROI/TCO Analysis

• Analysis and Design of Private Cloud Architectures

• Server Virtualisation Proof of Concepts

• Server Virtualisation build and production rollouts

• Existing Server Virtualisation health checks

• Desktop Virtualisation • Everything that we can do for the server we can do for the desktop also

• Application Virtualisation – Citrix XenApp/ App-V

• Optimised Remote Branch Office printing solutions

Slide 20

PROMOTIONS

• Free Private Cloud Pre-assessment (for the first 5 customers who email before 8th April 2011) • Analysis of existing server infrastructure using MAPS Tool.

• Business Case and TCO/ROI Analysis

• High Level Virtualisation Infrastructure design including server hardware and storage recommendations.

• Proposal for server virtualisation implementation and migration.

• Consulting services worth over $5,000 SGD

• Please quote MS Solution Day – PCPA01

• Desktop Virtualisation Proof of Concept (for the first 2 customers who email before 8th April 2011) • Setup of joint Citrix/Microsoft solution with a streamed Windows 7 OS

golden image

• POC server hardware provided by TechniCom

• Up to 5 virtual desktops and max 5 applications to be supported by POC.

• Please quote MS Solution Day – DVPOC01

• TechniCom IT Solutions - Contact • Daniel Mar - [email protected]

Slide 21