December 2005 - cddlm-wg

Last call for Application Contents Service Specification 1.0
by Keisuke Fukui 08 Mar '06

08 Mar '06

Folks in ogsa-wg, cddlm-wg and acs-wg, We, acs-wg, has come to completion of the ACS Specification 1.0 after discussions and reviews. This is the last call for comments before submission to the GGF Editor for publication. If you have comments, please get them to me by 9 am Japan time on Monday November 7. If there are no significant comments I plan to submit the document on Monday afternoon. Below is the link for the document: https://forge.gridforum.org/projects/acs-wg/document/draft-ggf-acs-spec-1.0… Regards, Keisuke Fukui ACS-WG co-chair

1 1

test result link
by Steve Loughran 21 Dec '05

21 Dec '05

Hi, I'm publishing my test results from the curious December 02: http://people.apache.org/~stevel/cddlm/2005-12-02/ December 21 : http://people.apache.org/~stevel/cddlm/2005-12-21/ Import without namespaces can be ticked off as done; import into namespaces is something I've raised as an issue. The next bit of work is parse-time resolution. -steve

1 0

CDDLM meeting tomorrow, Wed 12/21/2006, at 6am PST
by Milojicic, Dejan S (HP Labs) 21 Dec '05

21 Dec '05

Hi, We'll have a regular CDDLM meeting tomorrow. Please use our usual phone numbers: +1 866-639-4732 (toll free while in US) Code 2362906 (followed by a '#' sign) +1 574-948-0379 (toll & international) Thanks, Dejan.

1 0

namespaced importation
by Steve Loughran 20 Dec '05

20 Dec '05

The area where I am having fun is in namespaced imports. I'm going to have to read and reread the spec to understand it better and see where I am going wrong. Either I'm writing invalid test docs, or my code is broken, right now I cannot determine which. Has anyone got any test case files which (a) -import other .cdl files into a namespace (b) do (a) with the imported file declaring their stuff in a namespace (c) do (b) with the imported file importing bits of itself. I dont want to send out any of my examples today as it would only cause confusion; I want to see what other people have done first. -steve

1 0

Imports tests
by Steve Loughran 20 Dec '05

20 Dec '05

Our site is having severe networking problems right now, so I cannot check anything in to day. I have been moving many of my existing import tests into the xml test framework, and have basic (non-namespaced) importing working against them. As of this afternoon the hp implementaton can : -import .cdl files with absolute file:, http: URLs. There is no security here. -import .cdl files with a classpath:/package/package/filename.cdl URL. the classloader will only load signed JARs, so this is the secure way to load things. -do relative imports. If a file comes from http://example.org/a/b/example.cdl and it imports ../c/ex2.cdl, then the URL will be http://example.org/a/c/ex2.cdl. Same goes for classpath: imports. -do relative imports from imported documents, as with these two from a forthcoming test case <ct:document uri="http://cddlm.org/chain-target.cdl"> <cdl:cdl> <cdl:configuration> <WebServer> <hostname>localhost</hostname> <port>80</port> </WebServer> </cdl:configuration> </cdl:cdl> </ct:document> <ct:document uri="http://cddlm.org/chain-source.cdl"> <cdl:cdl> <cdl:import location="chain-target.cdl"/> </cdl:cdl> </ct:document> </ct:documents> -detect recursive imports and halt the process gracefully. SmartFrog classic doesnt do this incidentally; it runs out of stack space, which is an implicit failure, and not so good for diagnostics. I will be checking in tests for all of these, with the recursive ones marked as required=false as the spec says nothing about how well to handle recursive imports. We may want to mark everything with relative URLs as required=false too, as again, there is nothing explicit there.

1 0

[ogsa-wg] Proposed agenda for Dec. 21st call
by Hiro Kishimoto 20 Dec '05

20 Dec '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on Dec. 21st Wednesday from 4pm to 6pm (CST). This is the last call for 2005. Dial-in numbers for Wednesday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1221 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 (if available) Agenda bashing 2) CDDLM-WG joint call (45 min) > Actions: > - Dejan to arrange for a subteam call to discuss in more detail the > provisioning/deployment issues, JSDL, CDL, etc. > - Volunteers (mainly in Boston area or same timezone): Jay, > Andrew, Stuart, Michael. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20051109/en/1 3) GRAAP-WG joint call (45 min) From Dec. 7th telecon minutes: > * EMS Architecture update > > - Dec 21 is the planned joint call with EMS and CDDLM/GRAAP > - (This is also the final call of the year) > - Steven has been reviewing the WS-Agreement spec and will be > arranging a separate call with GRAAP-WG https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20051207/en/1 From GGF15 F2F minutes; > Action(4): Set up a team to explore WS_Agreements issues more, > especially relating to allocation and QoS assurance. And > come back to OGSA-WG on how to use WS-Agreement (possibly > evolved) with EMS. Clarify > - How WS-Agreement possibly needs to change to fit in OGSA > EMS > - Set the first review after 30 days; check what can be > done. > - Volunteers: Steven Newhouse (to lead), Dave Berry, Chris > Smith, (Jim Pruyne; not present >GRAAP-WG to confirm) 4) Jan. F2F meeting update (20 min) Proposed agenda with attendee list: https://forge.gridforum.org/projects/ogsa-wg/document/2006Jan-OGSA-F2F-agen… Survey result: https://forge.gridforum.org/projects/ogsa-wg/document/2005Winter_F2F_survay/ If you've not yet answered the survey please take a time to answer the following on-line survey to let us know your availability for sessions and group dinner. http://www.zoomerang.com/survey.zgi?p=WEB224VCKBH9KA 4) Wrap up (10 min) AOB <NEXT CALL> Jan. 9 (Mon) F2F preparation Jan. 11 (Wed) If we can make a quorum Jan. 16-20, interim F2F meeting in Sunnyvale. Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ Happy holidays! -- Hiro Kishimoto

1 0

Problems in the tests
by Guilherme Mauro Germoglio Barbosa / Projeto Ourgrid - Projeto Ourgrid/LSD 19 Dec '05

19 Dec '05

Hello, While implementing some of CDDLM tests (CDL/Deployment API), I've found the following problems: 1. The implementation of the CDLTestUtils.java has the method: / /** * Get a required attribute of an element. We search first for the namespace qualified attribute, * then the non-namespaced version. * * @param element element to search * @param attribute attr * @param docinfo document data * @return the attribute value * @throws CDLException if the attribute is not there */ public static String getAttribute(Element element, String namespace, String attribute, String docinfo) { String attr = element.getAttributeNS(namespace, attribute); if (attr == null)) { // if ("".equals(attr)) { attr = element.getAttribute(attribute); } if (attr == null)) { // if ("".equals(attr)) { //raise an error on an empty attribute throw new CDLException("No " + attribute + " for " + element.getTagName() + docinfo); } return attr; } /The commented part (/if.../) is how I think it is the correct, as the documentation of /org.w3c.dom.Element/ says: */String org.w3c.dom.Element.getAttributeNS(String namespaceURI, String localName)/* /(...) Returns: The Attr value as a string, or the empty string if that attribute does not have a specified or default value./ /(...) /Is anyone against I commit these changes? 2. The deployment API has the test: /*api-18: Create a System while subscribed with an invalid endpoint*/ Subscribe to a portal for creation events with a notification EPR that is invalid. There are the following types of invalid portal * Nonexistent URL (e.g. "http://notifications.example.org/epr1"). * endpoint with no open connection (e.g. "http://localhost:8081/epr1"), assuming port 8081 is closed * 404 URL (e.g. "http://deployment.sourceforge.net/example/epr1"). Assertions: * In all cases, the notification delivery failure is noted, the endpoint is no longer subscribed Don't you think this behavior of simply unsubscribing the consumer in its first failure can result in bad unsubscriptions? I mean, the failure can be transient and only by a few seconds can make the consumer unreachable/invalid. The other problem is that I didn't find in the WSN specification what must be done when a notification fails. Does it mean that it is free to the implementation have its own policy when notification fails? The Pubscribe implementation tries to notify a certain number of times when an EndPoint Reference is invalid and then quits, but does not unsubscribe the EPR - which means that, when in the future an event that must be notified occurs, the implementation will try to notify the invalid EPR again. Guilherme

2 1

Lifecycle of a system Endpoint
by Ayla Debora Dantas de Souza - Projeto Ourgrid 16 Dec '05

16 Dec '05

Hi, while implementing automatic tests for the deployment api, we got a doubt about the system endpoint lifecycle model. We thought that the system had to follow the lifecycle model defined by the component model, does it? However, some tests make us perform operations do not following that model such as invoking the destroy operation on a initialized system. Is there an explicit lifecycle model for the system? Thanks in advance, Ayla

1 0

About Deployment API test plan
by Guilherme Mauro Germoglio Barbosa / Projeto Ourgrid - Projeto Ourgrid/LSD 12 Dec '05

12 Dec '05

Hello, While implementing the deployment API test plan, I've found the following test: /*api-18:Create a System while subscribed with an invalid endpoint*/ /Subscribe to a portal for creation events with a notification EPR that is invalid. There are the following types of invalid portal/ * /Nonexistent URL (e.g. "http://notifications.example.org/epr1"). / * /endpoint with no open connection (e.g. "http://localhost:8081/epr1"), assuming port 8081 is closed/ * /404 URL (e.g. "http://deployment.sourceforge.net/example/epr1"). / /Assertions:/ * /In all cases, the notification delivery failure is noted, the endpoint is no longer subscribed/ Don't you think this behavior of simply unsubscribing the consumer in its first failure can result in bad unsubscriptions? I mean, the failure can be transient and only by a few seconds can make the consumer unreachable/invalid.

1 0

Survey for OGSA-WG F2F meeting in January 2006
by Hiro Kishimoto 12 Dec '05

12 Dec '05

Hi all, and sorry for the cross-posting. As you already know, OGSA-WG and fellow WGs are planning to have F2F meeting in January 2006. The meeting will be held in the week of January 16 from Monday morning to Friday noon at Fujitsu campus in Sunnyvale (SF Bay Area). Please let us know your plan for attendance by answering the following on-line survey. Deadline is EoB December 21st. http://www.zoomerang.com/survey.zgi?p=WEB224URW95UZU Session owners: Please provide detailed session agenda, I will incorporate your in the meeting schedule. The latest proposed agenda for January OGSA-WG and the fellow WGs F2F meeting is uploaded to the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/2006Jan-OGSA-F2F-agen… Thanks, -- Hiro Kishimoto

1 0