Revision edc282ad doc/admin.rst
| b/doc/admin.rst | ||
|---|---|---|
| 287 | 287 |
|
| 288 | 288 |
gnt-instance startup INSTANCE_NAME |
| 289 | 289 |
|
| 290 |
While the command to stop one is:: |
|
| 290 |
Note, that this will not work when an instance is in a permanently |
|
| 291 |
stopped state ``offline``. In this case, you will first have to |
|
| 292 |
put it back to online mode by running:: |
|
| 293 |
|
|
| 294 |
gnt-instance modify --online INSTANCE_NAME |
|
| 295 |
|
|
| 296 |
The command to stop the running instance is:: |
|
| 291 | 297 |
|
| 292 | 298 |
gnt-instance shutdown INSTANCE_NAME |
| 293 | 299 |
|
| 300 |
If you want to shut the instance down more permanently, so that it |
|
| 301 |
does not require dynamically allocated resources (memory and vcpus), |
|
| 302 |
after shutting down an instance, execute the following:: |
|
| 303 |
|
|
| 304 |
gnt-instance modify --ofline INSTANCE_NAME |
|
| 305 |
|
|
| 294 | 306 |
.. warning:: Do not use the Xen or KVM commands directly to stop |
| 295 | 307 |
instances. If you run for example ``xm shutdown`` or ``xm destroy`` |
| 296 | 308 |
on an instance Ganeti will automatically restart it (via |
Also available in: Unified diff