August 2006 - graap-wg - lists.ogf.org

GRAAP Sessions at GGF18
by Jim Pruyne 30 Aug '06

30 Aug '06

All, Here's a reminder on the sessions we have scheduled at the next GGF: * Monday at 10:30 status and follow-on * Monday at 2:00 on Interoperability * Monday at 4:00 on Dynamic Agreements and Negotiation I hope to see as many people as possible at these. Also, the interoperability workshop will be on Sunday as Wolfgang sent out earlier. We expect that some of the discussion in the two later sessions will be continued from the workshop, so I hope that people will come to those sessions with issues to discuss. Similarly, the first session will largely be dedicated to determining what activities GRAAP should begin after the spec. is complete, so I hope that people will bring their ideas to those sessions. Anyone who has specific ideas they would like to present should feel free to contact me and Wolfgang to let us know what session you'd like time at, and what you'd like to present. We'll do our best to accommodate any of these requests. Thanks. --- Jim

1 0

minutes from Aug 30 telecon
by Jim Pruyne 30 Aug '06

30 Aug '06

Are attached below... --- Jim Minutes of Aug 30, 2006 Teleconference Participants ------------ Toshi Nakata Jim Pruyne Wolfgang Ziegler Discussion ---------- - GGF Sessions: * Monday at 10:30 status and follow-on (Jim to lead) * Monday at 2:00 on Interoperability (Wolfgang to lead) * Monday at 4:00 on Dynamic Agreements and Negotiation (Jim to lead) - Oliver will provide a response to the e-mail from Mumtaz Siddiqui of 8/27 on the issue with the output from Axis. We think he'll provide a patch to the schema for the problem. - Jim will complete editting of the spec. and submit prior to the GGF meeting.

1 0

telecon on Aug 30
by Jim Pruyne 30 Aug '06

30 Aug '06

All, Our August hiatus is pretty much over, and GGF is only two weeks away, so I would like to continue our telecons starting on the 30th at the usual time and numbers: 9:00AM Central Daylight Time US (UTC-5) which should be: 10:00AM Eastern Daylight Time US 1500 UK 1600 Germany 2300 Japan 2100 Thailand Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the US. Conference code #8578310. My goal is to get the group talking again, and firm up the plans for GGF. Thanks. --- Jim

3 3

Workshop on WS-Agreement Implementations and Interoperability
by Wolfgang Ziegler 30 Aug '06

30 Aug '06

Dear all, here is the final program for our workshop we will hold Sunday prior to the OGF meeting. The venue is the same place as for OGF: Washington Convention Center 801 Mount Vernon Place NW Washington, DC 20001 Room number is 155, the workshop will start at 1 pm and will last four hours. Best regards Wolfgang -- Wolfgang Ziegler www.scai.fraunhofer.de/ziegler.html Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258; Fax: +49 2241 14 42258 CoreGRID Network of Excellence www.coregrid.net Collaboration Gateway www.coregrid.net/cg Institute on Resource Management and Scheduling www.coregrid.net/irms WS-Agreement Workshop September 10, 2006 Washington DC 1 pm to 5 pm Room 155 10 minutes Introduction -- Wolfgang Ziegler Session 1: Co-allocation Mechanisms: 1 hour 20 minutes HPC4U and WS-Agreement Matthias Hovestadt 20 minutes WS-Agreement in the VIOLA project Wolfgang Ziegler 20 minutes Using WS-Agreement for Risk Management in the Grid Karim Djemame Session 2: Discussion Session: 1 hour Based on contents of Session 1 Session 3: Dynamic SLAs and Negotaion: 1 hour 20 minutes WS-Agreement use in CATNETs Omer Rana 20 minutes A Framework for WS-Agreement Negotiation Shamimabi Paurobally 20 minutes Grid Capacity Planning with Negotiation-based Advance Reservation for Optimized QoS Mumtaz Siddiqui Session 4: Discussion: 1 hour Based on contents of Session 3. 1 hour Note: If participants from the audience wish to present, we can reduce discussion sessions to 45 minutes, and have two, 15 minute, presentations.

1 0

WSAG schema to java stubs: a confusion
by Mumtaz Siddiqui 27 Aug '06

27 Aug '06

Hi, There is a confusion between schema description and generated Java stubs. According to the WSAG specifications, multiple ServiceDescriptionTerms and Preferences can be defined/described as shown in appendix 2/3 examples. But, when we generate Java stubs (using WSDL2Java emmiter or castor), the generated stubs provide these fields as single element instead of array or vector. For examle TermCompositorType class: public class TermCompositorType implements java.io.Serializable { private org.ggf.wsag.TermCompositorType exactlyOne; private org.ggf.wsag.TermCompositorType oneOrMore; private org.ggf.wsag.TermCompositorType all; private org.ggf.wsag.ServiceDescriptionTermType serviceDescriptionTerm; //???? Should not it array like ServiceDescriptionTermType[]???? private org.ggf.wsag.ServiceReferenceType serviceReference; private org.ggf.wsag.ServicePropertiesType serviceProperties; private org.ggf.wsag.GuaranteeTermType guaranteeTerm; public TermCompositorType() { } ... } Here I expect ServiceDescriptionTermType[] instead of ServiceDescriptionTermType. probably, here we can use domain specific terms like JobDefinition from JSDL as JobDefinition_Type[] jdefs = new JobDefinition_Type[2]; jdefs[0] = new JobDefinition_Type(); jdefs[1] = new JobDefinition_Type(); sdterm.set_any(AnyHelper.toAnyArray(jdefs)); sdterm.setServiceName(new NCName("job1")); In this case the serialized XML document does not look like as expected! See the serialized form below: <agreement> .... <ns2:ServiceDescriptionTerm ns2:ServiceName="job1" xsi:type="ns2:ServiceDescriptionTermType"> <ns3:value xsi:type="ns4:JobDefinition_Type" xmlns:ns3="http://www.globus.org/namespaces/2004/06/core" xmlns:ns4="http://schemas.ggf.org/jsdl/2005/11/jsdl"> <ns4:JobDescription xsi:type="ns4:JobDescription_Type" xsi:nil="true"/> </ns3:value> <ns5:value xsi:type="ns6:JobDefinition_Type" xmlns:ns5="http://www.globus.org/namespaces/2004/06/core" xmlns:ns6="http://schemas.ggf.org/jsdl/2005/11/jsdl"> <ns6:JobDescription xsi:type="ns6:JobDescription_Type" xsi:nil="true"/> </ns5:value> </ns2:ServiceDescriptionTerm> .... </agreement> Similarly, in case of BusinessValueListType class public class BusinessValueListType implements java.io.Serializable { private java.lang.Integer importance; private org.ggf.wsag.CompensationType[] penalty; private org.ggf.wsag.CompensationType[] reward; private org.ggf.wsag.PreferenceType preference; <<<<<<???????? private java.lang.Object[] customBusinessValue; public BusinessValueListType() { } ... } again I expect PreferenceType field as array like PreferenceType[]. Probably my understanding is wrong or the Java stubs are incorrectly generated. Would be great if someone could explain it? How to specify multiple terms and preferences using generated Java stubs? Thanks mumtaz PS: Typo in wsag draft page 25? "A guarantee term can have one or more service scopes. A service scope describes to what service element specifically a service applies." May be the last 'service' is to be replaced with 'guarantee'?

1 0

[Fwd: WSAG Draft]
by Wolfgang Ziegler 02 Aug '06

02 Aug '06

Dear all, Here are some comments from my colleague Oliver: AgreementSchemaTypes: wsa-Namespace is not used (should be removed) wsrf-bf: fault section could be moved to wsdl, therefore eliminating the dependency to wsrf-bf in the xml-schema (only in wsdl). AgreementAcceptanceSchemaTypes: Namespaces wsa and wsrf-bf should be removed since they were not used in the schema. Best regards Wolfgang -- Wolfgang Ziegler www.scai.fraunhofer.de/ziegler.html Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258; Fax: +49 2241 14 42258 CoreGRID Network of Excellence www.coregrid.net Collaboration Gateway www.coregrid.net/cg Institute on Resource Management and Scheduling www.coregrid.net/irms

4 4