Revision 9ed6fcad

View differences:

README.md
64 64
omni: GENI Omni Command Line Aggregate Manager Tool Version 2.11
65 65
Copyright (c) 2011-2016 Raytheon BBN Technologies
66 66
```
67

  
68
## RSPEC generation
69

  
70
RSPEC files (extension .rspec) are XML files that describes which nodes to
71
allocate in a given testbed. For the TWIST and w.iLab1 testbeds the .rspec files
72
can be generated automatically using the `gen-rspec.py` script. The script
73
supports the following command line parameters:
74

  
75
* `-t` (`--testbed`): specifies which testbed the RSPEC will be generated for.
76
  Use twist for the TWIST testbed and wilab for w.iLab1;
77

  
78
* `-f` (`--filter`): comma separated list of node name prefixes. Only the
79
  available nodes whose name starts with one of the specified prefixes are
80
  inserted in the generated RSPEC. By default all the available nodes are used for
81
  generating the RSPEC file.
82

  
83
* `-n` (`--nodes`): comma separated list of node names. Only the available nodes
84
  whose name is listed with the `-n` option are inserted in the RSPEC file. By
85
  default all the available nodes are used. The `-n` option takes precedence over
86
  `-f`.
87

  
88
* `-w` (`--hardware`): comma separated list of hardware types (e.g., `pcgen05`)
89

  
90
For example, an RSPEC containing all the available nodes in the TWIST testbed
91
can be generated with the following command:
92

  
93
```
94
./gen-rspec.py -t twist > twist_all.rspec
95
```
96

  
97
Instead, an RSPEC containing all the nuc nodes in the TWIST testbed can be
98
generated with the following command:
99

  
100
```
101
./gen-rspec.py -t twist -f nuc > twist_nuc.rspec
102
```
103

  
104
An RSPEC containing only nuc4 and nuc6 from the TWIST testbed can be
105
generated with the following command:
106

  
107
```
108
./gen-rspec.py -t twist -n nuc4,nuc6 > twist_nuc_4_6.rspec
109
```
110

  
111
An RSPEC containing nodes of hardware type `pcgen05` from both the
112
VirtualWall1 and the VirtualWall2 testbeds can be generated with the following
113
command:
114

  
115
```
116
./gen-rspec.py -t wall1,wall2 -w pcgen05 > iof.rspec
117
```
118

  
119
Note that, in any case, a node is inserted in the RSPEC only if it is available
120
in the moment the `gen-rspec.py` command is executed. For this reason the
121
suggested best practice is to execute `gen-rspec.py` just before allocating the
122
resources using the `reserve.py` command.

Also available in: Unified diff