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

test reports
by Steve Loughran 24 Jan '06

24 Jan '06

for the curious, my latest test reports are up on http://people.apache.org/~stevel/cddlm/2006-01-24/ This has been achieved by (a) implementing compile-time (non-lazy) reference resolution (b) fixing up the namespace references in all references to match my current "strict" interpretation. Namely -the set of known prefixes is fixed at the time a node is parsed, and doesnt change as it is moved around during extension/deployment. -as you walk a reference graph, you dont pick up extra namespace/prefix declarations -even if you declare a default ns with xmlns, you still need to prefix it when referring to nodes in extends or references. If others could publish their results, it could be quite illuminating. Steve

1 0

new invalid test: extends and default xmlns
by Steve Loughran 23 Jan '06

23 Jan '06

There's a new invalid test soon to appear under invalid/set-01, one that effectively says "you need to use the full qname of something you are extending" <cdl:cdl xmlns="urn:uri:webapps" > <a> 100 </a> <cdl:system> <a2> 200 <a3 cdl:extends="a"> 300 </a3> </a2> </cdl:system> </cdl:cdl> The reason that I believe that this must fail, that in extends="a" , the a template must not be found, is the same as with references: you need the full qname with a prefix. -steve

1 0

Reminder: Regular Meeting Tomorrow, Wednesday January 18th, 6am PST
by Milojicic, Dejan S (HP Labs) 18 Jan '06

18 Jan '06

Hi, We shall have a regular meeting tomorrow (already today for UK/Japan), Wed 1/18/06, at 6am PST. We will use the following conference number: +1 866-639-4732 (toll free while in US) Code 2362906 (followed by a '#' sign) +1 574-948-0379 (toll & international) Agenda is the following: 1. Report from the F2F (Jun and Dejan attended) 2. Update on the reference implementations 3. Planning GGF16 in Athens 4. Planning OGSA F2F session 5. Steve's question about reported issues with CDL 6. Various Thanks, Dejan.

1 0

[cddlm-wg | CDL Spec Revisions - 1724] How does value resolution handle non-element children in a ref node?]
by Steve Loughran 17 Jan '06

17 Jan '06

One thing I'd like to discuss tomorrow is the outstanding tracker issues that I've been adding up against the CDL on the topics of resolution and namespaces. This one is something I think is just not quite explicit in the spec: is it an error to have text, PI or comment nodes under a reference, and if so, what to do with them. The spec only says "no child elements", not "no children". -steve -------- Original Message -------- Subject: [cddlm-wg | CDL Spec Revisions - 1724] How does value resolution handle non-element children in a ref node? Date: Tue, 17 Jan 2006 06:41:44 -0600 From: Sourceforge Tracker Monitor <noreply(a)forge.gridforum.org> Reply-To: followup-1724(a)forge-tracker.gridforum.org To: steve_loughran(a)hpl.hp.com A new artifact has been added: 1724 Submitted by: Steve Loughran Submitted date: 2006-01-17 12:41:43 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=734&aid=1724&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=734&aid=1724&group_id…) Summary: How does value resolution handle non-element children in a ref node? Project: cddlm-wg Tracker: CDL Spec Revisions Artifact ID: 1724 Category: <None> Group: <None> Status: Open Priority: - Last Modified By: Steve Loughran Last Modified: 2006-01-17 12:41:43 Submitted By: Steve Loughran Submit Date: 2006-01-17 12:41:43 Assigned To: &lt;None&gt; File(s): <None> Description: The CDL specification says on P17 that "Value references MUST NOT be placed in an element that has child elements" But there is no coverage of the policy with respect to other child types, such as comments, text and processing instructions Specifically, are the following valid or not <user1 cdl:ref="../toplevel"></user1> <user cdl:ref="../toplevel">  And some text </user> If they are invalid, the spec must say "no children of any type". If they are valid, the spec must say what is to be done with the nodes during reference resolution. There is an implicit specification in the value resolution process (the nested nodes are dropped). Test case org/ggf/cddlm/files/cdl/valid/set_02_references/cddlm-cdl-2005-02-0017.xml View the CDL Spec Revisions : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=130&atid… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=130&atid…) ________________________________________ Modify your monitoring preferences: https://forge.gridforum.org/monitoring/monitorPreference.php (https://forge.gridforum.org/monitoring/monitorPreference.php) Turn off monitoring for this Tracker: https://forge.gridforum.org/tracker/?group_id=130&func=monitor&category=734 (https://forge.gridforum.org/tracker/?group_id=130&func=monitor&category=734)

1 0

[ogsa-wg] Final proposed schedule for OGSA F2F meeting
by Hiro Kishimoto 15 Jan '06

15 Jan '06

Please accept my apologies for cross posting. Attached is the (hopefully) final proposed schedule for upcoming OGSA-WG and fellow WGs F2F meeting in Sunnyvale. The last minutes changes include; - Swap GRAAP and OGSA 1.5 on Tuesday. - Move WS-Management profile to Wed 1:30-2:30pm - Move Information to Monday afternoon, swapping with the EMS roadmap. It is also uploaded to GridForge; https://forge.gridforum.org/projects/ogsa-wg/document/2006Jan-OGSA-F2F-agen… See you in Sunnyvale! -- Hiro Kishimoto

1 1

[ogsa-wg] Ad hoc calls on Jan. 12th
by Hiro Kishimoto 12 Jan '06

12 Jan '06

Hi all, We will have an ad hoc call for F2F meeting preparation on Thursday. The following is a proposed agenda. ATTENTION: day of week, time, dial-in number are all different. Date: Jan. 12th Thursday Time: 8-10pm (CST) = 6-8pm (PST) = 11am-1pm JST = 2-4am UK The dial-in number: US Toll number: +1 408-961-6509 (San Jose) and +1 718-354-1071 (New York) UK Toll number: +44 (0)207 365-5269 JP Toll number: +81 (0)3 3570 8183 The pass code: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0112 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (Dec. 19) https://forge.gridforum.org/projects/ogsa-wg/document/minutes20051219/en/1 Agenda bashing 2) CDDLM-WG joint call (60 min) Jem has uploaded the revised version to the GridForge. - http://tinyurl.com/aez86 Look forward to proofread and tracker verification. (1) Deployment and configuration section break-down > == Proposed list of sections == > > 3.1 Provision (Deploy) an application on an existing BES container > (The application can then be used to instantiate a BES activity. > Mostly what is now 3.2 in EMS Architecture composition.) > > 3.2 Provision a BES container > (What is now 3.1 in EMS Architecture composition) > > [Both 3.1 and 3.2 assume that the 'level' of the BES container is > pre-determined and fixed. See below.] > > 3.3 Using ACS do 3.1 > > 3.4 Using ACS do 3.2 > > [Both 3.3 and 3.4 assume that the 'level' of the BES container is > pre-determined and fixed. See below.] > > 3.5 Add time predictions to provision 3.1 and 3.2 by a deadline > Using a deployment estimation service (perhaps based on > historical data, etc, but how the estimation is done is > out-of-scope.) Possibly requiring reservations. > > [3.5 assumes that the 'level' of the BES container is pre-determined > and fixed. See below.] > > 3.x Determine dynamically the optimal level of 'BES container' in the > system and provision containers appropriately depending on > workload etc > may depend on analysis of the entire application CDL (down to > hardware) for the entire workload of the system; use > deployment time predictions; etc > > <<Version 1 of the document could just cover scenarios 3.1-3.5 and > discuss 3.x as future work. Otherwise need to breakdown 3.x further.>> > == (2) - Deployment versus provisioning requirements > (Or, where to 'cut' the CDL tree. Above the 'cut' point is > deployment---assumed to be a relatively 'light' operation---and > below is provisioning---assumed to be more heavy-weight.) > - Deciding the cut point is orthogonal to CDDLM---it is policy or > best practices and is therefore a system choice > - Information (metadata) to help in making the choice could be > added to the CDL as mark up > - CDDLM implementations have walked the tree fairly far down (to > the hardware) for deployment > - CDL may be sufficient to express both deployment and > provisioning. But it is an open issue if these two activities > can, or should be unified in this way in OGSA. In particular CDL > may not be going to the full extent of supporting costing, etc., > that maybe needed to address all requirements > - Resources beneath the cut point can be considered as > pre-provisioned: they either exist or they don't. They are not > going to be deployed themselves; but they can be used to > deploy on. > - Which resource to choose for deployment? It is the choice of > the EMS architecture (EPS, CSG) and not of CDDLM. > - Discussion on how CDL may be viewed as a hierarchy of scripts; > and that one could have a history of costs associated with > each node. In other words the tree could be decorated with > other information (cost, etc, as metadata) (3) - JSDL and CDL relation and can one cover the requirements for the > other > - A JSDL submission may be associated with a deployment > description or request, and the deployment portion could be > described in CDL. [I.e., CDL could be a more specific > application > sub-type in a JSDL document.] > - JSDL is not intended to describe the configuration of the > software that will be used by the job. The aim is to describe > things at a higher level. There may be similarities between the > languages (perhaps around resource description) but it does not > mean that one language can, or should, replace the other because > they serve different purposes. > - Jay wants to pursue the issue further among a smaller group of > people. 3) OGSA F2F meeting update (30 min) Session leaders: Please provide your goals and detailed agenda. https://forge.gridforum.org/projects/ogsa-wg/document/2005Winter_F2F_survay https://forge.gridforum.org/projects/ogsa-wg/document/2006Jan-OGSA-F2F-agen… 4) Wrap up (10 min) AOB <NEXT CALL> OGSA-WG F2F Jan. 16-20. -- Hiro Kishimoto

1 1

FW: GGF 16: proposal for talk about Askalon resource management
by Milojicic, Dejan S (HP Labs) 11 Jan '06

11 Jan '06

Hi Team, Askalon team will present during our third session at GGF for 15 minutes. If appropriate, we can engage them in more in-depth discussions offline. Thanks, Dejan. -----Original Message----- From: Thomas Fahringer [mailto:tf@dps.uibk.ac.at] Sent: Wednesday, January 11, 2006 2:11 AM To: Milojicic, Dejan S (HP Labs) Cc: Mumtaz Siddiqui Subject: Re: GGF 16: proposal for talk about Askalon resource management Dear Dejan, 15 minutes is ok. Here is our abstract: Title: GLARE: Askalon's Grid Activity Registration, Deployment and Provisioning Framework. Abstract: Askalon Grid environment allows application developers to specify Grid application components at high level of abstraction which then requires an effective mapping between high level application description and actual deployed software components. GLARE is a part of Askalon's Grid middleware that provides dynamic registration, automatic deployment and on-demand provision of software components that can be used to build such applications and thus shields the Grid from application developers. It simplifies description and presentation of both component types and deployments so that they can easily be located in the Grid, mapped, and thus provisioned on-demand. GLARE has been implemented based on a super-peer model. The talk will be given by Mumtaz Siddiqui. Please let us know if you need any other information. Greetings Thomas Milojicic, Dejan S (HP Labs) wrote: > Hi Thomas, > > The offer is still valied, except that we may have to shorten it > somewhat. Would 15 minutes work for you. We are now getting fewer > meetings, so we have to economize. We have 3 sessions scheduled and > you will be part of the last session. > > Thanks, > > Dejan. > > >>-----Original Message----- >>From: Thomas Fahringer [mailto:tf@dps.uibk.ac.at] >>Sent: Monday, January 09, 2006 6:57 AM >>To: Milojicic, Dejan S (HP Labs) >>Cc: Mumtaz Siddiqui >>Subject: Re: GGF 16: proposal for talk about Askalon resource >>management >> >>Dear Dejan, >> >>coming back to your offer to provide us with a presentation slot for >>the Askalon resource manager. >>Could you give us up to 25 minutes for a presentation? >> >>We would send you a title and abstract immediately. >> >>Do you already know when the CDDLM session is scheduled in Athens? >> >> >>Greetings >> >>Thomas >> >> >>Milojicic, Dejan S wrote: >> >>>Hi Thomas, >>> >>>We'd be delighted to offer you a slot to present. How much >> >>time do you >> >>>need? We are looking forward to learn from your results. >>> >>>Thanks, >>> >>>Dejan. >>> >>> >>>>-----Original Message----- >>>>From: Thomas Fahringer [mailto:tf@dps.uibk.ac.at] >>>>Sent: Saturday, October 22, 2005 1:29 AM >>>>To: Milojicic, Dejan S >>>>Subject: GGF 16: proposal for talk about Askalon resource management >>>> >>>>Dear Dejan, >>>> >>>>we will attend GGF16 in Athens and wonder whether you would >> >>be willing >> >>>>to give us a chance for a presentation about the Askalon >> >>Grid resource >> >>>>management system at a CDDLM meeting? >>>> >>>>Here is what we could report on: >>>> >>>>We have designed and implemented a Grid activity registration, >>>>deployment and provisioning framework which handles dynamic >>>>registration, automatic deployment and and on-demand provision of >>>>software components. We separately provide registry services for >>>>component types (abstract >>>>descriptions) and actual deployed software. Application developer >>>>provides abstract description of application components in the Grid >>>>workflow application, which then mapped at runtime to actually >>>>deployed components. This mechanism shields the Grid from workflow >>>>application developers. This framework is an extention of >> >>our existing >> >>>>Grid resource management system. >>>>In the resource management system, we provide automatic >> >>discovery and >> >>>>brokerage of Grid resources along with advanced reservation and >>>>negotiation mechanism. Now the system covers not only physical >>>>resources but logical resource (like software components) as well. >>>>Currenly we are working on the semantic enhancement of our >> >>system with >> >>>>ontologies. >>>> >>>>Our system is running on the Austrian Grid and is being used for a >>>>variety of real world applications. >>>> >>>>I believe our system contains some very relevant ideas for >> >>CDDLM and >> >>>>may stimulate some interesting discussion. >>>> >>>>Regards >>>> >>>>Thomas Fahringer >>>> >>>>Askalon Research Group >>>>http://dps.uibk.ac.at/projects/askalon/ >>>>Univ. of Innsbruck >>>>Inst. of Computer Science >>>>Austria >>>> >>> >>> >

1 0

Notes from the CDDL Meeting on Wednesday January 11th
by Milojicic, Dejan S (HP Labs) 11 Jan '06

11 Jan '06

Attended: Ayla, Flavio, Guilherme, Jun, and Dejan. Apologies: Steve. 1. Update on reference implementations Jun: NEC will complete reference implementation by the end of the month and do the demo of everything at GGF: Deployment API, component model, and CDL resolution tests. Ayla: UFCG worked on the switch and parser part. Steve fixed some aspects. They are finishing switch. By the end of the month they will have the reference implementation. 2. Planning GGF16 in Athens Jun can do the demo on the 2/8 call as a preparation for GGF. UFCG recommends ppt presentation. They can also do the live demo, but it is risky because of connectivity. 3. Planning OGSA F2F session Jun will attend F2F. 4. Various Steve addressed all issues by email. Most of the technical issues by UFCG have been addressed. The Component model and Deployment APIs went out of the public comment periods and there have not been comments made. We may have to provide some of the comments. Thanks, Dejan.

1 0

FW: Attendees and session agenda for Jan. F2F. (Re: [ogsa-wg] Proposed agenda for Dec. 19 th call)
by Milojicic, Dejan S (HP Labs) 11 Jan '06

11 Jan '06

Hi, Jun asked for forward, but I think others might have interest as well. CDDLM is on on 1/17, 9-12:30am. Thanks, Dejan. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Hiro Kishimoto Sent: Monday, December 19, 2005 2:00 AM Cc: ogsa-wg(a)ggf.org Subject: Attendees and session agenda for Jan. F2F. (Re: [ogsa-wg] Proposed agenda for Dec. 19 th call) Hi all, So far, I got the following 11 attendants for Jan. F2F meeting. Dave Berry (NeSC) Fred Brisard (Computer Associates) Neil Chue Hong (EPCC) Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Dejan Milojicic (HP) Takuya Mori (NEC) Andreas Savva (Fujitsu) David Snelling (Fujitsu) Chuck Spitz (CA) Jem Treadwell (HP) Telephone Bridge: Michael Behrens (R2AD, LLC) Apologies: Abdeslem Djaoui (Rutherford Labs) Mathias Dalheimer (Fraunhofer ITWM) Donal Fellows (University of Manchester) Andrea Westerinen (Cisco) Keisuke Fukui (Fujitsu) If you've answered the survey but are not on the above list, you forgot to fill in your name. I got seven (!) nameless replies. Survey result: https://forge.gridforum.org/projects/ogsa-wg/document/2005Winter_F2F_sur vay/en/5 Proposed agenda with attendee list: https://forge.gridforum.org/projects/ogsa-wg/document/2006Jan-OGSA-F2F-a genda/en/5 Please answer the following improved on-line survey to let us know your schedule. http://www.zoomerang.com/survey.zgi?p=WEB224VCKBH9KA Hiro Kishimoto Hiro Kishimoto wrote: > Hi all, > > The following is a proposed agenda for OGSA-WG telecon on Dec. 19th > Monday from 4pm to 6pm (CST). > > The dial-in number for Monday; > Free: +1-866-639-4741 > Toll: +1-574-935-6703 > PIN: 8980700 > > Screen share service will be provided. > URL: http://ogsa.glance.net > Session key: 1219 > See more explanation: > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.ht > ml > > 1) Early discussion (10 min) > Note taker assignment > Roll call > Telecon minutes approval (Dec. 14) > https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20051214/e n/1 > Agenda bashing > > 2) OGSA-AuthZ joint call (30 min) > - XACML 3.0 based authorization query interface status > - Get buy-in from the OSG Privilege Project, the LCG Joint > Security Group, and Shibboleth community > - Status of OGSA-AuthZ WG's submitted specs > - New OGSA-AuthZ WG charter > - Jan F2F meeting session agenda (Jan. 19, 1:30-3pm) > > See excellent minutes by Alan Sill and Andreas Savva; > https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20051121 > /en/1 > > 3) OGSA Basic Security Profile discussion (30 min) > Takuya will send out a proposal to the list. > >> Takuya explained the current status. The Secure Channel was split >> into Core and Secure Channel a couple of weeks ago. But the >> relationship, if any, of these two specifications is still >> unclear. Alternatives were discussed and Takuya took on the >> assignment to clarify whether there is a need for a Core >> profile---if its contents are all MLS (message level security) >> specific perhaps it should be included within the (scheduled) MLS >> profile instead. >> >> Takuya is discussing this issue with Frank and he will send out a >> proposal to the list. > > > 4) Naming requirement discussion (30 min) > > OGSA-naming WG has had a teleconf on Dec. 9. > Mark uploaded a minutes to GridForge > > Andrew and Mark explain their discussion and show > revised requirement document which includes issues > pointed out on the list. > > From Nov. 16 telecon minutes; > >> 1. Andrew and Mark for the OGSA-Naming WG will summarize Naming >> requirements and issues >> - Including issues from the list discussion and also including a >> separate set of OGSA-DAI Naming requirements >> > > 5) Jan. F2F meeting and GGF 16 update (20 min) > Attendees and session agenda for Jan. F2F. > Hiro requested 2 sessions at GGF16 > >> - Proposal for 2 sessions: >> - Town hall: need to prepare for this and attract the right >> people. - How popular is this expected to be? Talk with >> Andrew G who >> proposed the idea. - One idea is to split the session in >> two parts: outreach >> followed by town hall >> - Technical session: Last GGF this was a joint session with >> CDDLM. CDDLM is scheduling a joint session with EMS as part of >> their agenda this time so a different topic should be chosen. >> - Proposal for an Information Model joint session---how it >> relates to other activities such as BES, ByteIO and JSDL and >> so on. >> - Fred will bring a proposed agenda to the Jan F2F > > > 6) Wrap up > AOB > > <NEXT CALL> > Dec. 21 (Wed) EMS Arch CDDLM/ACS/GRAAP joint call > ** DEC 21 IS THE LAST CALL OF 2005 ** > > Jan. 9 (Mon) F2F preparation > > Telecon schedule: > https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule > / >

1 0

Reminder: Regular Meeting Tomorrow, Wednesday January 11th
by Milojicic, Dejan S (HP Labs) 11 Jan '06

11 Jan '06

Hi, We shall have a regular meeting tomorrow/today, Wed 1/11/06, at 6am PST. We will use our usual numbers: +1 866-639-4732 (toll free while in US) Code 2362906 (followed by a '#' sign) +1 574-948-0379 (toll & international) Agenda is the same one as last time: 1. Update on reference implementations 2. Planning GGF16 in Athens 3. Planning OGSA F2F session 4. Various Thanks, Dejan.

1 0