1. Update on Grid User Network Interface (GUNI) Draft
Georgios Zervas, Eduard Escalona,
Reza Nejabati, Dimitra Simeonidou
University of Essex

2. 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

3. 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

4. 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

5. Draft updated formation
Introduction
Draft objectives
Current standardisation related to GUNI
Usecases
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

6. 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 (Gigi Karmous-Edwards)
China
3TNET (SJTU- Wei Guo)
Japan
G-Lambda (Tomohiro Kudoh)
GLIF
C3C (3 Continent Collaboration) 6

7. 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

8. Current standardisation related to GUNI8

9. Current standardisation related to GUNI
OIF
UNI v1.0
UNI v1R2
UNI v2.0
OGF
WS-Agreement
JSDL
GLUE …
OASIS
WSRF 9

10. Grid Network Use Cases with respect to GUNI10

11. Grid over GMPLS Architecture
Grid MW
GMPLS CP
GUNI (signaling)
GUNI
Optical Transport
Network
GUNI (transport) 11

12. Network Resource Provisioning System
Grid over NRPS
Grid MW
Network Resource Provisioning System
Optical Transport
Network 12

13. Grid over Grid-aware GMPLS Architecture
WS- Agreement
G2MPLS CP
WS- Agreement
GUNI
GUNI
Optical Transport
Network
GUNI (transport) 13

14. NRPS and NSP system interfaces In Phosphorus WP1
GRID APLICATIONS
&
MIDDLEWARE N e t w o r k S v i c P l a n
NRPS Broker
OTHER PROJECTS
Network Resource Provisioning Systems
ARGON
DRAC
UCLPv 2
GMPLS
Transport
Network D B
Request Handler
Reservation
Handler
Path Computer
Scheduler A WP 1
TOPOLOGICAL
CONFIGURATION C DB
JRA 3 G
MPLS
PHASE E
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

15. Interfaces for interoperability between different Provisioning systems in Phosporus15

16. Example of interface 16

17. Phosporus WP1-WP2 scenario
Grid App 1 G G G
Grid MW
Grid MW
Grid MW 2
Network Service Plane
Network Broker
GMPLS 5 5 4
N+G 3’ 3
NRPS Driver
NRPS Driver
NRPS
NRPS
This slide tries to summarize another option putting G2MPLS at “the same level” than the Network Broker. In this slide it is depicted a possible use case where we ask for a data transfer from the “Data source” to “Computational resources A”:
1- The Grid Application ask for a data transfer from the “Data source” to the “ Computational resources A
2- The Grid MW forwards the “data transfer” request to the G2MPLS domain since one of the GRID resources involves is on a G2MPLS domain.
3- The G2MPLS configures “computational resources A” and creates a connection (now or in the future) from A to B
3’- At the same time the Grid MW forwards the request to the domain managing the Data Source, the Grid MW configures the Data Source
4- G2MPLS asks to the Network Broker (or the IDM, I hope at Phase II we’ll have the IDM) for a connection from B to C (For now or in the future)
5- The Network Broker triggers the connections or the advance reservations on each domain.
WP1-WP2 meeting comments:
- On this scenario G2MPLS should be able to deal with advance reservations. N N
GMPLS
Computational resources B
SNMP/CLI/TL1
Data source N
Computational resources A C A TN
Data sink TN TN B

18. EL-GL Middleware Interoperability
Japan
Application GL
Grid Resource
Scheduler
EL→GL
wrapper
KDDI
NRM
CRM
Cluster
NTT EL US
GL→EL
GNS-WSI
JAPAN
HARC
Acceptor
Coordinator
App. Launcher
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

19. GUNI Role in Grid Networking environment19

20. 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

21. 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

22. GUNI Activities
Network Activities
Grid Network Service Activities 22

23. Requirements 23

24. 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

25. 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

26. General Requirements III26

27. GUNI Architecture and Functionalities27

28. NS architectural model with regards to GUNI
GUNI accepts connection requests from the Grid MW and establishes a new session with the NPS 28

29. 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 29

30. 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 31

31. Abstract messages and procedures32

32. Abstract messages for Overlay model33

33. Abstract messages for Integrated model I34

34. Abstract messages for Integrated model II35

35. Procedures - Message flows36

36. Network Service: Create, Reject, Delete37

37. Grid Network Service: Create38

38. Grid Network Service: Delete & Reject39

39. Grid Capability & Availability Advertisement40

40. 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 …) 41

41. Any Questions? 42