FROM NETWORK ADMINISTRATOR TO DOMAIN SCIENTIST: … · 2017. 10. 17. · from network administrator...

Preview:

Citation preview

FROMNETWORKADMINISTRATORTODOMAINSCIENTIST:CHALLENGESWITHCREATINGUSABLEHIGHSPEEDNETWORKS

S E A N D O N O VA N

R U S S C L A R K

J E R O N I M O B E Z E R R A

G E O R G I A T E C H

G E O R G I A T E C H / S O X

F I U

TWOQUESTIONS

• Movebulkdata

• Movestreamsofdata

• Connectinstrumentswithdataprocessing

• Shareresources

• Assumenothing

• Bandwidth(Mbps/Gbps),VLANs,regionalnetworks,researchnetworksmaybeaforeignconcepts

Whatdodomainscientistsneedtodo? Whatdodomainscientistsknowaboutnetworks?

USECASE:ASTRONOMERSWANTDATAFROMTELESCOPES

• Twopossibletypesofdata• Bulkdatafrompreviousnight’sviewing

• Streameddatafrominstruments

• Needtogetdatafromsourcetodestination• Bulktransfersaresimple

• Streameddatashouldusededicatedpathbetweeninstrumentandprocessingcenter

SETTINGUPANETWORKCONNECTIONASDOMAINSCIENTIST

• CalluplocalITpeople• Shuffledtotherightperson,eventually

• Localnetworkadminneedsdetails• Bulktransfers?Streamingdata?Howmuch?

Howfast?Whattimeframes?

• Localnetworkadminneedstotalktodestinationnetworkadminandnetworkprovider(s)• Tosetuppath/VLANs/everythingelse

• Halfadozenorsoemailsorphonecalls

• Daystoweekstosetupaconnection

IT ’SSETUP,RIGHT?

• UsualProcess• Setup

• Test

• Fix

• Retest

• Issues• Slowprocess– takesdays-to-weeks

• Fraughtwithissues– fatfingeringiscommon

• Toomanycooksinthekitchen

• Involvesoneortwopeoplepernetwork

HOWDOWEIMPROVETHIS?

Method:

• Automatedprovisioning

• Amethodforthedomainscientiststoaccesstheautomatedsystemtocreateownpaths

Madness:

• Multi-domainissuesabound

• Currentprocessisinplaceforanumberofreasons

WHATCOULDPOSSIBLYGOWRONG?

• Domainscientistsarenotknowledgeableofnetworkterminology• Globusisagoodexampleonhowtosimplify

fornon-specialists

• NetworkOperatorsdon’ttrustusers• Justifiably!

• ProcessisaboutApproval

OURPROPOSEDSOLUTION

• Portalfordomainscientists

• Simpleendpoints

• Submitarequest

• Administrators(endpointsandnetwork(s))approve• Automaticallyormanually

• Integrationwithtransferapplications• Globus,GridFTP,etc.

ATLANTICWAVE/SDXOVERVIEW

• Inter-domainSDNcontrollerforwide-area,highspeedsciencenetworks

• We’vetalkedaboutitbefore

• Adaptableformultiplesituations• Includingself-servicecasewe’redescribing

• Usedbynot-quite-PhDJoaquinChungforhisthesis

Fortaleza

Santiago

10Gbps

10Gbps

10Gbps

100Gbps

100Gbps

10GbpsSao Paulo

Miami

AMLIGHT LINKS

USECASESWE’RECONSIDERING

• Astronomerusecase

• NetworkOperator• “Advancedoptions”

• CommercialOperator• Howtohandleper-usecosts?

• Multi-domain• Howtohandledifferentmanagementand

authorizationlevels

• Computeintegration• ComputeresourcesasapartoftheSDX

• Whatotherusecasesshouldwebelookingat?• Isthereaparticulartypeofuserthatweshould

betalkingto?

ATLANTICWAVE/SDXARCHITECTURE

SDXController

LocalController

ATLANTICWAVE/SDXARCHITECTURE

ATLANTICWAVE/SDXARCHITECTURE

SDXCONTROLLER

• HighLevelinputs• Fromusers

• L2Connection:2endpoints,startandstoptimes,bandwidthrequired

• CreateanL2tunnelbetweenVLAN635onport7onATLswitchtoVLAN879onport3onBOSswitchbetween0000and1600tomorrowwith1gbpsreserved

• Mid-leveloutput• NotOpenFlow

• Per-LCrules

• PerLC:• ATL:VLAN635port7toport12

• WAS:VLAN635port4toport2

• BAL:VLAN635port8toport30

• NYC:VLAN635port14toport24

• BOS:VLAN635port1toVLAN879port3

LOCALCONTROLLER

• Mid-levelInput• E.g.,VLAN635port1toVLAN879port3

• Translatestowhatswitchcanhandle• OpenFlow 1.3orOF1.3+Corsa-specificREST,

inourcase

• Couldbeswappedforsomeotherprotocol

• E.g.,Netconf,NSI,P4,Cisco/Juniper/etc.APIs

• Rules• match(inport:1,VLAN:635)

action(modify(VLAN=879),fwd(3))

• match(inport:3,VLAN:879)action(modify(VLAN=635),fwd(3))

HOWDOESTHISALLFITTOGETHER?

ScientistwantstotransferafilefromserverAtoserverBacrossthenetwork

Usesafiletransferinterface

HOWDOESTHISALLFITTOGETHER?

HOWDOESTHISALLFITTOGETHER?

SDXControllertranslatestoper-LCrules 1. Connectports1and6onVLAN663

2. Connectports2and4onVLAN663

3. Connectports8and10onVLAN663translatedto3700

HOWDOESTHISALLFITTOGETHER?

EachLocalControllertranslatestheirrulesintoOpenFlow rules

• match(inport:8,VLAN:663)action(modifyVLAN:3700,fwd:6)

• match(inport:10,VLAN:3700)action(modifyVLAN:663,fwd:6)

HOWDOESTHISALLFITTOGETHER?

EachLocalControllertranslatestheirrulesintoOpenFlow rules

NOTJUSTL2POINT-TO-POINT

• MultipointVLANs

• Semi-Arbitraryrules

• RESTAPI• Forprogrammaticcontrol

{"l2multipoint":{"starttime":"1985-04-12T23:20:50","endtime":"1985-04-12T23:20:50+0400","endpoints": [ {"switch":"mia-switch", "port":5, "vlan":286},

{"switch":"atl-switch", "port":3, "vlan":1856},{"switch":"gru-switch", "port":4, "vlan":3332} ],

"bandwidth":1000}}

FUTUREWORK

• Integrationofcompute,notjustnetwork

• Duetotheuncertaintyofbig-sciencefunding• Whereelsecanthisbeused?

• Whatotherusecasesarethere?

• Isthereacommercialapplication?

• Pay-per-usesciencemodel• Complication

• Canwepredictcosts?

• Auctioningresources?

CURRENTSTATUS

• Web-basedGUIininfancy• L2point-to-pointishandledeasilyhere• OtherfunctionalityisRESTAPIonly

• Availableforuse!• Easy-to-deployVMdemousingVagrant• CustomizableDockercontainersformore

than“helloworld!”functionality• HappytohaveaSkype/Hangoutscall

withanyoneinterestedinusingtheAtlanticWave/SDXcontroller

CONCLUSIONS

• Domainscientistsarenetworkusers,buttheyarenotnetworkoperators

• Theyshouldbeabletogetnetworkresourceseasily

• Automationofnetworkresourcesshouldfollowtheself-servicemodelusedbycomputeresourcestoday

• TheAtlanticWave/SDXcontrollerisworkingonbeinganexamplenetworkresourceallocationmechanism

• Thecontrollerdesignnaturallylendsitselftomulti-domainsituations

• Itcanbeusedasaprototypetobuildoffof

QUESTIONS?

CONTACT

SeanDonovan

RussClark

Jeronimo Bezerra

sdonovan@gatech.edu

russ.clark@gatech.edu

jbezerra@fiu.edu

http://www.atlanticwave-sdx.net/https://github.com/atlanticwave-sdx/

SupportedbyNSFAwardACI-1451024

InternationalResearchNetworkConnectionsProgramIRNC-RXP

BACKUP

SDX Controller

Telescope Facility

Local Controller

Local network

SDX-to-LC Interface

SDX domain 1

Local Controller

Local network

SDX domain 2

Local Controller

Supercomputer Facility

SDX domain 3

Network Service Science Gateway

Scientist UserData Workflow

Management System

Interdomain links

SDX-to-LC: SDX to Local Controller

SDX-to-LC Interface

SDX-to-LC Interface

Local network

Network Operator

SDX User Interface

SDX User Interface

SDX User Interface

JOAQUINCHUNG’S THESISWORK

Recommended