September 2005 - ogsa-wg

OGSA WSRF BP 1.0 and UDDI
by Hiro Kishimoto 21 Sep '05

21 Sep '05

Hi all, AFAIK, UDDI is mainly for static registration and is not suitable for many gird scenarios. However section 5 of WS-I Basic Profile 1.1 sanctions UDDI 2.0 for Service Publication & Discovery. > When publication or discovery of Web services is required, UDDI is > the mechanism the Profile has adopted to describe Web service > providers and the Web services they provide. Business, intended use, > and Web service type descriptions are made in UDDI terms; detailed > technical descriptions are made in WSDL terms. Where the two > specifications define overlapping descriptive data and both forms of > description are used, the Profile specifies that the descriptions must > not conflict. > Registration of Web service instances in UDDI registries is optional. > By no means do all usage scenarios require the kind of metadata and > discovery UDDI provides, but where such capability is needed, UDDI is > the sanctioned mechanism. Should we exclude section 5 of WS-I BP 1.1? If so, section 1.2 Relationship to other profiles (page 4 line 114-116) should read; "This Profile extends the WS-I Basic Profile 1.1 [WS-I BP 1.1]. All requirements except for section 5 "Service Publication and Discovery" specified in WS-I BP 1.1 pertain to this Profile." However, more study is necessary for this topic, thus I also propose to start hearing several Grid projects on this questions in parallel. Let's discuss this issue on Wednesday. -- Hiro Kishimoto

1 0

Re: [ogsa-wg] Teleconference minutes - 14 September 2005
by Hiro Kishimoto 21 Sep '05

21 Sep '05

Thanks Ravi for your feedback, I agree with you and am happy to fix this at the minutes approval on Wednesday. ---- Hiro Kishimoto Subramaniam, Ravi wrote: > Hi Hiro, > > Thanks for the minutes. A quick correction if I may. > > The statement: "Ravi: CGS is not an asset management. CGS only handles > hardware Specs (like CPU type, memory size, etc)" is not correct. > > I had indicated that "CSG does not need to handle only hardware specs > (CPU type, memory etc) but it can also handle other elements of > significance like data etc. A simple CSG can be used for more purposes > than only job execution like for instance asset management." > > Thanks! > > Ravi > > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of > Hiro Kishimoto > Sent: Tuesday, September 20, 2005 6:26 AM > To: ogsa-wg(a)ggf.org > Subject: [ogsa-wg] Teleconference minutes - 14 September 2005 > > Minutes attached. > > * OGSA F2F meeting back-to-back with GGF15 > * Joint CDDLM-WG EMS discussion > > GridForge URL: > https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050914/e > n/1

1 0

Proposed agenda for Sept. 21st call
by Hiro Kishimoto 20 Sep '05

20 Sep '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on Sept. 21st Wednesday from 5pm to 7pm (CDT). 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: 0921 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 https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050912/en/1 GGF15 and F2F update (if any) Agenda bashing 2) OGSA WSRF BP 1.0 submission (10 min) Given that OGSA Basic Security Profiles needs more time to complete (maybe after GGF15), is it better to submit OGSA WSRF BP 1.0 alone to GGF Editor by this week? 3) WS-MetaData discussion (10 min) > The WSRF TC currently seeking an editor for the > WS-ResourceMetadataDescriptor specification. > Options are: > 1) Someone from OGSA could join WSRF and volunteer to be the > editor. > 2) WSRF could transfer responsibility for the spec to OGSA. > 3) OGSA could pursue an alternate mechanism for metadata. 4) EMS architecture discussion (90 min) > Hiro: Get editable scenario file from Mike and pass it to > Stuart. (done) > Stuart: Break down single “provisioner” box into multiple > services which CDDLM-WG and ACS-WG are working on. > Modifications should be color coded. > Dejan: Talk to Ayla when she can make her demo for OGSA team. See Sept. 14 telecon minutes; https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050912/en/1 5) Wrap up AOB <NEXT CALL> Sept. 26 (Mon) Information Modeling Sept. 28 (Wed) OGSA-AuthZ-WG, Basic Security Profile, GGF15 & F2F preparation Oct. 3-6: GGF15 Oct. 6-7: F2F meeting Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ -- Hiro Kishimoto

1 0

Teleconference minutes - 14 September 2005
by Hiro Kishimoto 20 Sep '05

20 Sep '05

Minutes attached. * OGSA F2F meeting back-to-back with GGF15 * Joint CDDLM-WG EMS discussion GridForge URL: https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050914/en/1 -- Hiro Kishimoto OGSA Teleconference - 14 September 2005 ======================================= * Participants Ellen Stokes (IBM) Mark Morgan (UVa) Dejan Milojicic (HP) Stuart Schaefer (Softricity) Soonwook Hwang (NAREGI) Andrew Grimshaw (UVa) Jay Unger (IBM) Allen Luniewski (IBM) Ravi Subramaniam (Intel) Tom Maguire (EMC) Jem Treadwell (HP) Hiro Kishimoto (Fujitsu) Minutes: Hiro Kishimoto * Sep 12 minutes approved with no changes * OGSA F2F meeting back-to-back with GGF15 schedule OGSA-WG will have F2F meeting on Thursday and Friday. CDDLM-WG have a couple of GGF15 sessions on Thursday. Dejan will talk to Joel to move them to another day. Ellen asks if we adjurn early on Friday to fly out Boston. Agree to adjurn around 3pm on Friday. The following sessions are proposed to have at the F2F. - EMS (CDDLM, ACS, WS-Agreement) - OGSA-naming - information/data model - OGSA-BES - OGSA-data Allen: Talk to DaveB if OGSA-data WG will have a session. Hiro: Send out early draft schedule to the list in order to solicit additional requests and comments. * EMS discussion (CDDLM in EMS architecture) Hiro sent out related materials pointers. Stuart started discussion thread on OGSA EMS sequence diagram (#3). Andrew: CSG generates list of CS. CSG needs information from IS. Jay: In order to run a peace of software (e.g. blast), job should have description of blast, which capability/date it needs. Andrew: Is it by JSDL? Does ACS provide such description? Does CSG understand such description? Ravi: Keep CGS simple. Jay: I see hierarchical problem here. Blast needs some capability, And that capability needs another onesc Ravi: CGS is not an asset management. CGS only handles hardware Specs (like CPU type, memory size, etc) Andrew: First of all, we should agree objects of CSG, CDDLM and ACS... JSDL is more user focus and does not describe how to deploy. Stuart: CDDLM-WG did this scenario walk through almost 2 years before. And then ACS came, and ACS is a contents archive, not CIM database. You should get a template for deployment first. Jay: For example, user wants to run blast with 500 MIPS CPU, with this middleware and that data. Does ACS support such dependency tree? Stuart: ACS is not such active service. You may get template from ACS and grand the template with allocated server name, etc. Ravi: Anyway we need generic archiver (bit bucket). Stuart: SDD (OASIS Solution Deployment Descriptor TC) is overlaping with ACS and CDDLM. Hiro: ACS is archiver for application package. It defines archiver interface specification and format specification. ACS format specification has mondatory/option/extention elements. Jay: there should be offline process to define template for blast and I don't want to tree-search at real time. Also the system should have cache capability: already deploy necessary middleware/library in containers. Dejan: CDDLM spec lacks temporal aspect of components, CDDLM-CDL can only describe dependency of components. Jay: If I want to run BLAST on Linux/Intel but the system does not have one, does some service give us Linux/Intel by provisioning? If ACS is rather bit bucket, does component model work for us. Stuart: NO, CDL language can do all for you. Which service handles stuffed JSDL and CDL? Not CDDLM service. CDDLM service only covers a part of deployment. Whole chain should be EMS. CDDLM is a gear box containing deployment and configuration. Ravi: Is JSDL and CDL overlapped? Does CDDLM service get JSDL document and get grounded one back? Jay: There are a lot of cases, you can choose a container, sometime container already ready to run blast, sometime it need to deploy BLAST application binary, sometime blast + middle ware, sometime blast + middle + os... We should have clean separation between, scheduling, deploy, workload management. Jay: provisioning and scheduling is related but different thing. Provisioning is very constrained by possible translation. Dejan: CDDLM service is not provisioner, it does just configuration change. Jay: It seems to me that CDDLM service has nugget of interesting functionalities. CDDLM service is gear box which passes back EPR ready to run BLAST. EMS team likes the granularity of its component model. Stuart: CDDLM service is not engine, it does just good thing. Ravi: CDDLM is handy man, not control tower. Hiro: At this moment, CDDLM-WG and ACS-WG scope only applications, no more than that (e.g. middleware, OSes). Stuart: CDDLM deploy container + code, thus you can use CDDLM engine to deploy OS but it is not CDDLM-WG's goal. Ravi: I guess EPS makes plan, hand it over to CDDLM to get things done. Jay: there is potentially big overlap between EMS and CDDLM we need more face time to discuss. Dejan: I have a proposal to show working demonstration using glance session. We did once last week. Also, we will have 4 demos at GGF15. There are at least three demo opportunities; 1: next Wednesday 2: following Friday 3: GGF15 * Next step: Hiro: Get editable scenario file from Mike and pass it to Stuart. Stuart: Break down single "provisioner" box into multiple services which CDDLM-WG and ACS-WG are working on. Modifications should be color coded. Dejan: Talk to Ayla when she can make her demo for OGSA team. We will have another joint CDDLM-WG call on next Wednesday (Sept. 21, 5-7pm CDT).

1 0

No RM teleconference on the 20th
by Fred Maciel 20 Sep '05

20 Sep '05

Hi, No RM teleconference on the 20th. I'll post an outline of the profile document later this week. Regards, Fred Maciel Hitachi America R&D

1 0

OGSA-WG F2F schedule/sessions
by Maguire_Tom＠emc.com 19 Sep '05

19 Sep '05

Folks, Lost some e-mails in my transition to my new employment. Could someone forward to the list the latest scheduling information for the upcoming F2F.... Thanks, Tom Senior Technologist, CTO Office EMC²|SMARTS 44 South Broadway 7th Floor White Plains, NY 10601 Email: maguire_tom(a)emc.com <mailto:maguire_tom@emc.com>

1 0

Teleconference minutes - 12 September 2005
by Andreas Savva 19 Sep '05

19 Sep '05

Minutes attached. * Jan 2006 F2F update * Roadmap 1.0 review * Secure Channel 1.0 review Griforge URL: https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050912/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 12 September 2005 ======================================= * Participants Jem Treadwell (HP) Andreas Savva (Fujitsu) Steven Newhouse (OMII) Takuya Mori (NEC) Tom Maguire (EMC) Hiro Kishimoto (Fujitsu) Mike Behrens (R2AD, LLC) Minutes: Andreas Savva * Sep 7 minutes approved with no changes * Jan 2006 F2F update Hiro has reserved a room at the FLA Sunnyvale facility for the week of Jan 16. (Same place used for the August meeting.) * Roadmap 1.0 review Review of draft 21. - The change in Introduction, first paragraph, should be propagated to the Abstract too. - "Use of SAML for OGSI Authorization version 1.0" - Since this is for OGSI it should be dropped from the Roadmap. - Version 2.0 of this document might be based on WSRF but there is no concrete decision by the AuthZ WG yet. (Rechartering discussion still going on.) So such an entry cannot be added now. - Agreed to drop and update Roadmap accordingly (incl. spreadsheet). - "Attributes used in OGSA Authorization" - In its current form it is not a Profile and so should be moved to section 4. - Roadmap title - The title should be changed so as to use OGSA as an adjective - It would also be nice to have OGSA(tm) in the title. - A number of alternatives were proposed and rejected before consensus was reached on "Defining the Grid: A Roadmap for OGSA(tm) Standards version 1.0" - Sec.2.3: The OGSA-Related Naming Guidelines draft was recently made public by the GGF Editor. Section 2.3 should be updated accordingly and include a reference to this note. - Sec.5.3.3. contents should be made similar to 5.2.3 since they are both about the 'same' kind of Profiles. - What are the criteria for including a profile in section 5? - Agreed to add a sentence that Profiles must be based on the OGSA Profile Definition document. - All editing actions to be done by Jem. - Issue final call on the next draft. * Secure Channel 1.0 review Reviewed draft sent out by Takuya. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-securi… - Title: It is different from the title given for this document in the Roadmap document. Agreed to change the title of this draft. - Status: Based on the contents of the Status section of the WSRF BP. Agreed to revise to make more specific to this Profile. - Abstract: Agreed to rewrite to focus on security aspects covered by this Profile. - Introduction: Agreed to rewrite to focus on security aspects of this Profile. - Profile Overview: Agreed to rewrite to focus on security aspects of this Profile. - Relationship with other profiles: Add relationship to WSRF BP and Anonymous Channel Profiles. - Targets: Reduce to the ones used in the document directly (and not just due to cross-referencing from terms in this section) - Conformance claim: Add the general basic security conformance claim URI defined by WSRF BP 1.0. - Sec.3 Security: Break into sections for each referenced profile (BSP and SAML) per WSRF BP. - Use of SSL: Takuya's intention with R0305 is to restrict use of SSL 3.0 ("MUST use TLS") - Agreed to revise R0305 for clarity. - R0301,0302: mandates that the RECEIVER support both TLS and MLS; and SENDER can use either. - Hiro thinks that this sets too high a bar on implementations and should be relaxed for the RECEIVER also. - Takuya thinks that the secure channel profile sets a high bar anyway so this additional requirement is acceptable and is needed to promote interoperability. - No consensus reached. - Takuya will put the issue to the list to get more opinions. * Next call - Secure Channel Profile review to be scheduled for the Monday call.

3 4

OGSA-WG F2F draft schedule in Boston (Oct. 6&7)
by Hiro Kishimoto 19 Sep '05

19 Sep '05

Hi all, Based on the all feedbacks on OGSA-WG F2F meeting which is back-to-back with GGF15, the following is the first-cut draft schedule. Let's discuss at upcoming Monday call. Oct.6 (Thursday) 1. 9-10:30 am: EMS (1) WS-Agreement discussion (GRAAP-WG) 2. 11am-12:30pm: EMS (2) CDDLM & ACS discussion (I) 3. 1:30-3pm: EMS (3) CDDLM & ACS discussion (II) 4. 3:30-5pm: Resource Management, info/data model discussion (Fred & Ellen) 5. 5-6pm: OGSA re-charter draft review Oct. 7 (Friday) 1. 8-9:30am: OGSA-BES session (Andrew) 2. 10-11:30am: OGSA-naming session (Andrew) 3. 12:30-2pm: OGSA-data session (DaveB and Allen) 4. 2-3pm: Wrap-up and next step Thanks, -- Hiro Kishimoto

1 0

WSRF Meta-Data Specification
by David Snelling 19 Sep '05

19 Sep '05

Folks, The WSRF TC currently does not have an editor for the WS-ResourceMetadataDescriptor specification. I believe that this specification is important to OGSA, as it captures the management of metadata of properties. For example, communicating default values, providing an indication of how fresh the data is (goodFrom & goodUnitl in OGSI), and whether the property is modifiable or readonly. There is an initial draft available and some agreement on what the direction from here should be, e.g. simplification. See http://www.oasis-open.org/committees/download.php/9758/wsrf-WS- ResourceMetadataDescriptor-1.0-draft-01.PDF Options are: 1) Someone from OGSA could join WSRF and volunteer to be the editor. 2) WSRF could transfer responsibility for the spec to OGSA. 3) OGSA could pursue an alternate mechanism for metadata. A similar note has been sent to the WSDM TC. Let me know what OGSA would like to do regarding this development. -- Take care: Dr. David Snelling < David . Snelling . UK . Fujitsu . com > Fujitsu Laboratories of Europe Hayes Park Central Hayes End Road Hayes, Middlesex UB4 8FE +44-208-606-4649 (Office) +44-208-606-4539 (Fax) +44-7768-807526 (Mobile)

1 0

Proposed agenda for Sept. 19th call
by Hiro Kishimoto 18 Sep '05

18 Sep '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on Sept. 19th Monday from 5pm to 7pm (CDT). 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: 0919 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 - Hiro will send out Sept. 14 minutes before the call Agenda bashing 2) GGF15 session and back-to-back F2F update (20 min) According to the tentative GGF15 session schedule, (http://www.ggf.org/gf/session_request/?browse&order=12) OGSA-WG has the following time slots; - OGSA status and direction: Oct. 3 (Mon) 11am-12:30pm - OGSA EMS architecture: Oct 3 (Mon) 4-5:30pm Back-to-back OGSA-WG F2F is on Thur & Fri in walking distance. Hiro will send out proposed schedule before the call. 3) Architecture & Glossary 1.5 discussion (30 min) Please provide first draft of v1.5 text to Andreas ASAP. Andreas and Jem will lead this discussion. 4) Basic Security Profile review (60 min) Takuya will post revised draft before the call. 5) Wrap up AOB <NEXT CALL> Sept. 21 (Wed) EMS discussion (joint CDDLM-WG), GGF15 & F2F preparation Sept. 26 (Mon) OGSA-AuthZ-WG, Information Modeling Sept. 28 (Wed) GGF15 & F2F preparation Oct. 3-6: GGF15 Oct. 6-7: F2F meeting Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ ---- Hiro Kishimoto

1 0