2. Agenda Application management discipline Industry trends Application management challenges What is changing? VMware approach – Active application management Q&A
3. What is application management An evolving discipline, separate from ESM, and can be defined as a the process and use of tools to: design; develop; test; provision; monitor/diagnose; and change/patch of apps & complex business transactions to ensure service quality as experienced by end-users’ and businesses’ expectations (often formalized as SLA’s). More importantly AM will dramatically evolve/change as result of new development methodologies & ISV/SaaS and Cloud.
6. Evolution of applications Saas Apps .Jar Packaged Applications .War .ear Paas CustomApplications PaaS WS AS DB AS OS OS OS OS Cloud Applications IaaS
7. Custom Applications destinations Highly controlled Applications Highly productive Applications PaaS IaaS Complete control of the OS, MW, No. of VMs, VM Size Little or no control on MW, configuration, machines. Consumer owns only the code.
8.
9.
10. How can I control cost of running our applications?
11. How can I meet the service level and compliancy requirement?
12.
13. I do not want to manage my infrastructure scalability for my application
14. I need Framework and development tools to increase & simplify my app development and increase productivity 8
16. Distinction of ownerships Application Owner App Ops Application Operating System VI Admin Infra Ops (NOC) VMware ESX/ESXi Infrastructure Admin
17. The emergence of App Ops Infrastructure is available in no time Pressure moves higher in the stack to set up a complete environment App Ops will be focused on managing the application itself, completely abstract the underlying infrastructure Focus on delivering value to the business – enabling new capabilities, assuring service levels and not setting up infrastructure
19. VMware’s Active Application Management strategy for IaaS The move towards cloud and use of modern application frameworks and methodologies is creating an opportunity to think differently on managing applications Manage applications holistically and separately from the supporting infrastructure Help manage applications that move across, and run across, public and private clouds Horizontally integrates management across deployment, monitoring and change Collaborate Monitoring Policy Add Capacity Optimize Isolate, trouble shoot, remediate, change Deploy Components, Topology, resource allocation, environment binding . Monitor Resources, compliancy, transactions, users, change impact Topology Update Reboot Burst compute Scale Policy
20. Application provisioning load balancer load balancer appserver appserver appserver worker Automated model driven Provisioning on Hybrid IaaS 1 cache database messaging Best-practice Application templates for deployment patterns Standardization of heterogeneous middleware, packaged apps, OS 2 3 Collaborative, Integrated App Management 4
21. Establish “your clouds” Define available clouds as potential deployment environments Establish a library of standardized application components and scripts
22. Build your app Define relationship to create a topology and Set configurations and parameters Select components from a standardized catalogue
24. Cloud application performance monitoring load balancer load balancer appserver appserver appserver worker Consolidated application management console spanning business critical KPIs (Cost, change, performance, compliancy…) 1 cache database messaging 3 4 2 Closed loop system for optimization- scale, restart, burst, roll back Application life cycle Spring, Deploy, Monitor Consolidated and integrated monitoring across all layers
25. Applications dashboard Consolidated dashboard presenting an overall health view Key application oriented KPIs to provide full visibility Confidential 19
26. Auto generated topology map Visualize health on each component of the app Dynamically pick up business transactions and provide them with health scores Automatically detect application components and relationships Confidential
27. Detailed monitoring Overlay config and code change information on performance graph Simple navigation makes it easy to zoom in on relevant areas Confidential 21
28. Summary IaaS will drive the adoption of the cloud operating model which define clear separation of ownerships It requires a new approach – let go of some operational aspects in favor of others An horizontal approach is best suited for the cloud operating model Collaborate Monitoring Policy Add Capacity Optimize Isolate, trouble shoot, remediate, change Deploy Components, Topology, resource allocation, environment binding . Monitor Resources, compliancy, transactions, users, change impact Topology Update Reboot Burst compute Scale Policy
Editor's Notes
CIO and Company ExecutivesWe constantly need to find new and innovative ways to monetize our core competencies. Ideas for new features are coming through all the time, and for us to be able to turn those features around and get them to market quickly is absolutely keyCan you help make my company more competitive?Can you help make my company more profitable?Can you help remove risk from my IT strategy?Web and IT OperationsOur application infrastructure is not scaling with demand. Can you help?I need to reduce the cost of running all of these applications. Can you help?DevelopersThe business is asking us to get applications to market faster. Can you help?We need to deliver business data faster on every new project. Can you help?We need to build modern applications like people use at home. Can you help?
As applications get virtualized and pushed into a cloud (Private or public) there is a very clear separation between the infrastructure management paradigm and the application management one – they are no more intertwined.The infrastructure managers are provider of compute platform for the VMs running on them and should not care what is in that VM.The Application owners do not care where physically or on which HW their applications are runningThere is however the need to provide visibility to both sides of the wall as to what is happening on the other side: Application owners need to know the platform is indeed providing adequately to the demand of the application (Compute power, I/O, disk latency etc..) in a clear aggregated matter. The Infrastructure owner will need to know the Application is running well if they conduct change to the platform
The separation of Application and Infrastructure (Cloud provider / cloud consumer model)By moving to an horizontal approach, customers will able to gain a lot more control on the Application and adapt it to the business needs (Scale & Remediation)The motivation of the separation and focus on the Application layer as a complete operational stack it to allow the Application owners and developers achieve better agility, more flexibility, control and performance and ultimately migrate maintanance cost to innovation
The separation of Application and Infrastructure (Cloud provider / cloud consumer model)By moving to an horizontal approach, customers will able to gain a lot more control on the Application and adapt it to the business needs (Scale & Remediation)The motivation of the separation and focus on the Application layer as a complete operational stack it to allow the Application owners and developers achieve better agility, more flexibility, control and performance and ultimately migrate maintanance cost to innovation