JRA4 F2F meeting Day 2 (10 May 2005) - the main BAR meeting ========================================== ========================================== Note that these notes augments the slides available from the Agenda page, http://agenda.cern.ch/fullAgenda.php?ida=a052821 Discussions =========== Architecture ------------ L-NSAP is not considered, but HLM-BAR, BAR-BAR and BAR-NSAP Endsites and NRENs, backbones described in Slides! Issue: No contact from GRNet to install and test the software. BAR Functional Scope [KK] Identify a contact in GRNet to install and test software. BAR service ----------- Implement - BT and VLL Request Services - Cancel Service - BAR-2-BAR communication - Basic security Discussion about IP Premium and usefulness for BT. IP Premium is wrong service to use for large amount of data, but currently the only option, although only 10% of bandwidth is available with IP Premium. Best use of IP Premium: Real time data transfer, e.g. for interactive video conference BAR is a pilot service, what service should we present for this pilot? VLL: guaranteed Bandwidth for time A to B (MB). BT: to solve scheduling problems to transfer x Bytes before a deadline (MB). The term BT is misleading to EGEE community. We need a better name so as not to confuse people. Suggested by Kostas - "Guaranteed Deadline". i.e., the service name "Bulk Transfer" is changed to "Guaranteed Deadline" Need to finalise on a name by next week. Note, this require updating of *all* documentation. [ALL] Suggests an aternative name to "Bulk Transfer". The current suggestion is Guaranteed Deadline" In general, MJRA4.4 must have a well defined interface, stable code. The workflow shown in the architecture doc should be able to be tested with two end sites. NSAP service ------------ Agreement between SA2,... GN2's first release of NSAP is planned for October 2005, a basic functional provisioning system to be produced by December 2005. NSAP Chaining will be done first by DANTE, but no time line available. Extended NSAP for June prototype to get one step closer to actual NSAP functionality. NSAP for MJRA4.4 could response on which amount of bandwidth is requested (low bandwidth will always gets reserved, high bandwidth will not). BAR Client ---------- Within the scope of the June prototype there will be a client. The components of the BAR client will be: - BAR Demo (GUI part) - BAR Integration Tests (test the BAR Service) - BAR Client Interface (is used by BAR Demo and BAR Integration Tests) BAR Integration Tests should test all possible combinations of request and responses. NSAP prototype will response with all possible responses. AP will provide logic for NSAP to know what can be expected for which request. The BAR Demo will be a simple JSP to display a form with hardcoded dropdown boxes [AP]. The form will be submitted to another JSP which will pass the information to client modules [FS]. BAR demo -------- Where will the Demo be presented: probably at the next EGEE conference (October 2005). No external presentation for MJRA4.4. BAR Demo will be a JSP site which provides simple options to request services. JSP templates will be provided by Anand. [AP] Provide FS with BAR Demo JSP templates Deployment, configuration & system testing ------------------------------------------ Responsibilities of, End sites (GARR, GRNet): - install "base installation" (see slides), jra3 security library, BAR client and BAR service - configure and test them. - The BAR service should be available at *all* the time NRENs (GARR, GRNet) - install "Base installation", jra3 security library, NSAP service - Configure and test them. - The NSAP service should be available all the time. backbone (Geant) - install "Base installation", jra3 security library, NSAP service - Configure and test them. - The NSAP service should be available all the time. We may have to simulate GRNet roles using another site. Adding security to NSAP should be easier than to HLM-BAR (AKP). [AP + AKP] get together to add Security to NSAP updates/modifications to DJRA4.1 -------------------------------- The Service Class only one value for now -> "IP Premium". BAR has to map it service types to NSAP-Metrics: Planned metrics: Bandwidth (Now) Delay (December) Jitter (Next Year) Packet Loss (Next Year) Bandwidth calculation has to include a safety factor (See minutes for 9 MAy 2005). NSAP-Min/MaxBandwidth will be removed. Alternative Parameter negotiation. BAR should do it. NSAP can provide hints, but cannot provide an alternative option. Problem is that not all involved network parts can provide sufficient information to provide a guaranteed alternative for NSAP. So BAR needs to guess. BAR config needs to specify Min/Max Bandwidth. Will be needed to check if Service Request are valid or not. Additionally it can be used to calculate alternative parameters. Time for Average: Can be used to calculate alternative average bandwidth. Availability: Will be needed for connection oriented networks. Ignore it in the meanwhile. AS Number: Is a world-wide unique number for a network (e.g. CERN) Source/Destination AS: Currently not in use, just for GEANT2, will be used in EGEE2. Not used in EGEE1. In future, it would be possible to use the central registry service of glue schema (built up by SA1). [Ratna] Talk to Jennifer/Elisabeth about glue schema In/Egress Node: Does every BAR within an endsite has just exactly one NSAP? Agreement: The assumption is taken that there will not be more than one NSAP per BAR. Egress is optional. Idea would be to contact the remote BAR to ask for the Egress node (= Ingress of remote BAR) How to get remote BAR for a specific endsite? Open point for tomorrow. Direction: Add new parameter to North Interface called "Direction". Default is bidirectional. Question is if not only direction should be specified as boolean, but it could be used to specify separate bandwidth per direction. Transaction ID: Just for logging, bookkeeping. MJRA4.5 ------- [AP] Provide new version of DJRA4.1. This version will be used as a reference to MJRA4.5. NSAP Chaining will be mentioned in document, but it will be clearly stated that chaining is not in the scope currently. NSAP: Interactions, Expected responses on requests, error conditions(?) Discussion about L-NSAP: Build using GRS(NRS) ? Examine the Agreement-Architecture (July-Sept 05). Responsibilities are stated in the TOC. [FS] Email TOC MJRA4.5 to everyone. BAR schema/WSDL --------------- Highlighted changes + additions since March 05 prototype. [AP] Provide changes to NSAP.wsdl as discussed by end of next week (20. May 2005) Workplan for MJRA4.4 + MJRA4.5 ------------------------------ * Progress Vs workplan * Assignment of effort [FS] Write functional spec of BAR Client [FS] Write design doc for BAR Client BAR road map until end of EGEE 1 -------------------------------- Not full Security will be implemented for MJRA4.4. More Information from Alistair. MAYs for later development: Agreement, Query Service, Notification Other ----- Use Axis 1.2 RC3, [AKP/FS] to investigate difference between RC3 and final version and report. [AP] Increament the version of DJRA4.1 and update the interfaces. Next meeting 12/13 July 2005 at EDI. Dante's Tasks ------------- (AP is busy with GN2-SA3 meeting the whole of this week.) Update DJRA4.1 - word doc Update NSAP WSDL and schema 0.5md = 2days AP due 18-05-2005 JSP for GUI client 0.5md = 2 days AP due 20-05-2005 Start the MJRA4.5 end-to-end specification document continuous task MB - 0.25 md AP - 0.25 md - will start after 20-05-2005 NSAP specification 1 md = 4 days AP due ??? NSAP development - generate using axis 1.2 RC3 or final - add NSAP to JRA4 CVS - support all operations - dummy logic 5 md = 20 days = 4 weeks AP - due ??? NSAP Basic profile testing 1.0 md = 4 days AP due ??? Open issues =========== 1) No contact to GRNET to install and test the software. BAR Functional Scope Summary of actions ================== [KK] Identify a contact in GRNet to install and test software. [ALL] Suggests an aternative name to "Bulk Transfer". The current suggestion is Guaranteed Deadline" [AP + AKP] get together to add Security to NSAP. [AP] Provide new version of DJRA4.1. [FS] Email TOC MJRA4.5 to everyone. [AP] Provide FS with BAR Demo JSP templates [Ratna] Talk to Jennifer/Elisabeth about glue schema [AP] Provide changes to NSAP.wsdl as discussed by end of next week (20. May 2005) [FS] Write functional spec of BAR Client [FS] Write design doc for BAR Client [AKP/FS] to investigate diff between RC3 and final version and report. [AP] Increament the version of DJRA4.1 and update the interfaces.