![Page 1: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/1.jpg)
GENI Architecture: Transition
July 18, 2007
Facility Architecture Working Group
![Page 2: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/2.jpg)
Outline• Requirements
– Top Level– Derived
• Facility Design– Hardware Configuration– Software Configuration
• Minimal Core• Construction Plan
![Page 3: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/3.jpg)
Top-Level Requirements
1. Generality A. Minimal Constraints
allow new packet formats, new functionality, new paradigms,… allow freedom to experiment across the range of architectural issues
(e.g., security, management,...)
B. Representative Technology include a diverse and representative collection of networking
technologies, since any future Internet must work across all of them, and the challenges/opportunities they bring
2. Slicability support many experiments in parallel isolate experiments from each other, yet allow experiments to
compose their experiments to build more complex systems
![Page 4: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/4.jpg)
Top-Level Req (cont)3. Fidelity
A. Device Level expose the right level of abstraction, giving the experimenter the
freedom to reinvent above that level, while not forcing him or her to start from scratch (i.e., reinvent everything below that level)
these abstractions must faithfully emulate their real world equivalent (e.g., expose queues, not mask failures)
B. Network Level arrange the nodes into a representative topology and/or distribute
the nodes across a physical space in a realistic way scale to a representative size expose the right network-wide abstractions (e.g., circuits,
lightpaths)
C. GENI-Wide end-to-end topology and relative performance economic factors (e.g., relative costs, peering)
![Page 5: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/5.jpg)
Top-Level Req (cont)
4. Real Users allow real users to access real content using real applications
5. Experiment Support A. Ease-of-Use
provide tools and services that make the barrier-to-entry for using GENI as low as possible (e.g., a single PI and one grad student ought to be able to use GENI)
B. Observability make it possible to observe and measure relevant activity
![Page 6: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/6.jpg)
Top-Level Req (cont)
6. Sustainability A. Extensible
accommodate network technologies contributed by various partners accommodate new technologies that are likely to emerge in next
several years support technology roll-over without disruption
B. Operational Costs the community should be able to continue to use and support the
facility long after construction is complete
![Page 7: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/7.jpg)
Facility Architecture
GMC
User Services
Physical Substrate
- name space for users, slices, & components
- set of interfaces (“plug in” new components)
- support for federation (“plug in” new partners)
![Page 8: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/8.jpg)
Derived Requirements1. Generality
A. Minimal Constraints i. All devices are programmable with open interfaces
ii. All devices expose multiple levels of abstraction, with the lowest level coming as close to the raw hardware as possible:a. socketsb. virtual links
– point-to-point– multipoint
c. virtual radiod. virtual wire
– framed TDM electrical– unframed TDM electrical– unframed raw wavelength
![Page 9: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/9.jpg)
Derived Req (cont)1. Generality
B. Representative Technology i. Architected to accommodate a wide range of technologies
ii. Initially selected technologies:a. national fiber backboneb. connected edge clustersc. mobile client devices & sensorsd. 802.11 access networke. WiMAX access networkf. cognitive radio access net
![Page 10: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/10.jpg)
Derived Req (cont)2. Slicability i. Virtualize resources
ii. Partition resources (time & space)iii. Isolate and contain slicesiv. Support slice compositionv. Minimum capacity
a. 1000-10000 total projectsb. 100-1000 active experimentsc. 10-100 continuously running servicesd. 1-10 high-performance/low-jitter nets
![Page 11: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/11.jpg)
Derived Req (cont)3. Fidelity
A. Node Level
B. Network Level
C. GENI-Wide
i. For each selected technology (1.B.ii)a. support interfaces as appropriate (1.A.ii)b. sliver behavior (e.g., jitter) c. node capacityd. transmission capacity
i. For each selected technology (1.B.ii)a. points-of-presenceb. distribution/topology
i. Rich topologyii. Federation of autonomous domains
![Page 12: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/12.jpg)
Derived Req (cont)4. Real Users i. Wide coverage
ii. Opt-in mechanismsi. Generic proxiesii. GENI-aware applications
iii. Legacy Internet connectivitya. number of edge connection pointsb. number of peersc. capacity per peer
![Page 13: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/13.jpg)
Derived Req (cont)5. Experiment Support
A. Ease-of-Use
B. Observability
i. Rich set of user servicesa. slice embeddingb. experiment managementc. legacy Internetd. building block services
i. For each selected technology (1.B.ii)a. instrumentation sensors
ii. Data collection/archiving/analysis tools
![Page 14: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/14.jpg)
Derived Req (cont)6. Sustainability
A. Extensible
B. Operational Costs
i. Same as 1.B.i (representative technology)ii. Support federated ownership
i. Renewal costs contribute to 1.B.ii.ii. Adopt sustainable software
engineering practicesiii. Architect for securityiv. Develop monitoring & diagnosis tools
![Page 15: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/15.jpg)
National Fiber Facility
![Page 16: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/16.jpg)
+ Programmable Routers
![Page 17: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/17.jpg)
+ Clusters at Edge Sites
![Page 18: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/18.jpg)
+ Wireless Subnets
![Page 19: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/19.jpg)
+ ISP Peers
MAE-West
MAE-East
![Page 20: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/20.jpg)
Internet
backbone wavelength(s)
ProgrammableEdge Cluster
ProgrammableCore Node
Wireless Subnet
ProgrammableWireless Nodes
ProgrammableEdge Node
ProgrammableEdge Node
Edge Site
CommodityInternet
Sensor Network
![Page 21: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/21.jpg)
Internet
Site B
GENIBackbone
Site A
Suburban Hybrid Access
Network
Sensor Net
PEN
PEN
Urban GridAccess Network
PWN
PWN
PWN
PWN: Programmable Wireless NodePEN: Programmable Edge NodePEC: Programmable Edge ClusterPCN: Programmable Core NodeGGW: GENI Gateway
GGW
PEC
GGW
PEN
PCN
PCNPCN
![Page 22: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/22.jpg)
Substrate Hardware
Substrate HW Substrate HW Substrate HW
![Page 23: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/23.jpg)
Virtualization Software
Virtualization SW
Substrate HW
Virtualization SW
Substrate HW
Virtualization SW
Substrate HW
![Page 24: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/24.jpg)
Components
Substrate HW Substrate HWSubstrate HW
CM
Virtualization SW
CM
Virtualization SW
CM
Virtualization SW
![Page 25: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/25.jpg)
Aggregates
Resource Controller Auditing Archive
Aggregate(Proxy for set of components)
CM
Virtualization SW
Substrate HW
CM
Virtualization SW
Substrate HW
CM
Virtualization SW
Substrate HW
O & M ControlSlice Coordination
![Page 26: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/26.jpg)
Federation
![Page 27: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/27.jpg)
User Portals
Researcher Portal(Service Front-End)
![Page 28: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/28.jpg)
PEC(Site 1)
GENIBackbone
PCN
PCNPCN
Wireless SubnetPEN
PWN
PWN
PEC(Site n)
. . .Internet
Wireless SubnetPEN
PWN
PWNOps Team
Researchers
Edge SiteMgmtAggregate
WirelessMgmtAggregate
WirelessMgmtAggregate
BackboneMgmtAggregate
ResearcherPortal
OperationsPortal
O&MControl
O&MControl
O&M Control
O&M Control
SliceControl
SliceControl
SliceControl
SliceControl
![Page 29: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/29.jpg)
Hour-Glass Revisited
User Services
Substrate Components
BootstrapStructure
ReferenceImplementations
MinimalCore
Universal
Fixed Point
![Page 30: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/30.jpg)
Minimal Core• Principals
– Slice Authorities (SA)– Management Authorities (MA)– User (experimenter, not “end user”)
• Objects– Slices
Registered, Embedded, Accessed– Components
• Data Types– GENI Global Identifiers (GGID)– Tickets (credentials issued by component MA)
rspec: resource specification– Slice Credentials (express live-ness, issued by SA)
![Page 31: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/31.jpg)
Core (cont)• Default Name Registries
– Slice Registry (e.g., geni.us.princeton.codeen)– Component Registry (e.g., geni.us.backbone.nyc)
• Component Interface– Get/Split/Redeem Tickets– Control Slices– Query Status
![Page 32: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/32.jpg)
Construction Plan• Objectives
– Allow broader community to contribute (not just subs)– Scale (federate) the integration effort
• Strategy– Feature Development
Roughly equivalent to open source development process
– Component/Aggregate Integration Roughly equivalent to preparing a Linux distribution
![Page 33: GENI Architecture: Transition July 18, 2007 Facility Architecture Working Group](https://reader035.vdocuments.net/reader035/viewer/2022081513/56649f425503460f94c626ef/html5/thumbnails/33.jpg)
Design Develop Unit Test
Node Integration
Node Testing
Feature Repository
Distrib
ution
Distrib
ution
Aggregate Integration
Aggregate Testing
Component
Repository
Dep
en
den
cy
Sp
ecia
lizatio
n
Distrib
ution
Aggregate
Repository
Sp
ecia
lizatio
n
DEPLOY
• Features (hardware and software) are developed through the working group and tested locally
• Once complete a feature is passed to a feature repository where acceptance testing occurs (queued until dependencies resolve)
• Features in the repository can be picked up to enable development of other features
• A collection of hardware and software features are integrated into a canonical node
• The canonical node is distributed to a node repository for acceptance testing
• Nodes are available for specialization
Acceptance Testing
Acceptance Testing
Acceptance Testing
• A collection of nodes and communication features are integrated into a coherent aggregate
• Aggregates are themselves integrated to create, ultimately, the GENI Facility