Green DC Transformation Through Optimisation – Best...

Green DC Transformation Through Optimisation – Best Practices

M. GowthamanDirector, Professional and Engineering Services

Green DC Transformation through Optimisation

Agenda

• Green DC Transformation – Business Drivers

• Green DC Transformation – Technologies

• DC Consolidation / Virtualisation Methodologies

• Managing the Consolidated DC

Market Trends

– Reduced time to market

– Demand for greater business flexibility

– Rising cost of platforms

– Drive for operational efficiencies

– Core versus context (smart-sourcing is a key trend)

– IT optimisation is now a business process enabler

Green DC Transformation: Business Drivers


Customer Challenges

– Complex infrastructure: too much infrastructure, poorly utilised, varying standards

– High value problems: legacy platforms, high costs,specialised resources

– Business strategy: leveraging infrastructure forbusiness change

– Innovation: willingness to do things differently to achieve business objectives

– Move away from Victorian engineering principles:designing systems not to the maximum but on demand


Achieving business sustainability

Managing the increasing

cost of energy

Adhering to environmental

laws and improving the

company image

Running out of power

Running out of

coolingRunning

out of space

Minimising loss of

energy and ROI

Concerns that CIOs have about IT needs


Why Need a Green Data Centre• Data centres consume 1.5% of all electricity in 2006 and growing

at 12% annually– Department of Energy– If IT were an industry, it would be approaching the top five energy

consumers• Data centres forecasted to surpass airlines in terms of CO2

emissions by 2020 due to energy consumed – McKinsey & Co. 2008– Can you say “threat of regulation”?

• Data centre power demands have doubled in last five years and 76% growth is predicted between 2005 and 2010 – IDC

• Three year cost of powering and cooling a typical server is now 1.5x the purchase cost of the hardware – Uptime Institute 2007

• Energy costs are 15-20% of IT’s operating expenses – Dave Ohara, Microsoft 2007

• 50% of data centres will have insufficient power and cooling capacity by 2008 – Gartner 2006

• 70% of Global 1000 will need to significantly change their data centres in the next five years to meet current and future energyneeds – Gartner 2007

Utilisation rate

IT equipment

Facilities

What can I do?Who can help?

Unuseful redundancies?

Silos? Usage resource monitoring?

Billing? Virtualisation? Consolidation?

Energy efficient hardware? Capping?

Local cooling? How is billing done?

Thermal monitoring? Power Monitoring?

Old, expensive? How is energy used?

Humidity? Lighting? Heat removal? Air flow? Space?

Power/performance oriented? DCiE? Power distribution?

Which type of equipment? Location?

Which tier am I?

Water cooling?


Data centre assessment: Ask effective questions

?

SolutionDesign, Build and Manage Consolidated / Virtualised

GREEN DC

Green DC Transformation through Optimisation – Solution Defined

DC Facility Infrastructure

DC IT Infrastructure


Green Data Centre – Defined

A green data centre is defined as a data centre in which the mechanical, lighting, electrical and computer systems are designed for maximum energy efficiency and minimum environmental impact.

Centralisation

Physical Consolidation

Virtualisation

Application Integration

Improved Operations

Best Practices

State-of-the-Art

IT Infrastructure Energy Efficiency Strategy

Facility Infrastructure Energy Efficiency Strategy

Consolidate many centres into fewer

Reduce infrastructure complexity

Improve facilities management

Reduce stuffing requirements

Improve business resilience (manage fewer things better)

Improve operational costs

Consolidate many servers into fewer on physical resource boundaries

Reduce system management complexity

Reduce physical footprints

Remove physical resource boundaries

Increase a hardware utilisation

Allocate less than physical boundary

Reduce software licensingcosts

Migrate many applications into fewer images

Simplify IT environment

Reduce operations resources

Improve application specific monitoring an tuning

Conservation techniques

Infrastructure energy efficiency

Improved airflow management

Hot and cold aisles

Improved efficiency transformers, UPS, chillers, fans, and pumps

Free cooling

Flywheel technology

Integrated power management

Direct liquid cooling

Combined heat and power

Green DC Transformation through OptimisationJourney towards the Green data centre


Virtualisation in Perspective• Virtualisation is the ability to create logical abstraction of

physical assets. In the case of server virtualisation, it allowsfor multiple “virtual” servers to run on one physical server, thereby consolidating many physical servers onto one.

• Reducing the number of physical components that provide a service

• Reducing cost and improving the quality of service• Standardising the operating environment

Green DC Transformation through OptimisationBenefits of Virtualisation• Maximise server utilisation• Less physical servers

– Lower maintenance– Accommodation and environmental savings (space, power,

A/C, lighting)• Improve deployment time = quicker to market • Reduce manpower overheads• Simplify centralised management• Future proof technology• Seamless server upgrade path and transportable server

technology (VMOTION)• Help to benefit disaster recovery, backups and rapid

development with snapshot and rollback features• Increase server availability, no single point of failure,

minimise downtime• Reduce TCO

Green DC Transformation: Technologies

• Storage Virtualisation– Storage virtualisation applies an abstraction to the storage systems within

the enterprise and is often a key component used with blade systems. Virtualising the storage allows storage virtual disks to be defined to components running on the server and separates the physical management and sometimes connection of those disks from the application software on the server.

• I/O Virtualisation– I/O virtualisation is similar to network virtualisation. It abstracts the I/O

interface away from the blade• Network Virtualisation

– Abstraction layer is applied to the networking components to provide better service, availability, and security to the physical servers and their applications

– Implementation at switch level, NIC card or in software (e.g VLAN, load balancer where sender does not know actual address)

• I/O Virtualisation– I/O virtualisation is similar to network virtualisation. It abstracts the I/O

interface away from the blade (e.g. Egenera pBlades and cBlades)


Virtualisation Models for Servers• Below Kernel

– Happens below the OS, which may not even be aware that virtualisation is happening

– Modus operandi of hypervisor-based virtualisation technologies– Common type of virtualisation– Pros:

• Transparency of strategic perspective, as application running in VMs get their own OS – hence look and like as it was before virtualisation

– Cons:• Virtualisation layer overhead as it intercepts operations

intended for hardware components• Overcome by a techniques “Par Virtualization” by making

the OS aware that it has been virtualised – allowing to account for this in its operation and avoid unnecessary overhead


Virtualisation Models for Servers (cont’d)• Above Kernel

– Isolation of applications from within the OS, segregating and containing them from one another executing within the same OS kernel - Containers, Jails, Zones, Workload Partitions

– Pros:• Efficiency gained through economies of scale• Allows the apps to communicate directly with device

drivers, avoiding overhead– Cons:

• Single patch may affect many running applications• Level of separation may not be sufficient for certain

environment

DC Consolidation / Virtualisation Methodology

Green DC Transformation: Methodologies

Data Centre Consolidation Process

Feasibility

Business Objective

Success Criteria

TCO/ROI

Implementation

Servers

Storage

Network

Applications

Security

Assessment

Application

Servers/OS

Storage

Network

Security

Infrastructure

Architecture

Application groupings

Servers Architecture

Storage Architecture

Network Architecture

Security Architecture

Infrastructure

Manage

Enterprise Management

Optimization

Monitoring

Documentation

Transfer of Knowledge

Completion of Project

Phase I Phase II Phase III Phase IV & V


• Business Objectives– Establishing business justification for consolidation of

servers– Reduce TCO– Improve service levels– Provide increased application availability– Increase the manageability of the information technology

(IT) environment• Business benefits

– Reducing IT costs– Keeping up with business challenges– Improving service levels and availability– Minimising the impact of external pressures


• Avoiding Common Pitfalls and Failures– Convince business units to surrender servers– Gain and maintain executive sponsorship– Manage politics– Apply best practices and adhere to standards– Develop and adhere to well-defined processes– Rely on established consolidation methodologies– Consider prohibitive bandwidth costs of high data-traffic

applications– Select appropriate applications to consolidate together– Identify application or middleware coexistence problems– Consider legal requirements to keep data locally


Step 1 – Assessing the Technical Feasibility• Feasibility

– Conduct an interactive workshop with customer’s management and IT admin teams

– Gather information on business requirements and objectives and the desired technical objectives

– Define the business objectives for consolidation/virtualisation and expected results of the project

– Estimate the expected reduction in TCO and the expected ROI– Feasibility report on consolidation for management’s decision

making


Step 1 – Assessing the Technical Feasibility (cont’d)• Assessment

– Assess Application Requirements– Interviewing application owners and maintainers– Describing major software components– Creating a flowchart of network inputs and outputs– Describing an operational schedule– Identifying and describing important dependencies– Creating a road map for the future growth of the application– During this assessment, we will document all of the various

aspects of the application.


Step 1 – Assessing the Technical Feasibility (cont’d)• Assess Platform Requirements

– Deploying tools to assess the following– Verifying inventories– Assessing technical configurations– Gathering server utilisation statistics

• Assess Storage Requirements– Corporate standards, and storage architecture road map &

Capacity Plan– Online storage of applications and data– Offline storage for backup

• Assess Networking Requirements– During assessment we will examine the following:

• Assess the topology and technologies utilised for the network.

• Assess throughput, bandwidth, and latency (for each server involved in the consolidation)


Step 1 – Assessing the Technical Feasibility (cont’d)• Assess Security Requirements

– Assessment will focus on the following four major areas:– Security operations– Security policy and standards– Security procedures– Security implementation


Step 1 – Feasibility and Assessment Phase: Deliverables

• Management Summary• Business Objectives• Criteria for Success• TCO Assessment Details

– Other assumptions– Assessing apps profiling, platforms, storage, network, security,

infrastructure and ops, assessing risks– Scenarios (e.g 40% reduction in server/storage)– ROI analysis (Scenario 1 or 2)

• Conclusions


Step 2 – Designing a Consolidated Architecture• Technical Constraint Analysis

– Server Analysis – Storage Analysis – Network Analysis

• Business Constraint Analysis– Business Constraints– Process Constraints – Security Constraints


Step 2 – Designing a Consolidated Architecture (cont’d)

• Workload Constraint Analysis – CPU Analysis – Memory Analysis – Disk Analysis – Network Analysis – Aggregate Utilisation Analysis – Power Consumption Analysis

• Combining All Constraints: Comprehensive Analysis– Net-effect view of constraints – Permutation-based optimisation

• What-If Analysis– Exploring Technical Options – Exploring Business Options

Step 2 – Designing a Consolidated Architecture: Deliverables

• Consolidated/Virtualised Architecture Report– Detailed apps, platform, storage, network, security and DC

facilities with assumptions on sizing and capacity planning withdetailed calculations

– Walkthrough the Design with the customer’s steering committee project team

– Highlights on risk in implementation and mitigation process



Step 3 – Implementing a Consolidation Solution• Preparing for the consolidation

– Creating a build specification– Building the environment– Defining your migration strategy– Practicing the consolidation

• Implementing the Consolidation– Migrating applications– Testing the configuration– Tuning the configuration– Documenting the results of the configuration– Training the administrative staff


Step 3 – Implementing a Consolidation Solution: Deliverables

• Handover the consolidated working DC with the following documents– Design specification and configuration docs– Checklist to verify the business objective met– Train the operations staff on the implemented systems

• Tools and Specification: TIA 942 specs for DC facility and best practices from Principal vendors


Step 4 – Managing Consolidated Environment

Demand

Business Value

IT GovernanceStrategic IT Planning & Organisation

Application Development

Architecture & Design

Acquisition & Development

Application Development

Infrastructure Integration

Performance Test

Applications & Services

IT Service Management

ServiceDelivery

Monitoring

ServiceSupport

Enterprise Arch

SOA/ILMITIL

Development Infrastructure

Deployment Infrastructure

Production Infrastructure

Questions and Answers

© 2008 Quest Software, Inc. ALL RIGHTS RESERVED.

VMware Management with Foglight

Unlock a New View on Application Management -Managing the Impact of VMware on Applications and End Users

Mark TritarisOctober 22, 2008

Continuous change is inevitable and driven from the top by the need to improve results across the organization.

Change Driver

Quest is the only provider of adaptive application and services management to connect:Business Services to InfrastructureEnd User to DatabaseProduction to Development

to unify IT and the business.

Foglight Application and Services Management

Fundamental ChallengeUnderstanding the impact of resource sharing

CPUMulti-Core Processors

NetworkShared Connectivity

Load Balancing

Redundancy

MemorySharing

Over-commitment

DiskShared storage

Fiber, iSCSI, NAS

Core 4 Resources

• Existing tools show data in many tabs

• Alarming is simplistic and doesn’t show trends

• Management frameworks require multiple management servers– Administering servers independently– Missing “single pane of glass”

virtualization data views– Struggling to compare metrics, virtual

infrastructure layers

Clarity To see what you need to quickly and easily

• No context around virtualization metrics

• Expert advice not given• Virtual machine metrics

inaccurate– Hypervisor has dynamic

resource scheduling– Live migrations to

alternate hardware– Timekeeping issues

inside virtual machines

Expertise To manage new and different technology

• Host issues could impact virtual machines

• Host issues alarm when issue detected

• Each VM on host raises its own alarm

• One single issue can escalate to many– Complicates root-cause

analysis and resolution– Makes problem appear

more significant that it is

ContainmentOf alarm storms and information overload

• VMs moving across hosts due to VMotion, DRS, HA

• Could move to more/less powerful systems

• May impact overall VM performance

• Migrations impact share pools and allocations

• Need to track migrations to assist with root cause analysis

• Impact analysis prior to migration

Asset TrackingTo know what happened and why

• Impact analysis prior to migration– For all “Core 4 Resources”– Understand growth trends

• Ensure service levels are maintained

• Understand “Best Practice”configurations and patterns

• Starting to move toward the fluid datacenter– Predictive– Automated

PreventionOf future problems

SummaryAddressing the Challenges of Monitoring a Virtual Environment

Clarity Containment Expertise

Tracking Prevention

VMware Management with FoglightSolution Overview

• Foglight helps organizations understand the entire virtual infrastructure

• Manages relationships and interactions between all the components in the virtual infrastructure:

– Data centers– Data stores– Clusters– Resource pools– ESX servers– Virtual machines

Foglight Complements VirtualCenter

VMware VirtualCenter• Ideal for configuration and administration• Helpful when laying out the virtual infrastructure

Foglight for VMware• Ideal for managing performance and availability

• Helpful to visualize and understand the virtual environment and how it affects applications

VMware Management with FoglightKey Capabilities

• Role-based Views• Out-of-the-Box Alerts with

Expert Advice• Asset and Configuration

Tracking• Workload Migration Modeling• Service Level Management

• Resource Utilization Management

• Multiple Virtual Center Management

• Reporting

Role-Based Views Key Capabilities Summary

•Single view of all Alarms in Datacenter by Infrastructure level or severity

• Single view of key performance metrics aggregated at Datacenter level

• CPU (%Ready / % Used)• Network I/O• Disk I/O• Memory

• Summary View of Datacenter objects• Resource Pools• Hosts• VMs

• Unique Drill-Down ability to quickly isolate issues

Out-of-the-Box Alerts with Expert Advice Key Capabilities Summary

• Detailed analysis and expert advice• Understand where the incident is

occurring• ESX Server• Virtual Image• Operation System

• Out-of-the-box expert advice surely allows you to review data on how to resolve the problem effectively

Asset and Configuration Tracking Key Capabilities Summary

Asset Tracking• Tracks the movement of virtual machines from one

physical server to another• Migration Modeler allows you to understand the impact

that a virtual machine will have on the physical server

Workload Migration Modeling Key Capabilities Summary

• Show the impact of moving a virtual machine from one physical system to another

• Determine if planned moves will have unfavorable impact on:

• Resources• Applications• End users

Service Level Management Key Capabilities Summary

• Structure services as KPIs, SLOs or OLAs

• Determine SLA compliance through:

• Service windows• Role of user

investigating the service

• Performance and availability data

• Service desk metrics and custom logic

• Measure service levels for business-critical applications that leverage a virtual infrastructure

Resource Utilization Management Key Capabilities Summary

• Network summary• Network throughput• Current send/receive data

• Per Host• Per NIC

• Data store summary• Capacity• Used space vs. free space• Growth rate• Estimated time until full

Multiple VirtualCenter Management Key Capabilities Summary

Foglight for VMware

VMware VirtualCenter Management

Server

VMware Virtual Infrastructure 3 (VI3)

Web-BasedInterface

Single VirtualCenterImplementation

Multiple VirtualCenter Management (CONTINUED)

Key Capabilities Summary

Foglight for VMware

VMware VirtualCenter Management

Server

VMware VirtualCenter Management Server (2)

VMware VirtualCenter Management Server (N)

VMware VirtualCenter Management Server (1)

VMware Virtual Infrastructure 3 (VI3)

Web-BasedInterface

Multiple VirtualCenterImplementation

Reporting Key Capabilities Summary

• Out-of-the-box reports to help you understand:

• Individual virtual images• Physical servers• Resource groups• Virtual asset tracking• Resource allocation

changes• Virtual infrastructure

events• Examine performance in real-

time• Correct resource imbalances• Analyze historical data to assess

usage over time

VMware Management with FoglightKey Benefits

• Understand how the virtual environment impacts the application

• Quickly determine the root-cause of an incident or problem

• Contain alarm storms from virtual machines and physical servers

• Track movement of virtual machines and understand their impact

• Identify contention for resources between virtual machines

��

��

��

��

Oracle SQL ServerSybase DB2 UDB

ApacheMicrosoft IISCitrixRich clients

Application• Transaction monitoring and correlation from end user to database• Service level monitoring and correlation from business services to

Infrastructure component• Application dependency mapping• Detect, diagnose and resolve issues quickly

Java .NETSiebel PSFTOEB SAP

��

End User• Synthetic user performance analytics• Real user performance analytics• Real user session analytics

Service Levels• Cross domain service modeling

• Role-based dashboards• Service chain discovery and mapping

• Prioritize problems based on business impact

Database• Monitoring• Diagnostics

• Past and Present Analytics• SQL Optimization

• Database ‘Defrag’/Reorg• Toad Development/Admin

Infrastructure• OS Monitoring• Network Device Management• Middleware Management• Virtualization Management• Integrate with existing monitoring assets

Windows VMwareSolaris SUSEHP/UX RedhatMQ AIX

What’s Next?

• Foglight Application & Service Management:http://www.quest.com/application-and service-management/

• Foglight VMWARE Application Management:http://www.quest.com/application-and-service-management-

technology/vmware.aspx

• Feature Whitepaper: Five Ways to Ensure Your Virtualization Initiatives Effectively Support Applications and End Users

http://www.quest.com/application-and-service-management-technology/vmware.aspx

Check out our Demo Booth at VMWARE Vforum!

Green DC Transformation Through Optimisation – Best...

Documents

Transcript of Green DC Transformation Through Optimisation – Best...