Changes between Version 29 and Version 30 of GENIConcepts


Ignore:
Timestamp:
06/11/13 17:48:23 (6 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIConcepts

    v29 v30  
    4040== GENI Rspecs and the GENI AM API ==
    4141
    42 Experimenters 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.  Experimenters send to aggregates a ''request'' Rspec that describes the resources they want and get back from the aggregates a ''manifest'' Rspec that describes the resources they got.  The manifest includes information such as the names and IP addresses of the compute resources (e.g. virtual machines), user accounts created on the compute resources, etc.  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.
     42Experimenters 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.  Experimenters send to aggregates a ''request'' Rspec that describes the resources they want and get back from the aggregates a ''manifest'' Rspec that describes the resources they got.  The manifest includes information the experimenters will need to use these resources such as the names and IP addresses of compute resources (e.g. virtual machines), user accounts created on the resources and VLAN tags assigned to network links.  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.
    4343
    4444The figure below shows an experimenter using the Allocate call of the GENI AM API to add resource from two different aggregates to her slice.