Enterprise Management:- Where have we been?- Where are we now?- Where are we (or where should we be) going?

Tom BishopChief Technology

OfficerVIEO, Inc.

2

Systems Management Evolution’80s

“Big Iron”Early ’90s

Client/ServerLate ’90s

Web / n-tiers2000’s

Fabric Computing

Emphasis Tactical: Configure and Monitor IT ResourcesStrategic:

Optimize Business

Organization / Scope

IT Line of Business

Monolithic, homogeneous, server-centric

computing

Computing Paradigm

Distributed, heterogeneous, server-centric computing

Standards-based fabric [+ grid]

computing

Emerging new standards; proliferation of vendors and tools; decentralized

ownership and control; little instrumentation -- low QoS

Standard; centralized;

policy-based -- high QoS

Product Attributes

Active, policy-based; auto-provisioning;

self-healing; central-ized -- high QoS

Source: Gartner & VIEO

3

1989

Powerful Parallels2002

DecentralizedIT withoutBusinessTools orSkills

n-tiered, Web-Based Modular

Computing

Inadequate Systems

Managemen

t Solutions

EmergingStandards

Serverdisaggregation

Huge Anticipated Problem Huge Real & Anticipated Problem

Mainframedisaggregation

Client/Server

Computing Emerging

No Systems

Management Solutions

Centralized IT without Technical Tools or Skills

EmergingStandards

Management of a static collection of distributed resources in a static environment previously on the mainframe. Due to changes in:• Computing cost• Physical topology• Application architecture (client/server)

Management of a dynamic collection of distributed resources in a dynamic environment previously inthe client/server environment.Due to changes in:• Computing utilization• Physical topology• Application architecture (web services)

4

“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

"Systems management is a promise the industry has not delivered on despite years and years of talking about it."

Steven MacKay, Sun

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

“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:

1.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?

Too many alligators!

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

9

The “drier swamp” approach says: it’s really about increasingthe alignment betweenbusiness and IT

In other words, it’s about focusing IT resources onapplication certainty and Application Quality of Service: 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

How Does it Work?HardwareAssisted

Capability

UserSpace

Applications & Middleware

UnixOS

LinuxOS

WinOS

UMN “Fabric”

KernelSpace

2nd G

enerationS

ystem M

anagement

Managem

ent Appliance

15

Visibility, Instrumentation & Control

AAIM agent traffic

AAIM host agent

Normal network traffic

• 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

Architectural Approach

Mgt at appropriate speeds

Server-basedSoftware-only Mgt Ntwk Device

Separate, scalable execution environment

Priority access to and control of application

resourcesImmune to changes in application environment

Complete visibility with no overhead

Low cost on going maintenance & upgrading

Timely application resource measurement

Plug and play install, deployment & use

Dynamic application and network topology

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Impossible

Partial

Impossible

Impossible

Impossible

Impossible

Impossible

Impossible

Impossible

Impossible

Yes

Impossible

Partial

Impossible

Yes

Impossible

Partial

Impossible

Capabilities

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 (and failures) 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

initiallife cycle

executable runningappstatus

sub-model

installation

runtime model config

ura

tion

indica

tion

history

systemsfunctionstructure

dataexternal systems

21

Example: Logical View

DatabaseLayer

Business Layer

Presentation LayerPresentation

(session handling, navigation)

Database

Webserver

Business(logon, search, modify)

Cache

Middleware(DB access, communication)

CommPlugIn

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

1. 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.

2. Industry ratification of an architecture and standards profile for #1.

3. Identification of standards gaps and an action plan to close gaps and insure interoperability.

24

An AQoS Mgmt Standards Initiative

0 Framework High-Level AQoS Mgmt architecture

1 Application Knobs and Gauges

2 Application AQoS specification standards

3 Application Distributed application management

4 OS Knobs and Gauges

5 OS Distributed application services

6 Storage Knobs and Gauges

7 Management Standard behaviors

8 Management Tool interaction processes/protocols

9 Human Agents

Policy template standards

10 Human Agents

Business dashboard standards

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

(atleast in thenear term)

itwill need

to bedelivered

asan

appliance