Changes between Version 7 and Version 8 of Internal/Presentation/GENIMar09


Ignore:
Timestamp:
Mar 12, 2009, 7:10:10 AM (15 years ago)
Author:
thierry
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/Presentation/GENIMar09

    v7 v8  
    1212=== Step 1: Install new Grid Service. ===
    1313
    14 * Update the current Grid Services for the outdoor testbed with the GS package attached below
     14 * Update the current Grid Services for the outdoor testbed with the GS package attached below
    1515
    16 * All the services configuration should be the same as before for: cmc, frisbee, inventory, oml2Server, pxe
     16 * All the services configuration should be the same as before for: cmc, frisbee, inventory, oml2Server, pxe
    1717
    18 * We now have a new service called 'result' (which allows user to access experiment measurement databases without login to the server hosting that database).
     18 * We now have a new service called 'result' (which allows user to access experiment measurement databases without login to the server hosting that database).
    1919
    20 * The 'result' service needs to be activated on the same server that runs the 'oml2Server' service. Indeed, it will look for the databases that OMLv2 server has created on the disk of that machine.
     20 * The 'result' service needs to be activated on the same server that runs the 'oml2Server' service. Indeed, it will look for the databases that OMLv2 server has created on the disk of that machine.
    2121
    22 * The 'result' service needs 'sqlite3' and 'libsqlite3-ruby1.8' to be installed on that same server as well ('apt-get install sqlite3 libsqlite3-ruby1.8').
     22 * The 'result' service needs 'sqlite3' and 'libsqlite3-ruby1.8' to be installed on that same server as well ('apt-get install sqlite3 libsqlite3-ruby1.8').
    2323
    24 * To configure the 'result' service: configuration file should be '/etc/gridservices2/available/result.yaml.winlab'. This file does not exist in the package at the moment, but there is a 'result.yaml.nicta' which you could use as a template. In fact, you should pretty much be able to use it as is.
     24 * To configure the 'result' service: configuration file should be '/etc/gridservices2/available/result.yaml.winlab'. This file does not exist in the package at the moment, but there is a 'result.yaml.nicta' which you could use as a template. In fact, you should pretty much be able to use it as is.
    2525
    26 * To active the 'result' service: as usual, create symlink '/etc/gridservices2/enabled/result.yaml' pointing to '/etc/gridservices2/available/result.yaml.winlab'
     26 * To active the 'result' service: as usual, create symlink '/etc/gridservices2/enabled/result.yaml' pointing to '/etc/gridservices2/available/result.yaml.winlab'
    2727
    28 * To test the 'result' service: assuming the server name is 'oml' then use 'wget -O - http://oml:5022/result' to get a list of available commands, then call one of these commands with a valid experiment ID.
     28 * To test the 'result' service: assuming the server name is 'oml' then use 'wget -O - http://oml:5022/result' to get a list of available commands, then call one of these commands with a valid experiment ID.
    2929
    30 === Step 1: Install new Node Handler. ===
     30=== Step 2: Install new Node Handler. ===
    3131
     32 * Update the current Node Handler for the outdoor console with the NH package attached below
    3233
     34 * To configure NH:  in '/etc/nodehandler4' create a symlink named 'nodehandler.yaml' to nodehandler.yaml.winlab'
    3335
     36 * If necessary, modify nodehandler.yaml.winlab as you would do for other consoles at winlab.
    3437
     38 * Nothing special (compared to a normal NH upgrade on other winlab testbed) should be done here. By default with 'nodehandler.yaml.winlab, config file, the NH should use Multicast to communicate with the nodes, which is exactly what we want for this demo
    3539
    3640