(3) Deployment and configuration section break-down (Andreas S to send out)
See attached file for a section list. This is not too different from what's in the document already. Andreas Andreas Savva wrote:
[Tom and Hiro are unavailable but that should not stop us from having a teleconference. I'll be chairing this call.]
Proposed agenda for OGSA-WG telecon, Dec. 14th Wednesday, 4-6pm (CST).
Dial-in numbers: US Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815
Screen share service: URL: http://ogsa.glance.net Session key: 1214 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 (Dec. 12) https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20051212/en/1 Agenda bashing ## If there are updates and time allows, consider: 1. Basic Security Profile (re)-factoring 2. OGSA Arch and Glossary 1.5
2) OGSA Profile Definition final call (10 min)
The OGSA Profile definition has been updated to address public comments received. Please take a moment and review the FINAL CALL document (link below). Positive acknowledgement of the document would be appreciated to achieve rough consensus. The chairs would like to submit the final document to GGF Editor by 12/16. To that end we will agenda a final discussion on the OGSA Profile Definition for Wednesday 12/14.
https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profile...
2) EMS architecture (45 min) (1) Review sequence diagrams from composite roadmap (Steven N to send out) 2.4 Job Termination 2.5 Dynamic Job Selection
(3) Deployment and configuration section break-down (Andreas S to send out)
EMS Architecture Composition Roadmap draft: https://forge.gridforum.org/projects/ogsa-wg/document/proposed-ems-roadmap/e... (Now also linked under the Root Folder)
4) Wrap up (10 min) AOB
<NEXT CALL> Dec. 19 (Mon) OGSA-AuthZ joint call Naming requirement discussion Jan F2F preparation Dec. 21 (Wed) EMS Arch CDDLM/ACS/GRAAP joint call ** DEC 21 IS THE LAST CALL OF 2005 **
Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/
-- Andreas Savva Fujitsu Laboratories Ltd == Proposed list of sections == 3.1 Provision (Deploy) an application on an existing BES container (The application can then be used to instantiate a BES activity. Mostly what is now 3.2 in EMS Architecture composition.) 3.2 Provision a BES container (What is now 3.1 in EMS Architecture composition) [Both 3.1 and 3.2 assume that the 'level' of the BES container is pre-determined and fixed. See below.] 3.3 Using ACS do 3.1 3.4 Using ACS do 3.2 [Both 3.3 and 3.4 assume that the 'level' of the BES container is pre-determined and fixed. See below.] 3.5 Add time predictions to provision 3.1 and 3.2 by a deadline Using a deployment estimation service (perhaps based on historical data, etc, but how the estimation is done is out-of-scope.) Possibly requiring reservations. [3.5 assumes that the 'level' of the BES container is pre-determined and fixed. See below.] 3.x Determine dynamically the optimal level of 'BES container' in the system and provision containers appropriately depending on workload etc may depend on analysis of the entire application CDL (down to hardware) for the entire workload of the system; use deployment time predictions; etc <<Version 1 of the document could just cover scenarios 3.1-3.5 and discuss 3.x as future work. Otherwise need to breakdown 3.x further.>> ==