Revision b9954290 README.md

View differences:

README.md
120 120
in the moment the `gen-rspec.py` command is executed. For this reason the
121 121
suggested best practice is to execute `gen-rspec.py` just before allocating the
122 122
resources using the `reserve.py` command.
123

  
124
## Generating SSH and Ansible config
125

  
126
After generating the `rspec` file, the `gen-config.py` script can generate
127
the SSH and the ansible configuration files to access the nodes of the
128
testbeds. To do so, simply run:
129

  
130
```
131
./gen-config.py -r <rspec file> -k <identity file>
132
```
133

  
134
The identity file is the private key or the certificate obtained after getting
135
an account from the [iMinds authority](https://authority.ilabt.iminds.be/).
136

  
137
This will generate:
138
* `ssh-config`: the configuration file to be given to the SSH command (e.g.,
139
  `ssh -F ssh-config ...`). This defines the names of the hosts as `node<i>`,
140
  for `i` going from 0 to N-1. To connect to one host, you can thus run
141
  `ssh -F ssh-config node0`.
142
* `ansible.cfg`: the Ansible configuration file.
143
* `ansible-hosts`: the Ansible inventory (list of nodes). In this file the
144
  group of nodes reserved for the experiments is named `nodes`. To test that
145
  this is properly working, try with `ansible nodes -m shell -a "uptime"`.
146

  
147
The filename of the configuration files can be changed via command line
148
arguments (see `./gen-config.py --help`).

Also available in: Unified diff