Title: PlanetLab Inspiration and Partner for ENGINE
1PlanetLab Inspiration and Partner for
ENGINE Jirí Navrátil jiri_at_cesnet.cz
2Talk overview
- First set of questions
- What is the relation ENGINE and PlanetLab
- Convergence of ENGINE and NREN infrastructure
- Second set of questions
- How to understand ENGINE a new sort of testbed
3GENI starting in the US and Europe
4My impression of it and first set of questions
- Too general picture to understand it
- What is main difference ENGINE and the other
testbeds ? - Who are the main users and main purpose of
ENGINE ? - if computer scientists, they are sitting in the
University campuses - How to connect them into the ENGINE ?
- If new Network applications
- Who are its users, who provide the servers ?
- Why the principles used in PlanetLab are the key
points for GENI ?
5(No Transcript)
6PlanetLab main goals
- PlanetLab is concorcium of the Universities and
academic institutions established in 2002 by 3 US
universities (UC Berkeley, UofWashington, and
Princeton University) with the goals which can be
shortly described in three main points - to provide infrastructure for planetary scale
experiments with networking services - to provide platform for new novel services with
real users - to catalyze the evolution of the Internet to new
service-oriented architecture
7(No Transcript)
8App - B
App - A
App - D
App - C
9Services/Applications and Node/Slice in Virtual
Lab
N1
N3
N8
N7
N2
N4
N9
N6
N5
Node
App1
On each node can run more users (slices) Each of
them is running in own virtual system One user
can run more applications
SLICE
App2
App3
10The layers have own addresses for objects, own
routing
71721e
Not only PlanetLab but also other applications
as Skype, Napster, GNet,
11From David Alderson CALTECH , NSF Find meeting,
Dec. 2005
12PASTRY (DHT)
How to address objects
function Lookup (key)
pdata personsjoe
value
key
index
224 -1 16 mil. objects
RNode
0
d471f1
Local Range ..67c5 to ..71f1 Not forwarding !
RNode
key
c2d0
d467c4
d46a1c
d462ba
Range of local keys (c2d1 32aaff)
d4213f
RNode
Hash Table
32ab00
Forwarding to d4xxxx
Lookup (d46a1c)
keydabcf2 ip address key
d13da3
Forwarding to dxxxxx
ip
key
index
RNode
RNode
1
1faab1
148.33.244.1
2
from RN with KEY 65a1fc
65a1fc
128.128.22.11
121
dabcf0
990
dabcf1
In Pastry max keyffff ffff ffff ffff
991
dabcf2
992
13SOA Service-Oriented Architecture
Application L a y e r INFRASTRUCTURE
c
b
a
App. Layer
B
C
A
IP layer (path capacity)
14SOA Service-Oriented Architecture
Application L a y e r INFRASTRUCTURE
AS
c
b
Layer 3
a
Reality is determined by BGP
AS 112
AS 333
AS 332
B
C
A
AS 111
a1e0fe
IP layer
AS 6732
15AS
What is better (for me) ?
B
IP layer
Rx
A
Router with different routing strategy for
different applications
or several virtual routers in one HW
CRS-1 or GPBS or ?
16From GENI backbone working group
17AS
Rx
Rx
Rx
Rx
Rx
Rx
IP layer
Rx
Rx
Routers with different routing strategy for
different applications everywhere in backbone!
18Convergence of ENGINE and PlaneLab
19ENGINE Potential PoPs and Links
UK
DK
PL
DE
FR
CZ
ES
CH
20ENGINE (two sides of testbed)
ENGINE scientific
Network engineering
21The ENGINE and NREN integration(connections,
VLAN, users, etc.)
GN2
UNI-1
u3
u4
NREN
PL
ENGINE testbed
w1
direct
vlan
u1
u2
VR
DE
CESNET backbone
NREN
CZ
CH
UNI-2
via workstation
w3
NREN
w2
u5
u6
Users resources Green part of ENGINE testbed
workstations
Users machines
22ENGINE users(connections, VLAN, etc.)
u4
ENGINE testbed
PL
u1
u2
u1, u2, w3 directly on ENGINE-VLAN u4,u5 via w3
DE
VR
CZ
CH
w3
u5
Users resources NREN infrastructure Virtual
part of ENGINE testbed
workstations
Users machines
23ENGINE virtual environment(connections, VLAN,
vAS, IPaddresses, etc.)
u4
client peer
u1
VR
u2
client peer
u1, u2, w3 directly on ENGINE-VLAN u4,u5 via w3
NREN-CZ
VR
VR
CZ
w3
with special service
u5
virtual address space
24ENGINE users and applications
Cheap and flexible infrastructure for many
scientific users and different network
applications
u44
u43
NREN
PL
u1
VR
u11
u2
u3
NREN
DE
VR
Ingres WS1
u4
VR
u5
VR
CZ
u22
u6
Ingres WS2
CH
u7
u21
NREN
Ingres WS3
GN2
Ingres WS4
u35
u1, u2 .u21,u22
directly on ENGINE-VLAN Ingres WS
connection via u4,u6,u7,
LAN or internet
u33
u34
25 ENGINE users and applications
Cheap and flexible infrastructure for many
scientific users and wide spectrum of network
applications
u44
u43
NREN
PL
u1
VR
u11
u2
u3
NREN
DE
VR
Ingres WS1
u4
VR
u5
VR
CZ
u22
u6
Ingres WS2
CH
u7
u21
NREN
Ingres WS3
GN2
Ingres WS4
u35
u1, u2 .u21,u22
directly on ENGINE-VLAN Ingres WS
connection via u4,u6,u7,
LAN or internet
u33
u34
26What type of users and applications can utilize
this architecture ?
- NREN itself ?
- YES for Network engineering
- ordinary Internet users ? Why ?
- Researchers and research teams ?
- Yes but who is ready ? (HW, SW, people)
- Modern network applications
- Yes, they are ready in PlanetLab !
27PlanetLab in frame of GREN (Global Research and
Educational Networks)
28Existing tools and network applications can be
re-implemented or extended into new architecture !
- Peer-to-Peer Systems (DHT Distributed Hash Table)
- CAN, Chord, Pastry, Tapestry (building
routing tables adaptively, automatic
reconfiguring, using effective algorithms) - Systems using effectively whole available
infrastructure - CDN Content Distributed Network
- Replication and other systems based on
Behive principles with O(1) lookup, Load peak
multiplexing
29(No Transcript)
30(No Transcript)
31http//coblitz.codeen.org3125/http//ephyra.cvut.
cz/links/tmp/FLOWS/CVUT/RAW/rawflow.02-15-2006.5
32In internet all peers are connected (logical
full mesh)
Can users utilize all infrastructure effectively?
33BitTorrent
Seed node
Seed node distribute file into all other nodes in
the network with active engage of all nodes and
segments
34(No Transcript)
35ENGINE (NE - second side of testbed)
ENGINE scientific
Network engineering
36Customer network on demand
(Heavy Commercial solution)
37Simple virtual solution
Fully meshed backbone with service shared virtual
or optical l paths Simple routing Load
balancing Fast level of resilience Easy Plug-in
Similar to the idea in the project Millions
Node access Network
H. Zhang et all in http//100x100network.org
38From GENI backbone working group,
39Thank You for your attention
40Questions ?