Your SlideShare is downloading. ×
0
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
ppt
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ppt

3,411

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,411
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • UCLP: User Controlled LightPaths – a network virtualization management tool built using web services ARGON: ARGON provides Network Services with advance network resource reservation capabilities and dedicated QoS DRAC: DRAC provides applications with the means to directly drive their network resources within a policy-defined envelope of flexibility using existing standards and toolsets for interfaces.
  • Wisdom: The goal within Phosphorus is the deployment of a CPU-intensive application generating large data flows to test the Grid infrastructure, compute and network services. KoDaVis: The main objective in Phosphorus is to adapt KoDaVis to the Phosphorus' environment to make scheduled synchronous reservations of its resources via the UNICORE middleware :
  • UCLP: User Controlled LightPaths – a network virtualization management tool built using web services ARGON: ARGON provides Network Services with advance network resource reservation capabilities and dedicated QoS DRAC: DRAC provides applications with the means to directly drive their network resources within a policy-defined envelope of flexibility using existing standards and toolsets for interfaces. NSP: is the responsible for gathering the topology of different domains, implements AAA functions, offers an interface to Grid App. , and coordinates advance reservations. NRPS Broker: is a block of the NSP and is responsible for finding inter-domain paths, manage the communication with the NRPSs, implement transactions, etc.
  • AAI: Authorization Authentication Infrastructure ( http://www.surfnet.nl/publicaties/surfworks2005/indi-2005-009-16.pdf ) Conclusions: This architecture definition covers all cases we currently see as a real scenario. The components and their interactions are described with the help of formal languages and including all relevant attributes. This forms the basis of the next step, the implementation of eduGAIN as a prototype. A testbed will be set-up in the coming months of the year to start functional tests of the implementation. Parts of the software will be provided for a first use in the performance monitoring environment (JRA1 in GÉANT2). Feedback and experiences with the installation will lead to a new version of the architecture document and conveyed into the first cookbook the will be written in the year two of the work item 2 of JRA5. In this deliverable the formal description is based on SAML1.1, a standard from 2003. We are aware of the fact that SAML2.0 is already specified, however for practical reasons (missing publicly usable implementation) we had to stay with the older version for now. It is planned to adapt the protocol definition when an implementation and test environment will be available. VOMS: The VOMS Admin service is a web application providing tools for administering member databases for VOMS, the Virtual Organization Membership Service. VOMS serves as a central repository for user authorization information, providing support for sorting users into a general group hierarchy, keeping track of their roles, etc. Its functionality may be compared to that of a Kerberos KDC server. VOMS Admin provides an intuitive web user interface for daily administration tasks, and a SOAP interface for remote clients. (The entire functionality of the VOMS Admin service is accessible via the SOAP interface.) The Admin package includes a simple command-line SOAP client that is useful for automating frequently occuring batch operations, or simply to serve as an alternative to the full-blown web interface. It is also useful for bootstrapping the service.
  • Objectives: Requirements analysis and design of the test-bed Construction of the test-bed and configuration of all related software components, middleware and applications Tests of project’s developments Demonstration of project’s results Recognizing, description, deployment and testing of new types of Layer 0 and Layer 1 resources Current status: Work package is in the phase of test-bed design. The members are gathering information about their local network requirements and possible connections with other partners, and the coordinator is collecting data from other work packages, regarding e.g. applications’ requirements.
  • (UCLPv2) provides a network virtualization framework upon which communities of users can build their own services or applications without having to deal with the complexities of the underlying network technologies while still maintaining the functionality that the network provides. The system has been designed as a Service Oriented Architecture (SOA) where Web Services and Web Services Workflows are the basic building blocks. Articulated Private Networks (APNs) are presented as the first services built upon the UCLPv2 network virtualization middleware. APNs can be considered as a next generation Virtual Private Network where a user can create a complex, multi-domain network topology by binding together network resources, computers, time slices and virtual or real routing and/or switching nodes. A first implementation of the UCLPv2 software has been deployed on CAnet 4, Canada’s research and education network, and it is currently being used by Environment Canada, a federal government department, to enable an APN that links its research facilities across the country.
  • APNs can be considered as a next generation Virtual Private Network where a user can create a complex, multi-domain network topology by binding together network resources, computers, time slices and virtual or real routing and/or switching nodes
  • Transcript

    • 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 <ul><li>Instrument: Integrated Project under FP6 </li></ul><ul><li>Activity: IST-2005-2.5.6 – research networking test-beds </li></ul><ul><li>Project duration 30 months </li></ul><ul><li>Project started 01 October 2006 </li></ul><ul><li>Project budget 6.868.969 euro ( 5.125.098 euro EC contribution ) </li></ul><ul><li>Project resources 814 person months </li></ul><ul><li>http://www.ist-phosphorus.eu </li></ul>
    • 3. Participants
    • 4. Phosphorus Project <ul><li>European and Global alliance of partners to develop advanced solution of application-level middleware and underlying management and control plane technologies </li></ul><ul><li>Project Vision and Mission </li></ul><ul><ul><li>The project will address some of the key technical challenges in enabling on-demand end-to-end network services across multiple heterogenous domains </li></ul></ul><ul><ul><li>In the Phosphorus&apos; implementation the underlying network will be treated as first class Grid resource </li></ul></ul><ul><ul><li>Phosphorus will demonstrate solutions and functionalities across a test-bed involving European NRENs, GÈANT2, Cross Border Dark Fibre and GLIF </li></ul></ul>
    • 5. Project key features (I/II) <ul><li>Develop integration between application middleware and transport networks, based on three planes: </li></ul><ul><ul><li>Service plane : </li></ul></ul><ul><ul><ul><li>Middleware extensions and APIs to expose Network and Grid resources and make reservations of those resources </li></ul></ul></ul><ul><ul><li>Network Resource Provisioning plane : </li></ul></ul><ul><ul><ul><li>Adaptation of existing Network Resource Provisioning Systems (NRPS) to support the framework of the project </li></ul></ul></ul><ul><ul><ul><li>Interworking of NRPS-based domains with GMPLS-controlled network domains, i.e. interoperability between G [2] MPLS and UCLPv2 , DRAC , ARGON and JRA3(GN2) . </li></ul></ul></ul><ul><ul><li>Control plane : </li></ul></ul><ul><ul><ul><li>Enhancements of the GMPLS Control Plane (G²MPLS) to provide optical network resources as first-class Grid resource </li></ul></ul></ul>
    • 6. Project key features (II/II) <ul><li>Studies to investigate and evaluate further the project outcomes : </li></ul><ul><ul><li>Study resource management and job scheduling algorithms incorporating network-awareness, constraint based routing and advance reservation techniques </li></ul></ul><ul><ul><li>Develop a simulation environment, supporting the Phosphorus network scenario </li></ul></ul><ul><li>Disseminate the project experience and outcomes, toolkits and middleware to NRENs and their users, such as Supercomputing centres </li></ul>
    • 7. PHOSPHORUS NETWORK SCENARIO Applications NREN+vendor 1 Service plane 1 Control plane Equipment transport+Data NREN+vendor 2 Service plane 2 NRPS Equipment transport+Data NREN+vendor n Service plane n NRPS+Control plane Equipment transport+data Application 1 Application 2 Application n  
    • 8. PHOSPHORUS ARCHITECTURE The different domains of the Phosphorus&apos; test-bed will have: <ul><ul><li>Two “flavours” of GMPLS </li></ul></ul><ul><ul><ul><li>standard ( Ph. 1 ) </li></ul></ul></ul><ul><ul><ul><li>Grid-enabled ( Ph. 2 ) </li></ul></ul></ul><ul><ul><li>Three types of NRPS: </li></ul></ul><ul><ul><ul><li>UCLP </li></ul></ul></ul><ul><ul><ul><li>DRAC </li></ul></ul></ul><ul><ul><ul><li>ARGON </li></ul></ul></ul><ul><ul><li>Grid middleware </li></ul></ul><ul><ul><ul><li>UNICORE as a reference point </li></ul></ul></ul><ul><ul><ul><li>AAA policies </li></ul></ul></ul>
    • 9. Initial Applications <ul><li>WISDOM - Wide In Silica Docking On Malaria (FHG, PSNC): </li></ul><ul><ul><li>Large scale molecular docking on malaria to compute million of compounds with different software and parameter settings (in silico experimentation) </li></ul></ul><ul><li>KoDaVis – Distributed visualisation (FZJ, PSNC , UESSEX ) </li></ul><ul><ul><li>Compute capacity on the data server and the visualisation clients </li></ul></ul><ul><ul><li>Allocate network bandwidth and QoS between server and clients </li></ul></ul><ul><li>TOPS – Technology for Optical Pixel Streaming (FHG, SARA) </li></ul><ul><ul><li>Streaming of Ultra High Resolution Data Sets over Lambda Networks </li></ul></ul><ul><ul><li>Use lossy protocols for long distance connectivity: High performance TCP hard to achieve, UDP performance trivial </li></ul></ul><ul><ul><li>Light weight application – scalable bandwidth usage </li></ul></ul><ul><li>DDSS - Distributed Data Storage System (PSNC, HEL, FZJ, FHG , UESSEX ) </li></ul><ul><ul><li>Possible scenarios of usage: </li></ul></ul><ul><ul><ul><li>Data gathering or data distributing </li></ul></ul></ul><ul><ul><ul><li>Backups of large medical data volumes (bandwidth demanding) from one or many clients </li></ul></ul></ul>
    • 10. Phosphorus Work Packages
    • 11. WP 1: Network Resource Provisioning Systems (NRPS) for GRID Network Services <ul><li>Objectives: </li></ul><ul><li>Definition of NRPS and GMPLS control plane boundaries </li></ul><ul><li>Development of interfaces and NRPS driver </li></ul><ul><li>Implementation of the Network Service Plane: </li></ul><ul><ul><li>Implements advance reservations </li></ul></ul><ul><ul><li>AAA Functionalities </li></ul></ul><ul><ul><li>System information management (Topology, users, resource usage, etc.) </li></ul></ul>Interoperability between NRPS, G 2 MPLS,Grid middleware and JRA3 (GN2), 1 st Ph. Architecture: <ul><li>Planned delivery date: </li></ul><ul><ul><li>System requirements (D1.1): March 07 </li></ul></ul><ul><ul><li>SW prototypes by the end of 2007 </li></ul></ul><ul><li>International cooperation: </li></ul><ul><ul><li>EnLIGHTened </li></ul></ul><ul><ul><li>G-Lambda </li></ul></ul>TN NRPS SNMP/CLI/TL1 TN NRPS SNMP/CLI/TL1 GMPLS NRPS SNMP/CLI/TL1 NRPS Driver NRPS Driver NRPS Driver G H F D E B C A Grid App Network Service Plane NRPS Broker
    • 12. WP1: Architecture 2 nd Ph. <ul><li>Distributed architecture: </li></ul><ul><li>Phosphorus interoperability: </li></ul>NRPS NSP NRPS NRPS . . . NRPS NSP NRPS NRPS . . . NRPS NSP NRPS NRPS . . . DM G2MPLS TN NRPS NSP NRPS NRPS . . . JRA3 IDM TN TN TN TN . . . . . . G-Lambda EnLIGHTened ? ?
    • 13. WP2 - Enhancements to the GMPLS Control Plane for Grid Network Services (GNS) G 2 G 2 G 2 G 2 G.I-NNI G.E-NNI G.O-UNI G 2 MPLS VOa VOb VOc G.O-UNI Extensions to the GMPLS CP for automatic and single-step setup of Grid &amp; network resources <ul><li>Grid-GMPLS (G 2 MPLS) main tracks: </li></ul><ul><ul><li>seamless coexistence with NRPS &amp; Grid MW </li></ul></ul><ul><ul><li>Grid-aware network reference points (G.O-UNI, G.E-NNI, G.I-NNI) </li></ul></ul><ul><ul><li>CBR algorithms for recovery and TE </li></ul></ul><ul><ul><li>Integration with AAA system </li></ul></ul><ul><li>Planned delivery of G 2 MPLS CP prototypes </li></ul><ul><ul><li>R1.0 by M12: sw. rel. of G.I-NNI + G.O-UNI </li></ul></ul><ul><ul><li>R2.0 by M24: sys. rel. of full-fledged G 2 MPLS </li></ul></ul><ul><li>Technical validation </li></ul><ul><ul><li>supporting studies (WP5), demos (WP6) and disseminations (WP7) </li></ul></ul><ul><ul><li>cooperation with Intl. initiatives (i.e. EnLIGHTened, G-Lambda) and synergies with GN2-JRA3 </li></ul></ul>NRPS
    • 14. WP3 : Middleware and Applications <ul><li>Integration of network reservation services into existing Grid middleware </li></ul><ul><ul><li>services for user-driven or application-driven set-up of execution environments with dedicated capabilities &amp; performance </li></ul></ul><ul><ul><ul><li>Compute nodes, storage systems, visualization devices </li></ul></ul></ul><ul><ul><ul><li>Network resources with defined QoS </li></ul></ul></ul><ul><li>Integration of applications </li></ul><ul><ul><li>WISDOM: Wide in silicio docking on Malaria </li></ul></ul><ul><ul><li>KoDaVis: collaborative, distributed visualization of huge data sets </li></ul></ul><ul><ul><li>TOPS: Streaming of ultra high resolution data sets over lambda networks </li></ul></ul><ul><ul><li>DDSS: Distributed Data Storage System </li></ul></ul>Provide application access to PHOSPHORUS services and showcase their benefit via applications
    • 15. WP4: Authentication, Authorization &amp; Accounting <ul><li>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: </li></ul><ul><ul><li>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. </li></ul></ul><ul><ul><li>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 </li></ul></ul><ul><ul><li>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. </li></ul></ul>
    • 16. WP5: Supporting Studies Job routing &amp; scheduling algorithms Network &amp; resource management Simulation environment Control plane design <ul><li>Job demand models </li></ul><ul><li>QoS resource scheduling </li></ul><ul><li>Grid job routing algorithms </li></ul><ul><li>Physical layer constraints </li></ul><ul><li>Advance reservations </li></ul><ul><li>Optical network </li></ul><ul><li>Advanced control plane </li></ul><ul><li>Network service plane </li></ul><ul><li>Architectural issues </li></ul><ul><li>Integration strategies </li></ul><ul><li>Recommendations </li></ul>WP1 WP2
    • 17. WP6: Testbed &amp; Demonstration Activities
    • 18. WP7: Dissemination, Contribution to Standards, Liaisons <ul><li>Disseminate information concerning the technical developments to NR E Ns and related projects (MUPBED, GN2, NOBEL, EGEE, DEISA, OpenNet, RING, ONELAB, PANLAB, UCLP, DRAGON, Enlightened Computing, G - Lambda…) </li></ul><ul><ul><li>Collaboration of 3 Continents (C3C): Phosphorus, Enlightened and G-Lambda </li></ul></ul><ul><ul><li>Meeting between WP1, WP2 and JRA3 (GN2); WP4 and JRA5(GN2) and DRAGON </li></ul></ul><ul><li>Coordinate direct contributions to standards </li></ul><ul><li>Build a collaborative framework for participation to test-bed activities from within and external to EU </li></ul><ul><li>Questionnaire to collect information about NRENs that would want to deploy GMPLS &amp; G2MPLS protocol and NRPS systems in their networks and inform about Phosphorus directions of work. </li></ul><ul><li>We want to provide solutions which will expect by our community and could be deployed in short time as new offered service </li></ul><ul><li>http://www.ist-phosphorus.eu/documents.php </li></ul><ul><li>( http://www.ist-phosphorus.eu/files/press/phosphorus-questionnaire.doc ) </li></ul>
    • 19. <ul><li>UCLPv2: Applying the Web 2.0 phil osophy to the networking revolution </li></ul>
    • 20. Web 2.0: <ul><li>Provides tools and applications to empower user participation, content creation and sharing over the web. </li></ul>
    • 21. UCLP v2 (I) <ul><li>Provides tools to allow users to participate in the process of creating and setting up their own virtual/logical networking infrastructure </li></ul><ul><li>Virtual networking infrastructure made up of physical resources (partitions of physical nodes, physical links, sensors, instruments, …) provided by different physical administrators </li></ul><ul><li>Users can use this virtual infrastructure for their own needs and/or exchange/acquire/sell part of this infrastructure to other users </li></ul><ul><li>P rovides a network virtualization framework upon which communities of users can build their own services or applications </li></ul>
    • 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 <ul><li>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) </li></ul><ul><li>SOA is about creating modular, secure and reusable services that can be used to build other services and applications </li></ul><ul><li>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 </li></ul><ul><ul><li>Web 2.0 = The Web as a Platform </li></ul></ul><ul><ul><li>UCLPv2 = The Network as a Platform </li></ul></ul>
    • 24. A new Media eInfrastructure
    • 25. <ul><li>Internet is increasingly a media network, but limitations of current network media technology </li></ul><ul><li>The need for a Media eInfrastructure for Future Research on Visualization and Media </li></ul>Networking: 3/4G, Lambda Networking, GN2.. Digital repositories Media: HD/3D/Visualization Computing: SuperComputing/GRIDS, DEISA A new Media and Visualization layer to offer experimental media services, that integrates the new digital interfaces European eInfrastructures (2013) <ul><li>An environment to enable users to set up the media-network infrastructure under requests when needed </li></ul><ul><li>Collaboration between: </li></ul><ul><ul><li>Network engineering research community </li></ul></ul><ul><ul><li>Media content research community </li></ul></ul><ul><li>These Media eInfrastructure should provide: </li></ul><ul><ul><li>capacity detection: in order to distinguish between users (network and resources) </li></ul></ul><ul><ul><li>Transcodification: depending on the capacities the content should dynamically adapt, by means of different codifications schemes </li></ul></ul><ul><ul><li>Security, integrity and confidentiality </li></ul></ul><ul><ul><li>Balancing/distribution/ load clustering </li></ul></ul><ul><ul><li>Content Storage capacity </li></ul></ul><ul><ul><li>Detection, publish and new contents service </li></ul></ul>
    • 26. <ul><li>THANK YOU </li></ul>Sergi Figuerola [email_address]

    ×