390 likes | 477 Views
Update on Grid User Network Interface (GUNI) Draft. Georgios Zervas, Eduard Escalona, Reza Nejabati, Dimitra Simeonidou University of Essex. Talk Overview. Need for the Grid User Network Interface (GUNI) Draft Evolution and emergence of new applications and services
E N D
Update onGrid User Network Interface (GUNI) Draft Georgios Zervas, Eduard Escalona, Reza Nejabati, Dimitra Simeonidou University of Essex
Talk Overview • Need for the Grid User Network Interface (GUNI) Draft • Evolution and emergence of new applications and services • Broad range of Grid and Network Service Provisioning systems • Evolution of network infrastructure and technologies to support Grids • Interoperability between Grid service layer and Network Service Layer • Draft main areas • Current status and overview of all sections • Drafts’ Future Plan 2
New Solutions, Architectures, Technologies and Services are Emerging • Evolving Grid Network Architectures: • Proprietary solutions for specific implementations. • G-Lambda, Enlightened, Phosphorus, 3TNET, … • Need interface that can provide interoperable procedures between a wide range of service provisioning systems. • Support of a number of distinct layer architectural models across geographical organizational boundaries, heterogeneous environments with different • Grid service provisioning systems (co-allocation services, Brokers, etc.), • Network Resource Provisioning Systems • Control plane (e.g. GMPLS, Grid-aware GMPLS) • Transport planes (e.g. Ethernet, SDH, OTN, OBS) • Policy, security standards. 3
Talk Overview • Need for the Grid User Network Interface (GUNI) Draft • Evolution and emergence of new applications and services • Broad range of Grid and Network Service Provisioning systems • Evolution of network infrastructure and technologies to support Grids • Draft main areas • Current status and overview of all sections • Draft Future Plan 4
Draft updated formation • Introduction • Draft objectives • Current standardisation related to GUNI • Use cases • GUNI Role in Grid Networking environment • GUNI definition • GUNI roles and activities • Requirements • Architecture and Functionalities • Overlay and Integrated • Services offered by GUNI • Abstract messages and procedures 5
Grid User Network Interface (GUNI) Draft:Current Situation • Contribution from organisations so far • Europe • IST-Phosphorus • UEssex (G. Zervas, E. Escalona, R. Nejabati, D. Simeonidou) • NXW (N. Ciulli, G. Carrozzo) • PSNC (A. Binczewski, D. Parniewicz, B. Belter) • FHG (O.Waeldrich, W. Ziegler) • ISTe-photon/One+ • CARRIOCAS • Alcatel-Lucent (Dominique Verchere) • USA • MCNC, Research & Development Institute (GigiKarmous-Edwards) • China • 3TNET (SJTU- WeiGuo) • Japan • G-Lambda (Tomohiro Kudoh) • GLIF • C3C (3 Continent Collaboration) 6
GUNI Draft Objectives • Describe the requirements of a generic interface between the Grid Service Plane and the Network Service Plane. • Review existing standardisation documents in relation to GUNI • OIF UNI, OGF, OASIS • Report the role and activities of GUNI in Grid-Network environments • Describe architectural Grid Network models with regards to GUNI • Functionalities, procedures and services supported over GUNI. • Abstract messages required to • interface any Grid service provisioning system with any Network provisioning system • Report on existing Use cases utilizing proprietary interfaces 7
Current standardisation related to GUNI • OIF • UNI v1.0 • UNI v1R2 • UNI v2.0 • OGF • WS-Agreement • JSDL • GLUE • … • OASIS • WSRF • … 9
Grid over GMPLS Architecture Grid MW GMPLS CP GUNI (signaling) GUNI Optical Transport Network GUNI (transport) 11
Grid over NRPS Grid MW Network Resource Provisioning System Optical Transport Network 12
Grid over Grid-aware GMPLS Architecture G2MPLS CP WS- Agreement WS- Agreement GUNI GUNI Optical Transport Network GUNI (transport) 13
NRPS and NSP system interfaces In Phosphorus WP1 GRID APLICATIONS TOPOLOGICAL & MIDDLEWARE CONFIGURATION WP 1 C A PHASE 2 e n Request Handler a OTHER PROJECTS l P Scheduler e c E i v Reservation r Path Computer e Handler S JRA 3 k r o w DB t NRPS Broker E e N B 2 G MPLS Network Resource Provisioning Systems ARGON DRAC UCLPv 2 D Transport D GMPLS Network Transport Transport Network Network A) Northbound IF:It receives the reservation requests from the GRID Middleware. B) East-West IF:It is in charge of the communication between NRPSs. C) Topological IF:It is used to indicate to the NSP which resources are under control (NRPSs, endpoints, links). D) Southbound IF:It Communicates the NRPSs and the lower layers (GMPLS or transport layer). E) Phase 2 IF:It provides interoperability between the NSP and the G2MPLS CP or other projects. 14
N G G G 1 2 5 3 5 4 3’ N+G Phosporus WP1-WP2 scenario Grid App Grid MW Grid MW Grid MW Network Service Plane Network Broker GMPLS NRPS Driver NRPS Driver NRPS NRPS N N GMPLS Computational resources B SNMP/CLI/TL1 Data source Computational resources A C A TN TN TN Data sink B
Japan Application US Application EL→GL wrapper EL App. Launcher GL Grid Resource Scheduler EL Grid Resource Coordinator GNS-WSI GL→EL CRM wrapper GL→EL GNS-WSI wrapper HARC Acceptor US JAPAN EL NRM KDDI NRM NTT NRM CRM CRM CRM CRM CRM CRM CRM CRM Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster EL-GL Middleware Interoperability Credit: Tomohiro Kudoh GL: G-lambda EL: Enlightened Computing CRM: Compute Resource Manager HARC: Highly-Available Resource Co-allocator GNS-WSI: Grid Network Service-Web Services Interface NRM: Network Resource Manager
GUNI Reference Point Grid- Network service interface that links any type of Grid End or Grid Service Point with a broadened Network Provisioning System. 20
Proposal for a Generic GUNI architecture Grid Users Grid Resources Grid Applications Globus Middleware UNICORE Middleware gLite Middleware Any Grid Middleware GUNI-C GUNI-C GUNI-C GUNI-C GUNI-C GUNI-N GUNI-N GUNI-N GUNI-N GUNI-N NRPS GMPLS G2MPLS OBS/OPS ANY Transport Plane
GUNI Activities • Grid Network Service Activities 22 Network Activities
Requirements 23
General Requirements I • Interoperability: GUNI must be able to interface to any software, hardware and service boundaries between different layers • Grid Middleware • Grid Users/Resources • NRPS • GMPLS • Grid-aware GMPLS • OBS • Extensibility: GUNI architecture needs to scale to potentially support any possible Grid/network service provisioning system 24
General Requirements II • Performance and agility: GUNI should dynamically adjust the service provisioning level (e.g. Bandwidth provisioning) and accept different signal types and levels of granularity. • QoS assurance: • Service Level Agreement • Reliability • Security and Policy: GUNI should provide means to check and forward service credentials for using grid and network resources and accounting for the real resource usage. • Authentication and authorization • Failure notification 25
NS architectural model with regards to GUNI • GUNI accepts connection requests from the Grid MW and establishes a new session with the NPS 27
Network Services supported by GUNI • Connection creation • Connection deletion • Connection status enquiry • Network Topology Enquiry and Restoration • Network Resource Capability • Network Resource Availability • Network Advance Reservation • Traffic classification and shaping • Data plane enhanced security 28
Grid Network Services supported by GUNI Grid services mainly allow on-demand access to Grid resources considering reservation, allocation, actual use and release. Moreover, procedures such as discovery of capability and availability of computational resources are also required in order to facilitate Grid resource management. • Grid Service Discovery • Grid Resource Discovery • Grid Advance Reservation Request • Grid Advance Reservation Cancellation 30
Future plans • Incorporate final remaining contributions. • Await for comments from GHPN members. • Finalise and Submit before next OGF meeting. • Possible organization of BoF in OGF Europe as a follow up… with consideration on creation of GUNI-WG • Interact with other OGF groups (GRAAP, JSDL, GLUE,…) • Identify and agree on message transactions • Identify the platform (e.g. WS-Agreement, WS or …) 40
Any Questions? gzerva@essex.ac.uk eescal@essex.ac.uk 41