Capacity and Demand Management
•Transferir como PPT, PDF•
13 gostaram•21,672 visualizações
Service based / modeled IT operations demands that Infrastructure needs are catered to with minimal disruptions and loss of user experience. Demand and capacity management for a critical cog in IT / service design to ensure that the service / infrastructure is fully available to users through its lifecycle
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Capacity and Demand Management
Semelhante a Capacity and Demand Management (20)
Mais de Vishwanath Ramdas
Mais de Vishwanath Ramdas (20)
Último
Último (20)
Capacity and Demand Management
- 1. Demand & Capacity Management Vishwanath Ramdas
- 2. Capacity – Demand Management framework Identify usage patterns both short term and long term translate customer demands into workloads put upon critical components Monitor and collect performance data of critical components in current configuration Determine the current and future resource needs. Ensure resources are acquired & implemented in a timely and cost-effective manner Demand Management Performance Management Workload Management Resource Management
- 5. What are the criticality Maps to setup monitoring? Demand Management .b 1 Service Catalog developed for a petrochem - MNC Sample of a developed services catalog as part of SLM workshop. The Service catalog workshop defined the parameters of each service and listed all key IT services and created an SLA for each service
- 14. Different Monitoring approaches for critical applications System monitoring, setup measurement agents for capturing, CPU, memory, storage space, process metrics and OS metrics on the server & network nodes. .a .b 4 Different ways to monitor infrastructure. End user end to end transaction monitoring. This is done through remote agents that create synthetic transactions and trap various response times for each use case transaction. End User Monitoring was setup for a large IT services / consulting organization for their central – web project management software Performance Management
- 15. Different Monitoring approaches for critical applications Performance Management Capture logs and traces from web servers and DB servers to capture both response times for specific transactions and the patterns of usage of the resources. What are end users demanding? Transaction tracing within application servers to capture execution of software code on systems. Used in software performance engineering in load simulated environments. Used with prior care in production environments as these monitors can consume significant resources. .c 4 .d Different ways to monitor infrastructure.
- 16. Samples of Monitoring setup for different clients. Resource Management 4 Typical capacity monitoring done for a large US MNC. Trend view of hosting center bandwidth consumption from AT&T services. These trends are used as inputs for fine tuning the demand models and for capacity planning. Capacity usage trends for staff usage for the network service, showing available capacity and usage. Such a trend was used to re-contract and redeploy resources in network management and support
- 17. Modeling Capacity (Six Sigma: Process Capability) Identify critical apps managed by the DC, define performance criteria and setup the monitoring systems Map and identify demand scenarios in critical apps [ in pilot – 2/3 apps] – monitor demand - sys monitors Correlate application into infrastructure elements and collect data on infrastructure Join demand & infrastructure performance and monitor capacity metrics w.r.t limits App - DC inventory 1 2 4
Notas do Editor
- Usage patterns would mean use Scenarios and cases by end users both in volume terms and functionality terms. There by identify critical services from a capacity management perspective.
- In this presentation we presume that there is no services listed and catalogued. You may already have a well defined catalogue which can form the starting point for discussions This exercise has value beyond the current requirement of capacity management. This exercise ensures a proper SCatM and SLM. The next step is to furnish the catalog with data to help identify and classify services and there by the infrastructure from a monitoring perspective.
- The key parameters in classifying services is shown here. There are 3 areas [ describe ] for service classification overall out of which 2 apply to capacity management as marked [ describe] We would bring pre-defined templates based on experience and standard practices like ITIL. We would then custom fit it to the Cap One Context.
- Here is a sample Service catalog created for a Petrochem Major where we helped them list and present their services to their business users. The presentation format was an interactive MS Powerpoint document and would finally be built into a web platform.
- Once the parameters are finalized, the team then needs to collect the service information for these parameters. [Desscribe] Capacity critical information would be derived from technical functions and the business parameters would be finalized with the central team [ who should have a good perspective into the business and the business impact of the applications
- Based on the parameters, we then use some simple arithmetic functions to derive Criticality ratios for each service and present it in a 2-D domain. [Describe] Typically this map is created in phases taking most important obvious service first and then following up with lesser critical applications.
- We would like to introduce a concept called CCIM – which is very simlar to Component Failure Impact Analysis and QFD. It is a core asset – Not only Capacity but Business Value for portfolio SLM and IT Governance. The artefact attached is a sample showcasing how CCIM would look and the values there would be numbers rather than classifiers. The CCIM would have the service Breakdown along the left column derived using usage scenarios and cases & sequence Diagrams for each service The infrastructure breakdown is thereby built [ forming a CMDB like model]
- CCIM looks at the supply side relationships WE would need to model the demand side to capture how business drivers affect service usage volumes. Typically there are 5 end measures for the services
- Ensure that changes to the infrastructure are incorporated in the framework.
- Designed and sized the hosted servers for a Education Services provider. The objective was to create a deployment road map based on the demand growth. Sat with the end customer team to identify the key use cases for the application. Also derived the relation of users to concurrency Ran multiple performance tests and a pilot environment. The performance tests had runs at different levels of concurrency and marked the workload at which utilization was 70% also ran multiple tests with varying database sizes. Identified the business drivers with the customer, based on user population profile, derived concurrency and database size with time. Transferred the performance data from the tests into EXCEL application for both application , network and database. Developed a mathematical transformation that would calculate system specifications for different business scenarios. Arrived at a road map for the client on how the should approach the hosted for the next 4 years. Based on a business growth plan. Created a future proofed architecture to minimize re-build and obsolescence.