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

CDL document for BLAST
by Hiro Kishimoto 29 Jun '06

29 Jun '06

Hi all, The following is my write up for CDL document for BLAST application based on the dialogue with Chris Smith. So far, I guess we will translate JSDL document to CDL document or extract necessary information from JSDL document and put them into CDL document. However JSDL document does not have a couple of information we need for CDL. (1) Application binary source location and its archive format. (2) File permission on the target server. We can add such necessary information into the JSDL document as extensions. For (2), we can assume default value (e.g. 755). Another possibility is we expect client tooling produce both JSDL document and CDL document at the same time. Advantage of this option is the tooling can guarantee consistency between JSDL document and CDL document. Chris and I agree this is reasonable scenario as our first step. Regarding to BLAST database, we expect client must run prep-job to format BLAST database and BLAST job should mount such formatted database before BLAST run. Formatted database should be reside e.g. /db/ncbiblast/est which should be mounted before BLAST run. The attached files are revised JSDL and CDL documents for review. I value your feedback. -- Hiro Kishimoto

1 0

Notes from the meeting on 6/28/2006
by Satish 28 Jun '06

28 Jun '06

*/Attended: Dejan, Ayla, Stuart, Satish and Guilherme /* _*1. Updates*_ * UFCG: *Continuing the interoperability tests against NEC and HP. But, NEC endpoint still has the 'hang-after-run' issue. Ayla has contacted Satish regarding this issue. She is likely to finish the tests today. * NEC:* CDL implementation of 'delegate' and 'wait' are done and the CDLs are ready. Will complete the 'switch' case very soon. After the CDL implementations, Satish will resolve the tomcat server issue that UFCG has reported. *Softricity:* Stuart is working on getting his endpoint ready for testing. According to him, it may take some time as it needs some more testing. Will soon post the interoperability test results. *_2. Interoperability document _* Ayla has started the document and according to Guilherme, not sure if she has committed the doc. Satish has also started composing the document and will have it ready by the start of next week. Stuart will look into the document scope and see if he can complete it before 7th July. Dejan said the deadline for this document is July 7th and it's important for everybody to stick to the deadline. _*3. GGF at Washington*_ Dejan said during this conf. we can meet and hopefully close all the CDDLM activities officially .

1 0

[ogsa-wg] Proposed agenda for June 29th call
by Hiro Kishimoto 28 Jun '06

28 Jun '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 29th. Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: 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: 0629 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (June 22 & 29) - https://forge.gridforum.org/sf/go/doc13624?nav=1 - https://forge.gridforum.org/sf/go/doc13628?nav=1 Action Items status review (see the bottom of this email) July F2F and GGF18 plan update (if any) Agenda bashing 2) CDDLM & EMS joint discussion (Jun and Hiro, 30 min) Jun and Hiro will send out revised material before the call. minutes form July 12 call > - Reviewed Hiro's presenation and XML documents. > > - Jun pointed out that codebase is used incorrectly. It should be > used in the BLAST declaration not in the PosixApplication. > - Also it is not clear what the meaning of pre-script is. > > ACTION: Hiro to talk with Chris Smith and clarify meaning of > pre-script > ACTION: Jun will correct the CDL XML examples written by Hiro. > > - What should be the granular unit of components? > - It may be better to define 'filesystem' or 'database' as > separate components since they may be re-usable in other > contexts. For example, they might be usable also by a 3-tier > application component. > - It was agreed that this kind of refinement is needed. But it is > not a showstopper for delivering the top level CDL for the EMS > sequence scenarios. > > - For the EMS scenarios the following CDL documents are needed: > - Original CDL from the repository; > - CDL modified by JM before submission to Deployment service > (portal) > - CDL after deployment (can be retrieved by JM to refine the JSDL > document) > [The deltas should be fairly small.] > - Some explanation on what the constructs in the CDL document mean > would also be useful since not everyone will have read the CDDLM > documents. > - Also highlighting what information (if any) is expected to taken > from the JSDL document and used in CDL (and vice versa) > - In the simplest case it is 'hostname' and path to the installed > executable. > - Andreas volunteered to review these CDL documents before the EMS > call to make sure they provide the expected information. 3) EMS scenarios (Steven and Andreas, 30 min) Andreas will send out revised scenario document before the call > - EMS team (Steven, Andreas, Donal) to review data staging scenario > (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1 ) > Bring to people's attention again at the next EMS call. > (postpone until June 29) > - Add sequence diagrams to the scenarios: (postpone until June 29) > - Andreas will do the "Install application" scenario (3.1) > - Mike will do the "Install application using ACS" scenario (3.3) > - Other volunteers welcome. (Andreas will ask Donal for the EPS > scenario) > - Andreas has started doing the sequence diagrams in RSM > - Darren volunteered to help out > - Review again at the next EMS call (June 29) > - Andreas will merge draft scenarios and sequence diagrams to the > "EMS Architecture Scenarios" document (postpone until June 29) 4) OGSA authorization call-out proposal review (Frank 20 min) > - Frank is now consulting with people in GGF (David Chadwick, Von > Welch) on whether his approach can be defined within the AuthZ > group. If there is no agreement then he will accept the XACML > group's decision. 5) Basic Security Profile Public Comments review (Takuya 20 min) Takuya will send out proposed text change before the call Minutes from June 22nd call > Reviewed public comments and Takuya's proposed replies > 1. Add text explaining that the Secure Channel profile is not > required by all ogsa services. The introduction is probably a > good place for this. > 2. [Basic-Security-Profile] usage. The term is defined in the > document. Takuya to check whether such special terms are used > consistently and that they stand out. Refer to the WSRF BP for a > similar example. > 3. Ciphersuites: Agreed that it important to list acceptable > ciphers. > - As a first step Takuya will list up available ones (from the > WS-I BSP); select the ones that are in common use; and then > select the ones that are considered sufficiently safe. > - Review the list at the next BSP teleconf > 4. Multiple keys in keyinfo field? > - Takuya to talk to Von in order to understand the use case for > multiple keys; and will propose a resolution at the next BSP > teleconf. 6) Wrap up AOB <*NEXT CALL*> July 3 (Mon): Independence day (no call) July 6 (Thu): EMS scenarios (Steven and Andreas) July 10 (Mon): Information model (Ellen and Fred) Roadmap 1.1 (Hiro, ChrisJ, and Jem) Security & BSP Public Comments review (Frank and Takuya) CDDLM & EMS (Jun and Hiro) July 13 (Thu): F2F prep (Tom and Hiro) July 17-20: F2F meeting in Chicago (ANL) Telecon schedule on wiki: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Telec… <*ACTION ITEMS*> > From June 26 call - Hiro to confirm contact with (ex-)EGA TC > From June 12 call - Jun will correct the CDL XML examples written by Hiro. > From June 8 call - EMS team (Steven, Andreas, Donal) to review data staging scenario (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1 ) Bring to people's attention again at the next EMS call. (postpone until June 29) - Add sequence diagrams to the scenarios: (postpone until June 29) - Andreas will do the "Install application" scenario (3.1) - Mike will do the "Install application using ACS" scenario (3.3) - Other volunteers welcome. (Andreas will ask Donal for the EPS scenario) - Andreas has started doing the sequence diagrams in RSM - Darren volunteered to help out - Review again at the next EMS call (June 29) - Andreas will merge draft scenarios and sequence diagrams to the "EMS Architecture Scenarios" document (postpone until June 29) > From May 22 call - Jay will contact Platform (Chris Smith) and Condor (Miron Livny) to get feedback on pros / cons of the two rendering approaches (postpone until June 19) - Darren/Andreas will take the Modeling position paper and discuss it within the JSDL-WG as well (postpone until June 19) > From April 5 F2F meeting - Marvin to send e-mail that explains concerns on compliance suite by GGF & EGA. Deferred - Frank to write up and send to the list a one page summary of the authorization call-out proposal. (April 24 call, postpone until June 14) - Jay check and find out relatively small funding to Globus to develop document on their security work (April 6 F2F) - Hiro to schedule a discussion in the OGSA F2F after the converged specs drafts are released to discuss which sets of specs to use within OGSA. (April 4 F2F) -- Hiro Kishimoto

1 0

updated interop results
by Steve Loughran 21 Jun '06

21 Jun '06

I have updated the doc. It only has interop between the hp client and hp server, as I cant reach any of the other portals today. If they are back up tomorrow, then I'll try to get the results in then. -steve

1 0

how we create our logs
by Steve Loughran 21 Jun '06

21 Jun '06

This is the log4j.properties file used to create the logs you see on our interop site # Set root category priority to INFO and its only appender to CONSOLE. #log4j.rootCategory=INFO, CONSOLE log4j.rootCategory=INFO, CONSOLE,WWW #wire debugging of HTTP client #log4j.logger.httpclient.wire=DEBUG log4j.logger.org.smartfrog=INFO log4j.logger.org.smartfrog.sfcore.languages.cdl=DEBUG log4j.logger.org.smartfrog.services.cddlm=DEBUG log4j.logger.org.smartfrog.services.xml=DEBUG log4j.logger.org.smartfrog.services.deployapi=DEBUG log4j.logger.org.smartfrog.sfcore.languages.cdl.CdlCatalog=INFO log4j.logger.org.smartfrog.services.deployapi.binding.NuxStaxBuilder=INFO log4j.logger.org.smartfrog.projects.alpine=DEBUG # CONSOLE is set to be a ConsoleAppender using a PatternLayout. log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.Threshold=DEBUG log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout #log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n log4j.appender.CONSOLE.layout.ConversionPattern=%-4r %-5p %c %x - %m%n log4j.appender.WWW=org.apache.log4j.DailyRollingFileAppender log4j.appender.WWW.DatePattern='.'yyyy-MM-dd-HH'.html' log4j.appender.WWW.File=/home/slo/public_html/logs/server-log.html log4j.appender.WWW.layout=org.apache.log4j.HTMLLayout log4j.appender.WWW.layout.LocationInfo=true #the following options are for the RollingFileAppender, not the daily one #log4j.appender.WWW.MaxFileSize=1000KB #log4j.appender.WWW.MaxBackupIndex=48 The secret is the DailyRollingfileAppender with its HTMLLayout; this creates HTML pages and moves them every day -you need to create the destination directory as log4j fails if it is not already there. -to serve up the logs you need to publish them to a visible directory. We do this by deploying another jetty web app to serve the log direcotry -printing out the received messages is something that different stacks do differently. For Alpine I just wrote a LogMessageHandler that does nothing but log the current message. enjoy, -steve

1 0

FW: [gf-chairs] GGF18 Session Scheduling Now Open
by Milojicic, Dejan S (HP Labs) 21 Jun '06

21 Jun '06

Hi, This is a reminder that we need to schedule a session at Washington before July 7th and we need to submit the documents (interoperability documents) before 11 August. Therefore, I need an update on your attendance at GGF in the next couple of weeks and we need to work on completing the documents in the near future as well. I am out of office last three weeks of July. Thanks, Dejan. -----Original Message----- From: owner-gf-chairs(a)ggf.org [mailto:owner-gf-chairs@ggf.org] On Behalf Of Joel Replogle Sent: Monday, June 12, 2006 2:26 PM To: gf-chairs(a)ggf.org Subject: [gf-chairs] GGF18 Session Scheduling Now Open GGF Chairs - The next GGF event, GGF18, is coming up and session scheduling is now open! GGF18 will be held in conjunction with GridWorld September 11-14, 2006 in Washington, DC USA. For Group Session Requesting instructions and the link to the request form please go here: http://www.ggf.org/ggf_events_next_chairinfo.htm The scheduling deadlines are: Draft Documents: - Deadline for submitting working drafts is 11 August, 2006. Session Requests: - Deadline for session requests for a CG, WG or RG is 7 July, 2006 - Deadline for AD Hoc/Charter Discussion BOFs is 7 July, 2006. We anticipate that the schedule will be finalized by the last week in July. Thanks, Joel ------------------------------------------------------------------------ ----------- Joel Replogle - Manager of Standards, Global Grid Forum replogle(a)ggf.org http://www.ggf.org

1 0

Notes from the meeting on 6/21/2006
by Milojicic, Dejan S (HP Labs) 21 Jun '06

21 Jun '06

1. Updates UFCG: continue small updates in implementation, published next version with updates to CDL. Also looked at the interoperability document, continue testing. HP: doing a round of tests. Deployed a new version of server last week, should work better, publishes all logs through URL, you can see trace of all messages; you can trace the logs of yourself. NEC: implementing the CDL that is specified in Stuart's component model, because previous implementation did not implement delegate switch and late, this should be done in another week or so. In terms of interoperability tests, we are still stuck at the same place. Unless Steve implements WS-Notification, we are done with the deployment API tests. Still need some component model and Deployment APIs issues between UFCG and NEC. This is the only obstacle before we can declare interoperability success. Have been looking at the problem separately, if they allocate a common session, maybe will be more successful. 2. Interoperability document Right now we have only deployment API interoperability document in progress. Satish will talk to Jun about the CDL interoperability document. Dejan will call Stuart and check with him on the component model interoperability document. 3. Attendance at Washington Steve TBD, Dejan likely. Jun likely, Satish likely, UFCG unlikely, Softricity unclear. It is desirable to meet there and wrap-up. 4. Talk to Stuart/Softricity Dejan will do this, on the topics of component model interop document, Washington attendance, and engagement in general. 5. Timing Steve may provide updated document today. Thanks, Dejan.

1 0

deployment
by Steve Loughran 21 Jun '06

21 Jun '06

interop test results http://deployment.cvs.sourceforge.net/*checkout*/deployment/deployment/doc/… this is read only; to make changes you have to check things out and check them back in. -steve

1 0

CDL expression and Component Model's case-condition
by Jun Tatemura 20 Jun '06

20 Jun '06

Here are two clarification points related to each other: [1] For CDL expression, on which the spec says that "it must not contain any location path," please see the attached file that defines the syntax of expression (based on XPath1.0 spec). [2] For Component Model's cmp:switch, I am not really sure what cmp:case/@condition should support. The spec says "a valid XPath calculation on declared properties returning a boolean value" -- however, I do not think this includes the full set of XPath, which does not always make sense. I assume that cdl:pathType is used instead of the full-spec path expression. Then, the syntax of cmp:case/@condition can be given by extending the syntax of cdl expression as: ----- PrimaryExpr ::= VariableReference | '(' Expr ')' | Literal | Number | FunctionCall | CDLPath CDLPath ::= ('/')? Step ('/' Step)* Step ::= '.' | '..' | QName ----- which is also a valid XPath expression. (We may want to remove VariableReference from PrimaryExpr, since there is no way to define variables for cmp:switch). One possible problem here is that we cannot specify @cdl:refroot (this is the reason why I introduced cdl:expression and cdl:variable) within the expression. This may not be a problem if we just want to refer to properties within a component graph. -- Best Regards, Jun Tatemura CDL's expression is a subset of XPath 1.0. Its syntax can be described as follows (See Section 3 of XPath 1.0 specification for comparison) Functions supported are string functions (Section 4.2), boolean functions (Section 4.3), and number functions (Section 4.4). Expr ::= OrExpr OrExpr ::= AndExpr | OrExpr 'or' OrExpr AndExpr ::= EqualityExpr | AndExpr 'and' EqualityExpr EqualityExpr ::= RelationalExpr | EqualityExpr '=' RelationalExpr | EqualityExpr '!=' RelationalExpr RelatiopnalExpr ::= AdditiveExpr | RelationalExpr '<' AdditiveExpr | RelationalExpr '>' AdditiveExpr | RelationalExpr '<=' AdditiveExpr | RelationalExpr '>=' AdditiveExpr AdditiveExpr ::= MultiplicativeExpr | AdditiveExpr '+' MultiplicativeExpr | AdditiveExpr '-' MultiplicativeExpr MultiplicativeExpr := UnaryExpr | MultiplicativeExpr MultiplyOperator UnaryExpr | MultiplicativeExpr 'div' UnaryExpr | MultiplicativeExpr 'mod' UnaryExpr UnaryExpr ::= PrimaryExpr | '-' UnaryExpr PrimaryExpr ::= VariableReference | '(' Expr ')' | Literal | Number | FunctionCall FunctionCall ::= FunctionName '(' (Argument (',',Argument)*)? ')' Argument ::= Expr

1 0

updated HP CDDLM server
by Steve Loughran 16 Jun '06

16 Jun '06

Hi, I've rolled out an updated HP server recently,at the usual address ,http://deployapi.iseran.com:8080/alpine/portal/ now versioned according to <api:build/> field of the static system status property as as $Date: 2006/05/15 15:18:56 $ This release -correctly implements the WSDM management capabilities attribute -handles empty starttime terminatedtime responses. that is <getResourceProperty /> is a valid response for a query of anything with a minOccurs=0 value. -has updated hp tests to match these changes. William Vambenepe clarified what the spec really meant and showed that I'd misinterpreted a bit of it. What is also interesting about this deployment is that we are using the integrated smartfrog/commons-logging/log4j logging components, so that commons-logging stuff goes to smartfrog logs, which then relays to log4j. Which is set up to generate rolling html log files: http://deployapi.iseran.com:8080/logs/ Callers are now free to debug their own operations, as the logger logs received messages and responses. No more need to set up tcpmonitors to this endpoint. Everyone else is free to see what messages get sent around too, which may be informative. -steve

4 5