Changes between Version 3 and Version 4 of DesktopExoGeni


Ignore:
Timestamp:
Mar 3, 2014 4:42:21 PM (5 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DesktopExoGeni

    v3 v4  
    2626In addition, users will need to get ther DETER accounts authorized to create federated experiments.  DETER administration controls this facility because it allows users to reach outside DETER, which we normally do not allow.  To get an account authorized for federation, contact [mailto:faber@isi.edu].
    2727
     28== Connecting a Single ExoGENI node to a DETER Experiment ==
     29
     30The simplest form of lightweight federation is to conect a single ExoGNEI node to a deter experiment.  We do this by creating a single-node ExoGENI slide that runs teh federation software and connecting a DETER experiment to it when that experiment is created.
     31
     32To create the single-node ExoGENI experiment, create one a single node slide using the federation image above.  When the slice exists, log in to the node and configure the federation software.  To do that the experimenter needs to know the two facts above.
     33
     34The image provides a script to set up a single node for federation.  The script and the federation configuration both are stored in the {{{/usr/local/etc/fedd}}} directory.  To configure the federation system, log into the node, change directory to {{{/usr/local/etc/fedd}}} and run the {{{init_fedd}}} script there.  It takes 2 parameters, the management IP address and the experimenter to authorize.  The following sequence will configure fedd to allow user "faber" to contact DETER using IP address 192.1.242.14:
     35
     36{{{
     37~# cd /usr/local/etc/fedd
     38/usr/local/etc/fedd# ./init_fedd 192.1.242.14 faber
     39}}}
     40
     41When that script completes, start the federation system on the ExoGENI node.  When debugging we recommend leaving a window open and running the daemon as:
     42
     43{{{
     44# fedd.py --config /usr/local/etc/fedd/desktop.config --debug
     45}}}
     46
     47You can also run it in the background, logging to {{{/var/log/fedd.log}}} by:
     48
     49{{{
     50# touch /var/log/fedd.log
     51# fedd.py --config /usr/local/etc/fedd/desktop.config --logfile /var/log/fedd.log &
     52}}}
     53
     54There are some detailed debugging messages that libraries and other dependent software produce that are visible with {{{--debug}}} that are lost during normal logging.
     55