Changes between Version 8 and Version 9 of GeniGlossary


Ignore:
Timestamp:
03/14/08 03:01:06 (16 years ago)
Author:
Mike Patton
Comment:

Copied some more definitions from GDD-06-35

Legend:

Unmodified
Added
Removed
Modified
  • GeniGlossary

    v8 v9  
     1 Active Sliver::
     2  A ''sliver'' that supports user-installed code.
     3
    14 Aggregate::
    25  An ''aggregate'' is an object representing a group of components, where a given component can belong to zero, one, or more aggregates.  Aggregates can be hierarchical, meaning that an aggregate can contain either components or other aggregates. Aggregates provide a way for users, developers, or administrators to view a collection of GENI nodes together with some software-defined behavior as a single identifiable unit. Generally aggregates export at least a component interface‚ i.e., they can be addressed as a component‚ although aggregates may export other interfaces, as well. Aggregates also may include (controllable) instrumentation and make measurements available. This document makes broad use of aggregates for operations and management.  Internally, these aggregates may use any O&M systems they find useful.
     
    69
    710 Components::
    8   ''Components'' are the primary building block of the architecture. For example, a component might correspond to an edge computer, a customizable router, or a programmable access point.  A component encapsulates a collection of resources, including physical resources (e.g., CPU, memory, disk, bandwidth) logical resources (e.g., file descriptors, port numbers), and synthetic resources (e.g., packet forwarding fast paths). These resources can be contained in a single physical device or distributed across a set of devices, depending on the nature of the component.
     11  ''Components'' are the primary building block of the architecture. For example, a component might correspond to an edge computer, a customizable router, or a programmable access point.  A component encapsulates a collection of resources, including physical resources (e.g., CPU, memory, disk, bandwidth) logical resources (e.g., file descriptors, port numbers), and synthetic resources (e.g., packet forwarding fast paths). These resources can be contained in a single physical device or distributed across a set of devices, depending on the nature of the component.  Each component runs a component manager that implements a well-defined interface for the component.  In addition to describing physical devices, components may be defined that represent logical devices as well.
     12
     13 Component Manager::
     14  The entity responsible for allocating resources at a component.  It exports a standard interface defined in the GENI architecture document.  That interface is also exported by aggregates.  Though it is intuitive to think of the component manager residing on the component it manages, this is not necessarily the case.
     15
     16 Component Registry:: A registry that maps between a component name, e.g. `geni.us.princeton.component` and a GENI Global Identifier. Components and aggregates share a name space, so a component registry maps aggregate names to GGIDs as well.
    917
    1018 Experiment::
     
    1422  Resource ''federation'' permits the interconnection of independently owned and autonomously administered facilities in a way that permits owners to declare resource allocation and usage policies for substrate facilities under their control, operators to manage the network substrate, and researchers to create and populate slices, allocate resources to them, and run experiment-specific software in them.
    1523
     24 GENI Global Identifier (GGID)::
     25  Unambiguous, certified unique identifiers assigned to GENI objects.  Specifically these are assigned to users, components, and slices. A GGID consists of an X.509 certificate that binds a UUID to a public key.
     26
     27 Internet eXchange Point (IXP):: A facility where Internet networks exchange traffic.  GENI will connect to the commodity Internet at one or more IXPs.  This allows GENI services to be accessed by Internet users via user opt-in.
     28
     29 IXP:: Internet eXchange Point
     30
    1631 Management Authority::
    1732  A ''management authority (MA)'' is responsible for some subset of substrate components: providing operational stability for those components, ensuring the components behave according to acceptable use policies, and executing the resource allocation wishes of the component owner.  (Note that management authorities potentially conflate owners and operators. In some cases, an MA will correspond to a single organization in which case the owner and operator are likely the same. In other cases, the owner and operator are distinct, with the former establishing a “management agreement” with the latter.)
     33
     34 O&M:: Operations and Management
    1835
    1936 Owner::
     
    2441
    2542 Resource::
    26   ''Resources'' are abstractions of the sharable features of a component that are allocated by a component manager and described by an RSpec. Resources are divided into computation, communication, measurement, and storage.  Resources can be contained in a single physical device or distributed across a set of devices, depending on the nature of the component.
     43  ''Resources'' are abstractions of the sharable features of a component that are allocated by a component manager and described by an RSpec. Resources are divided into computation, communication, measurement, and storage.  Resources can be contained in a single physical device or distributed across a set of devices, depending on the nature of the component.
     44
     45 Resource Specification (RSpec)::
     46  Represents all GENI resources that can be bound to a sliver within GENI.  An rspec describes both the resources available, advertised or allocated at a component and the relationships between those resources, and perhaps other resources in GENI.
    2747
    2848 Sharing::
     
    3252  From a researcher's perspective, a ''slice'' is a substrate-wide network of computing and communication resources capable of running an experiment or a wide-area network service.  From an operator's perspective, slices are the primary abstraction for accounting and accountability—resources are acquired and consumed by slices, and external program behavior is traceable to a slice, respectively.  A slice is the basis for resource revocation (i.e., shutdown).  A slice is defined by a set of slivers spanning a set of network components, plus an associated set of users that are allowed to access those slivers for the purpose of running an experiment on the substrate. That is, a slice has a name, which is bound to a set of users associated with the slice and a (possibly empty) set of slivers.
    3353
     54 Slice Authority (SA):: Entity responsible for the behavior of some set of slices. Participates in the slice naming hierarchy.
     55
    3456 Slivers::
    3557  It must be possible to share component resources among multiple users. This can be done by a combination of virtualizing the component (where each user acquires a virtual copy of the component's resources), or by partitioning the component into distinct resource sets (where each user acquires a distinct partition of the  component's resources). In both cases, we say the user is granted a ''sliver'' of the component. Each component must include hardware or software mechanisms that isolate slivers from each other, making it appropriate to view a sliver as a “resource container.”
     
    3759 Substrate::
    3860  GENI provides a set of physical facilities (e.g., routers, processors, links, wireless devices), which we refer to as the ''substrate''. The design of this substrate is concerned with ensuring that physical resources, layout, and interconnection topology are sufficient to support GENI’s research objectives.
     61
     62 Ticket::
     63  Signed data structure issued by a component or aggregate that guarantees the availability of a given set of resources.  The ticket may have time or other constraints.  Tickets are redeemed to create slivers.
    3964
    4065 User Opt-In::