70 likes | 184 Vues
This document outlines the strategic deployment plan for the SPP (Slicing Protocols and Platforms) as developed by John DeHart and Jon Turner at the Applied Research Lab of Washington University. Key deployment locations include Kansas City, Salt Lake City, and Washington D.C., with an extension planned for Atlanta and Houston. The plan emphasizes achieving 1 GbE connections and the integration of a 10 Gb/s optical network to optimize performance. It defines priorities and ongoing tasks for a successful rollout by July 1, detailing configurations, bug fixes, and documentation requirements.
E N D
SPP Deployment Plan John DeHart and Jon TurnerApplied Research Lab, Washington Universitywww.arl.wustl.edu/~jdd
SPP Deployment Locations 1 GbEconnections KANSas City SALT Lake City WASHington DC 3 3 1 1 2 2 4 4 1 3 5 6 2 4 planned extension toinitial deployment ATLAnta HOUSton 2 4 5 5 1 3 4 2 3 1
SALT Configuration 1 Gb/s each private IPaddresses GbE Switch (Proto-GENI) SPP Optical Network 10Gb/s 1234 connectionto CP (10/100)public IP LC portscopper connections 8 9 10 public IPaddresses 1 Gb/s each GbE Switch (I2) Router (I2) 10Gb/s
WASH Configuration (same as SALT) 1 Gb/s each private IPaddresses GbE Switch (Proto-GENI) SPP Optical Network 10Gb/s 1234 connectionto CP (10/100)public IP LC portscopper connections 8 9 10 public IPaddresses 1 Gb/s each GbE Switch (I2) Router (I2) 10Gb/s
KANS Configuration 1 Gb/s each private IPaddresses GbE Switch (Proto-GENI) SPP 123456 10Gb/s Optical Network connectionto CP (10/100)public IP 8 9 10 LC portscopper connections public IPaddresses 1 Gb/s each GbE Switch (I2) Router (I2) 10Gb/s
3 Month Priorities • Deployment by July 1. • ProtoGENI folks are deploying at same time. • Configure for Deployment and Exercise • Rename three nodes (John and Dave) • Configure exactly as will be when deployed (John and Dave) • Code option for Games Application (Ritun) • Without taking up much if any of John or Fred’s time. • In Progress : Other people using SPPs (Ken, Ritun) • Re-do SPP3: hub and GPE boot sequence (Dave) • Boot sequence (srm, scd, rmp, natd, …) (John and Fred) • Sharing things like sliced, SPPMon, etc. Should they go in the ref. file system give to each slice? (John) • Bug Fixes • DONE: Filter API calls (Mart) • Flow Control (Dave) (but not necessarily for July 1) • DONE: NM/RMP timing (John and Fred) • DONE: Verify removing a slice cleans up correctly (John) • DONE: First ICMP NAT connection fails. NAT initialization file had ICMP start ID of 0, should be 1. (John, Mart) • In Progress: Reservations (Fred) • Security Holes (Fred) • In Progress: Flowstats (John) • In Progress: FSD • DONE: SCD • SRM • NATD • DONE: Updates to ME FlowStats: add TimeRecord, add Command to FlowRecord and TimeRecord • Change SubstrateOnly Lookup to NPE Bypass Lookup (John) • Power Control for remote reboot capability (Dave) • Documentation (Ken) • Plan for software upgrades and version control (John) • Detailed installation instructions and diagram (Dave) • SPP PLC: Any changes needed? Open up to outside WU. • EIT doing backups of SPP PLC • PLC Admin email for new user requests
Not Priorities • NPE V2 • Mike can keep working on it but should not distract the rest of us. • GEC-5 (mid-July) Demo • Geniwrapper and RSPecs • Its not ready for us anyway… • Openflow code option and demonstration • Nick McKeown wants to hold off until GEC-6 also.