... | @@ -182,8 +182,8 @@ memory, and compare it with the node's capacity: |
... | @@ -182,8 +182,8 @@ memory, and compare it with the node's capacity: |
|
|
|
|
|
watch -n5 -d 'gnt-instance list -o pnode,name,be/vcpus,be/memory,disk_usage,disk_template,status | sort; echo; gnt-node list'
|
|
watch -n5 -d 'gnt-instance list -o pnode,name,be/vcpus,be/memory,disk_usage,disk_template,status | sort; echo; gnt-node list'
|
|
|
|
|
|
The latter does not show disk usage for secondary volume groups, for a
|
|
The latter does not show disk usage for secondary volume groups (see
|
|
complete picture of disk usage, use:
|
|
[upstream issue 1379](https://github.com/ganeti/ganeti/issues/1379)), for a complete picture of disk usage, use:
|
|
|
|
|
|
gnt-node list-storage
|
|
gnt-node list-storage
|
|
|
|
|
... | @@ -802,7 +802,10 @@ above case: |
... | @@ -802,7 +802,10 @@ above case: |
|
It's also possible to use the `--no-disk-moves` option to avoid disk
|
|
It's also possible to use the `--no-disk-moves` option to avoid disk
|
|
move operations altogether.
|
|
move operations altogether.
|
|
|
|
|
|
Both workarounds obviously do not correctly balance the cluster...
|
|
Both workarounds obviously do not correctly balance the
|
|
|
|
cluster... Note that we have also tried to use `htools:migration` tags
|
|
|
|
to workaround that issue, but [those do not seem to work correctly
|
|
|
|
either](https://github.com/ganeti/ganeti/issues/1497).
|
|
|
|
|
|
## Adding and removing addresses on instances
|
|
## Adding and removing addresses on instances
|
|
|
|
|
... | | ... | |