Changes between Version 52 and Version 53 of GENIConcepts


Ignore:
Timestamp:
06/14/13 11:37:27 (6 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIConcepts

    v52 v53  
    88
    99== Project ==
    10 A project organizes research in GENI, containing both people and their experiments. A project is created and led by a single responsible individual: the Project Lead.  A project may have many experimenters as its members and an experimenter may be a member of many projects.  The Project Lead is ultimately accountable for all actions by project members in the context of the project.  GENI experimenters must have Project Lead privileges to create projects.
     10A ''project'' organizes research in GENI, containing both people and their experiments. A project is created and led by a single responsible individual: the ''Project Lead''.  A project may have many experimenters as its members and an experimenter may be a member of many projects.  The Project Lead is ultimately accountable for all actions by project members in the context of the project.  GENI experimenters must have Project Lead privileges to create projects.
    1111
    1212The following figure illustrates a situation where a professor is the Lead for two GENI projects Alpha and Beta.  Each project has one of the professor's research assistants as a member.  The professors and his post-doc are members of both projects.
     
    2626The following roles are defined for slice members:
    2727   * Lead.  The slice Lead can add members to and remove members from a slice; add resources to or delete resources from a slice; and change roles of other members of the slice.  The experimenter that created the slice is the slice lead.  In the above example, this would be the research assistant.
    28    * Admin.  A slice Admin has all the privileges of a slice Lead.  The Project Leader is automatically added to a slice as an Admin.  The slice Lead and any slice Admin can promote other slice members to Admin.  In the above example, the professor is an Admin on both slices by virtue of his being the Project Lead.
     28   * Admin.  A slice Admin has all the privileges of a slice Lead.  The Project Lead is by default a member of all slices in a project.  The slice Lead and any slice Admin can promote other slice members to Admin.  In the above example, the professor is an Admin on both slices by virtue of his being the Project Lead.
    2929   * Member. A slice Member can add  resources to a slice or delete them from a slice.  A Member can run experiments using these resources.  A Member cannot make changes to slice membership.  In the above example, the post-doc is a Member of Slice 1.
    3030   * Auditor.  An Auditor can list resources in a slice but cannot make any changes to the resources held by a slice or make changes to slice membership.
    3131
    3232
    33 == The GENI Portal ==
    34 The [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.
    35 
    36 
    3733== Aggregates and Resources ==
    38 A GENI aggregate provides resources to GENI experimenters.  For example, a [wiki:GENIRacksHome GENI Rack] at a university is an aggregate; GENI experimenters may 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.
     34A GENI ''aggregate'' provides resources to GENI experimenters.  For example, a [wiki:GENIRacksHome GENI Rack] at a university is an aggregate; GENI experimenters may 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.
    3935
    4036[[Image(GeniNewcomersWelcome/figures:SliceAndAggregates.png, 40%)]]
     
    4238== The GENI AM API and GENI RSpecs ==
    4339
    44 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 slices and delete resources from their slices.  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.
     40Experimenters 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 slices and delete resources from their slices.  The AM API uses resource specifications, commonly referred to as ''GENI RSpecs'',  to describe resources.  RSpecs are just an XML file in a [wiki:GeniRspec standard format].
     41
     42Experimenters 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.
    4543
    4644The figure below shows an experimenter adding resources from two different aggregates to her slice using the Allocate call of the GENI AM API.
     
    5149= Tying this all together: The GENI Experimenter Workflow =
    5250
    53 The following is the workflow for a typical GENI experiment.  The objective here is to show how the concepts described above tie together; this is not intended to be a complete description of the GENI experimenter workflow.  In this workflow, the experimenter:
    54   1. Requests an account at the [wiki:GENIConcepts#TheGENIPortal GENI Portal].
    55   2. Joins an existing [wiki:GENIConcepts#Project project] on the portal or creates a new project.  Only faculty and senior technical staff can create projects.
     51The following is the workflow for a typical GENI experiment.  The objective here is to show how the concepts described above tie together; this is not intended to be a complete description of the GENI experimenter workflow.  The experimenter in this workflow uses the [https://portal.geni.net ''GENI Portal''], a web-based tool for experimenters to create accounts, projects and slices and to manage project and slice memberships.
     52  1. Requests an account at the GENI Portal.
     53  2. Joins an existing [wiki:GENIConcepts#Project project] on the portal or creates a new project.  Only faculty and senior technical staff with project-lead privileges can create projects.
    5654  3. Creates a [wiki:GENIConcepts#Slice slice].
    5755  4. Decides what resources she needs and the [wiki:GENIConcepts#AggregatesandResources aggregates] from which she will get these resources.