Changes between Version 9 and Version 10 of OldFeddAbout


Ignore:
Timestamp:
Nov 6, 2009 5:04:27 PM (14 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OldFeddAbout

    v9 v10  
    3131[[Image(Full-Fed-Arch-New-tvf-small.png)]]
    3232
    33 Fedd plays the role of the Federator in the diagram above.
     33Fedd plays the role of the Federator in the diagram above.  It is divided into two parts:
     34
     35 '''Experiment controller'''::
     36  Presents the abstraction of a federated experiment to the users.  Allows allocation, configuration, and release of resources to the federated experiment.
     37 '''Access Controller'''::
     38  Negotaties access and allocation of resources from federant testbeds.
     39
     40The access controller is depicted by the regular plug-in shapes in the federator.  These are standard plug-in interfaces that allow standard access to a variety of testbed types.  Currently emulab style testbeds and DRAGON style transit networks are supported.  The regular system interface to fedd allows new systems to be added easily.
     41
     42Depending on the nature of the access controller it may be implemented on the local testbed, on the same host as the experiment controller (even in the same process) or partially in both places.  This depends on the access mechanisms of the underlying testbed and the policies of the administrators.  We have implemented plugins for Emulab-style testbeds that run completely remotely and access the testbed through ssh and plug-ins that run on the Emulab testbed directly and communicate outside the testbed entirely through fedd interfaces.  Access controllers that run directly on the remote testbed have more discretion in executing privledged local commands than remote access controllers.
    3443
    3544= Fedd: The DETER Federation Daemon =
    3645
    37 Fedd is the daemon process responsible for:
    38 
    39  * Creating and terminating federated experiments
    40  * Requesting access to remote resources on an experimenter's behalf
    41  * Granting access to local resources based on the testbed's policy
     46Fedd is the name for the codebase that supports both the access controller and experiment controller function.  Generally any instance of fedd will be acting as either an experiment controller or an access controller.  We continue to move toward reflecting the distinction in function in the codebase, but this is not complete.
    4247
    4348Generally fedd is configured by the testbed's administration to allow