Download presentation
Presentation is loading. Please wait.
Published byArron Sanders Modified over 8 years ago
1
Sponsored by the National Science Foundation Substrate Working Group GENI Engineering Conference 4 Miami, FL Peter O’Neil April 1, 2009 www.geni.net
2
Sponsored by the National Science Foundation 2 April 1, 2009 Agenda Welcome and Introductions – Peter O’Neil Generalized Aggregate Manager Interfaces – Patrick Crowley –Introduction – John Jacob –Spiral-1 Implementations Backbone Nodes (ProtoGENI) – Robert Ricci Regional Optical Network (ORCA) – Ilia Baldine Wireless Sensor Network (ORCA) – Hongwei Zhang WiMAX Base Station (ORBIT) – Ivan Seskar –Generalized Interfaces Dynamic Circuits - Chris Tracy Unified Measurements – Franz Fidler Substrate Working Group Charter – Joseph Evans –Defining our deliverables Slides available at http://groups.geni.net/geni/wiki/GEC4SWGAgenda
3
Sponsored by the National Science Foundation Generalized Aggregate Manager Interfaces GENI Engineering Conference 4 Miami, FL Patrick Crowley April 1, 2009 www.geni.net
4
Sponsored by the National Science Foundation 4 April 1, 2009 Introduction The Aggregate Manager IS the interface between substrates and the control framework which defines much of the vertical integration tasks –In prototype clusters the Aggregate Manager is defined by the cluster CF (ORBIT, ORCA, PlanetLab, ProtoGENI, TIED) –Eventually, there may be only one NSF GENI control framework associated with a GENI Aggregate Manager This currently does not exist
5
Sponsored by the National Science Foundation 5 April 1, 2009 GENI System Decomposition Operations NSF Clearinghouse Federations Researchers GENI Aggregates Component/Aggregate manager defines intersection between control framework and substrate aggregates – i.e. mechanism for vertical integration
6
Sponsored by the National Science Foundation 6 April 1, 2009 Specific Implementations and Generalized Interfaces Spiral-1 focused on “stove- piped” integration –Meeting their milestones Lower layer IF’s make- model-version dependent –Always some level of effort to stove-pipe Can a unification layer be defined? –Substrate type specific –Supports generalized interfaces Will this allow a broad re-use of GENI code? 3 Spiral-1 implementations (wired and wireless) 3 Generalized topics (wired, measurements, wireless)
7
Sponsored by the National Science Foundation Substrate Working Group Charter GENI Engineering Conference 4 Miami, FL Joseph Evans April 1, 2009 www.geni.net
8
Sponsored by the National Science Foundation 8 April 1, 2009 GENI Working Groups Working groups are expected to be the locus of technical work required to develop the GENI architecture and design. They will author & review requirements and design documents and evaluate software and services contributed by Working Group (WG) members (some of which may be sponsored by the GENI Project Office). Working groups are expected to provide input to integration activities, design bake-offs, and other prototyping tasks. Emphasis is placed on technical contribution, including expression of the research community's needs and use cases, regardless of the source of financial support. Academic, industrial, and government lab participants are encouraged. This document discusses the GENI working groups, their governance, publication process, and initial charters. It is a working draft and will likely be refined with experience. Check this page for future revisions and other information on working groups. http://www.geni.net/docs/geni-wgs-20070920.pdf
9
Sponsored by the National Science Foundation 9 April 1, 2009 GENI Substrate Working Group (Original Plan) Scope: What is the framework for evolution of substrate technologies? What technologies should be in GENI? How will they be used? Deliverables: Initial: Description of what can/should be implemented by the end of 2008, including high level functional architectures, initial capabilities definitions, projected development schedules with dependencies and identified risks, Technology Readiness Levels, and best-effort cost estimates. Substrate Framework: e.g., generic substrate requirements; appropriate abstractions for specific technologies; evolution strategies Technology Identification: e.g., technology survey; technology tradeoffs including justification in GENI's scientific context; identification of candidate substrate technologies plus characterization of additional development to meet GENI requirements Requirements Definition & Design: significant contributions to the GENI Project Deliverables. In particular, the WG will develop contribute to the Technical Requirements Document to cover the substrate portion of an eventual construction RFP. Risk Register: performance, cost, and schedule risks. Safe to say this is OBE
10
Sponsored by the National Science Foundation 10 April 1, 2009 Currently Planned Documents Scope: Understanding spiral implementations and how they shape GENI designs Substrate WG Documents and Dates (Spiral 1) –Substrate Catalog (GPO) –Spiral 1 based use-case(s) (GPO) Derived from Catalog Substrate WG Documents and Dates (GENI Design) –Generalized Aggregate Manager Interface Definition (SWG) –Aggregate Subsystem Technical Description (GPO) –Aggregate ICD (GPO) Derived from Aggregate Subsystem Technical Description and Substrate Capabilities Summary (Recommended By) www.geni.net
11
Sponsored by the National Science Foundation 11 April 1, 2009 Moving Forward Do we have a proper set of deliverable defined for the next 12 months? –SWG needs to agree on set of documents and an outline of the contents –Documents could be divided into two broad categories Those focused on spiral prototyping efforts Those applicable to a broader GENI design
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.