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

deployment API: next draft
by Steve Loughran 30 May '05

30 May '05

This is my revised draft. there are lots of changes, which is wh change tracking is turned on; so you can see. Some key points -SHOULD/MUST where appropriate -in a few places where stuart didnt agree with things, i removed the stuff altogether, opting for implementation ambiguity. example: best way to retrieve remote URLs in fileUpload -fileUpload now takes a schema element that lets you say "http", "file", "ftp", "ivy", whatever -relying on the implementation to support what you ask (or you get an error), and returns a list of URIs that are all resolvable URLs to the uploaded file. -pulled the xsd:any dynamic state stuff from the portal; use WSDM for that. -added capabilities for system and portal endpoints in MUWS. -XSD/WSDL as appendices with the proper URLs for the locations. Stuart, if you need to do the same thing, look at how build.xml automates the latter fixup in patch-api. I am now going offline for the rest of the week, not checking email until next monday. And at that point I will focus on getting a CDL parser working for GGF, so do not intend to spend any more time on this doc. If we are going to ship to GGF, it needs to go as is. If not, then not. I leave that to the rest of the group to decide. Personally, I think it is about as ready as you can get without actually building an implementation, but then I am a believer of XP/iterative development, rather than waterfall process, which is what we seem to have here. -steve

1 0

Component Model Comments
by Stuart Schaefer 27 May '05

27 May '05

Hi All, It is time to close down on the Component Model Specification. if I do not receive any comments by the end of today, I will send out the Last Call document on Monday for everyone to review. Thanks, Stuart

1 0

new draft of the deployment doc -postponed-
by Steve Loughran 27 May '05

27 May '05

sorry, I cant get the doc finished today, there are more than just layout/style changes to go through, and everyone supplied lots of excellent changes that need incorporation. Monday/tuesday next week. you can see how far I've got by looking in the CVS repository. -steve

1 0

phone conference notes, may 25 2005
by Steve Loughran 27 May '05

27 May '05

Summary Discussion of the deployment API. The doc is going to be updated with feedback from the group and Bryan Murray; a new version will come out friday afternoon. This will be the last call document; Steve is away the following week. For a friday release, all comments must be in by friday am 0900 UTC. There may or may not be a phone call next week. ------------------------------- Dejan -structure. consolidate fault tolerance consolidate architecutre -section numbering broken (word problems) s2.1.1 should be broken into language and s.2.1.2 comp model. Cover materials -needs to put stuff in context with the other specifications. This should go on the front page. -relationship to other working groups. JSDL, ACS, DRAMAA security: should vs must in recommendations about filesystem and visibility References -add Jun as author of XML CDL -dejan has verified that references appear in doc; all looks good. stuart email comment: -put sequence diagram example at back. (dejan: how are (relatively high level) use cases realized? steve: sequence diagrams show how stuart email comment: -consistency with pictures vs schema fragments. dejan: Pictures are good - how about both? steve: its hard work keeping everything consistent. The XSD will go in an appendix. Jun -put XSD at end. -s5.3 use prefix api for typing in XML namespace. -will have lots of feedback at implementation time. steve: we can spend some time talking about testing @GGF. Kojo -feedback by friday morning UTC.

2 2

[Fwd: CDDLM Deployment API]
by Steve Loughran 25 May '05

25 May '05

-----Original Message----- From: Murray, Bryan P. Sent: 24 May 2005 23:01 To: Loughran, Steve Subject: RE: CDDLM Deployment API Steve, The document looks pretty good. I did find a couple of places where you might consider changes: PDF --- 5.1.6: Destroy should be in the wsrf-rl (WS-ResourceLifetime) namespace. 6.1.2: MUWS ResourceId is in the MUWS Identity capability: http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Identity If you think of the Portal properties and operations as a management capability, you could also add a Portal capability to the list of ManageabilityCapability. 6.1.5: ActiveSystems could be modeled as a ServiceGroup or a set of MUWS relationships. However, for simple needs, I think the way you have done it is just fine. 9.1: This section has a sub-section 5.1.10 - should be 9.1.1. Also, DeploymentFault is used here - I wonder if the name has been changed to CddlmFaultType as per figure 5. Appendix A: I think the targetNamespace and name of the 2 TopicSpaces needs to be revisited. Namespace is reversed and the portal topicSpace should have a portal name. deployment-api.wsdl ------------------- I think WS-I suggests that wsdl:import only be used for importing WSDL docs and that you should use schema import for importing .xsd files. This has the unfortunate effect that you need a wsdl:types element as that is the only place a schema import can go. You may want to use absolute locations for schema/WSDL locations, especially for published specs. Otherwise, you require a specific directory structure for services. deployment-api.xsd ------------------ You declare a top-level ResourceID element that is never used. You also declare ResourceID as a child element in several places - you may want to ref the muws element rather than defining your own if you really mean to indicate the MUWS element. One example is in the SystemCreateEventType. Also, note that MUWS uses a lower 'd' and you have used an upper 'D'. Bryan -----Original Message----- From: Loughran, Steve Sent: Monday, May 23, 2005 8:39 AM To: Murray, Bryan P. Subject: CDDLM Deployment API Brian, Can I send you the latest draft of the deployment API for a quick overview? I think I've put the right subset of WSDM in to be useful to other things, though we (all) had a hard tiem working out exactly what that minimum was or should be. A suggestion to the team would be that a primer document of some form would be very useful to others in our situation. Everything has 1. ResourceID attributes 2. ManagementCapabilities listing Deployed systems also get their state from the CDDLM component model, which extends the MUWS states, and provides a state change alert. All comments welcome, -steve

1 0

Reminder for the meeing tomorrow and FW: [sched-chairs] NOTES: GGF SRM Area - Chairs Telecon, 24 May 2005
by Milojicic, Dejan S 24 May '05

24 May '05

Hi, Please be reminded of the regular meeting tomorrow, Wed 5/25, 6am PST. Provide the feedback on the deployment API and any last moment feedback on the component model. +1 866-639-4732 (toll free while in US) 2362906 (followed by a '#' sign) +1 574-948-0379 (toll & international) Thanks, Dejan. -----Original Message----- From: owner-sched-chairs(a)ggf.org [mailto:owner-sched-chairs@ggf.org] On Behalf Of Bill Nitzberg Sent: Tuesday, May 24, 2005 8:17 AM To: sched-chairs(a)ggf.org Subject: [sched-chairs] NOTES: GGF SRM Area - Chairs Telecon, 24 May 2005 GGF Sched Area - Chairs Telecon Notes, 24 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 LAST week for GGF14 advance registration! PLEASE Schedule GGF 14 sessions (if you haven't aleady). Status ------ ACS-WG -- ** PLEASE SEND STATUS TO sched-chairs(a)ggf.org (Having a F2F.) CDDLM-WG -- Having an outside review done before submitting doc to the GGF Editor; also discussing the level of reference implementation desired at time of initial publication -- hoping for something simple for GGF14, with more to come for GGF15. DRMAA-WG -- New version of "ideal" doc to cover all open issues; need to transfer this to the "spec" document for submission to the GGF Editor. Planning one DRMAA session at GGF14. GESA-WG -- (hibernating...) GRAAP-WG -- ** PLEASE SEND STATUS TO sched-chairs(a)ggf.org GSA-RG -- Work continued on 2 draft docs; expect to have updated Use Case doc for GGF14. Requested one session for GGF14. JSDL-WG -- JSDL progressing well; v1.0 issues mostly resolved. Perhaps a week away from going to the GGF Editor. RUS-WG -- ** PLEASE SEND STATUS TO sched-chairs(a)ggf.org UR-WG -- PLEASE SEND STATUS TO sched-chairs(a)ggf.org (No comments from last call on doc on WG list; expect it to go the Editor soon.) 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: 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: [cddlm] early draft of deployment API
by Milojicic, Dejan S 20 May '05

20 May '05

Team, Plese plan on reading the document and providing the feedback either directly to Steve or prior to the meeting on next Wednesday. Thanks, Dejan. > -----Original Message----- > From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] > On Behalf Of Steve Loughran > Sent: Thursday, May 19, 2005 8:45 AM > To: 'cddlm-wg(a)ggf.org' > Subject: [cddlm] early draft of deployment API > > > This is all in CVS, but for those without access, here is the > latest copy > > 1. moved over to MUWS (consistently) > 2. purged MOWS > 3. highlighted everywhere in the docs the namespace needs to be fixed. > > I've just noticed that my processing-of-options section names > two faults to be returned in specific cases, but does not > define the faults. I have them defined in a (non normative) > doc, constants.xml, and will knock up a quick XSL to make an > HTML doc. but it cannot be normative, as we will think up new > faults as we go along. Or to be precise, they will find us. > > ignore errors in the visio-derived images; visio is playing > up on that vmware instance, and my laptop is on loan to > someone else. I'll fix them from home, or even ssh down that > vmimage and use it at work. > > -steve >

2 2

RE: [cddlm] namespaces
by Milojicic, Dejan S 20 May '05

20 May '05

Hi Steve, Please flag it as an open issue that we need to address on the ongoing bases until completely resolved. I believe that we can still change the CDL in the spec, if needed. Thanks, Dejan. PS BTW Below I do not see the difference in the last two namespaces you provide. > -----Original Message----- > From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] > On Behalf Of Steve Loughran > Sent: Friday, May 20, 2005 6:04 AM > Cc: cddlm-wg(a)ggf.org > Subject: Re: [cddlm] namespaces > > > I am moving to the following namespaces > > > http://www.gridforum.org/cddlm/components/2005/02 > http://www.gridforum.org/cddlm/components/events/2005/02/ > > http://www.gridforum.org/cddlm/deployapi/2005/02 > http://www.gridforum.org/cddlm/deployapi/events/2005/02 > http://www.gridforum.org/cddlm/deployapi/wsdl/2005/02 > > The only one I am unsure about is the CDL namespace. On the > most recent copy of the CDL spec that I have to hand, the URL is > > http://www.girdforum.org/namespaces/2005/02/cddlm/CDL-1.0 > > This is from the document; I assume that it is a typo and > that it should be > > http://www.gridforum.org/namespaces/2005/02/cddlm/CDL-1.0 > > Even, then, it is different from Stuart's proposed scheme, > but if the CDL is already submitted, we have to flow with it. > I would note that would be good if at some point in the > future we could actually host the XSD at the various > locations, even though there is no requirement to do so -a > lot of XML parsers expect to fetch XSD from the (resolved) URI > > Dejan, can I flag up namespace consistency as an issue, > something we need to address as a group to avoid shipping > inconsistent documents. > > -Steve > > > > > >

2 1

RE: [cddlm] namespaces
by Stuart Schaefer 20 May '05

20 May '05

This is what I have. Stuart -----Original Message----- From: Steve Loughran [mailto:steve_loughran@hpl.hp.com] Sent: Wednesday, May 18, 2005 12:38 PM To: 'cddlm-wg(a)ggf.org' Subject: [cddlm] namespaces as a followup to the phone call, if we are to submit this week's draft to the editor, we must have consistent namespaces by the end of the week. So: 1. what is the root URL we should use >> http://www.gridforum.org/cddlm/ 2. what is the date extension we are all going to use >> 2005/02 3. accordingly, what will be the three consistent XSD/WSDL namespaces for the various specifications. cdl cmp api or (dapi) -Steve

2 2

Component Model Update
by Stuart Schaefer 19 May '05

19 May '05

Attached is the most recent draft of the Component Model. I believe that I have addressed all of the comments that have been sent to me. If everyone can take a look at this to ensure that it is complete, we can post it for last call next week. Thanks, Stuart

1 0