[ogsa-hpcp-wg] Globus Status

Christopher Smith csmith at platform.com
Mon Nov 6 11:43:35 CST 2006


Even though I had hoped to avoid it, Mark's service required the use of the
EPR and the WS-Addressing support in the client, so I added it. :-)

-- Chris


On 06/11/06 08:08, "Peter G. Lane" <lane at mcs.anl.gov> wrote:

> This is what Chris said:
> 
> I'm guessing that yours will require me to
> set some SOAP header blocks based on the WS-Addressing SOAP binding. I had
> hoped to avoid this detail for now....
> 
> By this I was under the impression that nobody was going to build clients that
> added WS-Addressing
> SOAP headers. If that was the case, then services shouldn't publish EPRs that
> have anything more
> than an address field.
> 
> Chris, did you change your mind? Was this only your point of view, or did you
> think that everyone
> was going to skip the SOAP headers as well?
> 
> At any rate, I should still be able to interop with those services that aren't
> expecting the SOAP
> headers. It just means I have to exclude at least the Genesis II
> implementation since I won't have
> enough time to implement the agreed upon version of WS-Addressing.
> 
> Peter
> 
> Mark Morgan wrote:
>> I think you misunderstood the result of that discussion.  The end result was
>> that services that didn't NEED EPRs, could use URLs.  However, we didn't
>> dissalow EPRs, only allowed the more degenerate case of them (the pure URL).
>> 
>> -Mark
>> 
>> --
>> Mark Morgan
>> Research Scientist
>> Department of Computer Science
>> University of Virginia
>> http://www.cs.virginia.edu
>> mmm2a at virginia.edu
>> (434) 982-2047 
>> 
>>> -----Original Message-----
>>> From: ogsa-hpcp-wg-bounces at ogf.org
>>> [mailto:ogsa-hpcp-wg-bounces at ogf.org] On Behalf Of Peter G. Lane
>>> Sent: Monday, November 06, 2006 10:28 AM
>>> To: ogsa-hpcp-wg at ggf.org
>>> Subject: [ogsa-hpcp-wg] Globus Status
>>> 
>>> I have the create and terminate operations implemented and
>>> working locally. I will put up an endpoint sometime today,
>>> and by them will hopefully have the other operations
>>> implemented. Is there a WSDL snipit or something of this
>>> "Show job output" operation, or does this just mean that I
>>> have an FTP server running?
>>> 
>>> Problems
>>> --------
>>> I am unable to get responses from either of the .Net
>>> implementations using my client. My SOAP message logging show
>>> that the client message is going out, but nothing is ever
>>> received back. Are these services still up?
>>> 
>>> I tried using my client on the Platform service (service URL
>>> https://plato.dreadnought.org), but I got an error saying
>>> that the client couldn't find the correct CA. I did download
>>> and install the CA cert and have debug output showing it was
>>> loaded, so I'm wondering if anyone has had success with this
>>> service recently. If so, Chris, could I get the public
>>> certificate of the server to help in my debugging?
>>> 
>>> After agreeing that we wouldn't use EPRs, I'm confused about
>>> the use of them on the wiki. I did what others did and didn't
>>> bother implementing support for the WS-Addressing SOAP
>>> headers. The Platform EPR is trivial so that's not a problem.
>>> The GenesisII EPR, though, is very non-trivial. That said, I
>>> see that some clients have indeed talked to the GenesisII
>>> endpoint, so I'm rather confused. Did I miss a discussion
>>> where it was decided that full WS-Addressing support was now
>>> mandatory?
>>> 
>>> Finally, I tried to use the CROWN endpoint too, but I get the
>>> following error:
>>> 
>>> Authentication failed [Caused by: Defective credential
>>> detected [Caused by: [JGLOBUS-96] Certificate
>>> "C=CN,ST=Beijing,L=Beijing,O=company,OU=department,CN=localhos
>>> t" expired]]
>>> 
>>> Peter
>>> 
>> 
> 
> --
>   ogsa-hpcp-wg mailing list
>   ogsa-hpcp-wg at ogf.org
>   http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg



More information about the ogsa-hpcp-wg mailing list