100 likes | 127 Views
Bandwidth Allocation and Reservation. Anand Patil EGEE 3 rd Conference, Athens. Outline . Scope Current status Issues Deployment Service availability Provisioning model Operational interface Discussion. Scope . Scope is limited to the current EGEE project
E N D
Bandwidth Allocation and Reservation Anand Patil EGEE 3rd Conference, Athens
Outline • Scope • Current status • Issues • Deployment • Service availability • Provisioning model • Operational interface • Discussion TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Scope • Scope is limited to the current EGEE project • What can be achieved in the next year? • What services will be available within the next year? • Assumption - only Premium IP service will be available • Light paths may not be available in the current EGEE lifetime, hence while kept in mind, should not be considered TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Current Status • BAR – Bandwidth Allocation & Reservation • First iteration of interface specification defined • Next iteration of interface underway • Basic handshake between BAR and NSAP done using the agreed interface • A basic prototype is released in JRA4 CVS • Next prototype will add more functionality – June 2005 • Architecture and AA being finalised TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Deployment • BAR requires GEANT2-SA3 software • GEANT2 has proposed the following sites for deployment: • GRNET • GARR • UKERNA • Sites have agreed in principle to take part in GEANT2 pilot • Makes sense for EGEE to deploy BAR at the same sites • Need to get formal agreement from the NRENs involved TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Service Availability • BAR expects networks to provide premium IP service (current EGEE project scope) • In which networks is Premium IP service available today? • In which networks will the service be available in the future? • What are the timelines for service availability? • What is the big picture? TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Provisioning Model • What is the operational level of the service? • Does it have an software service interface? • Is the service compatible on an edge-to-edge path? • What are the lead times for provisioning? • Assumption – manual configuration • Needs to be validated • Is the request granted on demand or are long term reservations in place? • What are the NREN policies for granting EGEE requests? TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Operational Interface • How does BAR interact with network in terms of AA? • One suggestion in EGEE is to use Transport Layer Security • Is this acceptable to all NRENs? • Will NREN use their own AA technologies? • EGEE may need to cater for diverse AA technologies • SA2 is defining the SLA installation (DSA2.2) • Will networks agree to provide SLAs? • It is not clear how BAR fits into the SLA scenario • SA2 is defining the operational interface (MSA2.3) • Needs to be validated with NRENs TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Discussion • Who is responsible for these issues? • Some grey areas between JRA4 and SA2 • Need more interaction between JRA4 and SA2 • How can TNLC help in some of these issues? TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005
Thank You Questions / comments / suggestions / feedback welcome Please contact anand.patil@dante.org.uk TNLC Meeting, EGEE 3rd Conference, Athens, April 21st 2005