1 / 46

GENI Global Environment for Network Innovations The GENI Project Office (GPO)

GENI Global Environment for Network Innovations The GENI Project Office (GPO). www.geni.net Clearing house for all GENI news and documents. Outline. What is GENI? Programmatics System concept of operations System overview (for discussion) How can you participate?.

sela
Télécharger la présentation

GENI Global Environment for Network Innovations The GENI Project Office (GPO)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GENI Global Environment for Network Innovations The GENI Project Office (GPO) www.geni.net Clearing house for all GENI news and documents www.geni.net

  2. Outline • What is GENI? • Programmatics • System concept of operations • System overview (for discussion) • How can you participate? www.geni.net

  3. Large, wide-area footprint Enables large-scale,end-to-end experiments Shared among researchers by virtualization & slices The GENI VisionA national facility to explore radical designs for a futureglobal networking infrastructure • Current / projected substrates • High capacity optical nets and programmable cores • Large clusters of CPUs, storage • Edge / access technologies(e.g. cellular, sensor networks) www.geni.net

  4. How We’ll Use GENI Note that this is the “classics illustrated” version – a comic book!Please read the GENI Research and Education Plan to learn all about the community’s vision for GENI and the research it will enable. Your suggestions are very much appreciated! www.geni.net

  5. A bright idea I have a great idea! The original Internet architecture was designed to connect one computer to another – but a better architecture would be fundamentally based on PEOPLE and CONTENT! That will never work! It won’t scale! What about security? It’s impossible to implement or operate! Show me! www.geni.net

  6. Trying it out My new architecture worked great in the lab, so now I’m going to try a larger experiment for a few months. And so he poured his experimental software into clusters of CPUs and disks, bulk data transfer devices (‘routers’), and wireless access devices throughout the GENI facility, and started taking measurements . . . He uses a modest slice of GENI, sharing the facility with many other concurrent experiments. www.geni.net

  7. It turns into a really good idea Boy did I learn a lot! I’ve published papers, the architecture has evolved in major ways, and I’m even attracting real users! Location-based social networks are really cool! His experiment grew larger and continued to evolve as more and more real users opted in . . . His slice of GENI keeps growing, but GENI is still running many other concurrent experiments. www.geni.net

  8. Experiment turns into reality My experiment was a real success, and my architecture turned out to be mostly compatible with today’s Internet after all – so I’m taking it off GENI and spinning it out as a real company. I always said it was a good idea, but way too conservative. www.geni.net

  9. Meanwhile . . . I have a great idea! If the Internet were augmented with a scalable control plane and realtime measurement tools, it could be 100x as reliable as it is today . . . ! And I have a great concept for incorporating live sensor feeds into our daily lives ! If you have a great idea, check out the NSF FIND, SING, or NGNIprograms which are funding new architectural work. www.nets-find.net www.geni.net

  10. Moral of this story • GENI is meant to enable . . . • Trials of new architectures, which may or may notbe compatible with today’s Internet • Long-running, realistic experiments with enough instrumentation to provide real insights and data • ‘Opt in’ for real users into long-running experiments • Large-scale growth for successful experiments, so good ideas can be shaken down at scale • A reminder . . . • GENI itself is not an experiment ! • GENI is a stable facility on which experiments run GENI creates a huge opportunity for ambitious research! www.geni.net

  11. How We’ll Build GENI Note that this is the “classics illustrated” version – a comic book!Please read the GENI Project Development Plan (PDP) and Project Execution Plan (PEP) for detailed planning information. www.geni.net

  12. An ambitious goal The GENI facility will allow experiments to incorporate all the key technologies for global networks and distributed services within a 10-20 year time frame – specifically CPU & disk farms, programmable ‘routers’, optical networks, and wireless access. That’s way too ambitious! Exactly what wireless? or optics? Technology becomes obsolete fast! Overlays are all you’ll ever need! Nobody will use it –it’s a white elephant! www.geni.net

  13. Managing real risks • You are identifying important risks. • A typical “blueprint then execute” process suitable for building many kinds of predictable engineering projects (such as chemical plants) will lead to extremely high levels of risk if used for planning and building GENI. • Our plan for building GENI successfully relieson two main risk-management techniques: • Spiral development • Federation www.geni.net

  14. Spiral DevelopmentGENI grows through a well-structured, adaptive process • An achievable starting pointExample: Rev 1 control framework, federation of multiple substrates (clusters, wireless, regional / national optical net with early GENI ‘routers’, perhaps some existing testbeds), Rev 1 user interface and instrumentation. • Envisioned ultimate goalExample: Planning Group’s desired GENI facility, probably trimmed some ways and expanded others. Incorporates large-scale distributed computing resources, high-speed backbone nodes, nationwide optical networks, wireless & sensor nets, etc. • Spiral Development ProcessRe-evaluate goals and technologies yearly by a systematic process, decide what to prototype and build next. Planning Design Use Use Integration Build out Strawman GENI Construction Plan www.geni.net

  15. FederationGENI grows by “gluing together” heterogeneous facilities over time My experiment runs acrossthe evolving GENI federation. Wireless#1 Corporate GENI facilities Backbone #1 ComputeCluster#1 My GENI Slice Other-Nation GENI facilities Access#1 Backbone #2 ComputeCluster#2 This approach looks remarkably familiar . . . Other-Nation GENI facilities Wireless#2 NSF parts of GENI Goals: avoid technology “lock in,” add new technologies as they mature, and potentially grow quickly by incorporating existing facilities into the overall “GENI ecosystem” www.geni.net

  16. It’s all about managing risksThe Central Goal of GENI Planning and Construction We’ll take it little by little. Those parts of GENI that are widely used will grow; those that aren’t, won’t get more funding. But it won’t be impromptu or ad hoc – we will follow a well-defined, formal process throughout: spiral development. I see. We are avoiding an “all or nothing” gamble – we don’t try to specify all of GENIright now, then live with it for the next 20 years. Thank heavens! www.geni.net

  17. Moral of this story • GENI has real risks . . . • Many have been identified already • Others will emerge as prototyping / construction get underway • The “white elephant” risk is certainly real, as are many technological risks including rapid obsolescence • Accurate understanding of operating expenses will be critical • Risk management is central to GENI planning • “Winging it” would almost surely lead to disaster • Systematic, formal processes must be used identify and drive down risks throughout planning and construction • Spiral development and federation greatly reduce risk • Rapid prototyping should begin immediately, as a key technique for risk reduction in GENI’s planning phase www.geni.net

  18. Outline • What is GENI? • Programmatics • System concept of operations • System overview (for discussion) • How can you participate? www.geni.net

  19. Their hard work has created GENI’s Conceptual Design, the starting point for all our work going forward. “Our founders” The GENI Planning Group and Many, Many Working Group Volunteers Larry Peterson, Princeton (Chair) Tom Anderson, Washington Dan Blumenthal, UCSB Dean Casey, NGENET Research David Clark, MIT Deborah Estrin, UCLA Joe Evans, Kansas Terry Benzel, USC/ISI Nick McKeown, Stanford Dipankar Raychaudhuri, Rutgers Mike Reiter, CMU Jennifer Rexford, Princeton Scott Shenker, Berkeley Amin Vahdat, UCSD John Wroclawski, USC/ISI CK Ong, Princeton And Within NSF Peter Freeman Debbie Crawford Larry Landweber Suzi Iacono Guru Parulkar Darlene Fisher Cheryl Albus Allison Mankin Ty Znati Gracie Narcho Paul Morton www.geni.net

  20.  Definitive source of “what we need in GENI” Authors of GENIResearch & Education Plan  Technical advisory & oversight to GPO  Project management and execution  GENI architecture and system engineering  Cost & schedule estimates for construction  Authors of GENI facility construction plan  Home for Working Groups GENI Roles & Responsibilities NSF GENI Science Council (GSC) GENI Project Office (GPO) “Voice of the Community” Project Management Key Roles and Responsibilities GPO GSC www.geni.net

  21. GPO Leadership Kristin Rauschenbach Substrate Architect Aaron Falk (Community Nominee) Engineering Architect Chip Elliott Project Director Heidi Picher Dempsey Operations & Integration Director Craig Partridge Outreach Director Henry Yeh Project Manager www.geni.net

  22. Current Timelinefor GENI Planning and Construction Planning Phase Construction Phase Operations Phase TBD years 5 years 3-4 years June 2007 GENI Engineering Conferences Solicitations issued for new prototypes & trials FDR CDR PDR 12 months 9 months 18-30 months Early 2008 www.geni.net

  23. Our plan for building GENI • Start with a clear, achievable starting point and an envisioned “ultimate goal” • Begin prototyping and trials immediately • Gain practical experience with prototypes, and adjust “wishlists” and requirements as we go • Make realistic estimates of cost and operational complexity based on early experience with prototype systems, rather than guess-work • Add features, complexity, and new technologies incrementally, based on experience to date • Repeatedly assess GENI’s current risk and usefulness as planning and construction unfold, and adjust plans accordingly www.geni.net

  24. GENI Needs Rapid PrototypesWork should begin immediately by multiple teams GENI’s envisioned technology TODAY GENI needs to be here before Construction Phase decision www.geni.net

  25. FDR PEP, PDP, etc. Planning Documents All Checklists 100% Satisfied End-to-end GENI system Subsystems Results Risk Prioritization All GENI Technologies Prototyped at TRL 7 Prototypes Risk Reduction Integration Trials GENI’s Planning PhasePrototyping while refining design & budget “Paper” Design Documents, Schedule, Budget, etc. GENI Engineering Conferences Academic / Industrial Prototyping, Integration, Experiments www.geni.net

  26. GENI will be Designed & Built by the CommunityVia an Open, Transparent, & Fair GPO Process • All design, prototyping, & construction will be performed by the research community (academia & industry) • Openness will be emphasized • Design process will be open, transparent, and broadly inclusive • Open-source solutions will be strongly preferred • Intellectual property is OK, under no-fee license for GENI use • GPO will be fair and even-handed • BBN brings no technology to the table • BBN does not intend to write any GENI software, nor does it envision bidding on any prototyping or construction activities(but “never say never”) • If BBN does create any GENI technology, it will be made public at no cost www.geni.net

  27. Working Groups will drive GENI’s Technical Design Meet every 4 Months to Review Progress Together • Working Groups, open to all • The locus for all GENI technical design • Patterned on the early IETF • Discuss by email, create documents, meet 3x per year in person • Each led by Chair(s), plus a professional System Engineer • GENI Engineering Conferences, open to all who fit in the room • Held at regular 4-month periods • Held on / near university campuses (volunteers?) • All GPO-funded teams required to participate • Systematic, open review of each Working Group status(all documents and prototypes / trials / etc.) • Also time for Working Groups to meet face-to-face • Results in prioritized list for next round of prototype funding areas (priorities decided by GSC and GPO) www.geni.net

  28. How the GPO will FundRapid Prototyping and Experiments • Needs are driven by “long poles” in GENI construction – the high risk design and technology areas • High risks are identified at 4-month intervals by GSC / GPO review panel • GPO issues solicitations once or twice per year • Proposals are merit-reviewed by NSF-style panels • GPO continuously monitors contracts for performance • Quick decisions and quick funding are essential • Goal is to have multiple development teams up to speed in each area before construction begins, who can then bid on the big construction contracts www.geni.net

  29. Outline • What is GENI? • Programmatics • System concept of operations • System overview (for discussion) • How can you participate? www.geni.net

  30. Resource discoveryAggregates publish resources, schedules, etc., via clearinghouses What resources can I use? GENI Clearinghouse These Researcher Components Components Components Aggregate A Computer Cluster Aggregate B Backbone Net Aggregate C Metro Wireless www.geni.net

  31. Slice creationClearinghouse checks credentials & enforces policyAggregates allocate resources & create topologies Create my slice GENI Clearinghouse Components Components Components Aggregate A Computer Cluster Aggregate B Backbone Net Aggregate C Metro Wireless www.geni.net

  32. ExperimentationResearcher loads software, debugs, collects measurements Experiment – Install my software, debug, collect data, retry, etc. GENI Clearinghouse Components Components Components Aggregate A Computer Cluster Aggregate B Backbone Net Aggregate C Metro Wireless www.geni.net

  33. Slice growth & revisionAllows successful, long-running experiments to grow larger Make my slice bigger ! GENI Clearinghouse Components Components Components Aggregate A Computer Cluster Aggregate B Backbone Net Aggregate C Metro Wireless www.geni.net

  34. Federation of ClearinghousesGrowth path to international, semi-private, and commercial GENIs Make my slice even bigger ! GENI Clearinghouse Federated Clearinghouse Components Components Components Components Aggregate A Computer Cluster Aggregate B Backbone Net Aggregate C Metro Wireless Aggregate D Non-NSF Resources www.geni.net

  35. Stop the experiment immediately ! Operations & ManagementAlways present in background for usual reasonsWill need an ‘emergency shutdown’ mechanism GENI Clearinghouse Oops Federated Clearinghouse Components Components Components Components Aggregate A Computer Cluster Aggregate B Backbone Net Aggregate C Metro Wireless Aggregate D Non-NSF Resources www.geni.net

  36. Outline • What is GENI? • Programmatics • System concept of operations • System overview (for discussion) • How can you participate? www.geni.net

  37. Federation List of Organizations List of Aggregates O&M Policy Clearinghouse Research Organization Measure- ments O&M Measure- ments O&M Measurement Plane Control Plane Aggregate Control Aggregate Control Opt-in User (??) Data Plane Researcher with Tools Internet Trust Components Components Interface Aggregate A Aggregate B GENI Researchers and their tools A researcher belongs to one or more research organizations, who will vouch for him/her. A researcher has tools (user interfaces) to interact with Aggregates. A research organization may belong to one or more clearinghouses. www.geni.net

  38. Federation List of Organizations List of Aggregates O&M Policy Clearinghouse Research Organization Measure- ments O&M Measure- ments O&M Measurement Plane Control Plane Aggregate Control Aggregate Control Opt-in User (??) Data Plane Researcher with Tools Internet Trust Components Components Interface Aggregate B Aggregate A GENI Aggregates(We hope existing facilities can be ‘Geni-ized’ easily) An Aggregate is a coherent set of components which is controlled as a whole; it may belong to multiple clearinghouses. Components may include CPUs, disks, switches, optical or wireless nodes, (virtual) links, etc. Aggregates also include (controllable) instrumentation and make measurements available. Aggregates may use any O&M systems they find useful. Researchers interact with Aggregate Control to set up slices, download code, debug, etc. www.geni.net

  39. Federation List of Organizations List of Aggregates O&M Policy Clearinghouse Research Organization Measure- ments O&M Measure- ments O&M Measurement Plane Control Plane Aggregate Control Aggregate Control Opt-in User (??) Data Plane Researcher with Tools Internet Trust Components Components Interface Aggregate B Aggregate A GENI Clearinghouses A clearinghouse organizes trust relationships and policies; it also provides the basic means by which Aggregates may be discovered and their status, planned schedules, etc, can be obtained. There will be multiple clearinghouses which will federate. The GENI project will operate the NSF clearinghouse. ‘Federation’ is the interface between clearinghouses. www.geni.net

  40. System overview (strawman)Based on very large-scale, end-to-end virtualization Clearinghouse Resource Discovery & Authorization Researcher software . . . . . . running on researcher-specified topology Slice dataplane Slice Aggregate Control Experiment Control Plane Processors (virtual machines) Aggregate with Resources O&M Plane Data transport 29 Nov 07 Substrate with Components www.geni.net

  41. Test driving this system conceptCan it adequately represent every desired part of GENI? Backbone Wireless Aggregate Control Aggregate Control Control Plane Control Plane Experiment Control Plane Experiment Control Plane Data transport Mux Sensor / MANET Nodes Data transport ‘Router’ Aggregate Control Control Plane Cluster Aggregate Control Control Plane Experiment Control Plane Experiment Control Plane CPUs Storage CPUs Mux Data transport Data transport Mux Mux www.geni.net

  42. Outline • What is GENI? • Programmatics • System concept of operations • System overview (for discussion) • How can you participate? www.geni.net

  43. GENI Working Groups (WGs)Open to all, participate via geni.net email lists • SubstratesAll hardware, real-estate, facilities, etc., required for the GENI facility (including optical networks, wireless, computers, etc.) Includes Operational Expenses for the facility except Operations & Management costs. • Control Framework with FederationWritten definitions of the core GENI mechanisms for providing experimental control of a node or collection of nodes. The very earliest version must incorporate federation. • Experiment WorkflowTools and mechanisms by which a researcher designs and performs experiments using GENI. Includes all user interfaces for researchers, as well as data collection, archiving, etc. • User Opt-InHow do “real users” (not researchers) participate in GENI. Includes both mechanisms and considerations such as privacy, etc. • Operations, Management, and SecurityHow do operators provision, operate, manage, and trouble-shoot GENI? Includes all mechanisms for securely operating the facility, and Operations & Management costs. www.geni.net

  44. GENI Engineering ConferencesMeet every 4 months to review progress together • 3rd meeting July 21-22, 2008 in Palo Alto, open to all • Reviews current GENI status, Working Group meetings • Also discuss GPO solicitation, how to submit a proposal, evaluation process & criteria, how much money, etc. • Travel grants for participant diversity • Subsequent Meetings, open to all who fit in the room • Held at regular 4-month periods • Held on / near university campuses (volunteers?) • All GPO-funded teams required to participate • Systematic, open review of each Working Group status(all documents and prototypes / trials / etc.) • Also time for Working Groups to meet face-to-face • Results in prioritized list for next round of prototype funding areas (priorities decided by GSC and GPO) www.geni.net

  45. GPO SolicitationsAcademic-industrial teams favored but not required • First solicitation has just closed • February 2008 • Over 70 proposals received • Second solicitation planned for fall • What kinds of proposals do we solicit? • Analyses & idea papers • Prototypes of high-risk GENI technology • Integrations and trials of prototypes • How are proposals judged? • Merit review • Joint academic / industrial teams will be favored but not required • Open source will be favored but not required(IP licenses on www.geni.net for public review & comment) www.geni.net

  46. GENI is a Huge Opportunity • GENI is an unbelievably exciting project for the community • Our research community has changed the world profoundly. GENI opens up a space to do it again. • We believe the whole community will build GENI together • Our vision is for a very lean, fast-moving GPO, with substantially all design and construction work performed by academic and industry research teams. • We'd like the community to start building prototypes immediately • within a GENI project framework that is open, transparent, and broadly inclusive. www.geni.net Clearing house for all GENI news and documents www.geni.net

More Related