Upload
alan-mcsweeney
View
133
Download
0
Embed Size (px)
Citation preview
Infrastructure and Application Consolidation Analysis and Design
Alan McSweeney
November 26, 2009 2
Objectives
• To provide an understanding of the benefits of undertaking an infrastructure consolidation analysis and design exercise
• To describe the scope and outputs from an infrastructure consolidation analysis and design exercise
November 26, 2009 3
Agenda
•Approach to infrastructure consolidation analysis and design
•Consolidation options
•Consolidation issues
•Analysis and design scope
•Analysis and design delivery
•Analysis and design deliverables
November 26, 2009 4
Goal of Consolidation
• Reduce complexity
• Reduce cost of operation and administration
• Increase flexibility and responsiveness
•Do more with less
November 26, 2009 5
Infrastructure and Application Consolidation Analysis Objectives
• Understand the existing application and infrastructure landscape
• Provide details on application and infrastructure consolidation options and costs
• Produce optimised system architecture
• Identify hardware and software options and vendors
• Produce implementation plan
• Identify issues and resolutions
• Produce vendor independent design
• Provide all the facts needed to understand if server virtualisation and consolidation will deliver you bottom-line benefits
• Does not conflict with implementation of virtualised infrastructure by any vendor
November 26, 2009 6
Consolidation Areas
•Consolidation and virtualisation areas− Server
−Desktop
− Storage
•Which areas are you interested in?
November 26, 2009 7
Infrastructure Business Drivers
November 26, 2009 8
Application and Consolidation Options
November 26, 2009 9
Why Do It
• Virtualisation on its own may not be the best solution− Can hide some problems
− Same number of server images and applications, just not physical
• Comprehensive application and infrastructure consolidation view allows organisation see bigger picture
• Look at bigger picture to identify wider set of cost savings opportunities
• Identify all issues
• Provide business case for investment
• Provide a checkpoint before selecting implementation vendor
November 26, 2009 10
Sample Consolidation Reasons
November 26, 2009 11
Sample Information Technology Infrastructure Issues
• Cost and related issues tend to dominate
November 26, 2009 12
Objectives of Analysis
• To produce an inventory of the servers and applications and identify servers and applications eligible for virtualisation/consolidation
• To ensure that the implementation of any server virtualisation architectures takes into account planned and likely IT, infrastructure, organisation and operational changes and the IT strategy
• To audit the existing server environment including performing capacity planning and performance analysis on the Windows servers
• To define a server virtualisation/consolidation operational architecture and model, including disaster recovery and business continuity, data management and recovery, monitoring and reporting, capacity management, patching,
• To identify server virtualisation implementation options and their advantages and disadvantages
• To produce a cost benefit analysis for the implementation of server virtualisation
• To identify and document disaster recovery and business continuity requirements
• To understand the applications and infrastructure to be recovered
• To produce an implementation plan including internal and external resources required
• To quantify the costs associated with implementing the solution
• To identify any infrastructural requirements and pre-requisites such as facilities and communications network
• To produce material that can be included as part of any tendering process for the procurement of a server virtualisation/consolidation solution
• To define evaluation criteria for assessing responses to any tenders
November 26, 2009 13
Infrastructure Consolidation and Virtualisation Key Issues
1. Data and storage management− All data on a SAN
− Potential for changes to backup and recovery arrangements
2. Resource allocation and reservation
3. Server monitoring and reporting
4. Business continuity and disaster recovery− Virtualisation is a key enabler of business continuity
5. Server request process management− Processes for managing requests for new servers and for capacity
planning and management
− Requests for new servers and new hardware no longer connected
6. Networking
November 26, 2009 14
Data and Storage Management
• Existing Backup Arrangements • Possible New Backup Arrangements
November 26, 2009 15
SAN Capacity And Sizing
•Virtualisation of servers drives SAN storage and I/O capacity utilisation
• Physical server HBAs shared between virtual servers
•Need to know the potential impact
November 26, 2009 16
Resource Allocation and Reservation
• Reserve resources to provide capacity for
•Growth
• Recovery at main site
• Recovery at backup site, if implemented
November 26, 2009 17
Resource Allocation and Reservation
November 26, 2009 18
Resource Management During Recovery
VM1 VM2 VM3 VM4
Limit Reservation Actual Usage
VM5 VM6 VM7 VM8
Server 1 Server 2
HA Cluster
November 26, 2009 19
Resource Management During Recovery
VM1 VM2 VM3 VM4 VM5 VM6 VM7 VM8
Server 1 Server 2
VM1 VM2 VM3 VM4
HA Cluster
November 26, 2009 20
Server Monitoring and Reporting
• Consistent approach to hardware and software monitoring for physical and virtual infrastructure
November 26, 2009 21
General Monitoring Requirements
• To get a functional view of service availability that encompasses all elements of a system or application, including hardware and software
• To create a service oriented view of key business systems, including description of service
• To present management with a comprehensive view of the availability and status of a system
• To provide management reporting on system and application status and availability
• To provide an analysis, business intelligence and reporting toolfor integrated system and application availability
• To enable end-to-end compliance with SLAs and OLAs to be determined
November 26, 2009 22
System Monitoring and Alerting Challenges
•No single view of the status of all infrastructure
•No single view of system availability
•No information and no measurements
•No collection of capacity and usage information
•No auditing of system access
November 26, 2009 23
System Monitoring and Alerting
•Monitor all elements — hardware and software
• Enable monitoring and auditing of servers and clients
•Database of problems
• Pro-active alerting
•Online reporting
•Measure usage
•Capacity management and planning
• Integrated service management
November 26, 2009 24
Business Continuity and Disaster Recovery
1. Core server infrastructure virtualised for resilience and fault tolerance
2. Centralised server management and backup
3. SAN for primary data storage
4. Backup to disk for speed
5. Tape backup
6. Two-way data replication
November 26, 2009 25
Resilience
• Virtual infrastructure in HA (High Availability) Cluster
• Fault tolerant primary infrastructure
• Failing virtual servers automatically restarted
• Dynamic reallocation of resources
• Reduces need to invoke business continuity plan
November 26, 2009 26
Business Continuity and Disaster Recovery
• Failing servers can be recovered on other site
• Virtualised infrastructure will allow critical servers to run without the need for physical servers
• Virtualisation makes recovery easier —removes any hardware dependencies
November 26, 2009 27
Sample Highly Resilient Infrastructure
November 26, 2009 28
Sample Server Processes
• Processes to support the creation and management of new and existing servers
• Provides checklist of actions
• Provides transparency
November 26, 2009 29
Networking
•Virtualising servers drives network usage
• Physical NICs shared between virtual servers
•Need to know the potential impact
November 26, 2009 30
Desktop Consolidation
•Application Delivery and Management analysis
•ADM is an integrated set of service offerings around desktop and laptop application delivery and management, encompassing a range of solutions, depending on customer requirements
•ADM examines a range of server and desktop operational and management platforms
•Deliver the most appropriate application delivery and management solution to meet customer requirements
November 26, 2009 31
ADM Analysis
•ADM model will focus on the means of delivering the application to the user
•Delivery models:−Hosted application with user access via PC or thin client
−Dynamically delivered application on request
−Hosted virtualised desktop with user access via PC or thin client
−Centralised distribution of software to clients
November 26, 2009 32
ADM Application Delivery Points
Server Desktop
Dynamically Server-Based Application
Access
Automated Distribution of
Software Updates to Desktops
Hosted Virtualised Desktop
Hosted Applications
3 4
2 1
November 26, 2009 33
Traditional Application Delivery
• Applications loaded on PCs
• Significant management overhead and cost− Applications must be updated
− Desktop operating system must be updated
November 26, 2009 34
Centralised Application Distribution and Management
• Roll-out software from central application update distribution server− Install new applications, based on roles
− Install application updates
− Update operating system
• Access via standard PC
November 26, 2009 35
Hosted Desktop
• Applications packaged and hosted on application deliver servers
• Access via thin client or PC− PC — allows local software and data
− PC — still requires operating system and updates
November 26, 2009 36
Virtualised Desktop
• Desktop virtualised and hosted− Entire desktop including operating system, applications and data
• Access via thin client or PC− PC — allows local software and data
− PC — still requires operating system and updates
• Thin client− No software
− Full desktop experience
November 26, 2009 37
Storage Virtualisation
• Simplify storage environment
• Centralisation to reduce the number of locations where data is stored to only those that are really needed
− Reduce the number of points of management and the number of physical devices
− Fewer elements to reduce the chance of error or failure, avoid the creation of islands of storage, and take better advantage of economies of scale
• Physical consolidation to smaller number of larger-capacity devices
• Application integration by moving applications from clusters or multiple linked- servers to a smaller number of storage devices
November 26, 2009 38
Storage Virtualisation
• Increase resource utilisation by combining the storage capacity of multiple disk arrays into a single reservoir of storage
• Improve productivity by enabling administrators to manage their reservoir of storage from a single user interface centrally
• Enable a tiered storage environment where the cost of the storage can be matched to the value of the data
• Assist with the consolidation of resources and simplification ofmanagement to help reduce cost and complexity
• Enable use of heterogeneous hardware providers with common server management, storage management, and copy services software
November 26, 2009 39
Storage and Connectivity Technologies and Protocols
• FCP
• iSCSI
•NFS
•CIFS
• SATA
November 26, 2009 40
Storage Virtualisation
• Common storage presentation layer across all
• Support multiple protocols across multiple physical devices
• Support multiple storage devices
November 26, 2009 41
Scope of Service to
• Site DiscoverySite DiscoverySite DiscoverySite Discovery− Server and Application Inventory− Virtualisation Architecture and
Implementation Options− Identification of Requirements− Identification of Virtualisation Exclusions− Disaster Recovery and Business
Continuity Requirements− Data Management Requirements− Quantification of Cost Savings− Definition of Virtualisation Benefits− Information Technology Strategy − Projected Server Requirements− Capacity Planning
• Consolidation ArchitectureConsolidation ArchitectureConsolidation ArchitectureConsolidation Architecture− Definition of Physical Architecture− Definition of System Management Model− Implementation Roadmap and Schedule− System Availability and Continuity of
Operations
− Detailed Delivery Plan− Infrastructure Acquisition− Virtualisation Installation, Configuration
and Implementation− Server Migration− Documentation, Training and Handover
Requirements− Operation, Maintenance, Support and
Administration Requirements− System Benefits
• Financial Analysis Financial Analysis Financial Analysis Financial Analysis − Business Case− Project Costs− Project Savings
• Draft Solution Presentation Draft Solution Presentation Draft Solution Presentation Draft Solution Presentation
• Final Solution Documentation And Final Solution Documentation And Final Solution Documentation And Final Solution Documentation And Presentation Presentation Presentation Presentation
November 26, 2009 42
Business Case Preparation
Strategic FitStrategic FitStrategic FitStrategic Fit Options Evaluation and Options Evaluation and Options Evaluation and Options Evaluation and IdentificationIdentificationIdentificationIdentification
Procurement and Procurement and Procurement and Procurement and ImplementationImplementationImplementationImplementation
WholeWholeWholeWhole----Life CostsLife CostsLife CostsLife Costs Plan for AchievementPlan for AchievementPlan for AchievementPlan for Achievement
Business need and its contribution to the organisation's business strategy Key benefits to be realised Critical success factors and how they will be measured.
Cost/benefit analysis of realistic options for meeting the business need Statement of possible soft benefits that cannot be quantified in financial terms Identify preferred option and any trade-offs
Proposed sourcing option with reasons Key features of proposed commercial arrangements Procurement approach/strategy with supporting details
Statement of available funding and details of projected whole-life cost of project (acquisition and operation), including all relevant costs Expected financial benefits
Plan for achieving the desired outcome with key milestones and dependencies Contingency plans Risks identified and mitigation plan External supplier plans Resources, skills and experience required
November 26, 2009 43
Benefits
• Produce design before embarking on implementation
•Milestone before proceeding further
•Allow detailed cost and time estimates for implementation project
•Give certainty to costs and schedule
• Enables controlled innovation
•Vendor independent analysis and design
• Build on proven architecture design skills and experience
• Backed by architecture design methodology
November 26, 2009 44
Infrastructure and Application Consolidation Analysis Service Delivery Process
• Six steps− Assessment
− Inventory
− Workload Data Collection
− Analyse Data
− Design and Specify Solution Including Options
− Documentation and Planning
Inventory AnalyseRecord Documentation and Planning
Assessment Design andSpecify
November 26, 2009 45
Sample Server Utilisation Analysis — Multiple Different Physical Server Models
0.00
20.00
40.00
60.00
80.00
100.00
120.00
Perc
enta
ge U
tilisation
APDAPP1 APDAPP2 APDAPP3 APDDOMAIN APDEXCHANGE APDEXCHANGE2K
APDFILE001 APDGEMQ APDMQ APDPRINT APDREP1 APDTEST01
APDTEST02 APDWEBAPP1 APDWEBAPP2 APDWEBTEST APDWEBTEST02 APFSEXCH1
November 26, 2009 46
Server Utilisation Normalisation and Consolidated Sizing —Including Business Continuity
0.00
5.00
10.00
15.00
20.00
25.00
Perc
enta
ge U
tilisation (C
om
mon
Serv
er M
odel)
0
1
2
3
4
5
Num
ber of C
onsolidate
d S
erv
ers
APDAPP1 APDAPP2 APDAPP3 APDDOMAIN APDEXCHANGE APDEXCHANGE2K APDFILE001
APDGEMQ APDMQ APDPRINT APDREP1 APDTEST01 APDTEST02 APDWEBAPP1
APDWEBAPP2 APDWEBTEST APDWEBTEST02 APFSEXCH1 Consolidated Servers
November 26, 2009 47
Infrastructure and Application Consolidation Analysis Service Delivery Process
• Assessment − Questionnaire
− Qualification of scope
• Inventory− Install tools to gather application and server inventory
• Workload Data Collection− Collect application and server utilisation and performance information
• Analyse− Analyse inventory and performance data
• Design and Specify− Identify options and architectures
• Documentation and Planning− Produce detailed planning and financial analysis
November 26, 2009 48
Deliverables
• Documented site audit including capacity planning and performance analysis of applications and servers
• A defined and documented application consolidation architecture that includes disaster recovery and business continuity, data management and recovery, monitoring and reporting, capacity management
• Quantified costs for implementing the solution identifying all costs: hardware, software, infrastructure, services
• Implementation options and plans
• Quantified cost savings
November 26, 2009 49
Sample Analysis and Design Report Contents• 1. Executive Summary
• 2. Introduction, Purpose and Scope− 2.1 Objectives of this Analysis− 2.2 Summary of Information Sources− 2.3 Definitions
• 3. Site Discovery
• 3.1 Server and Application Inventory− 3.2 Server Configuration− 3.3 Data Storage and Access− 3.4 Existing Information Technology Structure and
Operations− 3.5 Software Products and Vendors− 3.6 Infrastructure
• 4. Current Issues and Requirements
• 4.1 Business Requirements and Issues− 4.2 Information Technology Requirements and Issues− 4.3 Information Technology Strategy and Planned and Likely
Developments
• 5. Capacity Planning and Performance− 5.1 Server Performance and Capacity− 5.2 Server Capacity Projections− 5.3 Server Virtualisation Anomalies, Issues and Resolutions− 5.4 Server Virtualisation Options and Advantages and
Disadvantages
• 6. Server Virtualisation Architecture− 6.1 Virtualisation System Architecture and Configuration− 6.2 Server Virtualisation Solution Design− 6.3 Definition of Physical Architecture− 6.4 Virtualisation Architecture and Implementation Options− Reporting and Administration Model
− 6.5 Identification of Virtualisation Exclusions− 6.6 System Availability and Continuity of Operations− 6.7 Data Management, Backup and Recovery− 6.8 Definition of System Operation, Management,
• 7. Implementation Plan and Schedule
• 7.1 Project Plan and Schedule− 7.2 Project Organisation and Structure− 7.3 Project Resources− 7.4 Project Assumptions− 7.5 Project Risks− 7.6 Project Issues− 7.7 Project Dependencies− 7.8 Testing and Cutover
• 8. Financial Analysis− 8.1 Project Costs− 8.1.1 Infrastructure Requirements and Costs− 8.1.2 Software Licence Costs− 8.1.3 Project Costs− 8.2 Project Savings and Benefits
• 8.2.1 Server Reuse• 8.2.2 Server Acquisition Deferral• 8.2.3 Environmental Savings• 8.2.4 Operations and Management Savings• 8.2.5 Project Benefits
• 9. Tendering for Server Virtualisation− 9.1 Tender Technical Material− 9.2 Tender Response Evaluation− 9.3 Identification of Possible Vendors
November 26, 2009 50
Next Steps After Analysis and Design
November 26, 2009 51
Analysis and Design Effort
•Duration — 20 - 40 days — depends on−Requirements
−Complexity of existing infrastructure
−Backup, recovery and data and storage management
−Business continuity and disaster recovery
− Level of design detail
− Include a sample tender
−Business case
−Analyse applications
− Include operations and support processes
•Complete analysis, design and documentation with options and implementation plan