December 2006 - ogsa-bes-wg

GetActivityDocuments doesn't
by Peter G. Lane 20 Dec '06

20 Dec '06

In trying to finish up some stuff before I leave I noticed a discrepancy in the factory schema. The GetActivityDocumentsResponseType doesn't in fact return ActivityDocumentTypes. Here is the message type: <xsd:complexType name="GetActivityDocumentsResponseType"> <xsd:sequence> <xsd:element name="Response" type="bes-factory:GetActivityDocumentResponseType" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> And here is the response array element type: <xsd:complexType name="GetActivityDocumentResponseType"> <xsd:sequence> <xsd:element ref="bes-factory:ActivityIdentifier"/> <xsd:element ref="jsdl:JobDefinition" minOccurs="0"/> <xsd:element name="Fault" type="xsd:anyType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> The activity documents are more than just the JobDefinition: <xsd:complexType name="ActivityDocumentType"> <xsd:sequence> <xsd:element ref="jsdl:JobDefinition"/> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> The ref to jsdl:JobDefinition ought to be a ref to ActivityDocument as so: <xsd:complexType name="GetActivityDocumentResponseType"> <xsd:sequence> <xsd:element ref="bes-factory:ActivityIdentifier"/> <xsd:element ref="bes-factory:ActivityDocument" minOccurs="0"/> <xsd:element name="Fault" type="xsd:anyType" minOccurs="0"/> </xsd:sequence> </xsd:complexType> Just returning the JobDefinition means that any 'any's, such as the subscription or idempotent creation ID extensions, in the ActivityDocuments used in CreateActivity will be irretrievable. Peter

1 0

Good Bye
by Peter G. Lane 15 Dec '06

15 Dec '06

Hi All, Some recent circumstances have forced me to quit my job and become a stay-at-home dad for a year. I will probably monitor things from time to time, but at this point I don't have any plans to continue my involvement in the BES and HPCP working groups. Participating in these working groups has been a lot of fun as well as a useful experience. I learned a lot. It was nice meeting those of you who I did meet at OGF, and I regret missing many of the other HPCP demo participants at SC. Good luck to everyone and the future of open standards. Peter P.S. Please contact Stu Martin (smartin(a)mcs.anl.gov) if you need to ask any questions about the Globus Project's BES implementation/plans.

1 0

HPC Profile Conf Call - 12/6
by Richard Ciapala 06 Dec '06

06 Dec '06

Attendees · Marty · Glenn · Chris · Alessandro · Rich Notes · Faults o We agreed with Chris's refactoring of faults per his earlier email. Need to validate in tooling o We agreed with Chris's list of faults and decided to add a generic invalid input fault. Still need to decide if we have more specific faults for common invalid input such as activity ID or just use generic invalid input fault. · FactoryAttributesDocument o We agreed with Chris's refactoring of factory attributes document. The main changes included: § Minor naming changes § Embedding BasicResourceAttributesDocument in FactoryResourceAttributesDocument (as opposed to having the latter derive from the former) § Added ResourceName § Subelements of ContainedResource must be BasicResourceAttributesDocument or FactoryResourceAttributesDocument § Considering using lexical representation for values of NamingProfile and LocalResourceManagerType · Range_Type o We agreed to mandate support for min and max processor count via LowerBoundRange and UpperBoundRange · Filter o Reviewed reasons for needing filter o Discussed adding Filter element to GetFactoryAttributesDocumentType with Any subelements to allow for filter extensions o Discussed working through a filter extension which will likely be a profile extension · Security o Will discuss next week Thanks

1 0

Changes to factory attributes document
by Christopher Smith 06 Dec '06

06 Dec '06

Hi all, I just wanted to send out a couple of sample XML documents for discussion in tomorrow's call. The first attachment is an example of a factory attributes document, as is reflected with the current schema (including all the issues we've seen having to do with multiple xsd:any, etc). I've also added some sample "extensions" as placeholders. The second attachment reflects some schema changes that I'd like to propose. One is just a re-factoring to avoid the use of XML Schema extension as discussed in last week's call. I've also added a proposed new element to the basic resource (resource name) which I'd like to see added. -- Chris

1 0

To website admin
by Ahmed Shiraz Memon 04 Dec '06

04 Dec '06

Hi It seems OGSA BES website is down. Can anyone confirm please? cheers shiraz

2 1

Re: [OGSA-BES-WG] Where to find functional BES WSDL?
by Aleksandr Konstantinov 01 Dec '06

01 Dec '06

On Thu, 30 Nov 2006 12:13:23 -0700 "Peter G. Lane" <lane(a)mcs.anl.gov> wrote: > The HPCP interop demo wiki has links to usable WSDLs and schemas (see "Reference Documents": > > http://forge.ggf.org/sf/wiki/do/viewPage/projects.ogsa-hpcp-wg/wiki/HomePage > > They aren't official, but the HPCP working group is working on getting most of the changes adopted. Thanks a lot. It works. At least gSOAP digested it without any problem. Are there any other secret pages with Activity and Management WSDLs ? :) A.K. --

2 1