Changes between Version 5 and Version 6 of GENIGlossary


Ignore:
Timestamp:
01/23/14 14:08:49 (5 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIGlossary

    v5 v6  
    55'''Opt-in User:'''  A person or organization that makes an explicit choice to participate in a GENI experiment.  For example, a person may opt-in to an experiment by choosing to use a service offered by the experiment.  A campus may opt-in to an experiment by making select campus network traffic available to the experiment.  The experimenter is responsible for informing the opt-in user of any risks associated with participating in the experiment and the user must have to take an explicit action to participate.  It must be easy for an opt-in user to terminate participation in an experiment.
    66
    7 '''Project:''' A project organizes research in GENI, containing both people and their experiments. A project is led by a single responsible individual: the project lead. Many GENI experimenters may be members of a given project, and may be members of multiple projects. Experimenters can create slices and perform experiments in the context of a project. A GENI slice belongs to a single project. Project names are public, global and permanent; there can only ever be a single project with a given name, and that name is visible to all registered users.
     7'''Project:''' A project organizes research in GENI, containing both people and their experiments. A project is led by a single responsible individual: the project lead. Many GENI experimenters may be members of a given project, and may be members of multiple projects. Experimenters can create slices and perform experiments in the context of a project. A GENI slice belongs to a single project. Project names are public, global and permanent; there can only ever be a single project with a given name, and that name is visible to all registered users. For more information on Project Roles/privileges, see [wiki:ProjectSlicesRoles here.]
    88
    9 '''Project Lead:''' A principal investigator, professor or lead researcher that manages a set of experiments and associated research staff. The project lead is ultimately accountable for any operations taken on resources associated with slices of the given project.
     9'''Project Lead:''' A principal investigator, professor or lead researcher that manages a set of experiments and associated research staff. The project lead is ultimately accountable for any operations taken on resources associated with slices of the given project. For more information on Project Roles/privileges, see [wiki:ProjectSlicesRoles here.]
    1010
    1111'''Renewal:''' Slices and slivers are created with a particular expiration time, which is aggregate-specific. An experimenter may request that the expiration time be extended by a renewal request. Once the expiration time of a given slice or sliver has passed, however, these elements can no longer be renewed and may be reclaimed by GENI.
     
    1313'''RSpec:''' Resources in GENI are described in XML files called [wiki:GENIExperimenter/RSpecs Resource Specifications (RSpecs)]. Aggregate resource listings (advertisements), reservation requests, and manifests of resources you have reserved are all represented as RSpecs.
    1414
    15 '''Slice:''' A slice is the context for a particular set of experiments, and contains reserved resources and the set of GENI users ('members') who are entitled to act on those resources. A slice belongs to a single project, and can have multiple members. Experimenters can add and delete resources from a slice.
     15'''Slice:''' A slice is the context for a particular set of experiments, and contains reserved resources and the set of GENI users ('members') who are entitled to act on those resources. A slice belongs to a single project, and can have multiple members. Experimenters can add and delete resources from a slice. 
    1616
    1717'''Slice Credential:''' A signed statement from a GENI federation slice authority indicating that a given experimenter has particular rights to operate on a given slice. Such credentials have a specified expiration date. Aggregates receiving the credential will authorize operations only as permitted by the credential and only for the life of the credential.
    1818
    19 '''Slice Member:''' Many experimenters may view or act on a slice. Each experimenter with such privileges is said to be a 'member' of the slice. Experimenters must be a member of the project containing the slice before they can be a member of the slice. Within the slice, experimenters may have varying permissions, including having read-only access to the slice.
     19'''Slice Member:''' Many experimenters may view or act on a slice. Each experimenter with such privileges is said to be a 'member' of the slice. Experimenters must be a member of the project containing the slice before they can be a member of the slice. Within the slice, experimenters may have varying permissions, including having read-only access to the slice. For more information on Slice Roles/privileges, see [wiki:ProjectSlicesRoles here.]
    2020
    2121'''Sliver:''' A Sliver is one or more resources provided by an aggregate, whether virtual or whole ('bare metal'). Slivers are created and added to Slices through calls to the Aggregate Manager API at aggregates. Slivers are isolated from other slivers on the same resources.