Changes between Version 18 and Version 19 of FeddUsersGuide


Ignore:
Timestamp:
Jun 9, 2014 4:12:46 PM (10 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FeddUsersGuide

    v18 v19  
    417417}}}
    418418
    419 where {{{$EXPNAME}}} is replaced with a short mnemonic name for the combined experiment and {{{$MGMT_IP}}} is the external management IP of the node running the federation software.
     419where {{{$EXPNAME}}} is replaced with a short mnemonic name for the combined experiment and {{{$MGMT_IP}}} is the IP address of the node running the federation software.  You can use its DNS name as well.
    420420
    421421When that returns, it will return something like:
    … …  
    427427}}}
    428428
    429 DETER is coordinating between its local federation controllers and the one running on the ExoGENI node, allocating resources, and stitching them.  You can check the status using the {{{fedd_multistatus.py}}} command:
    430 
    431 {{{
    432 users:~$ fedd_multistatus.py
    433 faber-smart5:2b7b6852a2db53d3e77431937e1da01d8fbf335d:active
    434 faber-smart1:9a57f78345e04136e8696a3439b476f3bc2f444d:failed
    435 faber-smart2:7afc1dbbc29b6c7f46128d6dc0502136a95cb6cf:starting
    436 }}}
    437 
    438 That output shows three federated experiments.  The experiments are:
    439 
    440  * faber-smart5 which can be accessed and used for experimentation
    441  * faber-smart1 which failed and cannot be accessed
    442  * faber-smart2 which is in the process of being created.  It will eventually transition to active or failed.
    443 
    444 An experimenter can poll using {{{fedd_multistatus.py}}} or watch the debugging log using {{{fedd_spewlog.py}}}.  The second looks like (where $EXPNAME is faber-smart5):
    445 
    446 {{{
    447 users:~$ fedd_spewlog.py --experiment_name $EXPNAME
    448 03 Mar 14 16:46:50 fedd.experiment_control.faber-smart5 Calling StartSegment at https://192.1.242.14:23231
    449 03 Mar 14 16:46:50 fedd.experiment_control.faber-smart5 Calling StartSegment at https://users.isi.deterlab.net:23231
    450 Allocatation complete03 Mar 14 16:47:50 fedd.experiment_control.faber-smart5 Waiting for sub threads (it has been 1 mins)
    451 03 Mar 14 16:48:50 fedd.experiment_control.faber-smart5 Waiting for sub threads (it has been 2 mins)
    452 03 Mar 14 16:46:52 fedd.access.faber-smart5 State is none
    453 03 Mar 14 16:46:52 fedd.access.faber-smart5 [make_null_experiment]: Creating experiment
    454 03 Mar 14 16:47:14 fedd.access.faber-smart5 [make_null_experiment]: Create succeeded
    455 03 Mar 14 16:47:14 fedd.access.faber-smart5 [start_segment]: creating script file
    456 03 Mar 14 16:47:14 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/tmpFlZEWb faber@users.isi.deterlab.net:tmpFlZEWb
    457 03 Mar 14 16:47:14 fedd.access.faber-smart5 [ssh_cmd]: /usr/bin/ssh -n -o 'IdentitiesOnly yes' -o 'StrictHostKeyChecking no' -o 'ForwardX11 no' -i /usr/local/etc/fedd/deter/fedd_rsa faber@users.isi.deterlab.net sh -x tmpFlZEWb
    458 03 Mar 14 16:47:14 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/fedgw_rsa.pub faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/fedgw_rsa.pub
    459 03 Mar 14 16:47:15 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/fedgw_rsa faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/fedgw_rsa
    460 03 Mar 14 16:47:15 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/hosts faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/hosts
    461 03 Mar 14 16:47:15 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/ca.pem faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/ca.pem
    462 03 Mar 14 16:47:16 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/node.pem faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/node.pem
    463 03 Mar 14 16:47:16 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/deterdesktoptunnel0.gw.conf faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/deterdesktoptunnel0.gw.conf
    464 03 Mar 14 16:47:16 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/client.conf faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/client.conf
    465 03 Mar 14 16:47:17 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/experiment.tcl faber@users.isi.deterlab.net:/proj/DeterTest/exp/faber-smart5/tmp/experiment.tcl
    466 03 Mar 14 16:47:17 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/software/fedkit.tgz faber@users.isi.deterlab.net:/proj/DeterTest/software//faber-smart5/fedkit.tgz
    467 03 Mar 14 16:47:18 fedd.access.faber-smart5 [scp_file]: /usr/bin/scp -o IdentitiesOnly yes -o StrictHostKeyChecking no -o ForwardX11 no -i /usr/local/etc/fedd/deter/fedd_rsa /tmp/access-8Yev3U/software/seer-fbsd71-current.tgz faber@users.isi.deterlab.net:/proj/DeterTest/software//faber-smart5/seer-fbsd71-current.tgz
    468 03 Mar 14 16:47:18 fedd.access.faber-smart5 [modify_exp]: Modifying faber-smart5
    469 03 Mar 14 16:47:35 fedd.access.faber-smart5 [modify_exp]: Modify succeeded
    470 03 Mar 14 16:47:35 fedd.access.faber-smart5 [swap_exp]: Swapping faber-smart5 in
    471 03 Mar 14 16:49:46 fedd.access.faber-smart5 [swap_exp]: Swap succeeded
    472 03 Mar 14 16:49:46 fedd.access.faber-smart5 [get_mapping] Generating mapping
    473 03 Mar 14 16:49:47 fedd.access.faber-smart5 Node mapping complete
    474 03 Mar 14 16:49:47 fedd.access.faber-smart5 Link mapping complete03 Mar 14 16:49:48 fedd.experiment_control.faber-smart5 [start_segment]: Experiment faber-smart5 active
    475 active
    476 }}}
    477 
    478 The {{{--experiment_name}}} parameter is the same as on the {{{fedd_create.py}}} command, or selected from {{{fedd_multistatus.py}}} output.
    479 
    480 The {{{fedd_spewlog.py}}} command prints changes to the log as they appear and terminates when the experiment transitions to either active or failed state.
     429DETER is coordinating between its local federation controllers and the one running on the desktop node, allocating resources, and stitching them.  You can check the status same commands we used above.
     430
    481431
    482432=== Interacting with the Experiment ===
    … …  
    484434Once an experiment is active, it completes stitching itself together and a user can log in to the various nodes using the native testbed mechanisms.  That stitching may take a minute or two after the federation system declares the experiment active.  Additionally it may take the dynamic routing some time to converge, depending on the complexity of the topology.
    485435
    486 Inside the DETER experiment, one can log into the nodes and interact with them by node name as usual.  Details are [https://trac.deterlab.net/wiki/Tutorial/UsingNodes here].  With node b on ExoGENI and a on DETER, as shown above, this sequence shows the transparent connection.  A user logs into node a in the local experiment (experiment faber-smart5 in in project detertest) and pings node b from node a.
     436Inside the DETER experiment, one can log into the nodes and interact with them by node name as usual.  Details are [https://trac.deterlab.net/wiki/Tutorial/UsingNodes here].  With node b on the desktop and a on DETER, as shown above, this sequence shows the transparent connection.  A user logs into node a in the local experiment (experiment faber-smart5 in in project detertest) and pings node b from node a.
    487437
    488438{{{
    … …  
    494444}}}
    495445
    496 While for all intents and purposes, b (in ExoGENI) is part of the experiment, the long ping times make it easy to identify:
     446While for all intents and purposes, b (the desktop) is part of the experiment, the long ping times make it easy to identify:
    497447
    498448{{{
    … …  
    503453}}}
    504454
    505 Similarly, one can log into the ExoGENI node and see the DETER nodes by the same names:
     455Similarly, one can log into the desktop VM node and see the DETER nodes by the same names:
    506456
    507457{{{
    … …  
    512462}}}
    513463
    514 It may be surprising, but the ExoGENI node can route to nodes throughout our multi-hop DETER topology:
     464It may be surprising, but the desktop node can route to nodes throughout our multi-hop DETER topology:
    515465
    516466{{{
    … …  
    521471}}}
    522472
    523 The federated experiment in DETER runs [http://en.wikipedia.org/wiki/Ospf ospf] on each node, and fedd.py starts an ospf daemon on the ExoGENI node as well.  The ExoGENI node simply discovers the routing table from that connection.  We will show how to expolit this connection to interconnect more interesting topologoes.
     473The federated experiment in DETER runs [http://en.wikipedia.org/wiki/Ospf ospf] on each node, and fedd.py starts an ospf daemon on the desktop VM node as well.  The desktop simply discovers the routing table from that connection.  We will show how to expolit this connection to interconnect more interesting topologoes.
    524474
    525475=== Tearing The Experiment Down ===
    526476
    527 To tear down the experiment, use the command:
     477To tear down the experiment, use the same {{{fedd_terminate.py}}} command as before.
    528478
    529479{{{
    … …  
    531481}}}
    532482
    533 This releases the DETER resources and disconnects the ExoGENI node.  The ExoGENI slice remains intact and can be connected to another DETER experiment.
    534 
    535 If an experimenter tears down the ExoGENI slice before the {{{fedd_terminate.py}}} command is issued, or there is some other problem, the {{{--force}}} flag can be given to make {{{fedd_terminate.py}}} purge all state that the federation system can reach.
    536 
    537 == A More Complex ExoGENI Topology ==
     483This releases the DETER resources and disconnects the desktop node. 
     484
     485If an experimenter tears down the desktop VM before the {{{fedd_terminate.py}}} command is issued, or there is some other problem, the {{{--force}}} flag can be given to make {{{fedd_terminate.py}}} purge all state that the federation system can reach.
     486
     487== A More Complex Desktop Topology ==
    538488
    539489To connect a more complex ExoGENI topology, we look at routing from a two-node ExoGENI world into the same DETER topology.  The ExoGENI topology looks like this: