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

RE: [cddlm] RE: Notes from the meeting on 3/15/2006
by Milojicic, Dejan S (HP Labs) 15 Mar '06

15 Mar '06

Ok, Dejan. > -----Original Message----- > From: Stuart Schaefer [mailto:Sschaefer@softricity.com] > Sent: Wednesday, March 15, 2006 7:15 AM > To: Milojicic, Dejan S (HP Labs); cddlm-wg(a)ggf.org > Subject: RE: [cddlm] RE: Notes from the meeting on 3/15/2006 > > Dejan, > > Is that necessary? I think we can remind the team during > this evening's OGSA call. > > The UML was generic, not for deploying blast. > > Stuart > > -----Original Message----- > From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] > On Behalf Of Milojicic, Dejan S (HP Labs) > Sent: Wednesday, March 15, 2006 10:07 AM > To: cddlm-wg(a)ggf.org > Subject: [cddlm] RE: Notes from the meeting on 3/15/2006 > > Hi, > > Sorry, I gorgot one more action item: > > 5. Stuart will post a reminder to the OGSA mailing list that > he alerady did a UML diagram for deploying BLAST and provide > a URL for the posted document. > > Thanks, > > Dejan. > > > Action items: > > > > 1. Steve Loughran edited Steve Newhouse's document (there > may be a few > > more additions needed to address CDL server name, and other > strengths > > of the CDDLM server, such as loose coupling - we have an > independent > > CDDLM server with the deployment APIs, etc.). Jun will edit > next, and > > then Stuart. > > Ayla and UFCG team, you are also welcome to contribute. I will take > > last turn. Once we have it done, we will pass it back by Steve and > > OGSA. > > > > 2. Stuart will schedule a meeting next week to go over > importing CDL > > spaces. > > > > 3. Steve will post a summary paragraph on changes to the Deployment > > API specs, so that Dejan can resubmit the document. > > > > 4. Dejan will post a summary reply to Hiro's presentation > by attendees > > and team will follow-up so that we can post reply before > the meeting > > today. > > > > Thanks, > > > > Dejan. > >

1 0

RE: [cddlm] RE: Notes from the meeting on 3/15/2006
by Stuart Schaefer 15 Mar '06

15 Mar '06

Dejan, Is that necessary? I think we can remind the team during this evening's OGSA call. The UML was generic, not for deploying blast. Stuart -----Original Message----- From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] On Behalf Of Milojicic, Dejan S (HP Labs) Sent: Wednesday, March 15, 2006 10:07 AM To: cddlm-wg(a)ggf.org Subject: [cddlm] RE: Notes from the meeting on 3/15/2006 Hi, Sorry, I gorgot one more action item: 5. Stuart will post a reminder to the OGSA mailing list that he alerady did a UML diagram for deploying BLAST and provide a URL for the posted document. Thanks, Dejan. > Action items: > > 1. Steve Loughran edited Steve Newhouse's document (there may > be a few more additions needed to address CDL server name, > and other strengths of the CDDLM server, such as loose > coupling - we have an independent CDDLM server with the > deployment APIs, etc.). Jun will edit next, and then Stuart. > Ayla and UFCG team, you are also welcome to contribute. I > will take last turn. Once we have it done, we will pass it > back by Steve and OGSA. > > 2. Stuart will schedule a meeting next week to go over > importing CDL spaces. > > 3. Steve will post a summary paragraph on changes to the > Deployment API specs, so that Dejan can resubmit the document. > > 4. Dejan will post a summary reply to Hiro's presentation by > attendees and team will follow-up so that we can post reply > before the meeting today. > > Thanks, > > Dejan.

1 0

RE: Notes from the meeting on 3/15/2006
by Milojicic, Dejan S (HP Labs) 15 Mar '06

15 Mar '06

Hi, Sorry, I gorgot one more action item: 5. Stuart will post a reminder to the OGSA mailing list that he alerady did a UML diagram for deploying BLAST and provide a URL for the posted document. Thanks, Dejan. > Action items: > > 1. Steve Loughran edited Steve Newhouse's document (there may > be a few more additions needed to address CDL server name, > and other strengths of the CDDLM server, such as loose > coupling - we have an independent CDDLM server with the > deployment APIs, etc.). Jun will edit next, and then Stuart. > Ayla and UFCG team, you are also welcome to contribute. I > will take last turn. Once we have it done, we will pass it > back by Steve and OGSA. > > 2. Stuart will schedule a meeting next week to go over > importing CDL spaces. > > 3. Steve will post a summary paragraph on changes to the > Deployment API specs, so that Dejan can resubmit the document. > > 4. Dejan will post a summary reply to Hiro's presentation by > attendees and team will follow-up so that we can post reply > before the meeting today. > > Thanks, > > Dejan.

1 0

Notes from the meeting on 3/15/2006
by Milojicic, Dejan S (HP Labs) 15 Mar '06

15 Mar '06

Attendees: Ayla, Flavio, Steve, Stuart, Jun, and Dejan. Notes taken by Dejan > 1. Update on the tests for interoperability Ayla: UFCG worked on testing and will be ready for the March deadline (start interoperability tests). Not yet sure yet how they will make client available, but they will be done by the end of the March. Steve: worked on unrelated matters, but also updated the document. Is it ok with others to change the schema to reflect requested changes. Stuart: do it now, it is containable. Ayla: will there be many changes propagated? Steve: will change the XML schema, but not the name space. Jun: it is fine with him. Steve will either have it done by the end of the week or will be delayed. Issues are related to Apache Axes. The question is how much he will spend on the latter. Stuart: worked on the component model testing document. Would like to test WSRF compatibility sooner rather than later, so if there are other endpoint available, he'd love to start testing asap. Marching down the path to finish his testing. Jun: not able to work on cddlm last week, but this week, he will work on it, on CDL. Next week he will work on CDL path as well. His problem is that they are asking administration to have open access to end point. This may take some time. > 2. Preparation for the OGSA meeting in the afternoon (see attached emails) We will need a concerted effort to address the discussion on CDDLM within OGSA. We will try to understand a little bit more OGSA's objectives in today's meeting, but ultimately, we should enhance the document with what CDDLM brings on the table. > - JSDL v. CDL Dejan will prepare an email answer to Hiro and the working groups. > - Usage scenarios We will take turns in editing the documents to bring up the benefits of CDDLM. At the moment, for example, none of the component model benefits are brought up. > 3. Preparing for GGF17 Steve will not attend. Stuart has not yet planned it. Jun has planned it. UFCG team will not attend. Dejan may attend, but if there is no sufficient attendance, we may decide to skip this GGF and simply complete the work. > 4. Various Steve: Import CDL spaces in CDL, I do not think it works. We need to make some progress before we go through revise stage. Right now it is unworkable. Team will setup a meeting next week to address this. Action items: 1. Steve Loughran edited Steve Newhouse's document (there may be a few more additions needed to address CDL server name, and other strengths of the CDDLM server, such as loose coupling - we have an independent CDDLM server with the deployment APIs, etc.). Jun will edit next, and then Stuart. Ayla and UFCG team, you are also welcome to contribute. I will take last turn. Once we have it done, we will pass it back by Steve and OGSA. 2. Stuart will schedule a meeting next week to go over importing CDL spaces. 3. Steve will post a summary paragraph on changes to the Deployment API specs, so that Dejan can resubmit the document. 4. Dejan will post a summary reply to Hiro's presentation by attendees and team will follow-up so that we can post reply before the meeting today. Thanks, Dejan.

1 0

Meeting tomorrow, 3/15, 6am PST
by Milojicic, Dejan S (HP Labs) 15 Mar '06

15 Mar '06

Hi, We shall have a regular meeting tomorrow/today, Wed 3/15/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 the tests for interoperability 2. Preparation for the OGSA meeting in the afternoon (see attached emails) - JSDL v. CDL - Usage scenarios 3. Preparing for GGF17 4. Various Thanks, Dejan.

2 1

[ogsa-wg] Proposed agenda for March 15th call
by Hiro Kishimoto 15 Mar '06

15 Mar '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on March 15th Wednesday from 4pm to 6pm (CST). 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: 0315 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 (if available) Agenda bashing 2) April F2F meeting update (20 min) F2F meeting venue is Intel@Santa Clara & Fujitsu@Sunnyvale. The updated session schedule is uploaded to GridForge: https://forge.gridforum.org/projects/ogsa-wg/document/200604F2F_session In order to have general EMS discussion before CDDLM session, is it possible to switch these two sessions? a) joint CDDLM-WG session (Apr. 5 Wed. 1:30-4:30pm) b) EMS architecture session (Apr. 6 Thu. 9am-12:30pm) 3) joint CDDLM-WG discussion (60 min) From the minutes of joint F2F meeting in Athens; > ACTION: Steven Newhouse to write up a first draft of a few more > scenarios on the relationship between JSDL and CDL. > - To be included in the current EMS scenarios document. > - To be delivered by mid-March > - Review on an OGSA call and continue refinement > > ** Whiteboard list produced during the discussion > > - Duplication of JSDL in CDL? > - Directory/user creation > - What is the difference between > [job / application / container] configuration] > - Where is line between JSDL and CDL and is it policy specific > - Job lifecycle including deployment and start/stop Steven will send out revised version of his "interaction between CDDLM & JSDL" scenarios before the call. Revised "CDL for BLAST" slides attached. 4) Wrap up (10 min) AOB <NEXT CALL> March 20 (Mon): OGSA-HPC profile (Marvin) March 22 (Wed): Security Architecture (Takuya and Frank) March 27 (Mon): EMS scenarios, Steven's scenarios review, Information Model, Ellen's CIM profile review March 29 (Wed): F2F preparation Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ -- Hiro Kishimoto

1 1

updated document
by Steve Loughran 13 Mar '06

13 Mar '06

This is the updated document. It is not yet ready to submit, because one of the spelling changes affects the API schema. In the document I have moved from URL schema to URL scheme, which is the correct terminology for a scheme such as http:. However there is a <schema> element in the addFile request. We need to change this, sooner rather than later, and once the change is made, also update the relevant bits of the document, including the appendix xsd and the embedded example. 1. Whose code is going to break when I change the name of AddFileRequest/schema to AddFileRequest/scheme 2. Do we need to increment the API XSD numbering in the process? -steve

1 0

Re: [ogsa-wg] OGSA-EMS Telecon
by Hiro Kishimoto 13 Mar '06

13 Mar '06

Thanks Steven for your scenarios. > 5. A CDL document is constructed by the JM using information > retrieved from the IS. The CDL document is passed to the CDL > server located on the platform hosting the BES instance. IMHO, We need to discuss the following two issues in order to design sequence diagram among EMS services. (A) Which information should be included in the CDL document. (B) Who provides CDL document for application deployment. In order to discuss (A), I've read Chris's JSDL document for BLAST job and list up 7 candidates. - Application binary to install - File systems to mount - User to create - Data files to stage/de-stage - Environment variables to set - Hard/soft limits to set - Working directory to change See attached slides for detail. It is also uploaded to GridForge; https://forge.gridforum.org/projects/ogsa-wg/document/CDL_for_BLAST For issue (B), I see at least two options; - Client write down CDL document and provide it as a part of JSDL document (or put pointer in JSDL document). - Some module (e.g. JM) converts JSDL document to CDL document. Personally, I prefer to start from the first option (client provides). Your thoughts? ---- Hiro Kishimoto Steven Newhouse wrote: > All, > > Following on from the discussions at the F2F in Athens here are some > deployment and provisioning scenarios for discussion on Monday's telecon. > > Steven >

1 1

Notes from the meeting on 3/8
by Milojicic, Dejan S (HP Labs) 08 Mar '06

08 Mar '06

Attendees: Ayla, Flavio, Steve, Stuart, Jun, and Dejan 1. Stuart presented his plan for testing the interoperability of the component model >From the portal, one would be able to test one component which will represent others. Stuart will update the component model test plan, define the predefined components and build them in Java for everyone. Planning: update the component model test plan and put the CDL definition and how it works, from there, 1-2 more week for the final Java implementation. Component model will follow Deployment API interoperability. 2. Steve's expectations for the testing of interoperability of the deployment APIs Everyone will have to implement Nunit or Junit and everyone will have to make their own service publicly available. 3 ways (send the code, vmware image, bring up a public endpoint). The endpoint's benefit is that you can update it every day, the distributed code's benefit is that you can more easily debug it. There are some concerns about the WSRF and the MUSE stack. 3. Update on CDL, Jun: not much, but still on target to have the complete set of tests 4. Update on the Deployment API Spec: Steve will apply changes to the spec by the end of the week and he will post it to the group before next meeting. Steve will also write a short paragraph about why the changes are not fundamental to the spec so that we do not need to go through the cycle again. 5. SPML discussion Stuart: very high level protocol, does not say anything about how to do things. Has nothing to do with deployment. Telco works this way, how to provision a circuit. No desire to go anywhere near SPML. 6. Various: Steve: there was a question about CDL by Guilherme. There were some issues with the tests, can not tell what is right or wrong, but Steve assumes that HP Brazil's corrections are valid. NOTE: THERE WILL BE A MEETING ON 3/15. DEJAN IS NOT AVAILABLE ON 3/22. IF ANYONE ELSE IS WILLING TO HOST THE MEETING, THEN WE CAN HAVE IT, OTHERWISE, WE WILL SKIP THIS DATE.

1 0

Reminder: meeting in less than an hour
by Milojicic, Dejan S (HP Labs) 08 Mar '06

08 Mar '06

-----Original Message----- From: Milojicic, Dejan S (HP Labs) Sent: Wednesday, March 01, 2006 6:40 AM To: 'cddlm-wg(a)ggf.org' Subject: Notes from the CDDLM meeting on 3/1 6am PST - more Can I please ask everyone to post a quick status of the progress if he/she does not plan to attend the meeting in the future. The status should consist of a) update no the completeness of the reference implementation, b) the % of CDL tests passing and c) the progress of putting up endpoints for the deployment APIs tests. PLEASE: PLAN TO ATTEND NEXT MEETING, WE WILL DISCUSS STUART'S PROPOSAL FOR INTEROPERABILITY OF COMPONENT MODEL AND STEVE'S EXPECTATIONS FOR EVERYONE'S TESTING OF DEPLOYMENT APIs. Thanks, Dejan.

1 0