Enterprise Management: - Where have we been? - Where are we now? - Where are we (or where

1. Enterprise Management: - Where have we been? - Where are we now? - Where are we (or where should we be) going? Tom Bishop Chief Technology Officer VIEO, Inc.

2. ’80s “Big Iron” Early ’90s Client/Server Late ’90s Web / n-tiers 2000’s Fabric Computing Strategic: Optimize Business Tactical: Configure and Monitor IT Resources Emphasis Standard; centralized; policy-based -- high QoS Emerging new standards; proliferation of vendors and tools; decentralized ownership and control; little instrumentation -- low QoS Active, policy-based; auto-provisioning; self-healing; central-ized -- high QoS Product Attributes IT Line of Business Organization / Scope Monolithic, homogeneous, server-centric computing Standards-based fabric [+ grid] computing Computing Paradigm Distributed, heterogeneous, server-centric computing Systems Management Evolution Source: Gartner & VIEO

3. n-tiered, Web-Based Modular Computing Client/Server Computing Emerging Management of a static collection of distributed resources in a static environment previously on the mainframe. Due to changes in: Management of a dynamic collection of distributed resources in a dynamic environment previously inthe client/server environment.Due to changes in: Decentralized IT without Business Tools or Skills Centralized IT without Technical Tools or Skills Server disaggregation Mainframe disaggregation • Computing utilization • Physical topology • Application architecture • (web services) • Computing cost • Physical topology • Application architecture • (client/server) Inadequate Systems Management Solutions Emerging Standards No Systems Management Solutions Emerging Standards Powerful Parallels 2002 1989 Huge Anticipated Problem Huge Real & Anticipated Problem

4. "Systems management is a promise the industry has not delivered on despite years and years of talking about it." Steven MacKay, Sun “Management, management and management... Effective management solutions are needed that handle the entire infrastructure as a coherent whole.“ David Black, EMC “Management is the biggest single issue for blades.” Dave McAllister, Egenera "The new OS will be a multisystem manager that controls resources over the network. It’s a quality-of-service manager that will be all-knowing enough to be able to generate a service-level guarantee.“ Lin Nease, HP

5. Application Quality of Service: A holistic view of the delivery of application services to end-user constituents, consisting of the following operational characteristics: • Reliability & availability • Performance • Resource utilization • Scalability • Security • Well-behaved lifecycle

6. “When you’re up to your ass in alligators, it can be hard to remember that your original objective was to drain the swamp”

7. Two ways to think about this problem: • fewer (or nicer) alligators 2. a drier swamp

8. With all the tools and people, why are IT organizations still challenged to deliver consistent, desired AQoS? • They are flooded with raw instrumentation data, but not actionable information • Problem detection, analysis and resolution is still reactive and done at human speeds • It is virtually impossible to directly correlate application services to business performance Too many alligators!

9. The “drier swamp” approach says: it’s really about increasing the alignment between business and IT In other words, it’s about focusing IT resources on application certainty and Application Quality of Service: Line of Business Adaptive Management of the Application + Infrastructure

10. Application infrastructures will continue to disaggregate and increase in complexity. How must AQoS be managed? • With deep visibility into, and control of, the entire application environment • Intelligently, based on knowledge of the environment, learned behavior patterns, and current trends • Automatically, at machine speed • Reliably. AQoS management must be “always on” • Adaptively, based on business policies and dynamic business needs

11. Actionable Information vs. Raw Data

12. The secret sauce: Distinct (or overlay) Management Network The Distinct Management Network transforms application management integration from a complex and expensive technical challenge into the strategic ability to manage customer-facing business processes across and beyond the enterprise…in fact it makes Adaptive AQoS Management possible! Re-wire for Manageability

13. Management in the interconnect • Convergence of network & systems management; integral part of the infrastructure • Integrated application-aware networking and management capability (deep packet inspection)

14. Applications & Middleware Management Appliance Unix OS Win OS Linux OS 2nd Generation System Management How Does it Work? Hardware Assisted Capability User Space Kernel Space UMN “Fabric”

15. Normal network traffic AAIM host agent AAIM agent traffic Visibility, Instrumentation & Control • Integrated CIM-based application resource inventory • Achieving AQoS through dynamic use and control of application resources • Distinct and dedicated execution environment for management • Discovery, manageability, and user interface hosting

16. Limitations of Software Tools • Limited visibility into entire application infrastructure • Lack priority access to and control over application resources • Must continually probe into application environment • Often are impacted by same conditions that threaten AQoS

17. Impossible Partial Impossible Impossible Impossible Impossible Impossible Impossible Impossible Architectural Approach Capabilities Software-only Server-based Mgt Ntwk Device Impossible Yes Mgt at appropriate speeds Separate, scalable execution environment Yes Yes Priority access to and control of application resources Impossible Yes Immune to changes in application environment Partial Yes Complete visibility with no overhead Impossible Yes Low cost on going maintenance & upgrading Yes Yes Timely application resource measurement Impossible Yes Plug and play install, deployment & use Partial Yes Dynamic application and network topology Impossible Yes

18. Why An Appliance: Thinking “inside the box”… • Layer 2-like network device and application-aware management • Self-contained and secure • Deep visibility & instrumentation in real-time (no overhead) • Priority access to (and control of) application resources • Insulated from changes (andfailures) in app environment • Built-in analytics and optimization technology • Readily scalable • Supports 3rd party management interfaces • Low TCO • Rapid, easy deployment/use  No software distribution • No additional servers  Downloadable S/W updates

19. Current Standards Situation • Convergence of cluster/modular/blade architecture with autonomic/self-managing/utility computing requires new management paradigm • Existing major standards bodies are mired in legacy client-server management architectures, do not grasp the problem, and will not seize the opportunity to pioneer a new management paradigm • New management paradigm must be standardized to span data center network/server/storage platforms and distributed applications software—no single company rules the data center, requires cross-industry effort Model-based Management

20. An Application Runtime Model app status executable running initial life cycle installation sub-model runtime model systems configuration indication history function structure data external systems

21. Example: Logical View

22. A Charter for an AQoS Management Initiative • Develop an architectural framework, standards profile, and appropriate standards for an autonomic approach to managing (web services-based?) applications across one or more modular, virtual, dynamic data centers within one or more real-time enterprises.

23. Goals for an AQoS Mgmt Initiative • Recognition/acceptance/endorsement of autonomic approach to managing web services-based applications across one or more modular, virtual, dynamic data centers within one or more real-time enterprises. • Industry ratification of an architecture and standards profile for #1. • Identification of standards gaps and an action plan to close gaps and insure interoperability.

24. An AQoS Mgmt Standards Initiative

25. Summary

26. An AQoS Solution… • Notifies IT of actual or pending AQoS problems • Prevents many application service problems • Reduces outage duration when it cannot be avoided • Increases resource utilization and ROI • Reduces cost of delivering desired AQoS • Helps IT and LOB establish, negotiate, measure, and enforce AQoS targets • Accounts for resource use by application and user • Scales and adapts to future “utility” infrastructures

27. Self-Learning and Adaptive

28. The long-term recipe for success: • 1. Focus management on AQoS… • 2. Built on standard management • models/design patterns… • 3. Delivered over a distinct • management network… • 4. Fed by a standards-based • inventory of gauges and knobs

29. Of course, it should be simple, so (at least in the near term) it will need to be delivered as anappliance