[acs-wg] The call is starting....

[Keisuke Fukui]

Keisuke Fukui wrote:
> Folks,
> 
> Here is an agenda for the call tomorrow. See you there!
> 
> ### Proposed Agenda
> 
> 1. Agenda bashing, role call, note taker & time keeper. (10min)
> 2. Wrap up for F2F (15 min)
>    Review action items list and issues list (updated and attached)
>    Decide the deadlines.
>    KF will register them on tracker once approved.
>    Goal: Confirm who and what by GGF14.
> 3. Updates (15 min)
>    SDD TC call by KF.
>    CDDLM interface, if any..
> 4. Wrap up. (5 min)
> 
> ### Logistics for the call
> Date & Time:               Jun  2 Thu 20:00 EDT / Jun  3 Fri 9:00 JST
> Dial-in Number:            1-831-600-1000 (Santa Cruz, California)
> Participant Access Code:   7771111
> 
>  -Keisuke
> 
> 
> ------------------------------------------------------------------------
> 
> Title: Issues on the ACS specification. (Rev. 20050523d2)
> Date:  May 23, 2005
> Created by: Keisuke Fukui
> 
> - Clarify the requirements on version control.
> - Demonstrate the recommended interface between ACS and CDDLM
>    - 'addFile' interface in the deployment API looks to be a candidate
>      contact point with ACS, for example, "register" interface of ARI.
>    - where the ACS interfaces should stand in the CDDLM's lifecycle model.
>   AI-1: Sachiko, to post the proposed sequence for interaction with CDDLM.
>   AI-2: All, to make comment on the sequence with CDDLM.
>   AI-3: Tom, to propose a name for ARI interfaces (functions)
> - Demonstrate the recommended interface between ACS and NAREGI type 
>   deployment engine. i.e. separate archives for different binary from the 
>   same source code, or in multiple binaries in a single archive.
>   conclusion: flat description of the archive will work.
>   AI-4: Tom, to send a SDD hierarchy info to NAREGI PSE team.
> - Decide the detail service interface for ACS (ARI).
> - Find the interoperability target and scope in other grid activity.
>   e.g. EGEE, omii, etc. We need a research on possibilities.
>   conclusion: pursue only when European grid is OGSA based.
> - Find appropriate candidates for reference implementations.
>   AI-5: Tom, to ask David Martin about reference implementation.
> - Collect use case descriptions to be shown in the spec.
>   conclusion: Current one is suffice.
>   AI-6: All, to review the current draft of the ACS specification .
> - Find values and issues in storing (caching) the input and output data pairs 
>   through the lifecycle of the multiple executions of the application.
>   conclusion: postponed.
> - Decide the minimum set of requirements on security specification in ACS.
>   AI-7: Mike, to make a research on authentication/authorization.
>   AI-8: Pete, to make a research on signature/integrity.
> - Find the appropriate level of the security description in ACS 
>   specification regarding to overview, requirements and/or normative 
>   specifications.
>   See above.
> - Define the relationship of the SDD specification and ACS specification
>   AI-9: Tom, to update the section of AAF in the current draft of the ACS spec.
> - Converge the Archive Descriptor schema into IUDD schema in SDD TC.
>   See above.
> - Define the collaborate with OASIS SDD TC.
>    - Archive standard will be output from SDD standardization. How can
>      we contribute to it, to archive the common format for the grid
>      deployment. Probably we should discuss Grid specific consideration at
>      ACS, then report our outcome to the SDD TC.
>      See above.
>    - Repository interface standard for Grid system will be output from GGF
>      ACS.
> - Define the collaboration with other (expected) GGF WGs such as OGSA design 
>   teams.  BEM?
> 
> Open Issues in Strawman Draft of the ACS Spec.
> 
> -	More appropriate name and its abbreviation for Application Archive (AA).	
> [3.1 Definition of Application Archive]
> -	Details of Register interface, and method of uploading the entity to be 
> registered.	
> [5.1.1 Register]
> -	Details of Remove interface.	  [5.2.2 Remove]
> -	How to specify the Application Content in getContent interface.	[5.2.3 
> GetContent]
> -	Whether the putContent interface is necessary or not.	[5.2.4 PutContent]
> -	Details of events.	[5.3.1 event of AA updating and 5.3.2 event of AA 
> deletion]
> -	List up and details of types of Application Contents.	[6.4 Application 
> Contents]
> -	Clean up the relationship with DCML. 	[7.3.1 DCML]
> -	Details of security	[8 Security Consideration]
> -	Details of samples	[9 Samples] 
> -	Details of schema definition	[10 Schema Definition]
> 
> 
> ------------------------------------------------------------------------
> 
> Title: Action Items (Rev. 20050523d2)
> Date:  May 23, 2005
> Created by: Keisuke Fukui
> 
>>From the "Issues List":
> AI-1: Sachiko, to post the proposed sequence for interaction with CDDLM.
> AI-2: All, to make comment on the sequence with CDDLM.
> AI-3: Tom, to propose a name for ARI interfaces (functions)
> AI-4: Tom, to send a SDD hierarchy info to NAREGI PSE team.
> AI-5: Tom, to ask David Martin about reference implementation.
> AI-6: All, to review the current draft of the ACS specification .
> AI-7: Mike, to make a research on authentication/authorization.
> AI-8: Pete, to make a research on signature/integrity.
> AI-9: Tom, to update the section of AAF in the current draft of the ACS spec.
> 
>>From minutes:
> AI-10: Fukui, to send the request for two sessions in GGF14 by June 3.
> AI-11: Fukui, to add "Clarify the requirements on version control" to the 
>        issues list.
> AI-12: Fukui, to check the possibility of a joint session with CDDLM-WG 
>        at GGF14.
> AI-13: Fukui, to register the reviewed draft of the ACS spec. by May 27.
>