[[PageOutline]] = Understanding the GENI AM API using Content Centric Networking = == Overview == Understand how resources are described and reserved in GENI. Learn how to customize those resources using standard mechanisms. Use multiple tools to act on a slice and reserve resources. While doing this experiment, use and understand the following terms: resource specification (RSpec), sliver, and aggregate manager API (AM API) === What you will learn === At the end of this exercise, you will be able to: * Use and understand the following terms: - Resource Specification (aka RSpec) - sliver - Aggregate Manager API (AM API) * Customize the resources/RSpec you reserve using standard mechanisms. You will: - understand that an RSpec is an XML file that specifies resources which are reserved using the aggregate manager API (AM API) - understand how to load and edit an RSpec using Flack - know how to specify the image to load on a compute node - know how to have software automatically loaded and run on a compute node * Use the Omni command line tool to manage resource reservations * Use multiple tools to act on a slice and reserve resources - understand that all tools use common mechanisms to describe resources (RSpecs) and to reserve resources (the AM API) == Experiment Topology and Setup == {{{ #!comment Tutorial Setup }}} Use the Omni GENI client to reserve a topology. Then arrange for automatic installation and execution of software on these nodes (performing basic traffic measurement tests). == Procedure == {{{ #!html
Design/Setup
  • Part I: Design/Setup
    • Step 1: Design Experiment
    • Step 2: Establish Management Environment
    • Step 3: Obtain Resources
Execute
  • Part II: Execute
    • Step 4: Configure and Initialize Services
    • Step 5: Execute Experiment
    • Step 6: Analyze and Visualize Experiment
Finish