Changes between Version 1 and Version 2 of NewContainersAPISpec


Ignore:
Timestamp:
Jun 29, 2013 8:46:51 AM (11 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • NewContainersAPISpec

    v1 v2  
    99Each of these is sent to a container controller with a distinct address.  A controller is often responsible for more than one container.  In general we attempt to scale the number of controllers with the number of physical resources so that the testbed can communicate with them directly.  In very large testbeds, there may be interconnected controllers acting as relays.
    1010
     11The operations in this section are all exported from the container controller.  The testbed discovers container controllers when they report in using the operation in the following section.
     12
    1113All the control commands can be applied to multiple containers simultaneously.
    1214
    … …  
    1719 * '''Service:''' Containers
    1820 * '''Operation:''' start
    19  * '''Input Parameters:'''
    2021 * '''Input Parameters:'''
    2122   * NameRE - an optional list of regular expressions to match against container names
    … …  
    5152 * '''Operation:''' describe
    5253 * '''Input Parameters:'''
    53  * '''Input Parameters:'''
    5454   * NameRE - an optional list of regular expressions to match against container names
    5555   * Types - a list of container types to restrict the operations to
    … …  
    6161   * Interfaces - a list of pre-defined extension interfaces supported by the container.  If "custom" is given ExtendedOps is required
    6262   * ExtendedOps - an optional list of URIs from which the WSDL for custom extended operations can be gathered
     63
     64Get the state of containers
     65
     66 * '''Service:''' Containers
     67 * '''Operation:''' state
     68 * '''Input Parameters:'''
     69   * NameRE - an optional list of regular expressions to match against container names
     70   * Types - a list of container types to restrict the operations to
     71 * '''Return Values:'''
     72  * a list of fields of the form
     73    * Names - an array of container names
     74    * State - a string giving the state
     75      * Down - The container is in communication with the testbed, but not yet configured to act as an experiment element
     76      * Configured - The container is set up to act as an experiment element but is not yet doing so
     77      * Pinned - The container is not acting as an experiment element, but is carrying out an operation that renders it otherwise unusable. For example, a container that is capturing its state may be in this state.
     78      * Up - The container is acting as an experiment element
     79      * None - Nothing is known about the container. is is (as yet) unresponsive.
     80
     81== Containers to Testbed Operations ==
     82
     83A container controller can report a state change to the testbed using the call
     84
     85 * '''Service:''' Containers
     86 * '''Operation:''' newState
     87 * '''Input Parameters:'''
     88   * Controller - the URI of the container controller reporting
     89   * Names - an array of container names
     90   * State - a string giving the state, as in state above
     91
     92As containers are initialized, controllers will check in with the testbed using this call.