Are attached. We'll meet next week at the usual time. --- Jim Attendees --------- Christopher Dabrowski Toshi Nakata Jim Pruyne Asit Dan Heiko Ludwig Wolfgang Zeigler Discussion ---------- - GGF in Tokyo session scheduling needs to be done. Everyone's goal is to finish up the spec. by this time with a session to discuss. Two follow-up sessions continuing discussions on networking and perhaps on CIM in domain languages. Also a request for presentation on "functional specification" for terms to get dynamic agreements. - Comment row 21: On terminate operation: concern here is that there may be penalties associated with termination, but this is domain dependent. Terminate might still be followed by a destroy operation. The proposal is also to introduce a agreement state called terminated in section 7.1 that says that additional penalty may associated with entering the terminated state. Updates may require changes in the schema (e.g. in section 9.5). The new port type for the terminate operation would be introduced around section 9.4. We also need to introduce some discussion of the relationship between terminate and wsrl:Destroy. Toshi to start to pursue some of these updates, and send the proposed changes to the mailing list. - Comment row 22: 1) Use of Id was inconsistent. Decided to use "Id" everywhere, and made the appropriate changes. 2) Changed to TemplateId 3) Asking Heiko to double check this. And, we need to address the whole area of how we define our namespaces. JSDL uses the sort of namespac definition we use in other places, so we should continue to use this form, but will need to update the date before the final release. - Comment row 13: Using Asit's proposed text here. Will see if we can add some additional text below to use this example for assesment interval.
Hello:I've updated the Commentslist 1)Moved the ones which have already been discussed to the done page. (The entries are not in item order, as I need to be able to distinguish between the ones already discussed in GGF16. and the oned needed to be explained in GGF17) 2)Added 18 of Karl's comments. Best regards Toshi ----- Toshiyuki Nakata 中田 登志之 Executive Chief Engineer, Central Research Lab. NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60035) Fax +81-44-431-7609 (NEC Internal 22-60509)
-----Original Message-----
Usual list attached. Best Regards Toshi
<Begin Quote> - Comment row 21: On terminate operation: concern here is that there may be penalties associated with termination, but this is domain dependent. Terminate might still be followed by a destroy operation. The proposal is also to introduce a agreement state called terminated in section 7.1 that says that additional penalty may associated with entering the terminated state. Updates may require changes in the schema (e.g. in section 9.5). The new port type for the terminate operation would be introduced around section 9.4. We also need to introduce some discussion of the relationship between terminate and wsrl:Destroy. Toshi to start to pursue some of these updates, and send the proposed changes to the mailing list. <End Quote> Actually, most of the work had been resurrection of previously deleted material, with the exception of introduction of the Terminated State. (I am still not sure whether introduction of Teminated State is good or bad. Eg. what would be the difference between killing an NQS job using an NQS script (in which case I suppose the Agreement State would end in Complete and Using Terminate to teminate an executing job?) I do have a Word doc but excerpts from it may be easier to see. Please note <<...>> means some words exist but has not been changed so not included to make it easier to see. <<words>> are my comments. Section 7.1 7.1 Agreement States The overall Agreement has a state derived from the Agreement protocol. * Pending. <<...>> * Complete. The Complete state means that an Agreement offer has been received and accepted, and that all activities pertaining to the Agreement are finished This state MAY follow Observed. <<Begin Addition>> * Terminated. The terminated state means that an Agreement offer has been terminated by the Agreement Initiator and that the obligation no longer exists. This state May follow Pending or Observed. The fact that the Agreement is in this state MAY imply that a domain specific penalty is imposed. <<End of Addition >><<Please note that due to a race condition, Terminated might follow Complete..>> The Pending and Rejected states indicate that the responder is not obligated in any way. <<....>> The accepted Agreement is Complete only when all service states are Complete, and the accepted Agreement is otherwise Observed. <<Begin Addition>> The Terminated state indicate that neither parties are obligated. << End Addition>> <<9.4 is mostly resurrection except for the wording "Terminating an Agreement may result in domain-specific penalty imposed on the Agreement Initiator." <<Should may above be MAY??>> 9.4 Port Type wsag:Agreement 9.4.1 . Operation wsag:Terminate Terminates an Agreement, if permissible. Terminating an Agreement may result in domain-specific penalty imposed on the Agreement Initiator. 9.4.1.1 Input The form of the wsag:Terminate input message is: <wsag:TerminateInput> xsd:any </wsag:TerminateInput> The contents of the input message are further described as follows: /wsag:terminate/xsd:any Any domain-specific content may be added. This content may be used for a variety of purposes such as logging the termination condition, or evaluating if a domain-specific cause for termination is sufficient to permit the agreement to be terminated. 9.4.1.2 Result The result of the wsag:Terminate operation is always empty. <wsag:TerminateResponse> </wsag:TerminateResponse> 9.4.1.3 Faults A fault response indicates that the termination was rejected and may also indicate domain-specific reasons. <<Adding Terminated state >> 9.5.1 Resource Property wsag:AgreementState The property exposes an Agreement state for the whole agreement as defined in section 7.1. The property has the following structure: <wsag:AgreementState> <wsag:Pending> <xsd:any##other/> * </wsag:Pending> ? <<...>> <wsag:Terminated> <xsd:any##other/> * </wsag:Terminated> ? /wsag:AgreementState This element MUST have exactly one child from: Pending, Observed, Rejected, Complete and Terminated to indicate the overall state of the Agreement resource. Each of these states for the entire agreement have open content so that additional domain-specific state information can be expressed. The individual states are as described in Section 7.1. /wsag:AgreementState/wsag:Pending An agreement state which is in state Pending. <<...>> /wsag:AgreementState/wsag:Terminated An agreement state which is in state Terminated. I've also added WSDL definitions and Agreement Statetpes Schema but won't put them here. ----- Toshiyuki Nakata 中田 登志之 Executive Chief Engineer, Central Research Lab. NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60035) Fax +81-44-431-7609 (NEC Internal 22-60509)
-----Original Message----- From: owner-graap-wg@ggf.org [mailto:owner-graap-wg@ggf.org] On Behalf Of Jim Pruyne Sent: Thursday, March 16, 2006 1:11 AM To: GRAAP-WG Subject: [graap-wg] minutes from 3/15 telecon
Are attached. We'll meet next week at the usual time.
--- Jim
Hi: Found ways to just extract the updated part in an PDF File. Best regards Toshi ----- Toshiyuki Nakata 中田 登志之 Executive Chief Engineer, Central Research Lab. NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60035) Fax +81-44-431-7609 (NEC Internal 22-60509)
-----Original Message----- From: owner-graap-wg@ggf.org [mailto:owner-graap-wg@ggf.org] On Behalf Of Toshiyuki Nakata Sent: Thursday, March 16, 2006 4:26 PM To: 'Jim Pruyne'; 'GRAAP-WG' Subject: RE: [graap-wg] minutes from 3/15 telecon
<Begin Quote> - Comment row 21: On terminate operation: concern here is that there may be penalties associated with termination, but this is domain dependent. Terminate might still be followed by a destroy operation. The proposal is also to introduce a agreement state called terminated in section 7.1 that says that additional penalty may associated with entering the terminated state. Updates may require changes in the schema (e.g. in section 9.5). The new port type for the terminate operation would be introduced around section 9.4. We also need to introduce some discussion of the relationship between terminate and wsrl:Destroy. Toshi to start to pursue some of these updates, and send the proposed changes to the mailing list. <End Quote>
Actually, most of the work had been resurrection of previously deleted material, with the exception of introduction of the Terminated State. (I am still not sure whether introduction of Teminated State is good or bad. Eg. what would be the difference between killing an NQS job using an NQS script (in which case I suppose the Agreement State would end in Complete and Using Terminate to teminate an executing job?)
I do have a Word doc but excerpts from it may be easier to see.
Please note <<...>> means some words exist but has not been changed so not included to make it easier to see. <<words>> are my comments.
Section 7.1 7.1 Agreement States The overall Agreement has a state derived from the Agreement protocol. * Pending. <<...>> * Complete. The Complete state means that an Agreement offer has been received and accepted, and that all activities pertaining to the Agreement are finished This state MAY follow Observed.
<<Begin Addition>> * Terminated. The terminated state means that an Agreement offer has been terminated by the Agreement Initiator and that the obligation no longer exists. This state May follow Pending or Observed. The fact that the Agreement is in this state MAY imply that a domain specific penalty is imposed. <<End of Addition >><<Please note that due to a race condition, Terminated might follow Complete..>>
The Pending and Rejected states indicate that the responder is not obligated in any way. <<....>> The accepted Agreement is Complete only when all service states are Complete, and the accepted Agreement is otherwise Observed.
<<Begin Addition>> The Terminated state indicate that neither parties are obligated. << End Addition>> <<9.4 is mostly resurrection except for the wording "Terminating an Agreement may result in domain-specific penalty imposed on the Agreement Initiator."
<<Should may above be MAY??>>
9.4 Port Type wsag:Agreement 9.4.1 . Operation wsag:Terminate Terminates an Agreement, if permissible. Terminating an Agreement may result in domain-specific penalty imposed on the Agreement Initiator. 9.4.1.1 Input The form of the wsag:Terminate input message is: <wsag:TerminateInput> xsd:any </wsag:TerminateInput> The contents of the input message are further described as follows: /wsag:terminate/xsd:any Any domain-specific content may be added. This content may be used for a variety of purposes such as logging the termination condition, or evaluating if a domain-specific cause for termination is sufficient to permit the agreement to be terminated. 9.4.1.2 Result The result of the wsag:Terminate operation is always empty. <wsag:TerminateResponse> </wsag:TerminateResponse> 9.4.1.3 Faults A fault response indicates that the termination was rejected and may also indicate domain-specific reasons.
<<Adding Terminated state >> 9.5.1 Resource Property wsag:AgreementState The property exposes an Agreement state for the whole agreement as defined in section 7.1. The property has the following structure: <wsag:AgreementState> <wsag:Pending> <xsd:any##other/> * </wsag:Pending> ? <<...>> <wsag:Terminated> <xsd:any##other/> * </wsag:Terminated> ?
/wsag:AgreementState This element MUST have exactly one child from: Pending, Observed, Rejected, Complete and Terminated to indicate the overall state of the Agreement resource. Each of these states for the entire agreement have open content so that additional domain-specific state information can be expressed. The individual states are as described in Section 7.1. /wsag:AgreementState/wsag:Pending An agreement state which is in state Pending. <<...>> /wsag:AgreementState/wsag:Terminated An agreement state which is in state Terminated.
I've also added WSDL definitions and Agreement Statetpes Schema but won't put them here. ----- Toshiyuki Nakata 中田 登志之 Executive Chief Engineer, Central Research Lab. NEC 1753, Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan Tel +81-44-431-7653 (NEC Internal 22-60035) Fax +81-44-431-7609 (NEC Internal 22-60509)
-----Original Message----- From: owner-graap-wg@ggf.org [mailto:owner-graap-wg@ggf.org] On Behalf Of Jim Pruyne Sent: Thursday, March 16, 2006 1:11 AM To: GRAAP-WG Subject: [graap-wg] minutes from 3/15 telecon
Are attached. We'll meet next week at the usual time.
--- Jim
participants (3)
-
Jim Pruyne -
Toshiyuki Nakata -
Toshiyuki Nakata