Software deployment » History » Version 1
Simon Lacroix, 2018-08-15 17:26
| 1 | 1 | Simon Lacroix | h1. Software deployment |
|---|---|---|---|
| 2 | |||
| 3 | This pages presents the requirements of the set of tools that helps to easily configure, launch and run the robots on-board softwares. |
||
| 4 | |||
| 5 | h2. General requirements |
||
| 6 | |||
| 7 | * The tools must be very easy to use |
||
| 8 | * The tools must be very easy to maintain and update |
||
| 9 | * The tools must allow to specify and configure the softwares that will be run |
||
| 10 | * In a second step, the tools will endow means to supervise the execution of scenarios |
||
| 11 | |||
| 12 | h2. General principles |
||
| 13 | |||
| 14 | The following principles take very much after the "dala scripts" (see the git repo: git+ssh://softs.laas.fr/git/robots/dala-scripts.git ), the main file names in this suite are referred to hereafter. |
||
| 15 | |||
| 16 | # A shell script: (see shell-script/start.sh) |
||
| 17 | * sets a series of environment variables required to launch the softwares (in particular, a LOGDIR) |
||
| 18 | * Interprets a configuration file that specifies which softwares must be launched (a software can be a ROS node, a Genom3 module, some utilities -- e.g. redirecting the GPS correction data to the proper device, what else ?) |
||
| 19 | * Properly launches each software -- and warn the user in case launch failed |
||
| 20 | * Redirects standard and error outputs of each software |
||
| 21 | |||
| 22 | A companion shell-scripts terminates "in a clean manner" all the launched softwares |