ITIL Capacity Management for the Newbie For those new to system z. Charles Johnson Principal Consultant

Transcription

1 ITIL Capacity Management for the Newbie For those new to system z Charles Johnson Principal Consultant

2 Agenda ITIL Definition of Capacity Management Capacity Management and ITIL activities Difference between Capacity Management and Performance Management? How to be successful in Capacity Management Talking with Business stakeholders Creating a baseline and it s effect on forecasting? Different types of forecasts? Examples of Capacity Management scenarios for Mainframe

3 Performance Management vs. Capacity Management Performance Management: Alert problems Capacity Management: Prevent problems Response time Workload volume Resource usage Performance Management: Alert Forecasting KPI, Threshold Break Out Steady Incremental? Time Action: Proactive management Optimize before problem happened => CapMan Analyze: Provide root cause analysis and countermeasures => CapMan Time

4 Capacity Management Business Capacity Predict future capacity requirements from the business demand Revenue Business Index Forecasting required capacity according to Business plan # of Users Workload Management Service Capacity To manage items in the input directly to service a component capacity management, improved management. Response Availability Maintain SLA L.O.B Service Management Component Capacity Capacity information of each component to monitor and to manage change in. Storage size CPU Usage Component Resource Monitor, Analyze Optimize, Upgrade, Increase Resource Management

5 Key Performance Indicators Your Requirement Manage by KPI for Prevent problem occurring (Proactive Management) Operate with optimized resources (Saving Cost) Shorten MTTR if problem happened (Increase Availability) Know Current Understand whether the current system is healthy or not Resource Workload Well Balanced Service Know how much room remains Forecast the limit Find KPI to represent your system Correlation Set the threshold of the KPI Trend Analysis & Modeling Implement Capacity Management

6 athene ES/1 Forecasting

7 Quality of Service for Stakeholders

8 Forecasting Quality of Service to Stakeholder Modeling Trend

9 athene ES/1 Model Baseline SYSA CPU/CEC Modeling Hardware & I/O

10 athene ES/1 Model Increase ProdOnl 5% CPU/CEC Modeling Hardware & I/O

11 athene ES/1 Model Results CPU Change CPU/CEC Modeling Hardware & I/O

12 12 Capacity Management - Activities Business Service Component Monitor Analyze Tune Demand Management Modeling Application Sizing Implement Capacity Plan Capacity Management Information System (CMIS)

13 Models A model is a simplification of reality, built for a specific purpose

14 Modeling vs. Trending Trending Easy to do Scales well for multiple systems e.g. Windows, UNIX Easy to alert on No relationship to the performance (service) of a system or application Looks at just one metric Modeling Relates service to utilization View whole system interactions ITIL recommends modeling Moderate effort

15 Spreadsheet analysis Limitations occur when too much of too many types of data must be analysed and reported on repeatedly

16 Analytical Modeling Workflow Technical & Business Inputs Current System Current Configuration Technical & Business Inputs Expected System Expected Configuration Actual Inputs Actual Configuration Measure and Compare with Predictions Build and Calibrate the Model Describe the expected system Modify Model and Predict Performance Measure and Compare with Predictions

17 Modeling A model cannot answer all questions about a system All modeling studies should have defined objectives and requirements What questions will the model answer? How accurate do the results need to be? How long do you have to produce results? What components need to be included? What data is available and how can it be used? What are the limitations and assumptions?

18 Modeling A good modeling study requires a good understanding of the components involved Hardware Software Workloads Business volumes - Planners, company reports Workload volumes - Users, logs, audit trails Service Levels - SLAs, users, monitors, logs, staff Resource usage - System monitors New Systems - Development, users, other sites

19 Modeling Use the simplest modeling technique that will satisfy requirements Include more detail for components that are most likely to impact the system Make assumptions and abstractions where needed and justified Remember that modeling tools are only as good as the analyst using them Understand: Requirements > System > Data

20 Modeling Steps Build > Calibrate (debug) > Validate > Utilize > Document

21 Modeling Steps Analysis performed with the model is used to answer questions and examine system behavior Standard uses for systems models Determine system capacity Find system bottlenecks Examine system behavior

22 Modeling Results Present finding in an easy to understand fashion List requirements Defined terms, measures, and statistics Explain assumptions Data sources Simple charts Conclusions

23 Model Documentation Create additional content as needed Objective of the study Inputs and outputs Internal details of the model Calibration and validation details Relevant information learned Reason for using model type and technique Analysis details

24 Modeling Failures Why modeling studies fail Insufficient data Model does not accurately represent system Does not answer right questions Not completed in timely manner Not credible Lack of management support

25 ITIL Capacity Management Business Capacity Predict future capacity requirements from the business demand Revenue Business Index Forecasting required capacity according to Business plan # of Users Workload Management Service Capacity To manage items in the input directly to service a component capacity management, improved management. Response Availability Maintain SLA L.O.B Service Management Component Capacity Capacity information of each component to monitor and to manage change in. Storage size CPU Usage Component Resource Monitor, Analyze Optimize, Upgrade, Increase Resource Management

26 Capacity Reporting Technical vs. Services Gathering the necessary data Roadblocks encountered Weaving technical and services data effectively

27 Gathering the necessary data Business objectives Current performance data Data center forecasts Lines of Business

28 Roadblocks Encountered Business objectives not defined Performance data not consistent Lines of Business reluctance to provide information Lack of credibility in Capacity Planning process

29 Effective Service Levels Managing KPIs What are KPIs? How to determine KPIs? Types of KPI reporting methods?

30 Key Performance Indicator Measurements, agreed to beforehand, that reflect the critical success factors of an organization Not necessarily one metric, can be a relationship Key Performance Indicators Must Be Quantifiable Reflected in a scorecard

31 Key Performance Indicators Business KPIs, CSF, QOS Services Aggregate to Applications Demand Management Component Aggregate to Transactions System Measurements - DATA

32 Demand Management Providing knowledge How does Demand Management fit into Capacity Reporting? Data needs for effective Demand Management reporting

33 Goal Work with the Capacity process to ensure value is created by balancing the available capacity with the demands of the business

34 34 What is the Story? What is happening in the current environment Concise information Display forecasts Trends Models Gather further information

35 35 Types of Data required Technical data Current History Business metrics Current Forecast Key Performance Indicators Threshold levels

36 36 Different Capacity Plans for different audiences C level executives Information concise Elevator talk Information to the point / summary and findings first Do I need to spend more money? Leave detail reports in pocket Business owners What are the trends for my area? How does it affect my area? What do I need to budget for? Technical Show me the details Show me the trends

37 37 Different presentation mediums Dashboards / Web portals More suited for technical staff and business users Different look for each area Word documents More suited for C level executives Upfront summary is critical Historical document PowerPoint documents Used for different types of presentations Good for discussion groups What is left out?

38 38 Display of different presentation types

39 39 Management Overview Applications

40 Application Summary Arrival 1 Arrival 2 Arrival 3 Final Comments Estimating Accounting Reporting Mid-Tier Banking Breakpoint 15K users; Load balancing utilized across servers, Load balancing utilized across servers, incremental infrastructure Load balancing utilized across servers, incremental infrastructure Load balancing utilized across servers, incremental infrastructure Breakpoint 7500 users, incremental infrastructure * Scaled horizontally

41 Application Summary Arrival 1 Arrival 2 Arrival 3 Final Comments Call Center Infrastructure data patterns indicate spikes to be monitored and assessed in next model Warehouse Data Mart I/O bottleneck; new architecture I/O bottleneck; investigation in progress Sales History I/0 bottleneck; investigation in progress

42 42 Dashboard

43 43 Dashboard Overview Scorecard Detail

44 44 Modeling Scenario

45 45 Model oracleq000 10% growth server change

46 46 Model Linux server change & disk change