Version 6 (modified by 12 years ago) (diff) | ,
---|
Getting Started with GENI - Part I
Goal
- the instant gratification of doing "Hello GENI"
Overview
- doing a single aggregate, Layer 2 experiment
- use and understand 5 terms
- using two basic GENI tools: Experimenter Portal and Flack
Concepts
- Layer 2 with a rack
Terms
5 terms:
- Experimenter
- Project
- Slice
- Aggregate
- Resource (with mention of resource specification/RSpecs)
Tools
- GENI Experimenter Portal
- Flack
- ssh & ssh keys
Rough procedure
- Login to Portal
- join GEC17 project (maybe this is prework?)
- Create slice
- Launch Flack, look around and draw sample topology
- Draw two VMs with a link (tell them which site to use)
- ssh into the nodes
- download and compile pingPlus
- run the listener and the sender
- Delete resources
Outstanding issues
- What about IP addresses? ExoGENI not allow you to change IP addresses
- Non-Portal accounts?
Getting Started with GENI - Part II
Goal
- How to write a (first) RSpec (that automates startup)
- Pulling back the covers: RSpecs & AM API (aka "all tools are created equal")
Overview
- doing a two aggregate, Layer 2 experiment
- use and understand 3 terms
- using two basic GENI tools: (Experimenter Portal and ) Flack and omni
Concepts
- AM API
- customized RSpec
- image
- boot script
- Layer 2 across country
Terms
3 terms:
- RSpec (again)
- Sliver
- AM API
- others?
Tools
- (GENI Experimenter Portal)
- Flack
- omni
Rough procedure
- Launch Flack and load Part I slice
- if not in Part I create a slice
- Load the topology from an rspec
- load not reserve
- Look at the rspec document
- Add custom image and look rspec
- Add download/install services and look at rspec
- Quickly go over the script
- Save RSpec to a file
- (optional) Do a minor edit to the RSpec (eg edit
client_id
) - Run rspeclint on edited RSpec
- Reserve resources with omni
- Login
- Do experiment
- Delete resources
Outstanding issues
- pipe VLANs and/or use GENI for ExoGENI aggregates? What about other InstaGENI aggregates?