User Tools

Site Tools


scenario_file_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
scenario_file_format [2019/11/28 16:22] – [Grammar] mimbertscenario_file_format [2019/12/03 11:05] mimbert
Line 12: Line 12:
 ====== Grammar ====== ====== Grammar ======
  
-We're progressively adding new capabilities to the CorteXlab platform. There is now two different syntaxes for the scenario file, the legacy syntax, where commands are run on the nodes, and the new syntax, where docker containers are run on the nodes. Both syntaxes are allowed, even in the same scenario, but only one syntax is allowed per-node.+We're progressively adding new capabilities to the CorteXlab platform. There is now two different syntaxes for the scenario file, the legacy syntax, where commands are run on the nodes, and the new syntax, where [[docker|docker]] containers are run on the nodes. Both syntaxes are allowed, even in the same scenario, but only one syntax is allowed per-node.
  
 The scenario.yaml file is structured as follows: The scenario.yaml file is structured as follows:
Line 21: Line 21:
       * which //MUST// contain **//ONLY ONE//** of the following:       * which //MUST// contain **//ONLY ONE//** of the following:
         * **(new syntax)** a ''container'' key, value pair, whose value is a mapping with the following key, value pairs:         * **(new syntax)** a ''container'' key, value pair, whose value is a mapping with the following key, value pairs:
-          * ''image'' //MANDATORY// a string, the docker image name+          * ''image'' //MANDATORY// a string, the name of the docker image, which must be accessible on a public docker repository (such as the docker hub). See [[docker images]]
           * ''command'' //OPTIONAL// a string, the command to run in the container, which overrides the image default command (see https://docs.docker.com/engine/reference/run/#cmd-default-command-or-options https://docs.docker.com/engine/reference/builder/#cmd)           * ''command'' //OPTIONAL// a string, the command to run in the container, which overrides the image default command (see https://docs.docker.com/engine/reference/run/#cmd-default-command-or-options https://docs.docker.com/engine/reference/builder/#cmd)
           * ''exec'' //OPTIONAL// a string or array of strings: additionnal commands which are executed in the container (see https://docs.docker.com/engine/reference/commandline/exec/)           * ''exec'' //OPTIONAL// a string or array of strings: additionnal commands which are executed in the container (see https://docs.docker.com/engine/reference/commandline/exec/)
Line 40: Line 40:
   node3:   node3:
     container:     container:
-    - image: m1mbert/cxlb-toolchain:firsttry +    - image: m1mbert/cxlb-gnuradio-3.8:1.0 
-    - image: m1mbert/cxlb-toolchain:firsttry+    - image: m1mbert/cxlb-gnuradio-3.8:1.0
       command: /usr/sbin/sshd -p 2223 -D       command: /usr/sbin/sshd -p 2223 -D
   node4:   node4:
scenario_file_format.txt · Last modified: 2023/08/29 15:29 by cmorin

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki