Revision f313e7be doc/admin.rst
b/doc/admin.rst | ||
---|---|---|
181 | 181 |
internall by Ganeti as an *OpCode* (abbreviation from operation |
182 | 182 |
code). These OpCodes are executed as part of a *Job*. The OpCodes in a |
183 | 183 |
single Job are processed serially by Ganeti, but different Jobs will be |
184 |
processed (depending on resource availability) in parallel. |
|
184 |
processed (depending on resource availability) in parallel. They will |
|
185 |
not be executed in the submission order, but depending on resource |
|
186 |
availability, locks and (starting with Ganeti 2.3) priority. An earlier |
|
187 |
job may have to wait for a lock while a newer job doesn't need any locks |
|
188 |
and can be executed right away. Operations requiring a certain order |
|
189 |
need to be submitted as a single job, or the client must submit one job |
|
190 |
at a time and wait for it to finish before continuing. |
|
185 | 191 |
|
186 | 192 |
For example, shutting down the entire cluster can be done by running the |
187 | 193 |
command ``gnt-instance shutdown --all``, which will submit for each |
Also available in: Unified diff