GENI Research Plan Requirement for GENI 2007.09.21 Yeongjae Yu [email_address]
Table of Contents <ul><li>1. Requirement for GENI </li></ul><ul><li>1.1 Multiple Simultaneous Experiments </li></ul><ul><l...
<ul><li>1. Requirement for GENI </li></ul>
1.1  Multiple Simultaneous Experiments <ul><li>The concept behind GENI </li></ul><ul><li>- It can be used to multiple idea...
1.2  Generality <ul><li>We want to build an experimental platform that can support </li></ul><ul><li>a wide range of futur...
1.3  Support for Real Applications <ul><li>GENI should be able to support not just a  future network , </li></ul><ul><li>b...
1.4  Support for Real Users <ul><li>If we are to gain real experience with real applications, we </li></ul><ul><li>must al...
1.5  Fidelity <ul><li>Reach </li></ul><ul><li>- As wide a reach as possible </li></ul><ul><li>Topology </li></ul><ul><li>-...
1.6  Support for All Aspects of a New Network Architecture <ul><li>Support for management </li></ul><ul><li>- It must impo...
1.7  Support for Experimenters <ul><li>Ease of Use </li></ul><ul><li>- GENI must remove as many practical barriers as poss...
1.8  Federation & Sustainability <ul><li>GENI must be designed for a 15-20 year lifetime </li></ul><ul><li>To ensure the s...
1.9  Striking a Balance <ul><li>What makes GENI a unique and compelling instrument is </li></ul><ul><li>how it balances re...
<ul><li>2. Relate Work </li></ul>
2.1  PlanetLab & VINI <ul><li>PlanetLab </li></ul><ul><li>- PlanetLab is a global overlay network for developing and acces...
2.2  UCLP & APN <ul><li>User Controlled LightPath (UCLPv2) </li></ul><ul><li>- UCLP is a network virtualization management...
2.3  Relation among PlanetLab, VINI and UCLP <Current Relation> <Target Relation>
Upcoming SlideShare
Loading in …5
×

Chapter 5.1 Functional requirements

431
-1

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
431
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • * 5.1.5 discusses the specific requirements to support the anticipated range of application-level experiments. * One important aspect of fidelity is that the topology, physical scale and connectivity should mimic world.
  • * resources 로 links, switches, routers, ...
  • (1) PlanetLab 에서 되는 것 : End-node(PC Server) 에 대한 Virtualization (CPU, Memory, Hard Disk, NIC) (2) PL-VINI 도 되고 , UCLP 도 되는 것 : Network Virtualization (3) PL-VINI 는 되는데 , UCLP 는 안 되는 것 : Software Router 에서 1) 가상의 NIC 지원 2) Click 과 XORP 에 의한 일정 수준 Programmability 제공 3) Network Events Injection 기능 (4) UCLP 에서는 되고 , PL-VINI 에서는 안 되는 것 : Bandwidth Allocation (5) UCLP 에서는 안되고 , GENI 에서는 되는 것 : non-IP, mobility, ... * VR 에서 user 가 routing protocols, peering 등에 대해 configure 할 수 있도록
  • Chapter 5.1 Functional requirements

    1. 1. GENI Research Plan Requirement for GENI 2007.09.21 Yeongjae Yu [email_address]
    2. 2. Table of Contents <ul><li>1. Requirement for GENI </li></ul><ul><li>1.1 Multiple Simultaneous Experiments </li></ul><ul><li>1.2 Generality </li></ul><ul><li>1.3 Support for Real Applications </li></ul><ul><li>1.4 Support for Real Users </li></ul><ul><li>1.5 Fidelity </li></ul><ul><li>1.6 Support for All Aspects of a New Network Architecture </li></ul><ul><li>1.7 Support for Experimenters </li></ul><ul><li>1.8 Federation & Sustainability </li></ul><ul><li>1.9 Striking a Balance </li></ul><ul><li>2. Related Work </li></ul><ul><li>2.1 PlanetLab & Virtual Network Infrastructure </li></ul><ul><li>2.2 User Controlled LightPath & Articulated Private Network </li></ul><ul><li>2.3 Relation among PlanetLab, VINI and UCLP </li></ul>
    3. 3. <ul><li>1. Requirement for GENI </li></ul>
    4. 4. 1.1 Multiple Simultaneous Experiments <ul><li>The concept behind GENI </li></ul><ul><li>- It can be used to multiple ideas and concepts </li></ul><ul><li>To support multiple experiments simultaneously </li></ul><ul><li>=> The concept of slices </li></ul><ul><li>- The resources of GENI can be divided up among many different researchers in </li></ul><ul><li>such a way that each can run his own experiment </li></ul><ul><li>Virtualization </li></ul><ul><li>- One approach to slices </li></ul><ul><li>- A processor, a fiber link, wireless system, ... </li></ul><ul><li>Controlled Isolation </li></ul><ul><li>- GENI must provide strong containment for experiments </li></ul><ul><li>- GENI must support controlled interconnection of slices to each other and to the </li></ul><ul><li>current Internet </li></ul>
    5. 5. 1.2 Generality <ul><li>We want to build an experimental platform that can support </li></ul><ul><li>a wide range of future Internets </li></ul><ul><li>How much generality is required to support the anticipated </li></ul><ul><li>experiments? </li></ul><ul><li>- To experiment with packet formats that materially differ from those of the </li></ul><ul><li>Internet </li></ul><ul><li>- To move beyond the paradigm of packet switching and explore other modes for </li></ul><ul><li>sharing and resource allocation </li></ul><ul><li>- To exploit specific features of the different technologies included in GENI </li></ul><ul><li>- To experiment with architectures that include network-level operations other </li></ul><ul><li>than simple packet forwarding </li></ul><ul><li>Diversity of technology </li></ul><ul><li>Balancing generality with cost </li></ul>
    6. 6. 1.3 Support for Real Applications <ul><li>GENI should be able to support not just a future network , </li></ul><ul><li>but also the applications that might run on that network </li></ul><ul><li>To attract real applications, the GENI must include facilities </li></ul><ul><li>for development and deployment of applications , not just </li></ul><ul><li>data transport </li></ul>
    7. 7. 1.4 Support for Real Users <ul><li>If we are to gain real experience with real applications, we </li></ul><ul><li>must allow real users to try them out, and make real use of </li></ul><ul><li>them </li></ul><ul><li>What does it mean to support real users? </li></ul><ul><li>- The GENI facility must reach “to the edge” of the network, where the users </li></ul><ul><li>connect </li></ul><ul><li>- There must be a rich connectivity between GENI and the Internet of today </li></ul><ul><li>- There must be an adequate pool of potential users that have end-node </li></ul><ul><li>computers directly connected to, and a part of, the GENI infrastructure </li></ul><ul><li>- Some support for slices needs to be provided for the end-nodes that are </li></ul><ul><li>attached to GENI </li></ul>
    8. 8. 1.5 Fidelity <ul><li>Reach </li></ul><ul><li>- As wide a reach as possible </li></ul><ul><li>Topology </li></ul><ul><li>- Keeping delays within a small factor of physical distance </li></ul><ul><li>- Path diversity </li></ul><ul><li>- Underlying fiber paths </li></ul><ul><li>- Major interconnection points (exchange points, aggregation points) </li></ul><ul><li>Realism of virtualization </li></ul><ul><li>Physical distribution </li></ul><ul><li>Scale </li></ul><ul><li>Failure modes </li></ul><ul><li>- Intentionally induced failure, unanticipated failure </li></ul>
    9. 9. 1.6 Support for All Aspects of a New Network Architecture <ul><li>Support for management </li></ul><ul><li>- It must important that the management aspects of all devices be fully virtualized </li></ul><ul><li>- We can have the equivalent of “virtual system operators” </li></ul><ul><li>Support for security </li></ul><ul><li>- The GENI infrastructure itself must be stable and secure </li></ul><ul><li>- The mechanisms for isolation among slices must be very robust </li></ul><ul><li>- There may be a requirement for specialized security technology </li></ul><ul><li>Support for anticipated future capabilities </li></ul><ul><li>- In 10 years, there may be features that will be commonplace then, but are not </li></ul><ul><li>yet realized in any effective way </li></ul>
    10. 10. 1.7 Support for Experimenters <ul><li>Ease of Use </li></ul><ul><li>- GENI must remove as many practical barriers as possible to researchers being </li></ul><ul><li>able to make full use of the facility </li></ul><ul><li>Observability </li></ul><ul><li>- GENI must offer strong support for measurement-based quantitative research </li></ul><ul><li>Fail-safe </li></ul><ul><li>- GENI must be secure, so that its resources cannot accidentally or maliciously </li></ul><ul><li>be used to attack today’s Internet </li></ul><ul><li>Sources of real traffic </li></ul><ul><li>- GENI must provide a way experiments can be run with real traffic </li></ul><ul><li>- One approach: to have several large-scale popular services </li></ul><ul><li>ex) content distribution networks </li></ul>
    11. 11. 1.8 Federation & Sustainability <ul><li>GENI must be designed for a 15-20 year lifetime </li></ul><ul><li>To ensure the sustainability </li></ul><ul><li>- Support for federation </li></ul><ul><li>- Design with operational costs in mind </li></ul><ul><li>Addition of new technology </li></ul><ul><li>- Open hardware interfaces </li></ul><ul><li>- The ability to virtualize devices </li></ul><ul><li>- The ability to incorporate new devices into the GENI management mechanisms </li></ul><ul><li>Living in the future </li></ul><ul><li>- GENI is supposed to be a tolerably realistic emulation of a networking </li></ul><ul><li>technology base 10 years in the future </li></ul>
    12. 12. 1.9 Striking a Balance <ul><li>What makes GENI a unique and compelling instrument is </li></ul><ul><li>how it balances requirements to support research that </li></ul><ul><li>simply cannot be done today </li></ul><ul><li>- Resolving conflicts among requirements (ex. Sliceability vs Fidelity) </li></ul><ul><li>- Recognizing the specific combination of capabilities that are unique to GENI </li></ul><ul><li>(1) wide-spread deployment </li></ul><ul><li>(2) a diverse and extensible collection of network technologies </li></ul><ul><li>(3) support for real user traffic </li></ul>
    13. 13. <ul><li>2. Relate Work </li></ul>
    14. 14. 2.1 PlanetLab & VINI <ul><li>PlanetLab </li></ul><ul><li>- PlanetLab is a global overlay network for developing and accessing broad- </li></ul><ul><li>coverage network services [Chun 03] </li></ul><ul><li>- PlanetLab allows multiple services to run concurrently and continuously, each in </li></ul><ul><li>its own slice of PlanetLab [Chun 03] </li></ul><ul><li>* Slice: A horizontal cut of global resources [Chun 03] </li></ul><ul><li>The substrate resources bound to a particular experiment [Clark 07] </li></ul><ul><li>Virtual Network Infrastructure (VINI) </li></ul><ul><li>- VINI is a virtual network infrastructure that allows network researchers to </li></ul><ul><li>evaluate their protocols and services in a realistic environment that also </li></ul><ul><li>provides a high degree of control over network conditions. </li></ul><ul><li>- PL-VINI is a prototype of a VINI that runs on the public PlanetLab. PL-VINI </li></ul><ul><li>enables arbitrary virtual networks, consisting of software routers connected by </li></ul><ul><li>tunnels, to be configured within a PlanetLab slice. </li></ul>
    15. 15. 2.2 UCLP & APN <ul><li>User Controlled LightPath (UCLPv2) </li></ul><ul><li>- UCLP is a network virtualization management tool built using web services </li></ul><ul><li>[Lemay 06] </li></ul><ul><li>ex) XC-WS(Cross Connect Web Service) for SONET, SDH and Lambda Cross </li></ul><ul><li>Connects </li></ul><ul><li>- Users can create several parallel application specific networks from a single </li></ul><ul><li>physical network through UCLP [Lemay 06] </li></ul><ul><li>Articulated Private Network (APN) </li></ul><ul><li>- A n aggregate mix of resources [St.Arnaud 07] </li></ul>
    16. 16. 2.3 Relation among PlanetLab, VINI and UCLP <Current Relation> <Target Relation>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×