W3C home > Mailing lists > Public > www-ws-arch@w3.org > June 2002

RE: New top goal proposal: Management and SLA

From: Damodaran, Suresh <Suresh_Damodaran@stercomm.com>
Date: Mon, 3 Jun 2002 10:41:17 -0500
Message-ID: <40AC2C8FB855D411AE0200D0B7458B2B07C59630@scidalmsg01.csg.stercomm.com>
To: "'Sedukhin, Igor'" <Igor.Sedukhin@ca.com>, www-ws-arch@w3.org
Cc: "'Hao He'" <Hao.He@thomson.com.au>
I hear you saying you want the "what" captured in SLA? I think this is a
great idea.
My suggestion below is only to include it in D-AG002 bucket because it
already has many of the
"how" elements in it. It is fine with me if you want create another top goal
for "agreements."
 
When you on the subject of agreements, you may also consider "management and
service profiles"
and how to negotiate with profiles to from agreements. 
 
Cheers,

-Suresh 
Sterling Commerce, Inc. 

-----Original Message-----
From: Sedukhin, Igor [mailto:Igor.Sedukhin@ca.com]
Sent: Monday, June 03, 2002 8:41 AM
To: Damodaran, Suresh; www-ws-arch@w3.org
Cc: 'Hao He'
Subject: RE: New top goal proposal: Management and SLA


D-AC0018 is management and metrics for Reliability.
SLAs are not necessarily Reliability.
Here is what I wrote:
"Management metrics/instrumentation is merely "how" details of a bigger
goal, and the Reliability is an intermediate effect/characteristic.
Reliability goal has other aspects in messaging, etc. and while I do not
want to contend with it in any way,..."
 

-- Igor Sedukhin .. (Igor.Sedukhin@ca.com) 
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 

-----Original Message-----
From: Damodaran, Suresh [mailto:Suresh_Damodaran@stercomm.com] 
Sent: Sunday, June 02, 2002 11:22 AM
To: Sedukhin, Igor; www-ws-arch@w3.org
Cc: 'Hao He'
Subject: RE: New top goal proposal: Management and SLA


Igor,
 
Metrics & manageability are considered in D-AC0018 [1].
Hao He championed it, and we are refining it in Reliability Task Force
(RTF).
 
Can we  refine D-AC0018 to include this proposal?
 
[1] http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0391.html
<http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0391.html> 
 
cheers,

-Suresh 
Sterling Commerce, Inc. 

-----Original Message-----
From: Sedukhin, Igor [mailto:Igor.Sedukhin@ca.com]
Sent: Friday, May 31, 2002 12:03 PM
To: www-ws-arch@w3.org
Subject: New top goal proposal: Management and SLA



I was reading our requirements document and realized that there is not a
proper attention being paid to a very important aspect of a service:
agreements between a user and the owner. This is not any less important
element than security for that sake. How can business components comprise a
"digital economy" without agreements?

Now, agreements have to be established, maintained, accounted for, and may
be enforced. Management metrics/instrumentation is merely "how" details of a
bigger goal, and the Reliability is an intermediate effect/characteristic.

Reliability goal has other aspects in messaging, etc. and while I do not
want to contend with it in any way, I'd like to pull Manageability and SLAs
higher on the stack. Here is my proposal for the new top goal.

Goal: Manageability and Service Agreements 
Web Services Architecture must provide a manageable environment for
establishing, maintaining and enforcing Service Level Agreements.

Critical success factors for this goal are: 
To develop standard reference architecture for Web Services that: 

1. Identifies how to express SLAs and associate them with Web services 
1.1 Service usage policies 
1.2 Web service licensing standards 
1.3 Identify technical/legal boundary 

2. Identifies automatic/manual SLA negotiation process 

3. Identifies how agreements are established and preserved 
3.1 License persistence and verification procedures 
3.2 Privacy of SLAs 
3.3 Integrity and non-repudiation of SLAs 

4. Identifies management/instrumentation/metrics standards/technologies
necessary to meter and account for service usage

4.1 - subsume/reference D-AC018 

5. Identifies procedures/standards necessary to maintain the agreement 
5.1. Identify technology/commerce boundary 

6. Identifies SLA enforcement procedures 
6.1 Usage/metrics reconciliation procedures 
6.2 Attempt/provide for automatic conflict resolution 
6.3 Identify technology/legal boundary 

-- Igor Sedukhin .. (Igor.Sedukhin@ca.com) 
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 
Received on Monday, 3 June 2002 11:42:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:00 GMT