PowerPoint Presentation

Rick McGeerChief Scientist, US Ignite

March 17, 2014The GENI Experiment EngineA Fast, Simple On-Ramp for GENIHello, World Across GENI in FIVE MINUTES34

Need logos: Internet-2, SAVI, Glab, UCSD, CNS4ObjectivesHello, World Across GENI in < 5 MinutesAllocate GEE SliceletUpload/Deploy Program (one-click)ExecuteTear DownSandboxed environment powerful enough to do useful thingsBut not powerful enough to cause griefNon-Objective: be all things to all peopleMaking things fast & easy means giving up some optionsEasy to do something simple, go to full GENI for complex stuffUse as a starter for a full GENI slice5GENI Experiment Engine Architecture6

2 Principles, 3 ServicesDesign PrinciplesDont develop new GENI facilities: expose existing facilitiesPre-allocate to bring stuff up quicklyServicesGEE Compute Engine: PaaS Slicelet + Deployment serviceGEE Storage Engine: Global filesystem across the GENI InfrastructureGEE Message Service: Distributed Messaging System across the GENI Infrastructure7GEE Compute EngineGEE SliceletNetwork of PlanetLab sliversPrivate network between slivers (full port space)Python VM installed and running in sliversPre-allocatedAccess through use-once key pairFixed topology, IP addresses, etc.Automated Deployment (optional)Fabric-as-a-Service through GEE Portal8GEE NetworkTwo interfaces/sliverPrivate network (full access)Public internet (outbound only)Problem: how to expose the private networkIP addresses are specific to pre-allocated SliceletProgrammer doesnt know what addresses shell get per sliverBut she does know where slivers are (all Slicelets have slivers in the same places)Symbolic addresses (Python constants) for Slicelet nodes on private networkResolve to IP addresses in deployed sliverE.g. GEENetwork.NORTHWESTERN binds to 10.24.128.7 Resolution in simple binding in downloaded internal file9GEE Network ImplementationTunneling using GREUse of VLANsEnough now, more comingPerformance/broadcast isolation within a VLAN (TBD: experience)Overlay on Nick Bastins VTSVery attractive10GEE FilesystemOverall concept: POSIX Filesystem over the GENI substrateWill use standard Filesystem callsVolumes to indicate file locationImplementationSwift repositories as block storeSyndicate as meta data repository11GEE Message SystemStill in design phaseGlobal message queuesCurrent design: RabbitMQ-as-a-ServiceMultiple clientsRESTful APIStill TBD: centralized vs. distributedPlan on initial implementation GEC 2012How Do I Use This Stuff?GEE Compute Engine (today! Well, almost)Login at site, ask for slicelet (4 clicks)Unpack downloaded zip file(Easy) add experirment task to downloaded fabfile.py and run $ fab (Harder) ssh into slivers, yum, scp, run, etcGEE Filesystem (GEC 20+)Download Python libraryOpen, read, write, etc.GEE Message System (GEC 20, for sure)Download Python librarySend, receive,.13Current StatusGEE Compute EngineSlicelets allocated and demonstrated here(!)Production Use by GEC 20GEE NetworkDesign alternatives being evaluatedGEE Filesystem EngineSwift Adapter for Syndicate writtenDemonstratable for GEC 20GEE Message EnginePreliminary version under testDemonstratable for GEC 2014GEE TeamCompute Engine:Andy Bavier, PWNetworkingJoe Mambretti and Jim Chen, NW/StarLightFilesystemStephen Tredger, U VicMessage SystemRick McGeer, IgniteOverall ArchitectureRick, Andy, Joe, Jack Brassil (HP), Glenn Ricart (US Ignite), Marshall BrinnThanks to our collaborators and friendsJude Nelson, Nick Bastin, Rob Ricci, Niky Riga, Mark Berman15Thanks!