StarPlane & LightHouse

QuickTime™ and aTIFF (LZW) decompressor

are needed to see this picture.

StarPlane & LightHouse

Cees de Laatwww.science.uva.nl/~delaat

SURFnetEU

University of AmsterdamSARA

TITNO

NCFNCF

QuickTime™ and aTIFF (Uncompressed) decompressorare needed to see this picture.

http://www.science.uva.nl/~delaat






UvA/SARA LightHouseA joint network research lab of the University of Amsterdam and SARA.

Connects end resources to NetherLight.Proof of concept e.g. tier 0/1, webservices, GSP




Optical Exchange as Black Box

Optical ExchangeSwitchTDMStore &ForwardDWDM mux/demux

Optical CrossConnect

TeraByteEmail

Service

Ref: gridnets paper by Freek Dijkstra, Cees de Laat



LIGHTHOUSE




Key issue #1:how to describe such networks?

Semantic web

“a universal medium for the exchange of data where data can be shared and processed by automated tools as well as by people”

The Resource Description Framework (RDF) uses XML as an interchange syntax.

Data is described by triplets:

ObjectSubject Predicate

NDL - Network Description Language

A way to describe network resources using RDF.

Parser can use the data to:- generate network maps- provide information to schedulers

<ndl:Device rdf:about="#Vangogh3"> <ndl:name>Vangogh3</ndl:name> <rb:isOfType>ComputingElement</rb:isOfType> <ndl:locatedAt rdf:resource="#Lighthouse"/> <ndl:hasInterface rdf:resource="#Vangogh3:eth2"/></ndl:Device>



QuickTime™ and aTIFF (Uncompressed) decompressor


QuickTime™ and aTIFF (Uncompressed) decompressorare needed to see this picture.RDF -> pict

Key issue #2:How to book resources on such

networks?

Web services

Web services interfaces provide the API for the reservation framework:

<wsdl:operation name="getResourceInformation"> <wsdl:operation name="getResourceList"> <wsdl:operation name="getTypeList"> <wsdl:operation name="getResourcesOfType"> <wsdl:operation name="reservePath"> <wsdl:operation name="getPossiblePaths"> <wsdl:operation name="isPathAvailable"> <wsdl:operation name="confirmPathReservation"> <wsdl:operation name="cancelPathReservation">





StarPlaneDWDMbackplane

R

CP

U’s

R

CPU’sR

CPU’s

CP

U’s

R

CPU’s

R

NOC

CdL

CPU’s

MEMS

Client SURFnet

WS+AAANOC

WS+AAA



Common Photonic

Layer (CPL) in

SURFnet6

~5000 km

Dordrecht1

Breda1

Tilburg1

DenHaag

NLR

BT

BT NLR

BT

Zutphen1

Lelystad1

Subnetwork 4:Blue Azur

Subnetwork 3:Red

Subnetwork 1:Green

Subnetwork 2:Dark blue

Subnetwork 5:Grey

Emmeloord

Zwolle1

Venlo1

Enschede1

Groningen1

LeeuwardenHarlingen

Den Helder

Alkmaar1

Haarlem1

Leiden1

Assen1

Beilen1

Meppel1

Emmen1

Arnhem

Apeldoorn1

Bergen-op-ZoomZierikzee

Middelburg

Vlissingen Krabbendijke

Breukelen1

Ede

Heerlen2Geleen1

DLO

Schiphol-Rijk

Wageningen1 Nijmegen1

Hilversum1

Hoogeveen1

Lelystad2

Amsterdam1

Dwingeloo1

Amsterdam2

Den Bosch1

Utrecht1

Beilen1

Nieuwegein1Rotterdam1

Delft1

Heerlen1

Heerlen1

Maastricht1

Eindhoven1

Maasbracht1

Rotterdam4

3XLSOP

IBG1 & IBG2Middenmeer1

Hoogwaardig internet voor hoger onderwijs en onderzoek

Day 2 set-up: branching out…

Delft

Amsterdam1Amsterdam2

Amsterdam3

G5 G5

G5 G5

WSS <-

split

select

select

split

WSS ->

WSS <-

WSS ->

select

split

WSS ->

WSS <-

WSS <-

split

select

select

split

WSS ->

WSS <-

WSS ->

select

split

WSS ->

WSS <-

G3

Delft

G5G3

G3G3

GMD

GMD

G5

Utrecht

G1

Delft

G1

G1G1

GMD

GMD

G9

G9

G9

G9

GMD

GMD

Hilversum

G6

Delft

G6

G6

G6

GMD

GMD

G5

G5

Leiden

G4

G4

G4

G4

GMD

GMD

Den Haag

• Add WSSes at Amsterdam sites

• Is NOT supported in March 2006

• Full reconfigurability achieved

• Only limits are– Presence of card – Wavelength

blocking

• No changes to basic ‘static’ mesh

“branch” instead of “spur”

Adding WSSes increases reconfigurability


Day 2 detail

Delft

Leiden

Amsterdam1

WSS <-

split

select

select

split

WSS ->

WSS <-

WSS ->

select

split

WSS ->

WSS <-

Does this require CMDs

on all internal patches ??

A-D1, A -L2,

A -L3, A -V5, A -V6, A -D8

Amsterdam 2

Amsterdam 3 - VU

WSS <-

split

select

select

split

WSS ->

WSS <-

WSS ->

TO DELFT

G5

G5

G5

G5

G5

G5

select

split

WSS ->

WSS <-

Does this require CMDs on all internal patches ??

L-V1, L-A2, L-A3, L-D4

L-V1, L-A2,

L-A3, L-D4

L-V1, A -V5, A -V6, D-V7

V-L1, V-A5,

V-A6, VD 7

V-L1, A-L2, A -L3, D-L4

L-A2, L-A3, L-D4, V -A5,

V-A6, V-D7

V-L1, V-A5, V-A6, VD7

L-V1, L-A2, L-A3, L-D4

D-A1, D-L4,

D-V7, D-A8

A-L2, A -L3, D-L4, A-V5,

A-V6, D-V7

A-L2, A -L3, D-L4, A -V5, A-V6, D-V7

1 2 3 4 5 6 7 8

1 2 3 4 5 6 7 8

1 2 3 4 5 6 7 8

1 2 3 4 5 6 7 8

L-A2, L-A3, L-D4,

V-A5, V -A6, V -D7

G5 G5

A-D1, L-D4, V-D7, A-D8

L-A2, L-A3, L-D4, V -A5,

V-A6, V-D7

A-D1, A-L2, A -L3, A-D4,

A -V5, A -V6,

A-D1, A -L2, A -L3, A -V5,

A -V6,A -D8

D-A1, D-L4,

D-V7, D-A8

D-A1, L-A2,

L-A3, V-A5, V-A6, D-A8

• Wavelength assignment remains – no external changes

• Adding WSSes allows redirecting wavelengths from/to VU and AMS


Day 2 – black box reconfigurability

Amsterdam 1

Delft Leiden

Amsterdam VU

1

8

5

3

2

4

7 1

6

Hilversum

1

8

4

7

2

3

4

1

1657

581 6 3 2

AMS_VU + 1AMS-LE + 1AMS_DE + 0VU-LE + 0VU-DE + 1LE-DE + 1

DAS-3 Switch

DAS-3 Switch

DAS-3 Switch

DAS-3 Switch

DAS-3 Switch

• Compared to day 1 now four instead of one possible redirection

• Redirection only limited by presence of cards and internal wavelength blocking


Day 2 – increased reconfigurability - adding cards

• Adding two cards allows to create more connectivity between ALL sites!

• Some sites can connectivity threefold (from 10 Gb/s to 30 Gb/s)

Amsterdam 1

Delft Leiden

Amsterdam VU

1

8

5

3

2

4

7 1

6

Hilversum

1

8

4

71

2

3

4

1

1657

581 6 3 2

4

4

4

4

44

1

1

1

AMS_VU + 2AMS-LE + 2AMS_DE + 1VU-LE + 1VU-DE + 2LE-DE + 1

Module Operation

> this schematic shows• several input fibres and one output fibre• light is focused and diffracted such that each

channel lands on a different MEMS mirror• the MEMS mirror is electronically controlled to tilt

the reflecting surface• the angle of tilt directs the light to the correct port

> in this example:• channel 1 is coming in on port 1 (shown in red)• when it hits the MEMS mirror the mirror is tilted to

direct this channel from port 1 to the common• only port 1 satisfies this angle, therefore all other

ports are blocked

diffraction gratinginput and output fibres

collimatinglens

MEMS mirror array(1 pixel per channel)

λ1 λn

port 1common

ref Eric Bernier, NORTEL

32 compute nodes

Fast interconnectLocal interconnect

10 Gbit/s Ethernet lanphy

1 Gbit/s Ethernet

To SURFnet

head node

To localUniversity

StarPlane Goals

Goals in the proposed StarPlane project:

1. fast, application-specific allocation of the network resources with deterministic characteristics;

2. application-specific composition of the protocol stack that is used to control the resources;

3. low-level resource partitioning (and, hence, no interference);

4. high-level requests (whereby policies and inference are used to assist the user)..



GRID-Colocation problem space

CPU DATA

Lambda’s

Extensively under research

New!





Business as usual :-)



Questions ?

Credits:– Leon Gommans, Paola Grosso, Bas Oudenaarde, Arie Taal, Freek Dijkstra, Bert Andree, Jeroen van der Ham, Hans

Blom, Yuri Demchenko, Fred Wan, Karst Koymans, Martijn Steenbakkers Jaap van Ginkel– SURFnet / GigaPort, Kees Neggers, Erik-Jan Bos, et al!– NORTEL: Franco Travostino, Kim Roberts, Rod Wilson– SARA: Anwar Osseryan, Paul Wielinga, Pieter de Boer, Ronald van der Pol, teams– Joe Mambretti, Bill stArnaud, GLIF community– Tom & Maxine & Larry, Laurin, OptIPuter, OnVector team !!!!

QuickTime™ and aTIFF (Uncompressed) decompressorare needed to see this picture.QuickTime™ and a

TIFF (Uncompressed) decompressorare needed to see this picture.

Documents

StarPlane & LightHouse