May 2005 - cddlm-wg - lists.ogf.org

proposed change to deploy API state info
by Steve Loughran 13 May '05

13 May '05

looking at the deployment API, it has three components: state enum, stateInfo (a string) and extended state <xsd:element name="state" type="cmp:lifecycleStateType"/> <xsd:element name="stateInfo" type="xsd:string"/> <xsd:element name="extendedState" type="cmp:unboundedXMLAnyNamespace" minOccurs="0"/> We dont really need that stateInfo string do we? the cmp: state identifies every state; if you want to map that enum to a string in the language/locale of preference, you are free to do so. And the extended state can be anything you like. I propose, therefore, dropping that element, leaving a sequence of <xsd:element name="state" type="cmp:lifecycleStateType"/> <xsd:element name="extendedState" type="cmp:unboundedXMLAnyNamespace" minOccurs="0"/> Comments?

1 0

comments on the GGF13 notes
by Steve Loughran 13 May '05

13 May '05

I'm revising the deployment API. Here are my comments on the GGF13 notes. Feedback welcom. -steve Dejan: Why are we required to invoke "run" on the system. Stuart: it may be possible to come up with a thin client at the portal who could replace naïve users and invoke sequences of these calls. Steve: We could make this a standard option for the create() operation; run after creation. That way you dont need to listen for a response to run something; no need for external workflow/WS-N callbacks to initiate something. Note of course that there is nothing to stop you sending a run() operation to the EPR, even while it is busy instantiating itself; it will be queued for interpretation in whatever state it enters next. Dejan: there is a different state diagram for system and for component model. Stuart, yes, this is required because of the WSRF and not exposing faults to outside world. Dejan: Can you please introduce a few sentences describing your reasoning why there is a difference. steve: I've removed the state model from the deployment API. Stuart: WS component or endpoint reference should be instead of xsd:any for system epr resolveRequest.sic services, Steve: I'd kind of envisaged that you could resolve to anything, beyond just a component. So if I resolve to an attribute of a component, I get that attribute back. Do you imagine the operation to just get the component EPR that you talk to directly? That would just be the special case where you resolve the name of a component. (including /, the root component of the app). Question (Dejan) : What about CDL across multiple deployment engines? Steve: The deployment API is designed so that you can delegate stuff across to different engine clusters inside an existing deployment descriptor. That is, you could write a meta-descriptor that would delegate stuff to one framework impl, different bits to another. Question (Dejan) : Can SmartFrog be translated into CDL? -A subset can. There are some things in the smartfrog language that do not map. Question (Dejan) : Can you envision GUIs for writing CDL? Steve:Any graphical thing with boxes and lines doesn't scale past the simple demo. Case in point: BizTalk, UML design tools. Certainly you could enhance an XML editor. Question (Dejan) : Will we provide verification tools? Steve: XSD validation is relatively easy, apart from the bits where extra types are defined inline/in the <types> section. This is why the xsd:any bits in the configuration/system elements are marked as processContents=lax; to tell a validating parser to skip validating those bits. Validating that is more complex. The other bit of validation is parse time matching of all non-lazy references, and evaluation of expressions. These dont show up in the XSD, and need interpretation to validate. Question : How difficult is it to implement this? Steve:I think dynamic typing (with extra XSD) is going to be tricky. Not impossible (WSDL processors do it), just fiddly. You need to extract/generate the schemas, add them to parser dynamically and then get it to validate the docs. Steve: I expect that my GGF14 implemenation will not do this. That is, it wont fail if the deployment descriptor doesn't match the XSD-defined <types>. typing via attribute declarations in the templates is probably easier. We need test documents for both of these. comments from Keisuke Fukui (ACS Chair) - people from Naregi will a driving force - ACS and CDDLM have tight relationship -- especially: addfile operation, deployment API Steve: addfile is a very primitive file upload mechanism; but it is simple enough to work without too much engineering effort. Note that there is nothing to stop an implementation or third party components providing extra library integration. As an example, here is smartfrog supporting dynamic download of verisioned artifacts from the Maven2 repository, home to all the open source JAR files #include "/org/smartfrog/services/filesystem/components.sf" #include "/org/smartfrog/services/os/java/components.sf" #include "/org/smartfrog/services/os/java/library.sf" sfConfig extends Compound { sfSyncTerminate true; library extends Maven2Library { } commons-logging extends JarArtifact { library LAZY PARENT:library; project "commons-logging"; version "1.0.4"; sha1 "f029a2aefe2b3e1517573c580f948caac31b1056"; md5 "8a507817b28077e0478add944c64586a"; } axis extends JarArtifact { library LAZY PARENT:library; project "axis"; version "1.1"; sha1 "edd84c96eac48d4167bca4f45e7d36dcf36cf871"; } tcpmonitor extends Java { classname "org.apache.axis.utils.tcpmon"; classpath [ LAZY axis:absolutePath, LAZY commons-logging:absolutePath]; logLevel 5; } } Here I am declaring that I want axis1.1 and commons-logging 1.04, the pair of them forming the classpath for a JVM. This is working code incidentally, the maven2 library is http://ibiblio.org/maven2 ; the maven2 library component contains the policy to construct a full URL for each artifact, the artifact components themselves download/cache the JAR files at initialization time, then the tcpmonitor program runs using the classpath to the cache. Repository management is an interesting area of ongoing work. If the ACS group is interested, they could join in the Apache mailing list, repository(a)apache.org, which has de-facto ownership of the problem of providing a global, mirrored repository of all open source java libraries. It would make a lot of sense if the URLs and signatures of versioned artifacts matched those expected by the next generation of Java applications. Note that the addFile() operation has a metadata element that supports arbitrary XML. This could be RDF metadata, but it could equally well be a Maven2 POM describing an artifact, in the relevant maven2 namespace. If a file were uploaded to a maven2-aware system, the maven2 layout could then be used for download -at the expense of portability across CDDLM implementations.

1 0

namespaces for the GGF14 specifications.
by Steve Loughran 13 May '05

13 May '05

I want to get consistency on namespaces for the next round of documents, before those documents are finalised. I also want those namespaces used in all the test files I'm writing, and then I want the namespaces to stay frozen.The more test cases there are -in different places- the higher the cost of switching to new namespaces becomes. without inline validation of the .doc files, its also dangerously easy to be out of sync in the documents. I also think we ought to have a consistent structure/date for the namespaces, ideally one which can acually resolve at some time in the future to XSD documents, that being what some XML tools like. I am not going to state what I think the layout should be, but we need to be consistent and stable. After this next draft, we should leave the namespaces alone unless we have good reason to change them. Jun, Stuart, can we come up with consistent namespace naming/structure for the next drafts. What are your current namespaces? -steve

1 0

FW: WSDM interop demo session and related WG schedule
by Milojicic, Dejan S 11 May '05

11 May '05

Hi Team, Please consider attending this session. It will be useful to CDDLM for many reasons, such as learning about WSDM and its use and about demonstrating interoperability. Thanks, Dejan. -----Original Message----- From: Fred Maciel [mailto:Fred.Maciel@hds.com] Sent: Tuesday, May 10, 2005 6:43 PM To: foster(a)mcs.anl.gov; hiro.kishimoto(a)jp.fujitsu.com; grimshaw(a)cs.virginia.edu; daveb(a)nesc.ac.uk; luniew(a)us.ibm.com; dejan(a)hpl.hp.com; tkojo(a)mvi.biglobe.ne.jp; kfukui(a)labs.fujitsu.com; studwell(a)us.ibm.com; peter.ziu(a)ngc.com; asm100(a)doc.ic.ac.uk; darren(a)pulsipher.org; ali(a)epcc.ed.ac.uk Cc: David Snelling Subject: WSDM interop demo session and related WG schedule To: Ian Foster, Hiro Kishimoto, Andrew Grimshaw, Dave Barry , Allen Luniewski, Dejan Milojicic, Takashi Kojo, Keisuke Fukui, Thomas Studwell, Peter Ziu, Steve McGough , Darren Pulsipher, Ali Anjomshoaa Cc: David Snelling Folks, The OASIS WSDM will be participating very actively in GGF14, one of the highlights being a plenary/outreach kind of session from 2:00p - 3:30p on Wednesday, June 29. This session will show how WSDM is useful throughout the GGF, by showing very different devices using WSDM, and also to do an interoperability demonstration of WSDM using these devices. We will call the press and analysts for PR, and people from multiple companies will be developing software and bringing equipement (e.g. heavy servers) for that session. In other words, this is a major event for the WSDM TC which will require a considerable amount of effort from the WSDM participants and from OASIS. One of our concerns is having enough participation from GGF to justify the effort. So I am requesting the GGF not to schedule related WGs at the same time (this includes WGs in which the participants might have interest in WSDM). So, I included your WGs in the list that I submitted to the GGF: - OGSA - OGSA-BES - OGSA-D - CDDLM-WG - ACS - JSDL - Naming I presume that this does not affect your plans, and I'm just sending this e-mail just FYI. Of course, I'm looking forward to your presence in the WSDM demo session. Regards, Fred Maciel Hitachi America R&D

1 0

FW: [sched-chairs] NOTES: GGF SRM Area - Chairs Telecon Notes, 10 May 2005
by Milojicic, Dejan S 10 May '05

10 May '05

-----Original Message----- From: owner-sched-chairs(a)ggf.org [mailto:owner-sched-chairs@ggf.org] On Behalf Of Stephen Pickles Sent: Tuesday, May 10, 2005 9:44 AM To: sched-chairs(a)ggf.org Subject: [sched-chairs] NOTES: GGF SRM Area - Chairs Telecon Notes, 10 May 2005 GGF Sched Area - Chairs Telecon Notes, 10 May 2005 ================================================== Attendees (with '*'s): ---------------------- +Bill Nitzberg, Area Director *Stephen Pickles, Area Director Keisuke Fukui, ACS-WG Thomas Studwell, ACS-WG Peter Ziu, ACS-WG *Hrabri Rajic, DRMAA-WG Andreas Haas, DRMAA-WG *Wolfgang Ziegler, GRAAP-WG Jim Pruyne, GRAAP-WG Volker Sander, GRAAP-WG Jon MacLaren, GESA-WG Steven Newhouse, GESA-WG Steven Newhouse, RUS-WG Bill Horn, RUS-WG Rebekah Metz, UR-WG Stephen McGough, JSDL-WG *Ali Anjomshoaa, JSDL-WG Darren Pulsipher, JSDL-WG *Dejan Milojicic, CDDLM-WG Takashi Kojo, CDDLM-WG *Ramin Yahyapour, GSA-RG Uwe Schwiegelshohn, GSA-RG Jarek Nabrzyski, GSA-RG Ewa Deelman, WFM-RG Jim Blythe, WFM-RG Miron Livny, WRM-RG ('+' == could not attend, but emailed status report) NB: --- PLEASE nominate candidates for GFSG to: nomcom(a)ggf.org GGF14: 26-29 Jun 2005, Chicago GGF15: 3-6 Oct 2005, Boston Registration for GGF14 is now open. Advance registration to GGF14 (at reduced rates) closes 27 May. Several documents from SRM area are expected to be submitted to GGF editor in next 1-2 months (2 from CDDLM, 1 from GSA, 1 from DRMAA, 1 from UR, 1 from GRAAP, 1 from JSDL, and possibly 1 from RUS) AD's should be ready! Status ------ ACS-WG -- PLEASE SEND STATUS TO sched-chairs(a)ggf.org CDDLM-WG -- Good external reactions: Planning 1 CDDLM WG session with WSDM at GGF14. Dejan presented CDDLM at DMTF. Considering CDDLM session with DMTF at GGF14. Document progress: At least two drafts are expected to be with GGF editor by GGF14. XML based language spec ready for submission to editor. Component Model Spec is close. Deployment APIs delayed by work on interoperability. Not sure whether will make GGF14. DRMAA-WG -- Expect to resubmit document(s) around GGF14. Planning one DRMAA session at GGF14. GESA-WG -- (hibernating...) GRAAP-WG -- Have now dealt with most issues on WS-Agreement spec raised in public comment period. Version currently on gridforge reflects changes through to end of April. Still hope to submit to GGF editor around GGF14, and be published by GGF15. Several implementations are proceeding in parallel. GSA-RG -- Had a F2F last week in Dortmund and are working on the current drafts. Plan to have a session at GGF14 and have also replied to the corresponding request by Joel Replogle. Collaboration with the proposed OGSA-RSS-WG has also been discussed. [OGSA-RSS is still in pre-BOF planning stage] JSDL-WG -- Working hard on getting version 1 out (down to about 4 issues, of which 3 are agreed, and 1 yet to deal with); Hope to finalize these in next week's call, work on polishing document, and submit to GGF editor around 25-26 May. Some hope of being back in public comment by GGF14, if progression through GGF editor pipeline is quick. RUS-WG -- PLEASE SEND STATUS TO sched-chairs(a)ggf.org UR-WG -- [Merged document, combining natural language and XML Usage Record Specifications has been posted to the UR-WG list for one week WG comment period. Hope to submit to editor soon thereafter. -SP] PLEASE SEND STATUS TO sched-chairs(a)ggf.org WFM-RG -- PLEASE SEND STATUS TO sched-chairs(a)ggf.org Upcoming Telecons ----------------- Every other Tuesday (skipping holiday weeks) 8a US Pacific (see www.worldtime.com to convert) Usually very short (less than 15 minutes long) Dial-in: 1-800-387-6159 & 1-303-248-0173 Conference ID: 7144404 Upcoming Telecons / or status reports due before: 24 May 2005 7 Jun 2005 21 Jun 2005 If you can't make a telecon, please send us a note. If no chairs from your group will make a telecon, please also send a status update to everyone on the list (sched-chairs(a)gridforum.org) As always, please keep things moving forward --- if you need help setting up a separate mailing list or teleconference calls for your group, etc., don't hesitate to ask us. Thanks all! - Bill & Stephen GGF SRM Area Directors

1 0

RE: Notes from the meeting this morning
by Milojicic, Dejan S 10 May '05

10 May '05

Hi, This is a reminder that we have a meeting tomorrow, 6am PST (Wed). Please plan to attend. If you have any technical problems with getting on the conference line, please give me a call at my cell 650 468-3929. Phone: +1 866-639-4732 (toll free while in US) +1 574-948-0379 (toll & international) Code: 2362906 (followed by a '#' sign) If you have not already done so, please provide a written feedback to Stuart about the component model. This is the primary agenda item tomorrow. The other items to discuss are interoperability and what we demonstrate at GGF; interactions with other groups, various. Based on the feedback I received from you individually and based on our needs, I recommend that from now until next GGF (we will discuss what do we do thereafter), we hold meetings every week. We shall stick to 6am PST schedule. Again, please plan to attend. Thanks, Dejan. > -----Original Message----- > From: Milojicic, Dejan S > Sent: Wednesday, May 04, 2005 6:37 AM > To: 'cddlm-wg(a)ggf.org' > Subject: Notes from the meeting this morning > > Hi, > > Attendees: Sandro Rafaeli (HP Brazil), Vanish Talwar (HP), > Jun Tatemura (NEC), and Dejan Milojicic (HP) > > We had a short meeting since we missed some of the key > participants. We used the time to address a few CDL-related > questions. We decided to postpone Component Model related > discussion until next week. We also agreed to convey the > comments to Stuart by email prior to the meeting. > > The good news is that Jun is implementing a reference > implementation and he may be able to do some demo at the next > GGF. If we are lucky enough, we may even be able to do a very > limited interoperability, that is, send a minimal request > between two different reference implementations. > > Dejan has reviewed the Foundation Document to cross-check if > what we promised is consistent with where we are now. I have > not found any significant inconsistencies and/or missing > pieces between our current specs and what we have promised, > aside of the engines (basic services module deployment APIs). > However, I will pass the relevant pieces to the owners of the > specs to double check if my and their understanding overlaps. > > Next meeting is in a week from now, 5/11, 6am PST, please > make sure to attend and mark your calendars. We are grown ups > and we should not rely on reminders sent. > > Thanks, > > Dejan.

1 0

testing against the CDL specification.
by Steve Loughran 10 May '05

10 May '05

Jun, I am busy pasting the examples from the specification into XML files for validation of the XSD. Everything works, using Stuart's XSD. I'd like to move us all to a single, normative XSD, with that schema being under SCM in the sourceforge repository. How is the best way to go about doing that? This is something we may want to discuss on Wednesday. Here are my comments on the code in the examples S7.4.2: recommend example includes a use attr on an untyped element (to show it is allowed) <WebServer> <hostname cdl:type="xsd:string" cdl:use="optional"/> <port cdl:type="xsd:positiveInteger" cdl:use="required" >80</port> <protocol cdl:use="optional">80</protocol> </WebServer> S7.5.3.2 I'd suggest was expanded with a full example of the namespace aliasing <?xml version="1.0"?> <cdl:cdl xmlns:cdl="http://www.gridforum.org/2004/12/CDDLM/XML-CDL/1.0" xmlns:sys="urn:sysapi" > <cdl:configuration> <sys:systemProperties/> <deploymentTime cdl:refroot="sys:systemProperties" cdl:ref="/time" cdl:lazy="true"/> </cdl:configuration> </cdl:cdl> S7.6 replace <serer2> with <server2> in example Appendix B: Example 1. namespace "http://www.girdforum.org/namespaces/2005/02/cddlm/CDL- 1.0" is misspelled and has a space in it; its not legal. 2. Surely we need import statements to resolve the dependent

1 0

CDL: non-namespaced stuff
by Steve Loughran 09 May '05

09 May '05

The CDL XSD is currrently rejecting this doc as the stuff that is not in the CDL namespace is not in the namespace ##other, it is in the 'undefined' namespace. <?xml version="1.0"?> <cdl:cdl xmlns:cdl="http://www.gridforum.org/2004/12/CDDLM/XML-CDL/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > <cdl:configuration> <cdl:documentation> This is our web server </cdl:documentation> <webapps name="webapp-base"> <app>security</app> <app>logging</app> </webapps> <webapps2 extends="webapp-base"> <app>testing</app> </webapps2> <server name="server"> <port>8080</port> <security>true</security> <webapps /> </server> <server name="tomcat" extends="server"> <basedir> </basedir> </server> </cdl:configuration> <cdl:system> <deployment extends="tomcat" /> </cdl:system> </cdl:cdl> If I add xmlns="urn:webapps" at the beginning, all is well. But otherwise, Xerces is rejecting the no-namespaced elements as not being viewed as in the namespace set ##other. I dont know what to do about this. Does anyone have any ideas.

1 0

<cdl:documentation>
by Steve Loughran 09 May '05

09 May '05

I am writing my CDL test files. The current schema doesnt allow you to intermix documentation elements between typed stuff :- <?xml version="1.0"?> <cdl:cdl xmlns:cdl="http://www.gridforum.org/2004/12/CDDLM/XML-CDL/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > <cdl:documentation>Documentation is allowed here</cdl:documentation> <cdl:import location="../minimal.cdl" namespace="http://maven.apache.org" /> <cdl:documentation>Documentation is allowed here</cdl:documentation> <cdl:import location="../minimal.cdl" namespace="http://maven.apache.org"/> <cdl:types/> <cdl:documentation>Documentation is allowed here</cdl:documentation> <cdl:configuration/> <cdl:documentation>Documentation is allowed here</cdl:documentation> <cdl:system/> <cdl:documentation>Documentation is allowed here</cdl:documentation> </cdl:cdl> Do we allow it (and hence, shall I edit the XSD file accordingly)? -steve

1 0

Component Model Update
by Stuart Schaefer 04 May '05

04 May '05

Here is the long overdue Component Model Draft. I have updated most of the document, completely reorganizing the content. I have also fixed numerous errors and added lots of content to more deeply explain the concepts. I would appreciate everyone's time in reviewing the document for concepts and completeness of the idea. I will worry about typos later. I have a few TODOs in the document that will be cleaned up early next week. I am also attaching an updated schema for those interested. All of this will be checked into SourceForge today. Cheers, Stuart

3 2