1
PHOSPHORUS (FP6 IP IST Project) Web 2.0
UCLPv2 Media eInfrastructures

• European Future Networking Initiatives
• TERENA Workshop
• February 2007, Amsterdam
• Sergi Figuerola
• i2CAT Foundation

2
Phosphorus Overview

• Instrument Integrated Project under FP6
• Activity IST-2005-2.5.6 research networking
  test-beds
• Project duration 30 months
• Project started 01 October 2006
• Project budget 6.868.969 euro (5.125.098 euro EC
  contribution)
• Project resources 814 person months
• http//www.ist-phosphorus.eu

3
Participants
4
Phosphorus Project

• European and Global alliance of partners to
  develop advanced solution of application-level
  middleware and underlying management and control
  plane technologies
• Project Vision and Mission
• The project will address some of the key
  technical challenges in enabling on-demand
  end-to-end network services across multiple
  heterogenous domains
• In the Phosphorus' implementation the underlying
  network will be treated as first class Grid
  resource
• Phosphorus will demonstrate solutions and
  functionalities across a test-bed involving
  European NRENs, GÈANT2, Cross Border Dark Fibre
  and GLIF

5
Project key features (I/II)

• Develop integration between application
  middleware and transport networks, based on three
  planes
• Service plane
• Middleware extensions and APIs to expose Network
  and Grid resources and make reservations of those
  resources
• Network Resource Provisioning plane
• Adaptation of existing Network Resource
  Provisioning Systems (NRPS) to support the
  framework of the project
• Interworking of NRPS-based domains with
  GMPLS-controlled network domains, i.e.
  interoperability between G2MPLS and UCLPv2,
  DRAC, ARGON and JRA3(GN2).
• Control plane
• Enhancements of the GMPLS Control Plane (G²MPLS)
  to provide optical network resources as
  first-class Grid resource

6
Project key features (II/II)

• Studies to investigate and evaluate further the
  project outcomes
• Study resource management and job scheduling
  algorithms incorporating network-awareness,
  constraint based routing and advance reservation
  techniques
• Develop a simulation environment, supporting the
  Phosphorus network scenario
• Disseminate the project experience and outcomes,
  toolkits and middleware to NRENs and their users,
  such as Supercomputing centres

7
PHOSPHORUS NETWORK SCENARIO
8
PHOSPHORUS ARCHITECTURE
The different domains of the Phosphorus' test-bed
will have

• Grid middleware
• UNICORE as a reference point
• AAA policies

• Three types of NRPS
• UCLP
• DRAC
• ARGON

• Two flavours of GMPLS
• standard (Ph. 1)
• Grid-enabled (Ph. 2)

9
Initial Applications

• WISDOM - Wide In Silica Docking On Malaria (FHG,
  PSNC)
• Large scale molecular docking on malaria to
  compute million of compounds with different
  software and parameter settings (in silico
  experimentation)
• KoDaVis Distributed visualisation (FZJ, PSNC,
  UESSEX)
• Compute capacity on the data server and the
  visualisation clients
• Allocate network bandwidth and QoS between server
  and clients
• TOPS Technology for Optical Pixel Streaming
  (FHG, SARA)
• Streaming of Ultra High Resolution Data Sets over
  Lambda Networks
• Use lossy protocols for long distance
  connectivity High performance TCP hard to
  achieve, UDP performance trivial
• Light weight application scalable bandwidth
  usage
• DDSS - Distributed Data Storage System (PSNC,
  HEL, FZJ, FHG, UESSEX)
• Possible scenarios of usage
• Data gathering or data distributing
• Backups of large medical data volumes (bandwidth
  demanding) from one or many clients

10
Phosphorus Work Packages
11
WP 1 Network Resource Provisioning Systems
(NRPS) for GRID Network Services

• Objectives
• Definition of NRPS and GMPLS control plane
  boundaries
• Development of interfaces and NRPS driver
• Implementation of the Network Service Plane
• Implements advance reservations
• AAA Functionalities
• System information management (Topology, users,
  resource usage, etc.)

Interoperability between NRPS, G2MPLS,Grid
middleware and JRA3 (GN2),
1st Ph. Architecture

• Planned delivery date
• System requirements (D1.1) March 07
• SW prototypes by the end of 2007
• International cooperation
• EnLIGHTened
• G-Lambda

12
WP1 Architecture 2nd Ph.

• Distributed architecture

• Phosphorus interoperability

13
WP2 - Enhancements to the GMPLS Control Plane for
Grid Network Services (GNS)
Extensions to the GMPLS CP for automatic and
single-step setup of Grid network resources

• Grid-GMPLS (G2MPLS) main tracks
• seamless coexistence with NRPS Grid MW
• Grid-aware network reference points
  (G.O-UNI, G.E-NNI, G.I-NNI)
• CBR algorithms for recovery and TE
• Integration with AAA system
• Planned delivery of G2MPLS CP prototypes
• R1.0 by M12 sw. rel. of G.I-NNI G.O-UNI
• R2.0 by M24 sys. rel. of full-fledged G2MPLS
• Technical validation
• supporting studies (WP5), demos (WP6)
  and disseminations (WP7)
• cooperation with Intl. initiatives (i.e.
  EnLIGHTened, G-Lambda) and synergies with GN2-JRA3

VOa
G.O-UNI
G2
G2
G2
G2
G.I-NNI
G.E-NNI
G2MPLS
G.O-UNI
VOb
VOc
14
WP3 Middleware and Applications

• Integration of network reservation services into
  existing Grid middleware
• services for user-driven or application-driven
  set-up of execution environments with dedicated
  capabilities performance
• Compute nodes, storage systems, visualization
  devices
• Network resources with defined QoS
• Integration of applications
• WISDOM Wide in silicio docking on Malaria
• KoDaVis collaborative, distributed visualization
  of huge data sets
• TOPS Streaming of ultra high resolution data
  sets over lambda networks
• DDSS Distributed Data Storage System

Provide application access to PHOSPHORUS services
and showcase their benefit via applications
15
WP4 Authentication, Authorization Accounting

• Service Plane - AAA will focus on implementing
  and integrating AAA solutions for the Phosphorus
  test-bed. The objectives of WP4 in the first 18
  month are
• To study the applicability of current and
  emerging AAA related technologies in order to
  select a suitable set with enough flexibility to
  create and test the interoperability of optical
  network domains. Collaborations with GEANT2
  (JRA5), DRAGON and EGEE will be established which
  and will be used as a base.
• Collaborate with WP1, 2 and 3 to establish their
  specific needs towards AAA and describe their
  needs in a uniform way that allowing a more
  generalized implementation
• To create prototypes, running in a test-bed which
  demonstrates authorization sequences applied in
  multiple functional layers of the network. The
  AAI work within GEANT2 and VOMS work within EGEE
  will be used as starting point and expanded.

16
WP5 Supporting Studies
Job routing scheduling algorithms Network
resource management
WP2
WP1

• Job demand models
• QoS resource scheduling
• Grid job routing algorithms
• Physical layer constraints
• Advance reservations

Control plane design

• Architectural issues
• Integration strategies
• Recommendations

Simulation environment

• Optical network
• Advanced control plane
• Network service plane

17
WP6 Testbed Demonstration Activities
18
WP7 Dissemination, Contribution to Standards,
Liaisons

• Disseminate information concerning the technical
  developments to NRENs and related projects
  (MUPBED, GN2, NOBEL, EGEE, DEISA, OpenNet, RING,
  ONELAB, PANLAB, UCLP, DRAGON, Enlightened
  Computing, G-Lambda)
• Collaboration of 3 Continents (C3C) Phosphorus,
  Enlightened and G-Lambda
• Meeting between WP1, WP2 and JRA3 (GN2) WP4 and
  JRA5(GN2) and DRAGON
• Coordinate direct contributions to standards
• Build a collaborative framework for participation
  to test-bed activities from within and external
  to EU
• Questionnaire to collect information about NRENs
  that would want to deploy GMPLS G2MPLS protocol
  and NRPS systems in their networks and inform
  about Phosphorus directions of work.
• We want to provide solutions which will expect by
  our community and could be deployed in short time
  as new offered service
• http//www.ist-phosphorus.eu/documents.php
• (http//www.ist-phosphorus.eu/files/press/phosphor
  us-questionnaire.doc)

19

• UCLPv2 Applying the Web 2.0 philosophy to the
  networking revolution

20
Web 2.0

• Provides tools and applications to empower user
  participation, content creation and sharing over
  the web.

21
UCLP v2 (I)

• Provides tools to allow users to participate in
  the process of creating and setting up their own
  virtual/logical networking infrastructure
• Virtual networking infrastructure made up of
  physical resources (partitions of physical nodes,
  physical links, sensors, instruments, ) provided
  by different physical administrators
• Users can use this virtual infrastructure for
  their own needs and/or exchange/acquire/sell part
  of this infrastructure to other users
• Provides a network virtualization framework upon
  which communities of users can build their own
  services or applications

22
UCLP v2 (II)
Physical network administrator creates logical
resources by partitioning its network
User get resources from the administrator and
configures his own network setup
23
Web 2.0, SOA and UCLPv2

• Web 2.0 tools are a collection of software
  services (service mashups) whose API is usually
  publicly accessible trough open standards (XML,
  REST web services, SOAP web services)
• SOA is about creating modular, secure and
  reusable services that can be used to build other
  services and applications
• UCLPv2 is not an application software but a suite
  of different application modules based on SOA. By
  having these different modules interacting
  together users can create network behaviors
  specific to their needs
• Web 2.0 The Web as a Platform
• UCLPv2 The Network as a Platform

24
A new Media eInfrastructure
25

• Internet is increasingly a media network, but
  limitations of current network media technology
• The need for a Media eInfrastructure for Future
  Research on Visualization and Media

European eInfrastructures (2013)
Digital repositories
A new Media and Visualization layer to offer
experimental media services, that integrates the
new digital interfaces
Media HD/3D/Visualization
Computing SuperComputing/GRIDS, DEISA
Networking 3/4G, Lambda Networking, GN2..

• An environment to enable users to set up the
  media-network infrastructure under requests when
  needed
• Collaboration between
• Network engineering research community
• Media content research community
• These Media eInfrastructure should provide
• capacity detection in order to distinguish
  between users (network and resources)
• Transcodification depending on the capacities
  the content should dynamically adapt, by means of
  different codifications schemes
• Security, integrity and confidentiality
• Balancing/distribution/ load clustering
• Content Storage capacity
• Detection, publish and new contents service

26

• THANK YOU

Sergi Figuerola Sergi.figuerola_at_i2cat.net