NextGENI: The Nation’s Edge Cloud Rick.McGeer/Glenn.Ricart@us-ignite.org March 14, 2017

The World Wants Edge Clouds Small Edge Clouds to Control CPS Cloudlets Edge Cloud as Telco CO “Digital Town Square” Edge Cloud at Base Station

GENI: World’s Premier Edge Cloud ~60 POPs across the US 5-10 worker nodes/POP 80-150 cores 5-10 TB of Store SDN Capable GENI’s core strength: how do we sustain and enhance it? Viral growth Make it a platform

Successful Infrastructures Live Off The Land Easy to Adopt! Use local resources Spread by local action: software download and configuration Ex: Internet used existing computers, phone lines Ex: Web used existing Internet and services FTP Nine-line shell script was first web server!

Make Adoption Trivial Take it one step further… Currently: Use Dedicated Hardware, Runs GENI full time Not easy to adopt! Expensive: ~$70K/year in site opex/capex costs Software tools largely custom, GENI supported Bring Your Own Rack: Dedicate Existing Equipment to GENI Better (just download software) Software tools largely commodity, world-supported Still must dedicate the rack to GENI Take it one step further…

Why does GENI Need to Manage the Rack? Omni

Working With Existing Managers GENI-as-a-Service Tenant Omni Downloaded tenant

Big News: GaaS Already Prototyped GENI/SAVI Federation: 2015 Joint Project of GPO, University of Toronto, University of Victoria Let GENI Users attach VMs on SAVI to GENI Slices SAVI: Network of OpenStack clusters across Canada Method: Modify Omni to create VMs at SAVI sites through OpenStack nova Omni

PlanetIgnite: Add Your Campus to GENI in 20 minutes Modern version of PlanetLab Docker containers on VMs 12 sites, 3 infrastructures, two independents Runs on Any Ubuntu 14.04 VM Simple shell script to install ~15 minutes Still a Toy… Features and Scalability to come

GENI Software Architecture Current: ``Some Assembly Required’’: Slices Distributed Virtual Machines/Containers (“Slivers”) Future: Distributed, Composable Services Layered on top of existing GENI AMs Instantiating a Service: formalization of orchestration operations.

Layered Architecture New Services Architecture layered on top of existing VM/Container/Network Allocation PlanetLab Mantra: “Put it in a Slice” NextGENI Mantra: “Make it a Service – and the Service Lives In A Slice” Transparent to existing architecture