Changes between Version 2 and Version 3 of FeddInfoOperation


Ignore:
Timestamp:
Nov 16, 2011 5:55:19 PM (12 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddInfoOperation

    v2 v3  
    33The current {{{fedd}}} implementation creates and terminates multi-testbed topologies with minimal facilities for managing the elements that make up the topology.  This page describes the emerging interfaces that will provide information about the resources and their status as well as access to infrastructure-level operations on the elements.
    44
    5 A topology is made up of ''elements'' and ''substrates'' that interconnect them.
     5A topology is made up of ''elements'' and ''substrates'' that interconnect them.  Elements are owned by testbeds, interconnected by substrates that may span testbeds.  Two elements on the same substrate can communicate in some way.  Testbeds, substrates, and elements all support services and operations.  [FeddAbout#ExperimentServices Services] provide features to experimental environments, such as file service and authorization information.  Operations manipulate elements, substrates, testbeds or the services they provide.
    66
    7 == Services and Operations ==
    8 
    9 Testbeds, elements, and
    10 [FeddAbout#ExperimentServices services]
     7Operations and services are discovered through the info interface and manipulated through the operation interface.
    118
    129== Experiment Controller Interfaces ==
     
    1613=== Info Interface ===
    1714
    18 The info interface is broken into three sections, '''Testbed''', '''Element''', and '''Substrate'''.  The '''Testbed''' section tells which testbeds have given elements to the topology.  They are identified by the name the experiment controller knows them by and include the [FeddAbout#ExperimentServices services] used by the testbed and any operations that the testbed supports.
     15The info interface is broken into three sections, '''Testbed''', '''Element''', and '''Substrate'''.  The '''Testbed''' section tells which testbeds have given elements to the topology.  They are identified by the name the experiment controller knows them by and include the [FeddAbout#ExperimentServices services] used by the testbed and any operations that the testbed supports.  Similarly the substrate and element sections describe the current state of the object, the testbed(s) to which it is bound and the services and operations it supports.
    1916
     17The current data returned by the interface includes:
    2018
    21 
     19 * Testbeds
     20   * name
     21   * services (format below)
     22   * operations (format below)
     23 * Elements
     24   * testbed
     25   * local name
     26   * logical/topology name
     27   * status
     28   * services (format below)
     29   * operations (format below)
     30 * Substrates
     31   * testbed(s)
     32   * local name(s)
     33   * logical/topology name
     34   * status
     35   * services (format below)
     36   * operations (format below)