April 2006 - cddlm-wg - lists.ogf.org

A new endpoint!
by Steve Loughran 02 May '06

02 May '06

I am pleased to announce the availability of the HP CDDLM endpoint, public beta release The URL for the portal is :- http://deployapi.iseran.com:8080/alpine/portal/ It is visible through the (three) firewalls, and has been tested remotely. A GET will return a short note confirming the endpoint's existence. Make sure you have the trailing / as the servlet is unforgiving. If the connection is refused, the endpoint is probably down. Notes -this is a new SOAP stack with its own WSA and WSRF implementation. It only implements the subset we need, and those are not adequately interop tested. please mail your results to the group or direct to me. -deployment is not working. I will find out why next week, but will then have to actually implement security on the endpoint before deploying a fixed version -System:addFile is not finished, and when it is it will initially only support inline (base 64) content, not attachments. MTOM Is not on the todo list. -WS-Notification has not even begun; I dont even implement the properties that list supported topics. Frankly, I'm not overwhelmingly motivated to implement WS-N. -It's hosted on a laptop on the WLAN somewhere in my house. It needs more memory. Please be gentle with it :) Monday in the UK is a holiday (May 1st, Socialist Unity Day!), so there is no likelihood of any changes to the stack being made before Tuesday. I'll field basic interop problems first (namespaces, WSA headers, SOAPAction), then worry about -better fault reporting -automating a checkout, rebuild and redeploy early every morning. -testing Alpine's WSA impl. against the .NET 2.0 endpoints -making the server-side logs public by logging to log4j's HTML logger and serving those pages up somewhere. -have the server host the deployapi tests for our client and run them against all public stacks, again serving the data up for browsing. Clearly not all of these can be achieved in the finite time before GGF17, but we should be able to make progress along both the interop and functionality axes. Now if you'll excuse me, I have an extended weekend to attend to. Steve

1 2

mime type for CDL files
by Steve Loughran 27 Apr '06

27 Apr '06

Do we have any convention for the mime type for cdl files? I'm using application+cdl, and correcting the addFile example in the test docs to match this

1 0

updated api test doc
by Steve Loughran 26 Apr '06

26 Apr '06

I've updated the api test doc in CVS; please check it out with a non-anonymous account, as sourceforge's public repository mirror is out of sync with the developer once since the big filesystem corruption event earlier this month. it now says that you need to spin on waiting for things to become unavailable after a destroy, and that there is no single way to determine whether an endpoint no longer exists; 404, SOAPFault and WSRF-RP:NoSuchResource are all implicitly correct. -steve

1 0

[Fwd: FW: GGF Interoperability Fests]
by Steve Loughran 26 Apr '06

26 Apr '06

Announcement of the interop mail list. Currently quiet. -----Original Message----- > From: Stephen M Pickles [mailto:Stephen.Pickles@manchester.ac.uk] > Sent: 18 April 2006 12:33 > To: neilc(a)epcc.ed.ac.uk; delaat(a)science.uva.nl; > donal.k.fellows(a)manchester.ac.uk; kfukui(a)labs.fujitsu.com; > j.r.gallop(a)rl.ac.uk; grimshaw(a)cs.virginia.edu; > mike.jones(a)manchester.ac.uk; kacsuk(a)sztaki.hu; > kielmann(a)cs.vu.nl; wwhl(a)doc.ic.ac.uk; Loughran, Steve; > matsu(a)is.titech.ac.jp; dejan(a)hpl.hp.com; > dave.pearson(a)oracle.com; stephen.pickles(a)manchester.ac.uk; > darcy.quesnel(a)canarie.ca; ysaeki(a)grid.nii.ac.jp; > saga(a)grid.nii.ac.jp; sergiu(a)psc.edu; > andreas.schott(a)rzg.mpg.de; sekiguchi(a)m.aist.go.jp; > david.snelling(a)uk.fujitsu.com; yoshio.tanaka(a)aist.go.jp; > tatemura(a)sv.nec-labs.com; olli.tourunen(a)csc.fi; > travos(a)nortel.com; Treadwell, Jem; sachiko(a)ascade.co.jp; > wasson(a)virginia.edu; viktor.yarmolenko(a)manchester.ac.uk; > scrumb(a)ggf.org; jms(a)mcs.anl.gov; darren(a)pulsipher.org; > asm(a)doc.ic.ac.uk; norm(a)cs.man.ac.uk; mmm2a(a)virginia.edu > Subject: GGF Interoperability Fests > > Dear all, > > Thanks for attending the Interoperability Fests BoF at GGF16. > This is to bring you up to date with follow-on activities. > > A GGF mailing list, interop-bof(a)ggf.org, has been set up. > You are invited to subscribe. We have NOT subscribed you > automatically. It's a standard majordomo list: send mail to > majordomo(a)ggf.org with the body "subscribe interop-bof". > > Please do not spam each other. All follow up discussions > should take place on the list. > > I anticipate this list being used for several purposes, > including, but not limited to, the following: > - to provide a community self-help list for issues relating > to interoperability testing, especially in the context of > GGF standards development. > - to act as a forum for determining whether there is a real > need for some kind of interoperability group in GGF, and if > so, decide what it should do, produce a draft charter, and > find volunteers willing to drive it forward. > - to decide whether to hold another ad hoc BoF at GGF17, and, > if so, what should be on the agenda. There are still meeting > rooms available in Tokyo, but we'd need to move quickly. > > There is a gridforge project called "interop-bof" at: > https://forge.gridforum.org/projects/interop-bof/ > > Presentations from the GGF16 BoF are available at: > http://www.ggf.org/gf/event_schedule/index.php?id=212 > > The DAIS-WG has written a document entitled "Interoperability > Testing for DAIS Working Group Specifications" > describing their planned approach to interoperability testing. > It is now in public comment. You can view it and make > comments through the GGF public comment page: > http://www.ggf.org/gf/docs/?public_comment > > Stephen > >

1 0

CDDLM notes from 4/26
by Milojicic, Dejan S (HP Labs) 26 Apr '06

26 Apr '06

Attendees: Ayla, Guilherme, Steve, Satish, Jun, Dejan Interoperability: Ayla: Problems with the component model. Guilherme performed other testing with Jun's endpoint. Trying to initialize endpoint, but he could not initialize the system. Satish noticed some access and had some syntax errors on NEC side. XML was not really conforming to his implementation. Satish sent some email about how to create files. They have updated their own version, but they continuously do that. Steve said that he had some problems regarding test wrt Deployment API. Destroy the system, then try to access it, and it should not access it any more, but on UFCG side these activities are not synchronous, it will not happen immediately. Steve: The question is what WSRF considers a right behavior, not addressed in WSRF spec, probably. Neither do we say that destroy must be instantaneous. Should we modify the test? Steve: running his client against two public endpoints and rudimentary conversation with OurGrid, a lot of service side errors with NEC. Will run his endpoint before the end of the week. He will publish his outcome so that others can see what is going on. Once he puts his end point you can see what is the problem with Satish's end point. Probably related to WS-Addressing. So next 2 days, bring his endpoint and see what his client is not talking to others. His client a the moment can not deploy anything to his server. However, you can get properties and create/destroy the system, however sending the deployment descriptor is failing right now, will worry about this later. Jun/Satish: Satish worked on component model testing, found bugs and fixing them. Worked on Ayla's endpoints and have a few questions. When we create systems and issue lookup request. If the system is not there, the Ayla's implementation returns the stack, whereas NEC returns the app does not exist (return not the error but error string). What is the standard for returning errors? Steve: there is no normative standards. It seemed to early to mandate for each possible implementation. NI the deployment API spec, there is a bit of no-normative stuff and he has a sort of faults with some error code underneath, but it is not required for various faults. We have a very minimal set of faults. It would be good to have a consistent set of error codes. Satish will continue component testing and on the Ayla's endpoint. Quick checkpoint on where we are: Ayla: she feels that approach is good that they will continue to discover many interoperability problems. Everybody will continue with feedback. Not sure where we are wrt completion. At least 80% completed of deployment API, 60% of component model. Steve: quite enjoying interoperability tests. If he can get his endpoint up he feels he is 50%, the other 50% is how does he measure progress. One by one test, he will checking them off. There are issues of the underlying implementation of WSRF, NEC and OurGrid have the same WSRF implementation, they will not have interoperability with. Satish: NEC and OurGrid have different implementations because of the lack of the standard CDL implementation configuration file. Everything else, from the deployment API perspective it is ok. 60% component model completed and deployment APIs 75%. The goal is to have all tests passed between endpoints. Update on the specs, Deployment APIs and Component model are official GGF specs. CDL a few weeks away. Update on Wiki: it up, need to enable others. Jun: updates on the OGSA meeting, explained our position, Jun and Hiro will discuss the component model design for OGSA, in Tokyo. First Hiro and Jun will discuss it and then later on they will discuss it with Stuart. Next week, we will discuss the presentation at GGF. Especially interoperability. Thanks, Dejan.

1 0

RE: SourceForge project membership added: CDDLM-Interop
by Milojicic, Dejan S (HP Labs) 26 Apr '06

26 Apr '06

Team, we got the Wiki pages off of the GridForge. We can start using them and putting itneroperability data there. Thanks, Dejan. > -----Original Message----- > From: SourceForge Administrator [mailto:kdrew@mcs.anl.gov] > Sent: Monday, April 24, 2006 9:47 AM > To: dejan(a)hpl.hp.com > Subject: SourceForge project membership added: CDDLM-Interop > > > You have been granted access to the CDDLM-Interop project. > > Visit the project at > http://testforge.ggf.org/sf/projects/cddlm_interop > >

1 0

FW: [wg-all] New documents published!
by Milojicic, Dejan S (HP Labs) 25 Apr '06

25 Apr '06

Congratulations Team, We have two nice numbers: GFD #65 and #69. Best regards, Dejan. -----Original Message----- From: owner-wg-all(a)ggf.org [mailto:owner-wg-all@ggf.org] On Behalf Of Greg Newby Sent: Tuesday, April 25, 2006 12:10 PM To: wg-all(a)ggf.org Subject: [wg-all] New documents published! Several new documents have been published recently. Please visit the GGF Documents page to download these and others: http://www.ggf.org/gf/docs/?final GGF #69: Configuration Description, Deployment, and Lifecycle Management (CDDLM) Deployment API. Draft Recommendation. S. Loughran. GFD #68: Workshop on Grid Applications: From Early Adopters to Mainstream Users. Information tarck document. D. Wallom, T. Kielmann. GFD #67: OGSI Authorization Requirements. Informational document. V. Welch, F. Siebenlist, D. Chadwick, S. Meder, & L. Pearlman. GFD #66: Use of SAML for OGSI Authorization. Experimental document. V. Welch, R. Ananthakrishnan, F. Siebenlist, D. Chadwick, S. Meder, & L. Pearlman. GFD #65: Configuration Description, Deployment, and Lifecycle Management (CDDLM) Component Model v 1.0. Draft recommendation. S. Schaefer GFD #64: Grid Scheduling Use Cases. Informational document. R. Yahyapour. GFD #63: Copyright, Disclaimer and Intellectual Property Statements. Community practice document. D. Martin. Thanks to authors/editors and WG/RG/CG members for their work on these documents, and to the entire GGF community for participating in evaluation and feedback through public comment. -- Greg Newby (GGF Editor) Dr. Gregory Newby, Chief Scientist, Arctic Region Supercomputing Center Univ of Alaska Fairbanks-909 Koyukuk Dr-PO Box 756020-Fairbanks-AK 99775-6020 e: newby AT arsc.edu v: 907-450-8663 f: 907-450-8603 w: www.arsc.edu/~newby

1 0

OGSA call summary
by Stuart Schaefer 24 Apr '06

24 Apr '06

At today's OGSA call, three issues were on the table for our team. The first two were not discussed. Hiro and Jun have an action item to discuss default components. Steve Newhouse has an action item to document his usage cases for conversation. The final topic was the issue of CDL lazy references being overrideable by a user of the system. According to the CDL specification, the cdl:lazy attribute can have a Boolean value. Thus, this allows a template to have a property with cdl:lazy equal to true. In a CDL file which imports or extends from this template, the appropriate property can set the attribute value to false, and then provide a value for the property. This explanation was sufficient for the OGSA team to clarify the successful handling of this usage case. Stuart Stuart Schaefer CTO sschaefer(a)softricity.com Softricity, Inc. 27 Melcher Street Boston, MA 02210 ph 617.695.0336 x112 fx 617.338.7769 www.softricity.com - Virtually, Anything Is Possible(tm) The Softricity Desktop(tm) enables applications to be as instantly available and easy to use as electricity "All problems in computer science can be solved by another level of indirection". -- Butler Lampson

3 2

CDDLM Deployment API is published as GFD-R.069
by Hiro Kishimoto 23 Apr '06

23 Apr '06

Congratulations! ---- Hiro Kishimoto Sourceforge Tracker Monitor wrote: > Comment By: Greg Newby (2006-04-22 16:17:13) > This document will now be published as GFD-R.069 > > Thanks to the authors/editors for work on this document!

1 0

Firewall issue resolved - NEC portal EPR is up and running
by Satish Bhat 21 Apr '06

21 Apr '06

Hi All, Our Portal EPR is up and running now. It was a firewall issue! Cheers, Satish

2 4