... | ... | @@ -824,6 +824,10 @@ that they should be distributed. A special configuration was done, |
|
|
below, to avoid that problem in the future. But as a workaround,
|
|
|
instances can also be moved by hand and the cluster re-balanced.
|
|
|
|
|
|
Also notice that `-X` does not show the job output, use
|
|
|
`ganeti-watch-jobs` for that, in another terminal. See the [job
|
|
|
inspection](#Job-inspection) section for more details on that.
|
|
|
|
|
|
### Redundant instances distribution
|
|
|
|
|
|
Some instances are redundant across the cluster and should *not* end up
|
... | ... | @@ -946,6 +950,24 @@ IP. You can still do so with: |
|
|
|
|
|
gnt-instance modify --net -1:add,ip=116.202.120.174,network=gnt-fsn test01.torproject.org
|
|
|
|
|
|
## Job inspection
|
|
|
|
|
|
Sometimes it can be useful to look at the active jobs. It might be,
|
|
|
for example, that another user has queued a bunch of jobs in another
|
|
|
terminal which you do not have access to, or some automated process
|
|
|
did (Nagios, for example, runs `gnt-cluster verify` once in a
|
|
|
while). Ganeti has this concept of "jobs" which can provide
|
|
|
information about those.
|
|
|
|
|
|
The command `gnt-job list` will show the entire job history, and
|
|
|
`gnt-job list --running` will show running jobs. `gnt-job watch` can
|
|
|
be used to watch a specific job.
|
|
|
|
|
|
We have a wrapper called `ganeti-watch-jobs` which automatically shows
|
|
|
the output of whatever job is currently running and exits when all
|
|
|
jobs complete. This is particularly useful while [rebalancing the
|
|
|
cluster](#Rebalancing-a-cluster) as `hbal -X` does not show the job output...
|
|
|
|
|
|
## Pager playbook
|
|
|
|
|
|
### I/O overload
|
... | ... | |