Minutes of BAR telecon ====================== Date: Tuesday, 18 October 2005 time: 10:30 BST/ 11:30 CEST Venue: CERN Teleconference Attended ======== GARR: Gloria Vuagnin (GV) DANTE: Maarten Buchli (MB), Anand Patil (AP) EPCC: K Kavoussanakis (KK), Florian Scharinger (FS), Charaka Palansuriya (CP) Apologies: Agenda ====== 1) On going actions 2) WorkPlan + Gantt chart 3) Prioritised Wish List 4) Issues/bugs for DJRA4.4 5) Deprecating Architecture Document 6) AOB 7) DONM Phone Numbers for telecons ========================== The conference phone number at CERN is +41-22-767 7000 - ask for EGEE JRA4, the owner's name is Charaka New Actions ============ [AP] Review/update EGEE demo slides [AP] Modify NSAP implemetation so that it checks reverse bandwidth [FS] Ask Alberto Di Meglio to create a project in JRA1 repository for L-NSAP implementation [GV] Send an email raising issues with the L-NSAP spec. [KK] Add users of BAR to DJRA4.1 Ongoing Actions =============== [CP] Create a skeleton system test document - create a document with basic structure [CP] Create first draft of TOC for DJRA4.4 [FS/CP] Review GN2-SA3 NSAP WSDL [FS] Ask AP if "reservable path" in Glue Schema is still needed/necessary - Find a "home" for this. [KK] Investigate usage of BSD license in glite software - Software using BSD licensed software need not be under BSD - Modified version of a BSD licensed software needs to be published under the BSD license again - Speak to JRA2 (Quality) - Done. - Speak to Bob (EGEE technical director) [KK] Delete "Service Class" from South Interface (NSAP) of DJRA4.1 [AP/MB] Add L-NSAP Interface to DJRA 4.1 - Send modified version to KK directly [AP/MB] Update details on L-NSAP in BAR end-to-end specification *after* the MJRA4.7 review. [AP/MB] Update details on NSAP (and if necessary L-NSAP) in BAR end-to-end specification *after* the MJRA4.7 review. [GRNet] Deploy and Test NSAP on GRNET -> [FS] Help Chrisostomos at the EGEE04 conference [ALL] Discuss who manages resources -> BAR or L-NSAP ? AP: In principle, resource management should be done in L-NSAP. BAR should *not* perform any resource management. [ALL] Check actions listed in the *DJRA4.4* workplan. [ALL] Email few line of work plan for the next week to the minute taker. [ALL] Email few lines describing work done for BAR since previous week, send to chair of next TeleCon. Email by Monday. Completed Actions ================= [CP] Revise F2F agenda [CP] Send JRA4-SA2 agenda for meeting in Pisa to KK [CP] Write 1st draft of EGEE demo (slides) [CP] Contact KK conc. poster for EGEE04 conference - Maybe use a banner as proposed by Andy [CP] Add discussion of expected/unexpected error handling to F2F agenda [CP] Update BAR end-to-end specification as discussed in the BAR planning telecon held on 4 Oct 05. [CP] Update DJRA4.4 workplan as discussed in the BAR planning telecon held on 4 Oct 05. [AP] Obtain an eScience *host* certificate for Dante's test machine and renew certificate for internal test machine. Prioritised Wish List for DJRA4.4 ================================= Items in the list are prioritised as "MUST", "SHOULD", "MAY" and "NOT IN SCOPE" MUST ---- 1) Resolution of how to distinguish between a SR and SA (via the HLM-BAR interface). - include this in WP1.1 (updates to BAR end-2-end spec) and WP1.12 (BAR service design) 2) Description of BAR-L-NSAP interface (model) 3) BAR SR and SA management - Identify who does resource management; is it BAR or L-NSAP 4) Updated JSP client which support SR and SA SHOULD ------ 1) Development of dummy L-NSAP 2) A separate interface for BAR-BAR (east-west) communication 3) Identify a user for SR MAY --- 1) Validate HLM requests based on local BAR configuration. 2) BAR-NSAP security 3) Integrate NRS to L-NSAP 4) Evaluating EGEE Agreement interface 5) Further investigation of gLite Service Discovery NOT IN SCOPE ------------ 1) BAR-BAR security 2) BAR-L-NSAP security 3) HLM-BAR user authentication Issues/bugs for DJRA4.4 ======================= 1) How should we change BAR WSDL to reflect SR and SA ? 3) Can we match a SA to SR without HLM having to be aware of the SR (e.g., without having to use SR IDs ? - If so, how do we ensure that the user is allowed to make this SA for a specific SR? (or a SR ID is required per SA request? #9138 Dependency between bar.client and bar.service (GdftRequestFactory) 2005-Jun-20 11:51 fscharin fscharin #10358 Can not find BAR log4j logs 2005-Aug-19 11:12 charaka charaka #10339 Covert BAR bandwidths from double to integer 2005-Aug-18 12:49 charaka charaka #10377 Created an enumerated type for Notification Type 2005-Aug-19 12:51 charaka charaka #10408 Refactor Cancel Service 2005-Aug-22 15:40 charaka charaka #10409 Refactor Query Service implementation 2005-Aug-22 15:42 charaka charaka #10528 DJRA4.1 BAR-NSAP Request Network Service uses "Average Bandwidth" 2005-Aug-29 16:52 apatil charaka - review GN2 NSAP WSDL #11022 Add property 'sslCAFiles' to bar.config 2005-Sep-26 10:37 fscharin fscharin #11331 NSAP does not check reverse bandwidth 2005-Sep-30 12:22 apatil fscharin - Action on AP #11588 Update MJRA4.7 INSTALL.TXT as per Gloria's comments 2005-Oct-06 10:46 fscharin charaka Close the following issues -------------------------- 2) Will it be possible to re-use the BAR WSDL for North and East interface ? - Yes, FS is already doing this. #9244 Refactoring of build.xml is needed for better understanding 2005-Jun-28 13:42 fscharin fscharin - FS says no further refactroing is necessary #10413 Why do we have RequestService:TimeForAverage parameter in HLM-BAR interface? 2005-Aug-22 17:24 apatil charaka - close with the resolution -> For future use #10526 BAR request parameter "availability" is not currently used 2005-Aug-29 16:04 charaka charaka - close with the resolution -> For future use Discussion ========== Actions required to deprecate the Architecture Document ======================================================= ON GOING: - Users of BAR: Need to go into DJRA4.1 [KK] Add users of BAR to DJRA4.1 DONE: - Section 5: Comments and Issues: [CP] Raise in Savannah - WSDL: [CP] Replace WSDL with link to CVS - Section 4.5 ??? Request Mapping: [CP] Move Request Mapping to Functional Spec - Service IDs: [FS] Add Service ID handling to BAR Service Functional Spec - Section 3: Relevant Requirements: Superseded by the new list that was agreed at the F2F meeting. [CP] Check these are present in Savannah requirements - Section 4.4: SLA: Need this to be discussed at JRA4 or SA2? Goes to SA2. [CP] Delete these from the architecture document - Denial Of Service on BAR: AP: Any Web service has to deal with this, there should be a EGEE guideline for this. [CP] Just delete them Work scheduled for last week ============================ AP: - Leave MB: - BAR to L-NSAP interface specification GV: FS: - Write minutes :) - BAR-BAR communication - GRNET support CP: - Write EGEE demo slides - Write test plan document - MJRA4.7 Review feedback Work done last week ======================== AP: - Leave MB: - Added L-NSAP interface to DJRA4.1 - MJRA4.7 reviews GV: - Sick - ? FS: - BAR-BAR Design - BAR-BAR Implementation - Reviewed demo slides CP: - Updated Gantt chart and workplan - Updated MJRA4.5 - Created draft Demo slides - Revised and circulated BAR F2F Agenda - Created provisional SA2-JRA4 F2F Agenda - BAR service design discussions - Browsing existing test plan documents - Created a test plan documents with just the headings - Evaluated and assigned MJRA4.7 Review Comments Work planned for next week ========================== AP: - MJRA4.7 review responses and update of L-NSAP spec - Review BAR demo slides - Prepare slides for TNLC - Prepare for f2f meeting MB: - L-NSAP interface - Finish review and update L-NSAP spec accordingly GV: - ? FS: - Implement BAR-BAR Communication - Redesign BAR to use new design - EGEE04 preperations - EGEE04 CP: - MJRA4.7 review responses - Prepare slides for BAR F2F meeting - prepare slides for SA2-JRA4 F2F meeting - Re-examine BAR demo slides - Attend EGEE04 conference Milestones and deliverables =========================== PM15 MJRA4.4 (June 05) Prototype implementation of BAR service at specific network ingress points using static network configuration. DONE. PM15 MJRA4.5 (June 05) Specification of end-to-end BAR system. DONE. PM18 MJRA4.7 (September 05) Dynamic reconfiguration of key ingress points in response to reservations. PM21 DJRA4.4 (December 05) Implementation of single-domain BAR service in the network core (GEANT and NRENs). Risks ===== Convention: Mitigation = what we do to address it Resolution = what we do if the risk materialises -------------------- Risk: Likelihood: Impact: Mitigation: Resolution: -------------------- Leave/holiday ============= DANTE AP: 7- 9 Nov (GEANT2 Meeting) MB: 2- 7 Nov EPCC: CP: AM 1 Nov KK: 21 October 31 October - 15 Nov FS: 14 - 16 December GARR GV: DONM ---- Wednesday 2nd Nov 05 @ 10:30 BST/ 11:30 CEST