Automated GOLEs and Fenius -

0K - views

Automated GOLEs and Fenius

: Pragmatic interoperability. Winter Joint Techs 2011. Clemson, SC. Evangelos Chaniotakis, ESnet Network Engineer . Lawrence Berkeley National Lab. Introductions. GLIF: Global Lambda Integrated Facility.

Embed :
Download Link

Download - The PPT/PDF document "Automated GOLEs and Fenius" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.

Automated GOLEs and Fenius






Presentation on theme: "Automated GOLEs and Fenius"— Presentation transcript:

Slide1

Automated GOLEs and Fenius: Pragmatic interoperability

Winter Joint Techs 2011Clemson, SC

Evangelos Chaniotakis, ESnet Network Engineer

Lawrence Berkeley National Lab

Slide2

Introductions

GLIF: Global Lambda Integrated FacilityMany participants: NRENs

, exchanges, sites, companies

GOLE

: GLIF Open

Lightpath

Exchange

Many GLIF participants operate a GOLE

Automated GOLE Task Force

Founded in 2010 with the objective of automating

lightpath

provisioning across multiple

GOLEs

Current chair: Jerry

Sobieski

Close collaboration with GNI API Task Force, OGF NSI, NML

GNI API Task Force:

Founded in 2008

with the objective of developing a common API between circuit provisioning services

Chair: Evangelos Chaniotakis

Slide3

GLIF map

Slide4

Motivation

The research community has a global, well connected “network of networks”

Many networks provide some circuit-oriented service,

And, it

is becoming increasingly common for these circuits to be

“stitched”

across multiple networks,

SC09: ~20 L2 circuits. SC10: ~

50, SC11: ?

Stitching these “by hand” is

s

l

o

w

– and

cuasesss

errors.

Software does exist to automate circuit provisioning....

But it generally doesn’t work when stitching,

Because we don’t have a common provisioning

toolkit

Slide5

Fenius

A simple common provisioning

API and toolkit

+

Just good enough to support common stitching case today,

+

Software that implements it,

+

That works with existing provisioning software,

+

Motivation for network operators to deploy & operate,

=

(the potential for)

Global

Interoperability

Slide6

Automating the GOLEs

Several GOLEs committed network and human resources for a one-year test drive of automation,

The

Fenius

software

project by GNI

API Task

Force was decided be used as a thin interoperability layer.

Fenius

instances were deployed to Automated GOLE sites

The various

NRMs

were configured

to work with

Fenius

,

Topology

information

was collected,

PerfSONAR

PingER

nodes are deployed to test the data plane

Weekly calls to keep the project alive & kicking

Slide7

Automated GOLE Deployment

Asia:JGN2+, AIST, KDDIUSA: ESnet SDN, Internet2 ION & MANLAN,

StarLight

,

USLHCnet

, Caltech

Europe:

Netherlight

,

CERNLight

, University of Amsterdam,

NorthernLight

, PSNC,

CERNLight

,

Slide8

Global Deployment

Slide9

PingER Demonstration

JGN2+

PingER

KDDI

PingER

UvA

PingER

PSNC

PingER

JGN2+

KDDI

StarLight

,

USLHCnet

,

Internet2

ION,

NetherLight

,

PSNC

Slide10

Demonstration control plane

JGN2+

PingER

KDDI

PingER

UvA

PingER

PSNC

PingER

JGN2+

IDC

KDDI

G-Lambda

StarLight

Argia

,

USLHCnet

IDC,

Internet2

ION IDC,

NetherLight

DRAC,

PSNC,

Fenius

SuperAgent

Slide11

Demonstration

Slide12

Fenius Components

Common provisioning API over web services,Translation framework for Java (optional)Translators for IDC, G-lambda, Harmony, dynamicKL

Native implementation in

OpenDRAC

,

Scriptable command-line client

Web UI “

Superagent

” with topology and

pathfinding

Monitoring and visualization (in progress)

Slide13

Translation Framework

Common

Web UI

Client

G-lambda

Common API

G-lambda

Translator

IDC

Common API

IDC

Translator

Common

Command-Line

Client

Common

Monitoring

Client

DRAC

Common

API

Slide14

Challenges and lessons learned

Be enthusiastic and believe in your projectGetting collaborators interested

can be difficult

Get

buy

-

in from their management

Resources

can be

unreliable

Get

buy

-

in

from their

management (and yours)

Remember to account for differences in time zones, language, culture

Once project gains momentum, keep the ball rolling

Keep away from politics

Make sure everyone has a chance to contribute

You will need to work long hours

Slide15

Future directionsDeploy in more networks,

Implement missing features,Extend API and toolkit (keeping it simple!),Gain support from more network management software,

Harden software & make it operational,

Improve user interface

Better documentation

Take over the world

! :)

Slide16

Special Thanks

Frank BlankmanScott CampbellJoan Garcia

Espin

John Graham

Jeroen

van

der

Ham

Takatoshi

Ikeda

Nils Jacobson

Gigi

Karmous

-Edwards

Tomohiro

Kudoh

Kavitha

Kumar

Ali Lahlou

Andrew LakeTom LehmanMathieu LemayJohn MacAuleyGerben van Malenstein

Edoardo MartelliTakahiro MiyamotoAzher MughalFumihiro Okazaki

Jan RadilJordi Ferrer RieraSandor Rosza

Ryousei TakanoThomas

TamJin TanakaAlan

VerloJohn VollbrechtFred WanXi Yang