Changes between Version 21 and Version 22 of GENIConcepts


Ignore:
Timestamp:
06/11/13 12:50:00 (11 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIConcepts

    v21 v22  
    3131
    3232== The GENI Portal ==
    33 A web-based tool for experimenters to create accounts, projects and slices and to manage project and slice memberships.  The Portal also includes tools to discover and add resources to slices.
     33The [https://portal.geni.net GENI Portal] is web-based tool for experimenters to create accounts, projects and slices and to manage project and slice memberships.  The Portal also includes tools to discover and add resources to slices.
    3434
    3535
    3636== Aggregates and Resources ==
    37 A GENI aggregate provides resources to GENI experimenters.  For example, a GENI Rack at Clemson University is an aggregate; GENI experimenters my request resources from this aggregate and add them to their slice.  Different aggregates provide different kinds of resources.  Some aggregates provide compute resources: Virtual Machines or "bare machines" or both.  Some aggregates provide networking resources that experimenters can use to connect compute resources from multiple aggregates.  The figure below shows a GENI slice with resources from multiple aggregates.
     37A GENI aggregate provides resources to GENI experimenters.  For example, a [wiki:GENIRacksHome GENI Rack] at Clemson University is an aggregate; GENI experimenters my request resources from this aggregate and add them to their slice.  Different aggregates provide different kinds of resources.  Some aggregates provide compute resources: Virtual Machines or "bare machines" or both.  Some aggregates provide networking resources that experimenters can use to connect compute resources from multiple aggregates.  The figure below shows a GENI slice with resources from multiple aggregates.
    3838
    3939[[Image(SliceAndAggregates.png, 40%)]]
    4040
     41== GENI Rspecs and the GENI AM API ==
     42
     43Experimenters request resources from aggregates using a standard API called the [wiki:GeniApi GENI Aggregate Manager API] or GENI AM API.  The AM API allow experimenters to, among other things,  list the resources available at an aggregate, request specific resources from the aggregate be allocated to their slices, find the status of resources from the aggregate that are allocated to their slice and delete resources from their slice.  The AM API uses [wiki:GeniRspec GENI Rspecs] (resource specifications) to describe resources.  Most experimenters will not need to learn details of the AM API or read/write Rspec files; GENI experimenter tools hide much of this complexity.
     44
     45The figure below shows an experimenter using the Allocate call of the GENI AM API to add resource from two different aggregates to her slice.
    4146
    4247
    43 Experimenters request resources from aggregates using a standard API called the GENI Aggregate Manager API or GENI AM API.  The figure below
    4448