StarPlaneCees de Laat

SURFnetEU

NWOUniversity of Amsterdam

SARATI

TNONCFNCF

CommonPhotonic

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

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 grating

input and output fibres

collimating

lens

MEMS mirror array

(1 pixel per channel)

!1

!n

port 1common

ref Eric Bernier, NORTEL

StarPlane GoalsGoals in the proposed StarPlane project:1. fast, application-specific allocation of thenetwork resources with deterministiccharacteristics;2. application-specific composition of the protocolstack that is used to control the resources;3. low-level resource partitioning (and, hence, nointerference);4. high-level requests (whereby policies andinference are used to assist the user)..

StarPlaneDWDMbackplane

R

CPU’s

R

CPU’sR

CPU’s

CPU’

s

R

CPU’s

R

NOC

CdL

CPU’s

switch

university SURFnet

WS+AAANOCWS+AAA

SURFnet

32 compute nodes

Fast interconnectLocal interconnect

10 Gbit/sEthernet lanphy

1 Gbit/sEthernet

To SURFnet

head node

To localUniversity

DAS Cluster

Hoogwaardig internet voor hoger onderwijs en onderzoek

Day 2 set-up: branching out…

Delft

Amsterdam 1Amsterdam 2

Amsterdam 3

G5 G5

G5 G5

WSS <-

split

select

select

split

WSS ->

WSS <-

WSS ->

s e lec t

spli t

WSS

->

WSS

<-

WSS <-

split

select

select

split

WSS ->

WSS <-

WSS ->

s el ect

spl i t

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 atAmsterdam sites

• Is NOT supported inMarch 2006

• Full reconfigurabilityachieved

• Only limits are– Presence of card– Wavelength

blocking

• No changes to basic‘static’ mesh

“branch” insteadof “spur”

Adding WSSesincreasesreconfigurability

Hoogwaardig internet voor hoger onderwijs en onderzoek

Day 2 detail

Delft

Leiden

Amsterdam 1

WSS <-

split

select

select

split

WSS ->

WSS <-

WSS ->

select

spl it

WS

S ->

WS

S <

-

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

se lect

s pl it

WS

S ->

WS

S <

-

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-V71 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

• Wavelengthassignment remains– no externalchanges

• Adding WSSes allowsredirectingwavelengths from/toVU and AMS

Hoogwaardig internet voor hoger onderwijs en onderzoek

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 today 1 now fourinstead of onepossibleredirection

• Redirectiononly limited bypresence ofcards andinternalwavelengthblocking

Hoogwaardig internet voor hoger onderwijs en onderzoek

Day 2 – increased reconfigurability -adding cards

• Adding two cardsallows to createmore connectivitybetween ALLsites!

• Some sites canconnectivitythreefold (from10 Gb/s to 30Gb/s)

Amsterdam 1

Delft Leiden

Amsterdam VU

1

8

5

3

2

4

7 1

6

Hilversum

1

8

4

7 1

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

GRID-Colocation problem space

CPU DATA

Lambda’s

Extensivelyunderresearch

New!

Key issue #1:how to describe such networks?

Semantic web

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

The Resource Description Framework (RDF) uses XML asan 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>

NetherLight in RDF<?xml version="1.0" encoding="UTF-8"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

xmlns:ndl="http://www.science.uva.nl/research/air/ndl#"><!-- Description of Netherlight --><ndl:Location rdf:about="#Netherlight">

<ndl:name>Netherlight Optical Exchange</ndl:name></ndl:Location><!-- TDM3.amsterdam1.netherlight.net --><ndl:Device rdf:about="#tdm3.amsterdam1.netherlight.net">

<ndl:name>tdm3.amsterdam1.netherlight.net</ndl:name><ndl:locatedAt rdf:resource="#amsterdam1.netherlight.net"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/1"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/3"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/4"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:503/1"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:503/2"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:503/3"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:503/4"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:504/1"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:504/2"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:504/3"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:504/4"/><ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/2"/>

<!-- all the interfaces of TDM3.amsterdam1.netherlight.net -->

<ndl:Interface rdf:about="#tdm3.amsterdam1.netherlight.net:501/1"><ndl:name>tdm3.amsterdam1.netherlight.net:POS501/1</ndl:name><ndl:connectedTo rdf:resource="#tdm4.amsterdam1.netherlight.net:5/1"/>

</ndl:Interface><ndl:Interface rdf:about="#tdm3.amsterdam1.netherlight.net:501/2">

<ndl:name>tdm3.amsterdam1.netherlight.net:POS501/2</ndl:name><ndl:connectedTo rdf:resource="#tdm1.amsterdam1.netherlight.net:12/1"/>

</ndl:Interface>

RDF ->Picture

Key issue #2:How to book resources on such

networks?

Web services

Web services interfaces provide the API for thereservation 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">

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 !!!!