©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Session ID: BTOT-WE-1000/4 Twitter hashtag #HPSWU

©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Speaker: Colin I’AnsonDate: Wednesday December 1st Session ID: BTOT-WE-1000/4

Building your Private Cloud on a Converged Infrastructure

“By 2012,

20% of all businesses will own no IT assets.”

Top Predictions for IT Organizations and Users, 2010 and Beyond: A New Balance

Gartner, Jan. 2010

4 HP Confidential

Agenda– Importance of converged infrastructure

– Choose the components

– One Infrastructure Design for Cloud to combine the components

– Converged infrastructure appliance

– Extensible solutions using converged infrastructure appliances

5 Footer goes here

– Nothing ...

– Except ...

With Cloud infrastructure you see ...

Converged Infrastructure

Virtual resource poolsAdaptive compute, memory, storage & network resources

FlexFabric Wire-once, dynamic assembly, always predictable

Infrastructure operating environmentEnables shared-service management

Data center smart gridIntelligent energy management across systems and facilities

©2009 HP Confidential

6

7 HP Confidential

The Components– Servers

– Storage

– IP Network

– Storage Network

– Infrastructure Operating Environment

– Enclosures and racks

8 HP Confidential

Infrastructure Design – It’s about TCO and not just purchase price

• Power consumption/Cooling

• Power delivery to the data centre

• Space – VM per meter of rack!

• Converged infrastructure TCO

– Ensure SLA for cloud consumers• Performance – define a VM, external network, Disk IOPS/data bandwidth

• Availability

• Resilience and High Availability

• Recovery time MTTR

– Rapidly build more catalogue items• Hosting instances, not just VMs and disk

Design Guidelines– Deliver VMs with no practical constraints

• VM definition: EC2-like or customer specified physical core oversubscription

• IP and SAN bandwidth per VM: 100Mb/s IP, 200Mb/s SAN from Gartner

• User memory per VM: VMware 3GB and allow Linux 500M and Windows 1G

– Provide physical and virtual pools of servers (and storage)

– Network guidelines• Ensure no bandwidth limitations/bottlenecks from high oversubscription

• Distribute server and storage infrastructure to reduce load on core

• Decrease tiers in architecture to decrease latency

– Reduce component count – including NICS and cables

– Target best TCO

Server Guidelines and Proposals– Principles

• HP Blades in c7000 enclosures

• Provide physical dedicated and virtualised shared servers

• Virtual connect/Flex Fabric

• Use 1 or 2 standard blades with minimum options limited to memory and disk

– Proposals

• x Above minimum

requirement

More VM to recover if blade

fails

Some applications cannot use more than

4 cores

Servers                

Blade Option CPU TypeSlots in enclosure Speed (GHz)

ECU per processor  Number of CPU Cores per CPU Cores per blade

Max Memory (GB)

Max VM per Blade

Memory per VM (GB)

Max VM per enclosure

BL460c G7 General Virtualisation X5650 0.5 2.66 20 2 6 12 192 40 4.8 640BL685cGeneralVirtualisation 6174 1 2.2 18 4 12 48 512 72 7.1 576

BL460c G7 Dedicated and 4-core Virtualisation  E5640 0.5 2.66 13 2 4 8 192 26 7.4 416

11 Footer goes here

Storage Guidelines and Proposals– Principles & Proposals

• Dual site resilient storage

• Preference is to use all IP networks removing Fiber Channel complexity but not always possible

• Multi tenancy admin in storage arrays

• Recognize 2 storage requirements: Tiered and Scale out

– How many GB and IOPS for tiered storage per server?• GB is a customer specified item

• Typical server: 200 Mb/s (Gartner); use block size to get IOPS

Conventional Data Centre Network Design

…

144 Enclosures for 1152 Servers

…

8 Servers

…

8 Servers

…

8 Servers

…

L3 Core

No local switching

Oversubscribed

Oversubscribed!Latency

!Latency

!Latency

!Latency

VM VM VM VM VM VM VM VM VMVM VM VMVM VM VMVM VM VM

N-S and E-W network

No local switching

Oversubscription

Latency

FCoE not supported in legacy equipment

Core

Distribution

Top of Rack

Multiplexer

VM

L3 Core

13

HP’s Network Design

HP Edge

HP Interconnect Fabric

40GbE

16 Servers

……

72 Enclosures for 1152 Servers

72x 40GbE

HP Edge

16 Servers

…NEVA vSwitch

VM VM VM

NEVA vSwitch

VM VM VM

Local switching

Not oversubscribed

NEVA vSwitch

VM VM VM

NEVA vSwitch

VM VM VM

Flat Network (N-S and E-W)

Local switching

No oversubscription

Latency reduced

Core

Distribution

Top of Rack

/Enclosure

VM

Infrastructure Operating Environment– IOE Components

• Insight Control

• Insight Dynamics

• Virtual Connect Enterprise Manager (VCEM)

• Virtual Machine Managers (Optional but likely)

– For extensible solutions add to the Infrastructure Operating Environment• Application management using Cloud Service Automation for Matrix

• To provide heterogeneity, full scale ERP for cloud, comprehensive security and deep multi tenancy management use Cloud Service Automation (this includes Operations Orchestration)

• To include XaaS Application Store and Aggregation of services use AP4SaaS

L2/L3Resilient

Network Core

Infrastructure Design for Cloud Transport

(MPLS)

Transport (Internet) WAN

Network Services

iSCSI (/FCoE

) Storag

e

NAS Storag

e

FC Storag

e

Production Servers

Cloud Controller Servers

Production Servers

Top of Rack Switch

HP A58xx

Flex

Fab

ric

iSCSI (/FCoE

) Storag

e

NAS Storag

e

FC Storag

e

Top of Rack Switch

HP A58xx

Resilient SANFl

ex

Fab

ric

Flex

Fab

ric

Core Switch

HP A12500

Core Switch

HP A12500Network Services

16 Footer goes here

One Cloud Architecture• Easy to understand, practical

• End-to-End solution: users to provider; lifecycles from strategy to delivery, top-to-bottom solution stack

• Componentized architecture built around open standards as far as they exist 

• Has no lock-in with the design and works with heterogeneous infrastructures

• Will readily scale out the server, storage and network elements

• Highly automated to reduce time for operations and to remove errors

• Designs to secure customer data and ensure privacy of applications in multi tenant solution

• Multiple solutions to minimize the environmental impact

HP Cloud Functional Architecture v3Design/Deploy

Provision Use Assure

Contract Mgmt.

Change Mgmt.

Compliance

Monitoring

Product & Portf. Mgmt

Service Lifecycle

Mgmt

PrivacyMgmt.

Application Security

IDPS & Threat Mgmt

Identity Mgmt

Information Security

Infrastructure Security

Secure SDLC

Security Program

Security Monitoring

GovernSecure

InfrastructureNETWORKPOWER &

COOLINGSOFTWARE INFORMATION CLOUDSTORAGESERVERS

Service Catalog

Service Model Repository

Service Capacity Modelling, Allocation & Configuration

Charging Rating

Delivery Management

Incident & Problem Mgmt.

Dynamic Workload Management, Resource Metering and Resource

Health

Resource

Template

Design

Service Design

Service Offer

Mgmt.

Demand Modelling

Service Request and Activation

Resource Management Modelling, Allocation and

Configuration

Supply

Deliv

ery

Dem

and

User Management, Service Billing, SLA Management, Order Management, Service Access and Usage,

Quality of Experience

Resource Provider Manager

User Portal

18 Footer goes here

Converged Infrastructure: HP BladeSystem Matrix

MatrixSelf

Service Portal

MatrixService Catalog

MatrixResource Pool

MatrixService Delivery

MatrixCapacity &

Management

MatrixCloud APIs

Customise

• Billing/chargeback• Approval flows• Other processes

HP-UXWindowsLinux

HP Converged

Infrastructure

HP Converged

Infrastructure MatrixCloud APIs

19 Footer goes here

Cloud Software Integration for Converged Infrastructure EnablerCloud controller (OO/SA/NA/SE) provides all the workflows to deploy an instance of an item in the service catalogue

– Option 1 – configure infrastructure for service instance directly from cloud controller

– Option 2 – provide converged infrastructure as a service to the cloud controller

Infrastructure Operating Environment

Blades Server StorageBlades Server Storag

e

Cloud Controller

20

Matrix used as Converged Infrastructure ‘Appliance’ WS API

Operations; Version, Template, Service, Request, Logical Server Group, Logical Server, Server Pool

h20195.www2.hp.com/v2/GetPDF.aspx/4AA0-9219ENW.pdf

Self service portal and service catalogue

Infrastructure design tool for application template

Deployment automation

21 Footer goes here

Converged Infrastructure Software: Insight Dynamics

22 Footer goes here

Using the Converged Infrastructure Appliance– Expose the Infrastructure Operating Environment

– Standard hosting instances created using the Insight Dynamics Insight Orchestration designer tool. Deployment process is defined in the automation tool (OO based)

– Each instance is placed into the ID service catalogue and made available via the Web Service interface

– Instances are subscribed to via the web service interface. Insight Dynamics Workflow tool creates the instance

– Management of the converged infrastructure is via the Matrix Systems Insight Manager (including Insight Control, Insight Dynamics and extended by VMWare vCenter or Microsoft Virtual machine manager)

23 HP Confidential

Extensible System Design with Matrix Appliances

Infrastructure Appliance

• Multiple locations to support HA

• Cloud controller selects best infrastructure appliance (capacity, security, location)Cloud Controller

Self Service Portal(User interaction)

Infrastructure Appliance

Infrastructure Appliance

Infrastructure Operating Environment

Infrastructure Operating Environment

Infrastructure Operating Environment

Cloud Controller

Self Service Portal(User interaction)

24 Footer goes here

Summary– For today’s workloads, cloud built enterprise class infrastructure can offer the lowest

TCO

– Why?1. Lower energy consumption though efficient design, smart cooling, smart power capping

2. Less energy consumed, less cooling required

3. Less energy consumed, higher rack density and less data centre space required

4. Less human intervention avoids errors

5. Better performance from each blade permitting more VM per CPU

6. Better resource management decreases the infrastructure consumed

7. Better management keeps system running longer and allows migration of tenants when system is degraded

8. Better management allows lights out operation

9. Greater infrastructure reliability prevents failures (down time & rebates, repair cost, customer care cost)

10. Easier to design infrastructure with less risk in development and integration, greater flexibility for innovation

11. No network distribution layer decreases cost and improves performance

12. Less cables, NICs, etc.

– And in a highly competitive environment, this decreases TCO/break even time, improves profitability/ROI and makes you more competitive

Continue the conversation with your peers at the HP Software Community hp.com/go/swcommunity