Synnefo » snf-ganeti

    gnt-instance list -oname,admin_ram,sda_size,status,pnode,snodes \

.TH HBAL 1 2009-03-22 htools "Ganeti H-tools"

.BI "[-l" limit "]"

.BI "[-O" name... "]"

.BI "[-m " cluster "]"

.BI "[-i " instances-file "]"

  - percentage of instances living (either as primary or secondary) on

    offline nodes

Except for the N+1 failures and offline instances percentage, we use

the coefficient of variance since this brings the values into the same

unit so to speak, and with a restrict domain of values (between zero

and one). The percentage of N+1 failures, while also in this numeric

range, doesn't actually has the same meaning, but it has shown to work

well.

The offline instances percentage (meaning the percentage of instances

living on offline nodes) will cause the algorithm to actively move

instances away from offline nodes. This, coupled with the restriction

on placement given by offline nodes, will cause evacuation of such

nodes.

.RS

.TP

.B F

a character denoting the status of the node, with '-' meaning an

offline node, '*' meaning N+1 failure and blank meaning a good node

.TP

.B Name

the node name

.TP

.B t_mem

the total node memory

.TP

.B n_mem

the memory used by the node itself

.TP

.B i_mem

the memory used by instances

.TP

.B x_mem

amount memory which seems to be in use but cannot be determined why or

by which instance; usually this means that the hypervisor has some

overhead or that there are other reporting errors

.TP

.B f_mem

the free node memory

.TP

.B r_mem

the reserved node memory, which is the amount of free memory needed

for N+1 compliance

.TP

.B t_dsk

total disk

.TP

.B f_dsk

free disk

.TP

.B pri

number of primary instances

.TP

.B sec

number of secondary instances

.TP

.B p_fmem

percent of free memory

.TP

.B p_fdsk

percent of free disk

.RE

.BI "-O " name

This option (which can be given multiple times) will mark nodes as

being \fIoffline\fR. This means a couple of things:

.RS

.TP

-

instances won't be placed on these nodes, not even temporarily;

e.g. the \fIreplace primary\fR move is not available if the secondary

node is offline, since this move requires a failover.

.TP

-

these nodes will not be included in the score calculation (except for

the percentage of instances on offline nodes)

.RE

.TP

Note that this example are not for the latest version (they don't have

full node data).

.BR hn1 "(1), " hscan "(1), " ganeti "(7), " gnt-instance "(8), "

.BR gnt-node "(8)"

.TH HN1 1 2009-03-22 htools "Ganeti H-tools"

.RS

.TP

.B F

a character denoting the status of the node, with '-' meaning an

offline node, '*' meaning N+1 failure and blank meaning a good node

.TP

.B Name

the node name

.TP

.B t_mem

the total node memory

.TP

.B n_mem

the memory used by the node itself

.TP

.B i_mem

the memory used by instances

.TP

.B x_mem

amount memory which seems to be in use but cannot be determined why or

by which instance; usually this means that the hypervisor has some

overhead or that there are other reporting errors

.TP

.B f_mem

the free node memory

.TP

.B r_mem

the reserved node memory, which is the amount of free memory needed

for N+1 compliance

.TP

.B t_dsk

total disk

.TP

.B f_dsk

free disk

.TP

.B pri

number of primary instances

.TP

.B sec

number of secondary instances

.TP

.B p_fmem

percent of free memory

.TP

.B p_fdsk

percent of free disk

.RE

.BR hbal "(1), " hscan "(1), " ganeti "(7), " gnt-instance "(8), "

.BR gnt-node "(8)"

.TH HSCAN 1 2009-03-22 htools "Ganeti H-tools"

.SH NAME

hscan \- Scan clusters via RAPI and save node/instance data

.SH SYNOPSIS

.B hscan

.B "[-p]"

.B "[--no-headers]"

.BI "[-d " path "]"

.I cluster...

.B hscan

.B --version

.SH DESCRIPTION

hscan is a tool for scanning clusters via RAPI and saving their data

in the input format used by

.BR hbal "(1) and " hn1 "(1)."

It will also show a one-line score for each cluster scanned or, if

desired, the cluster state as show by the \fB-p\fR option to the other

tools.

For each cluster, two files named \fIcluster\fB.instances\fR and

\fIcluster\fB.nodes\fR will be generated holding the instance and node

data. These files can then be used in \fBhbal\fR(1) or \fBhn1\fR(1)

via the \fB-i\fR and \fB-n\fR options.

.SH OPTIONS

The options that can be passed to the program are as follows:

.TP

.B -p, --print-nodes

Prints the node status for each cluster after the cluster's one-line

status display, in a format designed to allow the user to understand

the node's most important parameters. For details, see the man page

for \fBhbal\fR(1).

.TP

.BI "-d " path

Save the node and instance data for each cluster under \fIpath\fR,

instead of the current directory.

.TP

.B -V, --version

Just show the program version and exit.

.SH EXIT STATUS

The exist status of the command will be zero, unless for some reason

loading the input data failed fatally (e.g. wrong node or instance

data).

.SH BUGS

The program does not check its input data for consistency, and aborts

with cryptic errors messages in this case.

.SH SEE ALSO

.BR hbal "(1), " hn1 "(1), " ganeti "(7), " gnt-instance "(8), " gnt-node "(8)"