Upload
colleen-morrison
View
220
Download
2
Tags:
Embed Size (px)
Citation preview
Talk 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
My 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 ?
PlanetLab 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
Services/Applications and Node/Slice in Virtual Lab
N4
N2
N3
N7N8
N1
N9
N5
N6
On each node can run more users (slices)Each of them is running in own virtual systemOne user can run more applications
App1App2App3
SLICE
Node
Not only PlanetLab but also other applications as Skype, Napster, GNet,…
The layers have own addresses for objects, own routing
App. Layer 1
a e
cfb
dg
h
App. Layer 3
[email protected] [email protected]
71721e
App. Layer 2p1
p2
p100
p111
p999
... App. Layer 9911e0fe
abe0fe
11e0fe
11e0fe
11e0fef11e00
2122fe11e0fe
c1e0fe
41e2f0
81e0fe
a1e0fe
bbe0fe
from RN with KEY: 65a1fc
key
d13da3
d462ba
d4213f
d467c4
PASTRY (DHT)function Lookup (key)
d471f1
Forwarding to dxxxxx
Forwarding to d4xxxx
Range of local keys(c2d1 – 32aaff)
d46a1c
Local Range ..67c5 to ..71f1 Not forwarding !
RNode
RNode
RNodeHash Table
key index value
$pdata= $persons{“joe”}
RNodeRNode
1
joe 88,180, $8880121
jiri 92,168, $39002
224 -1 = 16 mil. objects
Lookup (d46a1c)
82,181, $1900tom 99180,180, $8900jerry 992
1
65a1fc 128.128.22.11121
1faab1 148.33.244.12
192.161.1.12dabcf0 990192.161.1.12dabcf1 991
192.12.12.121dabcf2 992
$key=“dabcf2”$ip = $address {$key}
key index ip
In Pastry max key=ffff ffff ffff ffff
c2d0
32ab00
0
How to address objects
SOA Service-Oriented Architecture
IP layer(path capacity)
App. Layer
Application L a y e r INFRASTRUCTURE
b
B
c
a
A
C
AS
SOA Service-Oriented Architecture
IP layer
Layer 3
Reality is determined by BGP
AS 332
AS 111
AS 112 AS 333
AS 6732
a1e0fe
Application L a y e r INFRASTRUCTURE
b c
a
B
A
C
AS
Router with different routing strategyfor different applications
CRS-1 or GPBS or ?
orseveral virtual routers in one HW
Rx
IP layer
B
A
ENGINE Potential PoPs and Links
DE
UK
FR
CZ
CH
DK
ES
PL
UKERNA
CESNET
PSNC
DFN
SWITCH& CERN
NORDUnetSUnet
RedIRIS
RENATER
Cisco CRS-1 router
Open-source router40G wave10GE wave1GE link
Wave or link on GEANT2 fiber
Wave or link on cross-border fiber
Wave or link as managed service
Wave or link on country NRENs
Wave or link color codes:
NLR
The ENGINE and NREN integration(connections, VLAN, users, etc.)
DE
CH
PL
CESNETbackbone
UNI-1
UNI-2
CZ
User’s machines
workstations
Users resourcesGreen – part of ENGINE testbed
vlandirect
viaworkstation
u1 u2
u3 u4
u5
w3
w1
w2
u6
VR
GN2
ENGINEtestbed
NREN
NREN
NREN
ENGINE users(connections, VLAN, etc.)
DE
CH
PL
CZ
User’s machinesworkstations
Users resourcesNREN infrastructureVirtual part of ENGINE testbed
u5
w3
u1 u2
u4
u1, u2, w3 directly on ENGINE-VLANu4,u5 via w3
VR
ENGINEtestbed
ENGINE virtual environment(connections, VLAN, vAS, IPaddresses, etc.)
CZ
u5
w3
u1u2
u4
u1, u2, w3 directly on ENGINE-VLANu4,u5 via w3
VR
VR
User’s machines
workstations
Users resourcesGreen – part of ENGINE testbedvAS1 vAS2 vAS3
IP range IP range IP range
NREN-CZ
VR
client | peer
with special service
client | peer
ENGINE users and applications
DE
CH
PL
CZ
u5
u21
u2
u4
u1, u2 .u21,u22 directly on
ENGINE-VLANIngres WS
connection via u4,u6,u7,… LAN or internet
NREN
NREN
NREN
Ingres WS2
Ingres WS4
Ingres WS1
u6
u34
u7
u11
u22
Ingres WS3
u35
u44
u33
u43
u1
VR
VR
VR
u3
Cheap and flexible infrastructure for many scientific users and different network applications
VR
DE
CH
PL
CZ
u5
u21
u2
u4
u1, u2 .u21,u22 directly on
ENGINE-VLANIngres WS
connection via u4,u6,u7,… LAN or internet
NREN
NREN
NREN
Ingres WS2
Ingres WS4
Ingres WS1
u6
u34
u7
u11
u22
Ingres WS3
u35
u44
u33
u43
u1
VR
VR
VR
VR
PLbws
u3
PLbws
PLbws
ENGINE users and applications
Cheap and flexible infrastructure for many scientific users and wide spectrum of network applications
What 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 !
Existing 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
In internet all peers are connected (logical full mesh)
Can users utilize all infrastructure effectively?
BitTorrent
Seed node
Seed node distribute file into all other nodes in the network with active engage of all nodes and segments
Fully meshed backbonewith service shared virtual
or optical pathsSimple routingLoad balancingFast level of resilienceEasy Plug-in
Similar to the idea in the project “Millions Node access Network”
H. Zhang et all in http://100x100network.org
Simple virtual solution
ENGINE
future NGI backbone ?
NRENs