| 8 | | * To be installed on the Console: Node Handler |
| | 8 | [[BR]] |
| | 9 | [[BR]] |
| | 10 | |
| | 11 | |
| | 12 | === Step 1: Install new Grid Service. === |
| | 13 | |
| | 14 | - Update the current Grid Services for the outdoor testbed with the GS package attached below |
| | 15 | |
| | 16 | - All the services configuration should be the same as before for: cmc, frisbee, inventory, oml2Server, pxe |
| | 17 | |
| | 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). |
| | 19 | |
| | 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. |
| | 21 | |
| | 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'). |
| | 23 | |
| | 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. |
| | 25 | |
| | 26 | - To active the 'result' service: as usual, create symlink '/etc/gridservices2/enabled/result.yaml' pointing to '/etc/gridservices2/available/result.yaml.winlab' |
