- ogsa-hpcp-wg - lists.ogf.org

Platform SC06 endpoint
by Christopher Smith 13 Oct '06

13 Oct '06

Here is my endpoint information. I'm currently front ending an LSF cluster at: https://aristotle.dreadnought.org:9090 The CA cert (in DER format) can be found at: https://www.usertrust.com/cacerts/UTN-USERFirst-Hardware.crt All operations at this point will return a soap receiver fault saying the op is unimplemented, but the ops should not take long to appear. I'll post an appropriate JSDL later today when I have the CreateActivity operation implemented. -- Chris

1 0

Discuss open marketing issues
by Richard Ciapala 13 Oct '06

13 Oct '06

When: Tuesday, October 17, 2006 8:00 AM-9:00 AM (GMT-08:00) Pacific Time (US & Canada); Tijuana. Where: Conf Call *~*~*~*~*~*~*~*~*~* Close out most/all open marketing issues: Toll Free Number: 866-500-6738 International: 1-203-480-8000 Passcode: 231867 Thanks

1 0

Minutes from SC06 Interop Demo Call - 10/13
by Richard Ciapala 13 Oct '06

13 Oct '06

Here are the minutes from today's call: Attendees * Suzanne Balle - HP * Chris Smith - Platform * Glenn Wasson - UVA * Steve McGough - Imperial * Joel Replogle - OGF * John Ehrig - OGF * Duane Merrill - UVA * Dave Snelling - Fujitsu * Rich Ciapala - MS Announcements * Tokyo Institute of Technology has agreed to build an HPC Basic Profile web service for their Sun Grid cluster Web Service Status * Chris - Platform/LSF o Skeleton web service available. Chris will send email to mailing list with URI (and test JSDL when CreateActivity is functional) * Glenn - CCS o Full implementation available. Glenn will send out URI and test JSDL to mailing list. * Glenn - PBS o CreateActivity and GetStatus available. Glenn will send out URI and test JSDL to mailing list. * Steve - Imperial o Investigating effort required to move current BES web service to HPC Basic Profile * Duane - UVA o Plan to start migrating current BES web service to HPC Basic Profile next week. * Dave - Fujitsu o Finishing up a different demo this week. May have something working by the end of next week. * Rich - CCS o Full implementation available. I will send out URI and test JSDL. Marketing * Chris will reply to Joel's email to mailing list and answer some of the questions * We will have another conference call on Tues at 8am PDT on the same conf call number to close out any further marketing questions. Rich will send out a calendar request. Thanks

1 0

reminder: call today (right now!)
by Marty Humphrey 06 Oct '06

06 Oct '06

Folks, A quick reminder: We have a weekly conf call to discuss SC06 interop demo status and issues. It starts in just a few minutes. See you there! -- Marty Toll Free Number: 866-500-6738 International: 1-203-480-8000 Passcode: 231867

1 0

<no subject>
by Christopher Smith 04 Oct '06

04 Oct '06

Hi all, Seeing as SC06 isn't _that_ far away, especially for those planning their booths and the like, I'd like to start the ball rolling on how we present this demo to the community at large. Basically ... what's the marketing story here. Steve C ... not sure if you're the right OGF person ... if not please identify the correct person. It would be good if every group involved in the demo would identify a person who can get involved in the marketing aspect of the demo, so that we can craft some collateral and the like. For Platform, Ashar Baig (copied on the message) will be the contact person. Thanks, -- Chris

2 1

Update to HPC Profile Application extension
by Christopher Smith 02 Oct '06

02 Oct '06

Hi all, I've updated the HPC Profile Application document on gridforge. https://forge.gridforum.org/sf/go/doc13863?nav=1 Changes include: - application of new OGF template - added text around relationship of stdio file elements to WorkingDirectory - added some text about how filenames in the Executable might be related to things like PATH lookups I'm having one "technical" issue after applying the new template that I cannot seem to resolve. I cannot get the numbering of the appendix to start from 'A'. If anybody can coerce the document to get the numbering right, I'd be eternally grateful. :-) -- Chris

1 0

Minutes from Sept-29-06 call
by Marty Humphrey 01 Oct '06

01 Oct '06

Minutes from OGSA HPC Profile (SC 2006 Demo) call, Sept-29-06 11:00 EDT Participants: Marty Humphrey, University of Virginia Chris Smith, Platform Rich Ciapala, Microsoft Susanne Balle, HP Vivian Li, Fujitsu Steve McGough (GridSAM), Imperial College Ming Xu, Microsoft Note: the telecon has been moved, starting this week, to Fri 11:00 EDT Topics: [1] Put http://www.cs.virginia.edu/~humphrey/SC2006.htm at GridForge wiki? Yes or No? Marty gave an overview of the pros and cons of putting the current status of the interop work at the GridForge wiki site for OGSA-HPCP. Because there is potentially confidential information intended to be on this page, the group chose to keep the information in the current place (via a planned password-protected page at the University of Virginia, which was viewed as the simpler mechanism than the wiki). Chris Smith suggested that we divide the content into two types: public and private. The public could go on the GridForge page, while the private could stay at UVa. We generally tabled this discussion (because it's not a pressing issue right now). [2] "What should we do about faults" - see the message Glenn Wasson sent out recently for details It was discussed that the SOAP-1.2 fault message might be used in a problematic way, and that this is a topic for BES more than our group directly. Resolution: Rich will take the latest from Peter Lane and propose that instead of SOAP-1.2 fault element inside of the response message we use xsd:any, and [2] this should be brought up in BES. Rich noted that we might not need SOAP-1.2 because it was only brought in for faults. [3] "do you accept the following schema changes" - Glenn Wasson sent out a message about this ("these are typos or errors in the schema that have to be fixed for everyone's tooling") It was noted that Peter and Glenn seem to be converging, and then we believe that the ball was in Glenn's court. Rich used Peter's email from last night (Thurs/Fri), and that it seemed ok. Resolution: Noting that Peter's last email asked Glenn to identify the duplicate elements, and seeing that Glenn is currently at a conference, Rich is going to attempt to identify the precise duplicates and send email to the group. Related to this, we believe "GetFactoryAttributesDocument" is the correct name -- but this doesn't seem to be reflected in the current BES version (v26? Someone has the token to create a v27? We will check with Mark Morgan.) Rich will send out new schema today. Next call: Friday Oct 6 11:00 EDT

1 0

wsdl/xsd modifications for BES v26
by Glenn Wasson 30 Sep '06

30 Sep '06

Hello, As part of the HPC Profile interop work, I have been trying to process the BES v26 WSDL through my tooling (Microsoft's wsdl.exe). I have found a number of problems with the BES-Factory wsdl and xsd that appears in the appendix of the BES document. Some of these issues are simple typos and some require re-formulations of the wsdl/xsd in order to work with the tooling. I have attached modified versions of both the wsdl and xsd for bes-factory and, below, I have provided a summary of the changes. I contend that these changes (apart from fixing typos) don't actually change the defined interface/data types - they are merely an alternate way of expressing the same ideas using wsdl/xsd that (at least my) tooling can handle. I am interested in: a) comments on this reformulation b) whether anyone else, who is using different tools, has had similar (or different) issues with the wsdl/xsd in the BES v26 appendix c) whether anyone using different tools encounters issues processing the attached wsdl/xsd d) whether people participating in the HPCP interop work are willing to use the attached wsdl/xsd Glenn Summary of changes: 1. bes-factory wsdl (appendix E) and bes-factory xsd (appendix B) both have <xsd:schema> elements with the same target namespace - moved schema types from bes-factory.wsdl to bes-factory.xsd - changed <schema> element in bes-factory.wsdl to only import bes- factory.xsd (other imports seemed to create problems because the same schemas were also imported in the bes-factory.xsd file) - changed target namespace of <xsd:schema> element in bes-factory.wsdl to http://schemas.ggf.org/bes/2006/08/bes-factory/WSDL (added the /WSDL) - This doesn't effect anything since no types are defined in the bes- factory.wsdl's <xsd:schema>, but was necessary to prevent the namespace collision 2. the operation "ResponseType" elements are multiply defined - both the wsdl and xsd define <xsd:element>s for, for example, CreateActivityResponse (the definitions differ only in the name of an outer element wrapper) - kept the definition with the outer element wrapper around the type (i.e. <Response> as the outer element) - moved this definition to bes-factory.xsd and simply reference it from bes-factory.wsdl 3. typos in the types of the response elements for several operations - GetActivityStatusesResponse, TerminateActivitiesResponse, GetActivityDocumentsResponse should be of types GetActivityStatusesResponseType, TerminateActivitiesResponseType, GetActivityDocumentsResponseType respectively 4. added minOccurs and maxOccurs to the GetAttributesDocument related classes - spec seems undecided here

4 6

SC06 Interop Demo Conf Call
by Richard Ciapala 28 Sep '06

28 Sep '06

When: Occurs every Friday effective 9/22/2006 until 11/30/2006 from 8:00 AM to 9:30 AM (GMT-08:00) Pacific Time (US & Canada); Tijuana. Where: Conf Call *~*~*~*~*~*~*~*~*~* Updating to agreed upon time... Weekly conf call to discuss SC06 interop demo status and issues. Toll Free Number: 866-500-6738 International: 1-203-480-8000 Passcode: 231867 Thanks

1 0

Faults in BES v26 WSDL
by Glenn Wasson 28 Sep '06

28 Sep '06

Hello, I've been trying to push the WSDL/XSD in the appendices of the BES v26 document through my tooling and I have found an issue with the fault messages. The XSD for the BES-Factory defines 3 fault types (NotAcceptingNewActivitiesFaultType, UnsupportedJSDLVersionFaultType, and UnsupportedFeatureFaultType) as extensions of the base type SOAP Fault (there is a typo here, but what I believe is intended is for these types to derive from the Fault type defined in http://www.w3.org/2003/05/soap-envelope) However, I believe that SOAP faults cannot be used as a base type (i.e. other types cannot derive from Fault). Certainly my tooling (Microsoft's WSDL.exe for .NET 2.0.50727.42) will not allow this definition. The definition of the Fault type in http://www.w3.org/2003/05/soap-envelope is: <xs:complexType name="Fault" final="extension">, which I believe means no complex type can be derived from this. So, I have two separate, but related questions (it would be nice if they had the same answer, but they don't have to). 1. How should groups building HPC Profile-compliant services address this? 2. How should the BES wg address this? For #1, I have removed the fault type definitions. Groups implementing HPCP services should comment on ogsa-hpcp-wg about whether this is acceptable. For #2, it seems that BES has a couple of options. The first is to change the xsd so that the faults do not derive from SOAP fault (without returning to WSRF BaseFaults, which I believe were recently removed from the wsdl/xsd). The second option would be to establish a "best practice" on how fault types defined by BES should be included in normal SOAP faults (for example, they could be serialized into the <Detail> element). Comments/suggestions? Glenn

1 0