[ogsa-hpcp-wg] Agenda for Friday's Call

[Christopher Smith]

I wasn't going to put the text of JSDL or HPCProfileApplication in the same
way as the WSDL and BES Factory Schema, but I can put some links to the
schemas. 

FYI ... if you look in the list archives for HPCP, there should be a post
from me that has the schema as an attachment. I've also attached it to this
message. It should also be posted as a separate document in the JSDL working
group's project page.

https://forge.gridforum.org/sf/go/doc13911?nav=1

-- Chris



On 20/10/06 09:07, "Peter G. Lane" <lane at mcs.anl.gov> wrote:

> Along with the BES wsdl and xsd, could someone post an official
> HPCProfileApplication extensions
> schema on the wiki. All I am finding is a document with a pseudo schema.
> 
> Peter
> 
> Richard Ciapala wrote:
>> Toll Numbers:   USA     1-203-480-8000
>> TollFree Numbers:       USA     866-500-6738
>> Participant Passcode:   231867
>> 
>> -----Original Message-----
>> From: Peter G. Lane [mailto:lane at mcs.anl.gov]
>> Sent: Friday, October 20, 2006 7:27 AM
>> To: Richard Ciapala
>> Cc: ogsa-hpcp-wg at ogf.org
>> Subject: Re: [ogsa-hpcp-wg] Agenda for Friday's Call
>> 
>> What about the phone number and passcode?
>> 
>> Richard Ciapala wrote:
>>> Hi,
>>> 
>>> 
>>> 
>>> During tomorrow's conf call, maybe we can take another step forward with
>>> regards to coordinating the demos that show off the HPC Basic Profile
>>> web service implementations. As we have discussed on previous calls, the
>>> rough plan has been to balance some level of consistency across
>>> server-side implementations while allowing participants to build their
>>> own clients. Though in some cases participants may partner to build
>>> metascheduling  or workflow scenarios, we also discussed a "base" demo
>>> where any participant can execute an activity on any other participant's
>>> cluster, manage the activity and retrieve output. If we agree to have
>>> this base demo, besides the individual HPC Basic Profile web service
>>> implementations, each participant would be asked to provide the following:
>>> 
>>> 
>>> 
>>> *         An application hosted on their cluster
>>> 
>>>     * The JSDL to execute that application
>>>     * A consistent way to specify the name of the application in the
>>>       JSDL so it can be forwarded to the correct cluster (for those who
>>>       will do forwarding scenarios)
>>>     * A HTTP directory from where the results of the application is
>>>       produced. Possibly in the format of
>>>       (http://address/output/application/user)
>>> 
>>> With that said, an agenda for tomorrow's call could be:
>>> 
>>> 
>>> 
>>> *         Should we move forward with the base demo?
>>> 
>>>     * How should the application be specified in the JSDL for forwarding
>>>       scenarios?
>>>           o Use existing JSDL ApplicationName (which is not in HPC Basic
>>>             Profile but isn't precluded from being used)
>>>           o HPCProfileApplication\@name attribute (which is in the HPC
>>>             Basic Profile)
>>>           o Other?
>>>     * Open marketing issues
>>>     * WSDL/XSD changes
>>> 
>>> Thanks
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------
>>> 
>>> --
>>>   ogsa-hpcp-wg mailing list
>>>   ogsa-hpcp-wg at ogf.org
>>>   http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg
>> 
> 
> --
>   ogsa-hpcp-wg mailing list
>   ogsa-hpcp-wg at ogf.org
>   http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: jsdl-hpcp.xsd
Type: application/octet-stream
Size: 5787 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/ogsa-hpcp-wg/attachments/20061020/e1781eeb/attachment.obj