October 2006 - ogsa-hpcp-wg

Link/wiki for HPC Profile demo info (contacts etc)
by Joel Replogle 24 Oct '06

24 Oct '06

All - here is a link on the OGF website that will be referenced on the flyer, it takes you to a wiki for contain contact info & other info that we'd like people to see. http://www.ogf.org/hpc_profile The wiki is mostly blank, with its details to be filled in by the group. :-) Thanks, Joel ------------------------------------------------------------------------ ----------- Joel Replogle - Manager of Standards, Open Grid Forum replogle(a)ogf.org http://www.ogf.org

1 0

Draft flyer and reminder
by John Ehrig 24 Oct '06

24 Oct '06

Hi All, Attached is a very rough draft of the SC06 demo flyer. I'd like to get feedback prior to the call on Tuesday so I can have a second draft to review at that time. Also, please remember to provide me the below information, some progress by our meeting on Tuesday would be much appreciated. Thanks! Everyone - Please send to John Ehrig (jehrig(a)inventures.com) and hpcp-wg mailing list the following information: o Marketing contact to coordinate PR (i.e. get quotes) o Booth #'s and booth owner contact names o Timeslots for dedicated HPCP presentation, if possible o Plans for adoption (from commercial and non-commercial participants) John Ehrig Open Grid Forum Marketing Program Manager 925 275-6677 www.ogf.org <http://www.ogf.orgopen/> Open Forum | Open Standards

3 2

SC06 Flyer - Latest Rev for Discussion Tomorrow
by John Ehrig 24 Oct '06

24 Oct '06

John Ehrig Open Grid Forum Marketing Program Manager 925 275-6677 www.ogf.org <http://www.ogf.orgopen/> Open Forum | Open Standards

5 5

Re: [ogsa-hpcp-wg] SC06 Demo Marketing Conf Call - 10/17
by Richard Ciapala 23 Oct '06

23 Oct '06

Correction: I will send email regarding the first workitem bullet by EOD Wed (not Tues). Thanks From: Richard Ciapala Sent: Tuesday, October 17, 2006 9:34 AM To: 'ogsa-hpcp-wg(a)ggf.org' Subject: SC06 Demo Marketing Conf Call - 10/17 Participants on the call * Glenn Wasson * John Ehrig * Chris Smith * Mark Linesch * Michel Drescher * Steven Newhouse * Peter Lane * Ming Xu * Susanne Balle * Joel Replogle Notes * We need a volunteer to create the technical description and diagram * We will start using the wiki for the marketing collateral * Besides PR efforts, OGF will announce the demo for SC06 via a broadcast email and on their web site Participant WorkItems * Rich - Send email to working group with answers to following by EOD Tuesday: o What is the HPC Profile? o Why do people care? o Who are involved? o What are we showing (from a general perspective)? * Everyone - Please send to John Ehrig (jehrig(a)inventures.com<mailto:jehrig@inventures.com>) and hpcp-wg mailing list the following information: o Marketing contact to coordinate PR (i.e. get quotes) o Booth #'s and booth owner contact names o Timeslots for dedicated HPCP presentation, if possible o Plans for adoption (from commercial and non-commercial participants) * John - Drive responses to the above questions * Chris - Put together slides for participants to use for booth presentations (available closer to SC06) * Chris - Ask a few customers whether they are willing to provide quotes * John - Work on common placard for participants booths

2 1

Another Problem (maybe?) in the WSDL
by Mark Morgan 23 Oct '06

23 Oct '06

In trying to interop with Glenn's endpoint, I have found another potential problem with the BES-Factory's WSDL. However, the problem is at a level of WSDL that is slightly beyond my experience. In particular, the problem is with two message types; the GetActivityDocuments message type, and the TerminateActivitiesType message. Both problems are identical. In brief, here are three elements from the WSDL (the first of which is an example of a type declaration which works for me, and the latter two being the problem declarations). <xsd:complexType name="GetActivityStatusesType"> <xsd:sequence> <xsd:element name="ActivityIdentifier" type="wsa:EndpointReferenceType" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="GetActivityDocumentsType"> <xsd:sequence> <xsd:element ref="bes-factory:ActivityIdentifier" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="TerminateActivitiesType"> <xsd:sequence> <xsd:element ref="bes-factory:ActivityIdentifier" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> The first one works for me, and the last two do not. The problem with the second and third ones is that my tooling doesn't know what name to give the element for the EPRs inside of the message elements.. In otherwords, it generates messages which look like the following: <GetActivityDocuments xmlns="http://schemas.ggf.org/bes/2006/08/bes-factory"> <item xmlns="" xmlns:ns3="http://www.w3.org/2005/08/addressing" xsi:type="ns3:EndpointReferenceType"> <ns3:Address>https://wincluster1.cs.virginia.edu/HPCP/HPCPService.asmx</ns3: Address> <ns3:ReferenceParameters> <jobID xmlns="http://schemas.ggf.org/hpcp/2006/07/hpcp-app">113</jobID> </ns3:ReferenceParameters> </item> </GetActivityDocuments> <TerminateActivities xmlns="http://schemas.ggf.org/bes/2006/08/bes-factory"> <item xmlns="" xmlns:ns3="http://www.w3.org/2005/08/addressing" xsi:type="ns3:EndpointReferenceType"> <ns3:Address>https://wincluster1.cs.virginia.edu/HPCP/HPCPService.asmx</ns3: Address> <ns3:ReferenceParameters> <jobID xmlns="http://schemas.ggf.org/hpcp/2006/07/hpcp-app">113</jobID> </ns3:ReferenceParameters> </item> </TerminateActivities> Notice the child element called "item" in each message. The simple (and obvious to me) fix was to change the GetActivityDocuemntsType and TerminateActivitiesType type definitions to specify the name of the inner element, i.e. to change them to: <xsd:complexType name="GetActivityDocumentsType"> <xsd:sequence> <xsd:element name="ActivityIdentifier" ref="bes-factory:ActivityIdentifier" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="TerminateActivitiesType"> <xsd:sequence> <xsd:element name="ActivityIdentifier" ref="bes-factory:ActivityIdentifier" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> I know that these are legitimate fixs, the questions are, A) are these in fact real errors that my tooling is finding and thus the WSDL is in error, and B) can we make these changes permanent in the BES-Factory WSDL to fix these problem? -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2047

4 8

Some question from the CROWN project
by Liang Zhong 22 Oct '06

22 Oct '06

Dear All, After a brief discussion with Steven Newhouse when we visiting OMII two weeks ago, we decided to try and participate in the SC06 interop Demo with one service from the CROWN project (http://www.crown.org.cn) we naming it CROWN Scheduler; CROWN Scheduler is a Webservice-based service using JSDL as is job submission description language, we have working for more than one year; and now it could interoperation with GridSAM. In the last few weeks we have been trying to modify the service to follow the BES draft specification. But there still have some unsolved questions from us, I hope you would be so kind to answer these questions: 1) Is there any demo scenario have been proposed? 2) What version of WSDL should we follow to implement the BES? 3) Is there any template client for us to verify the interop? 4) What kind of resource should we contribute during the demo? Shell we setup a server or a cluster at the China side and deploy the services on them, or we just setup a temp environment at the conference demo location? Best Regards, Liang ZHONG Grid Computing Research Group Institute of Advanced Computing Technology, Beihang University Tel: +86 10 8231 6262 Fax: +86 10 8231 6796 Addr: Room 803, Shining Tower, 35# Xueyuan Rd., Haidian District, Beijing 100083, PRC

2 2

Information from CROWN for the SC06 Demo Draft flyer
by Liang Zhong 22 Oct '06

22 Oct '06

Dear John, Following information from CROWN is for the draft flyer at SC06 Demo. 1. Marketing contact to coordinate PR (i.e. get quotes) Liang Zhong <mailto:zhongl@act.buaa.edu.cn> zhongl(a)act.buaa.edu.cn +86 13811997699 2. Booth #'s and booth owner contact names There will be no booth for CROWN at SC06 Demo 3. Timeslots for dedicated HPCP presentation, if possible No. 4. Plans for adoption (from commercial and non-commercial participants) We will try to adoption the HPC Profile in our CROWN Scheduler, which can be used for meta-level scheduler and Job Execution on the back-end system. Some additional information: In this Demo, CROWN will use CROWN NodeServer as the Web Service Tooling, the CROWN Scheduler as the Scheduler. Could you help me to add this information to de draft flyer? Thank you~. Best Regards, Liang ZHONG Grid Computing Research Group Institute of Advanced Computing Technology, Beihang University Tel: +86 10 8231 6262 Fax: +86 10 8231 6796 Addr: Room 803, Shining Tower, 35# Xueyuan Rd., Haidian District, Beijing 100083, PRC

1 0

Minutes from SC06 demo call - 10/20
by Richard Ciapala 21 Oct '06

21 Oct '06

Here are the minutes from Friday's call: Participants * Peter Lane * Susanne Balle * Joel Replogle * Chris Smith * Mark Morgan * Marty Humphrey * Glenn Wasson * John Ehrig * Duane Merrill * Alessandro Maraschini * Rich Ciapala Notes * Chris went over schema changes and already posted new WSDL/XSDs to wiki * To enable various interop demos there is an ask for each participant to: o Provide a hosted application o Publish the JSDL for the application to the wiki o Specify the JSDL ApplicationName element with the public name of the application for job forwarding scenarios o Provide a URL for job's output using HTTP as the transport * There will be another marketing call on Tues. I have already sent out the meeting request. Thanks

1 0

Re: [ogsa-hpcp-wg] Another Problem (maybe?) in the WSDL
by Peter G. Lane 21 Oct '06

21 Oct '06

Doesn't JSDL cause problems for your tooling as well? Element refs are a very common XMLSchema feature. JSDL uses quite a number of them. What about the HPCProfileApplication schema? I'm wondering whether changing the BES schema would actually help that much. I'm also worried that changing the demo copy of the schema for broken tooling would cause those changes to get propagated to the normative BES schema. My personal preference is that you change it locally rather than forcing us to endorse the change. Peter Mark Morgan wrote: > OK -- I thought as much. So, my tooling is bad -- can we change the WSDL > anyway since the change shouldn't only be duplicate information for other > peoples tooling (the goal is to be maximally interoperable right?). > Ofcourse, I have to change the WSDL one way or the other, would just like to > use the same WSDL everyone else is using. > > -Mark > >> -----Original Message----- >> From: Peter G. Lane [mailto:lane@mcs.anl.gov] >> Sent: Friday, October 20, 2006 5:04 PM >> To: Mark Morgan >> Cc: ogsa-hpcp-wg(a)ggf.org >> Subject: Re: [ogsa-hpcp-wg] Another Problem (maybe?) in the WSDL >> >> From the XMLSchema spec >> (http://www.w3.org/TR/xmlschema11-1/#cElement_Declarations) >> >> "The (top-level) element declaration .resolved. to by the >> .actual value. of the ref [attribute]." >> >> This means essentially that the global element declaration >> will be substituted for the element reference. In other >> words, the name must be "ActivityIdentifier" in the >> bes-factory namespace. If your tooling isn't doing this then >> it's non-compliant. >> >> Peter >> >> Mark Morgan wrote: >>> In trying to interop with Glenn's endpoint, I have found another >>> potential problem with the BES-Factory's WSDL. However, >> the problem >>> is at a level of WSDL that is slightly beyond my experience. In >>> particular, the problem is with two message types; the >>> GetActivityDocuments message type, and the TerminateActivitiesType >>> message. Both problems are identical. In brief, here are three >>> elements from the WSDL (the first of which is an example of a type >>> declaration which works for me, and the latter two being >> the problem declarations). >>> <xsd:complexType name="GetActivityStatusesType"> >>> <xsd:sequence> >>> <xsd:element name="ActivityIdentifier" >>> type="wsa:EndpointReferenceType" >>> maxOccurs="unbounded"/> >>> </xsd:sequence> >>> </xsd:complexType> >>> >>> <xsd:complexType name="GetActivityDocumentsType"> >>> <xsd:sequence> >>> <xsd:element ref="bes-factory:ActivityIdentifier" >>> minOccurs="0" maxOccurs="unbounded"/> >>> </xsd:sequence> >>> </xsd:complexType> >>> >>> <xsd:complexType name="TerminateActivitiesType"> >>> <xsd:sequence> >>> <xsd:element ref="bes-factory:ActivityIdentifier" >>> minOccurs="0" maxOccurs="unbounded"/> >>> </xsd:sequence> >>> </xsd:complexType> >>> >>> The first one works for me, and the last two do not. The >> problem with >>> the second and third ones is that my tooling doesn't know >> what name to >>> give the element for the EPRs inside of the message elements.. In >>> otherwords, it generates messages which look like the following: >>> >>> <GetActivityDocuments >>> xmlns="http://schemas.ggf.org/bes/2006/08/bes-factory"> >>> <item xmlns="" >>> xmlns:ns3="http://www.w3.org/2005/08/addressing" >>> xsi:type="ns3:EndpointReferenceType"> >>> >>> >> <ns3:Address>https://wincluster1.cs.virginia.edu/HPCP/HPCPServ > ice.asmx</ns3: >>> Address> >>> <ns3:ReferenceParameters> >>> <jobID >>> xmlns="http://schemas.ggf.org/hpcp/2006/07/hpcp-app">113</jobID> >>> </ns3:ReferenceParameters> >>> </item> >>> </GetActivityDocuments> >>> >>> <TerminateActivities >>> xmlns="http://schemas.ggf.org/bes/2006/08/bes-factory"> >>> <item xmlns="" >>> xmlns:ns3="http://www.w3.org/2005/08/addressing" >>> xsi:type="ns3:EndpointReferenceType"> >>> >>> >> <ns3:Address>https://wincluster1.cs.virginia.edu/HPCP/HPCPServ > ice.asmx</ns3: >>> Address> >>> <ns3:ReferenceParameters> >>> <jobID >>> xmlns="http://schemas.ggf.org/hpcp/2006/07/hpcp-app">113</jobID> >>> </ns3:ReferenceParameters> >>> </item> >>> </TerminateActivities> >>> >>> Notice the child element called "item" in each message. >>> >>> The simple (and obvious to me) fix was to change the >>> GetActivityDocuemntsType and TerminateActivitiesType type >> definitions >>> to specify the name of the inner element, i.e. to change them to: >>> >>> <xsd:complexType name="GetActivityDocumentsType"> >>> <xsd:sequence> >>> <xsd:element name="ActivityIdentifier" >>> ref="bes-factory:ActivityIdentifier" >>> minOccurs="0" maxOccurs="unbounded"/> >>> </xsd:sequence> >>> </xsd:complexType> >>> >>> <xsd:complexType name="TerminateActivitiesType"> >>> <xsd:sequence> >>> <xsd:element name="ActivityIdentifier" >>> ref="bes-factory:ActivityIdentifier" >>> minOccurs="0" maxOccurs="unbounded"/> >>> </xsd:sequence> >>> </xsd:complexType> >>> >>> I know that these are legitimate fixs, the questions are, >> A) are these >>> in fact real errors that my tooling is finding and thus the >> WSDL is in >>> error, and B) can we make these changes permanent in the >> BES-Factory >>> WSDL to fix these problem? >>> >>> -Mark >>> >>> -- >>> Mark Morgan >>> Research Scientist >>> Department of Computer Science >>> University of Virginia >>> http://www.cs.virginia.edu >>> mmm2a(a)virginia.edu >>> (434) 982-2047 >>> >>> -- >>> ogsa-hpcp-wg mailing list >>> ogsa-hpcp-wg(a)ogf.org >>> http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg >>> >> >

2 3

Wiki updates
by Christopher Smith 20 Oct '06

20 Oct '06

Hi all, I've put references to the various schema and wsdl documents on the wiki front page. There are links to the gridforge pages for JSDL and HPCProfileApplication, and then wiki pages for the bes factory schema and wsdl so that we can edit. These are the versions of the documents that I am using, so if there are any discrepancies, please let me know! :-) -- Chris

1 0