Some service management topics/ideas/thought experiments

["Jeffrey A. Estefan" <jeffrey.a.estefan@jpl.nasa.gov>]

Colleagues,

 

Attached are some ideas based on a few external resources to try and help us think about the service management model.  While there are some areas of the remaining elements of the RA that need a bit of cleanup, this is one area we need to turn our attention.  We should be able to identify some key areas we want to cover and then divide an conquer.

 

Cheers...

 

 - JAE

Management Functions/Services
-----------------------------

Provisioning:  The act of supplying something (needed materials or supplies)


AventNet (SUN):
Provisioning
Configuration
Performance
Topology
Policy
Fault
Security
Maps

WS Stack (DISA Talk):
QoS Stack-->
Integrity
Managmeent
Framework
Performance
Security
Interoperabiity
Reliability
Accessbiliyt
Availability

Monitor status and performance.

From Newcomer/Lomow:
The approach taken to managing services (such as deploying, starting, stopping, and monitoring services) defines the servel-level management model.  Support for versioning services.  Support for auditing service usage.  Support for metering and billing for service usage.  Service-level support for business activity monitoring (BAM) including service monitoring, service status, service responsiveness, and compliance or deviations from service-level agreements.

From ZapThink SOA Roadmap:
Under Manage Services...
Business Management: Includes business process management, transaction management, business activity monitoring, and billing and metering.
System Management:  Includes Web service monitoring, alerting, exception management, and root cause analysis.
Enterprise Security & Policy Management:  Hooks to Identity and Access Management, Governance & Policy, and Content-Aware Networking.
SOA Enablement: Provides for the encapsulation and composition of the underlying implementation in a scalable, fault-tolerant manner.  Hook to Service Intermediary.
Lifecycle Management: Includes provisioning, version control, Web service depedencies, and deprecation.  Hook to Registry/Repository.

From WSA:
Web service management is the management of Web services through a set of management capabilities that enable monitoring, controlling, and reporting of, service qualities and service usage. Such service qualities include health qualities such as availability (presence and number of service instances) and performance (e.g. access latency and failure rates), and also accessibility (of endpoints). Facets of service
usage information that may be managed include frequency, duration, scope, functional extent, and access authorization.

A Web service becomes manageable when it exposes a set of management operations that support management capabilities. These management capabilities realize their monitoring, controlling and reporting functions with the assistance of a management information model that models various types of service usage and service quality information associated with management of the Web service. Typical information types include request and response counts, begin and end timers, lifecycle states, entity identifiers (e.g. of senders, receivers, contexts, messages, etc.).

Although the provision of management capabilities enables a Web service to become manageable, the extent and degree of permissible management are defined in management policies that are associated with the Web service. Management policies therefore are used to define the obligations for, and permissions to, managing the Web service.

Just as the Web service being managed needs to have common service semantics that are understood by both the requester and provider entities, Web service management also requires common management semantics, in relation to management policies and management capabilities, to be understood by the requester and provider entities.

ITtoolbox Blogs:
The challenges of monitoring SOA can be overcome by instrumenting the services for monitoring and management. A service that does not provide any status on its health or the execution of a transaction is like a black box - the service consumer and the administrators who monitor the environment cannot tell if things are working. 

Amberpoint Management Foundation:
Access Control
Management & Monitoring
Business & System Alerts
Online Upgrades & Testing
Auditing & Logging

UDOP RFP:
Basic CES Management
	Integrate w/Security services
	Monitoring
	Heartbeat and Ping
	Alerting
	Pause/Restore/Restart Service Access
	Logging, Auditing, Non-Repudiation
	Runtime version management
Message Routing & Redirection
	Failover
	Load-Balancing
QoS, Management of SLOs (Objectives) and SLAs (Agreemtns)
	Availability
	Response Time
	Throughput
Fault and Exception Management

Service Level Management (SLM) Definition (From Amberpoint):
Is the continuous process of measuring, reporting and improving quality of service (QoS) 
It includes a proactive way to establish acceptable levels of service that address business goals

Service Lifecycle:
 - Service Planning
 - xxx
 - Service Retirement

IBM Systems Journal Article by D.E.Cox and H.Kreger
http://www.research.ibm.com/journal/sj/444/cox.html