- From: Sedukhin, Igor <Igor.Sedukhin@ca.com>
- Date: Mon, 3 Jun 2002 09:49:52 -0400
- To: Hao He <Hao.He@thomson.com.au>, www-ws-arch@w3.org
- Message-ID: <849C1D32E4C7924F854D8A0356C72A9E046F12A6@usilms08.ca.com>
Service Level Agreements are not part of D-AC0018. Management instrumentation is needed to ensure SLAs, reliabiliy is usually one of the parameters of an SLA. And while I have no problems with Reliability being a top goal for other reasons, I propose to have *SLA* and Management as another top goal. D-AC0018 is altogether part 4.1 of my proposal. Again, I'm primarily concerned about *agreements* and management instrumetation/metrics being a way to maintain an agreement. -- Igor Sedukhin .. (Igor.Sedukhin@ca.com) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 -----Original Message----- From: Hao He [mailto:Hao.He@thomson.com.au] Sent: Sunday, June 02, 2002 7:27 PM To: Sedukhin, Igor; www-ws-arch@w3.org Subject: RE: New top goal proposal: Management and SLA I believe this is what D-AC0018 was originally intended for. Hao -----Original Message----- From: Sedukhin, Igor [mailto:Igor.Sedukhin@ca.com] Sent: Saturday, June 01, 2002 3:03 AM 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 09:51:38 UTC