Slides

EOT_PW_icon.ppt | 1/4/2007 | 1

BOEING is a trademark of Boeing Management Company.Copyright © 2007 Boeing. All rights reserved.

Quality of Service (QoS) Management for

Enterprise Service Level Management (SLM)

Guijun Wang, Ph.D.Technical Fellow

Boeing Phantom WorksSeattle, WA 98124

11th SOSoRNet Workshop - Advances in Quality of Service Management King's College London, 22-23 April 2008

EOT_PW_icon.ppt | 2

Engineering, Operations & Technology | Phantom Works

Copyright © 2007 Boeing. All rights reserved.

E&IT | Networked Systems Technology

Outline

• QoS Management Concepts: QoS, QoSM, SLA, SLM• QoS Management Issues• Related Work• QoS Management Framework• QoS Management Architecture • QoS Characteristics, Specification Language, and

Policy Management• Integrate QoS Management with Enterprise

Architecture, Domain, and Infrastructure for SLM• Conclusions• Future Work

EOT_PW_icon.ppt | 3




QoS Management Concepts

• Quality of Service (QoS) is the perceived or measured quality by users or applications expressed in QoS characteristics like performance, reliability, timeliness, and security.

• QoS Management is to provide strategies, tactics, and algorithms to enable networked systems to deliver best possible outcomes for all concurrent users and applications in recognition of their differences in QoS characteristics: differentiation and guarantee.

• Service Level Agreement (SLA) defines service providers and consumers involved, QoS contracts, and obligations.

• Service Level Management (SLM) is a process that involves the creation of SLAs, provisioning of system resources, management of system QoS to meet the demands specified in the SLAs.

EOT_PW_icon.ppt | 4




QoS Management Issues

• Design Time Issues • Specifications: develop QoS Framework, Architecture, & Languages• Modeling: understand QoS characteristics of services and their

compositional effects• Profiling: understand QoS characteristics under various load and

resource conditions• Developing Policies: specify rules and constraints that govern the

behaviors of services and their relationships with consumers

• Runtime Issues: • Policy-based admission control• Resource Management• Monitoring, Diagnostics, and Prognosis• Automation and Adaptation

• Architecture (SOA), Domain, and Infrastructure Issues• Web Services: description and composition• Domain Services: characterization and resource allocation• Infrastructure Services: differentiation and guarantee

• Key to Enterprise SLM is a mission driven, autonomous, and integrated QoSM approach

EOT_PW_icon.ppt | 5




Related Work

• Foundational work: OoS Management Concepts and Framework in ISO, RM-ODP, OMG, OASIS WS-Reliability

• Research work in SLA/SLM, Web Services, Enterprise Monitoring

• Research work in modeling and instrumentation of QoS metrics at design time and use them as the basis for runtime verifications

• Research work in runtime QoS management at the middleware and network levels

EOT_PW_icon.ppt | 6




QoS Management Framework and Architecture

EOT_PW_icon.ppt | 7




QoS Management: Demanded vs Offered

• View QoS as demanded & offered to highlight QoS management issues• Demanded: express requirements

• Determine QoS requirements• Express QoS requirements

• Offered: provide QoS contracts of services• Allocate Resources: Computation, Storage, Comm., Energy• Design and Activate Mechanisms: controls (e.g., access,

admission, upgrade, downgrade, shed, drop, suspend, resume), transformations (e.g., compression, encryption), and resource allocations

• Research issues• A framework that separates and unifies Architecture, Domain, and

Infrastructure QoS concerns• A common language for expressing QoS requirements and offered

QoS contracts• Design time characterization and runtime management services

EOT_PW_icon.ppt | 8




End-to-End QoS Management Framework

Domain QoS PoliciesAdmin and Mgmt

Traffic Control API

Transport API

Application

Transport / NetworkQoS Service Provider(IntServ / RSVP)

IP Stack

middleware Interface

Packet Scheduler

Middleware

Middleware QoS Facility

Host NICs

Traffic Control API

Transport API

Application

Transport / NetworkQoS Service Provider(IntServ / RSVP)

IP Stack

middleware Interface

Packet Scheduler

Middleware

Middleware QoS Facility

Host NICs

QoS (e.g., Diff Serv) Enabled Network

Network / transport QoS Performance Observation

points

An end-to-end (E2E) approach include:

• Determine and express QoS requirements (demanded QoS)

• Control & Optimize resources and mechanisms to meet demanded requirements (offered QoS)

• Monitor, Diagnose, Manage Resource Contention and Degradation, and Adaptation (runtime SLM)

Presentation Presentation

EOT_PW_icon.ppt | 9




QoS Management Architecture: Major Services

An Infrastructure Perspective

EOT_PW_icon.ppt | 10




QoS Characteristics, Specification Language, and Policy Management





QoS Characteristics: Diverse Sets

• Different types of services may have different characteristics:

(1) Tasking: task-oriented services perform operations on demand (e.g., Web Service);

(2) Messaging: message-oriented services deliver pieces of information from a source to destinations on demand; and

(3) Streaming Media: streaming media services deliver stream of information continuously.

• Parameterize QoS characteristics

to measurable values in Nominal, Ordinal, or Numerical forms.

• Use QoS characteristics as vocabularies of a QoS language.

JitterDuplicate Elimination

Response Time

IntegrityAccountability

ConfidentialityAvailability

Message Delay

Priority

ThroughputDelivery Guarantee

Deadline

AccuracyOrderingCriticality

Tasking

Retry Limit

StreamingMessaging





QoS Language for Demands & Offers

• A standard set of QoS vocabularies and semantics is needed for a QoS language capable of expressing QoS requirements, contracts, and policies.

• Pieces exist today, e.g., WS-Reliable Messaging.• XML-based representation is common for extensibility.• General policy languages exist (but not specific to QoS).• QoS policies may be in the form of decision tables (e.g.,

routing QoS), rules, decision trees.

• There is a need for a unified QoS specification XML schema for tasking, messaging, and streaming QoS characteristics and for expressing requirements, contracts and policies based on these characteristics.





A QoS Language for Demands & Offers: XML schema and resource policies

A snippet of QoS XML Schema:<xs:schema …> <xs:element name="qos-requirement"> <xs:complexType> <xs:sequence> <xs:element ref="criticality" …/> <xs:element ref="performance" …/> <xs:element ref="reliability" …/> <xs:element ref="security" …/> … <xs:element ref="constraints" …/> <xs:element ref="monitoring" …/> </xs:sequence> … </xs:complexType> </xs:element> <xs:element name="reliability"> <xs:complexType> <xs:attribute name="guaranteed-delivery" …/> <xs:attribute name="duplication-elimination"…/> <xs:attribute name="message-ordering" …/> </xs:complexType> </xs:element> …</xs:schema>

A Snippet of Resource Allocation Policy – decision tree:<qos-policy name="…" version="1" target="resource-management" target-dtd="ResourceManagement.dtd"> <variable name="criticality"><path>/…/@level</path></variable> … <create name="topic" type="attribute"><path>…/topic</… ></…> <create name="message-queue"> <create name="queue-size"> <create name="target"> <node><condition><function name="lt"> <varref name="pay-load"/><constant>5120</…></…></…> <constant>100</constant></node> <node><condition><function name="lt"> <varref name="pay-load"/><constant>10240</…></…></…> <constant>50</constant></node>… <node><constant>3</constant></node></create></create> <create name="receiver"> <create name="monitor "><create name=”pay-load”/> <create name="threshold"><function …>…</…></…> <create name="@cross-up”><constant>adapt</...></…> <create name="@cross-down"><constant>restore</…></…> </create>…</create> … </node> …

Design time monitoring & adaptation may be instrumented in the policies and contracts.





A QoS Language for Demands & Offers: QoS Contract – a basis for SLA

Monitoring and adaptation could be part of the contract:<create name="monitoring-point"><create name=”name”> <constant>payload-size</constant> </create> <create name=”facet”> <create name=”target”><varref name=”target”/></create> <create name="threshold"> <create name=”name”><constant>upper-bound</…></create> <create name=”value”><function name=”multiply”> <varref name=”target”/><constant>1.2</constant> </function></create> <create name="cross-up”> <create name=”action”><create name=”class”> <constant>….AdaptationChangeDeliveryGuarantee</…> </create></create></create> <create name="cross-down”> <create name=”action”><create name=”class”> <constant>….AdaptationRestoreDeliveryGuarantee</…> </create></create></create>

Example QoS Parameters in a SLA contract:<qos-requirement …> <performance> <volume-rate unit='second'>100</volume-rate> <pay-load volume='32' unit='kilobyte'/> </performance> <reliability> <guaranteed-delivery>yes</guaranteed-delivery> </reliability> <criticality>green</criticality>

</qos-requirement>

Design time monitoring and adaptation are part of this example runtime contract.





QoS Policy Management

• Separate QoS Policies into two levels, system of systems (SoS) level and system level, for global constraints and local control.

PolicyRepository

Global PolicyManager

Web UI

StoreRemoveUpdateRetrieve

CreateDeleteModifyBrowse

Service #1

QoS Management

Local PolicyManager

CacheEnforce

Policy

Service #N

QoS Management

Local PolicyManager

CacheEnforce

Policy

SoS Policies define global coarse grained enterprise constraints.

System Policies define platform level resource allocations under enterprise constraints and SLA.





Integrate QoS Management to Enterprise Architecture, Domain, and Infrastructure for SLM





Integrate QoS Management to Enterprise Architecture, Domain, and Infrastructure

• QoS Management must address Architecture, Domain, and Infrastructure Concerns

• Architecture: Enterprise SOA, Processes• Domain: Networked Services and Data Management• Infrastructure: Middleware, Servers & Networks

• Integrate QoS Management to Enterprise Infrastructures is fundamental (e.g., for Enterprise Service Bus, Servers and Networks)





Infrastructure QoS Management Example

• Example: Integrate QoS Management Architecture into Messaging Middleware, Server and Network Platforms

InfoBroker

QoS Manager

Pub

lishe

r

Su

bsc

rib

er

Pu

blis

her

Pub

lish

er

Su

bscr

ibe

rS

ubsc

rib

er

Contract Negotiation

Messages Flow

AdmissionControl

...

Re

sou

rce

Ma

nage

me

nt

Ad

aptio

n

Pre

dic

tion

Mo

nito

ring

Pub

licat

ion

Sub

scri

ptio

n

Fu

sio

n

Dis

trib

utio

n

Pe

rsis

ten

ce

Filt

eri

ng

Discovery Security

...

Infrastructure QoS Management is fundamental to Enterprise SLM

Networked Server Platforms





QoSM: QoS MonitorRM: Resource ManagerQoSP: QoS ProberQoSDx: QoS Diagnostics Engine

InternetInternet

Router

Router

CLIENTS

Firewall

QoSDxDx Engine Net.

Monitor

Repos .

RM

QoSM

App

App

RM

QoSM

App

App

App

Boeing QoSMgt

“QoS Proactive”System/Apps

QoSP

“QoS Passive”System/Apps

App


InternetInternet

Router

Router

CLIENTS

Firewall

QoSDxDx Engine Net.

Monitor

Repos .

QoSDxDx Engine Net.

Monitor

Repos .

RMRM

QoSMQoSM

AppApp

AppApp

RM

QoSM

App

App

App

RMRM

QoSMQoSM

AppApp

AppApp

AppApp

Boeing QoSMgt

Enterprise SLM

QoS Mgt


QoSPQoSP

“QoS Passive”System/Apps

AppApp


Integrate Monitoring to QoS Management for Enterprise SLM

Enterprise Service Monitoring must be integrated into a comprehensive QoS management system for autonomous SLM





Monitoring in QoS Management Architecture

Diagnostic Model Engine

QoS Data Repository

Traffic/ Sys Monitoring

Tools

Network TrafficSystem Status

Diagnostic Models

Abstracted Variable/ Raw Parameter Definitions & Tables

Message (Transaction / Packet) Definitions & System Resource Definitions

Dx Outputs

QoS Abstracted Variables

Dx Triggers

QoS Raw Parameters

QoS Raw Parameters to

Monitor

Dx Output Def.

Offline In/Out

Online In/Out

Online Dataflow

Offline Dataflow

Prediction Service

Monitoring

Service

Alarms and Condition Data

QoS Data Query

Register alarms and predicates





QoS Management may also be Integrated with Multi-Level Security

QoS Manager

Sys Mgmttools

QoS Rqmts + user security label

QoS-MLS Policy

Policy Manager (Security)

EstablishmentService

(Adm CTL)

CMDB

Host B Host A

SW Lib

Security Config Service

QoS message w/ Security labelContract

Host /Net CM Query /ResponseHost install &

config script HostConfig Validation

and Setup

Net ConfigValidation and Setup

Sec. Infrast ConfigValidation and Setup

Net Mgmttools

Sec. Res.

Rqmts +

label

Ready/fail code

Security Resource

Rqmts + allowed

actions for defined

Obj statesCM Validate

/ Setup

Ready

Appl/DomainController/

tools

Download,

reconfig

Data feed

Network

Route Entries,

ACL updates

Host CM Cache

KMI / EDS

DNS AD

RADIUS

Role, User Key

1

2

34

5

67

8”

8’

89

9”

9’

VPN

HAIPE

1213

14

10

10’

12’

Object Sec.Mata database

User /

Application

Targeted

Object

location

3’

3’’

Security label

+User profile

11’’

10’’

11

11’

12’’

15 Contract Id

Other QoS Manager

components

Ready

PKIProxy

Quality of Security Service is defined by User & Service Provider Security Parameters.QoS Contract is a unifying concept for both QoS and Security.

QoS Management for MLS Architecture





Conclusions

• QoS management for enterprise SLM is all about cost, efficiency, meeting or exceeding customer expectations.

• A mission driven, autonomous, and integrated QoS management approach is key to Enterprise SLM

• Formalize enterprise missions as business processes and composition of services

• Model and assure mission and service QoS characteristics• Derive QoS management strategies and policies from enterprise

missions• Create SLM architecture with QoS management for autonomous

enterprise systems and services• Develop and integrate QoS management across all layers of

concerns and responsive to enterprise missions & conditions





Future Work

• More research work needed for Architecture, Domain, and Infrastructure QoS concerns, at both design time and runtime, towards a mission driven, autonomous, and integrated QoS management capability

• Address QoS and Security issues in enterprise processes and SOA

• Address QoS characteristics and provisioning of domain services

• Address design time and runtime dynamics• Address QoS challenges in infrastructures of large scale

networked services• Address QoS interoperability across heterogeneous platforms

and systems





Additional Information

• G. Wang, A. Chen, C. Wang, C. Fung, S. Uczekaj, “Integrated Quality of Service (QoS) Management in Service-Oriented Enterprise Architectures”, Proceedings of the 8th IEEE International Enterprise Distributed Object Computing Conference, IEEE CS Press, Monterey, CA, September 2004, pp. 21-32.

• G. Wang, C. Wang, A. Chen, H. Wang, C. Fung, S. Uczekaj, Y. Chen, W. Guthmiller, J. Lee, “Service Level Management using QoS Monitoring, Diagnostics, and Adaptation for Networked Enterprise Systems”, Proceedings of the 9th IEEE International Enterprise Distributed Object Computing Conference, IEEE CS Press, September 2005, PP. 239-248.

• C. Wang, G. Wang, A. Chen, H. Wang, Y. Pierce, C. Fung, S. Uczekaj, “A Policy-Based Approach for QoS Specification and Enforcement in Distributed Service-Oriented Architecture”, Proceedings of IEEE International Conference on Services Computing, Orlando FL, July 11-15 2005.

• C. Fung, P. Hung, R. Linger, G. Wang, G. Walton, "A Service-Oriented Composition Framework with QoS Management", Journal of Web Services Research, JWSR 3(3), pp. 108-132, July-September, 2006.

• A. Mohammad, A. Chen, G. Wang, C. Wang, R. Santiago, “A Multi-Layer Security Enabled Quality of Service (QoS) Management Architecture”, Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference, IEEE CS Press, October 2007, PP. 423-434.

• C. Wang, G. Wang, H. Wang, A. Chen and R. Santiago: “Quality of Service Contract Specification, Establishment, and Monitoring for Service Level Management”, in Journal of Object Technology, vol. 6, no. 11, Special Issue December 2007, pp. 25-44 http://www.jot.fm/issues/issue_2007_12/article2/

http://www.jot.fm/issues/issue_2007_12/article2/





• Thank You!

• Any Questions?

Documents

Slides