-
Iustin Pop authored
I've seen that man pages, as generated by the version of pandoc we use, show single dashes in option names instead of double ones (- versus --). After bringing it up with upstream (http://groups.google.com/group/pandoc-discuss/browse_thread/thread/9c4589a4001d42f9/95ee8dae8932dc93 ), it seems that this is a known behaviour of pandoc that has been improved in newer versions. Until then, let's use correctly double dashes; from the two options in the above thread, I chose to use \-- as that doesn't change the actual output; whereas ``--nodes`` make this a code block, which will look differently from a short option and could change how the output looks (e.g. when in a bold span). Additionally, I've removed two cases where unescape em was explicitly intended, as that makes automated checking harder and we can use other formatting. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
f624fa95
gnt-debug(8) Ganeti | Version @GANETI_VERSION@
Name
gnt-debug - Debug commands
Synopsis
gnt-debug {command} [arguments...]
DESCRIPTION
The gnt-debug is used for debugging the Ganeti system.
COMMANDS
IALLOCATOR
iallocator [--debug] [--dir DIRECTION] {--algorithm ALLOCATOR } [--mode MODE] [--mem MEMORY] [--disks DISKS] [--disk-template TEMPLATE] [--nics NICS] [--os-type OS] [--vcpus VCPUS] [--tags TAGS] {instance}
Executes a test run of the iallocator framework.
The command will build input for a given iallocator script (named
with the --algorithm option), and either show this input data
(if DIRECTION is in) or run the iallocator script and show its
output (if DIRECTION is out).
If the MODE is allocate, then an instance definition is built
from the other arguments and sent to the script, otherwise (MODE is
relocate) an existing instance name must be passed as the first
argument.
This build of Ganeti will look for iallocator scripts in the following directories: @CUSTOM_IALLOCATOR_SEARCH_PATH@; for more details about this framework, see the HTML or PDF documentation.
DELAY
delay [--debug] [--no-master] [-n NODE...] {duration}
Run a test opcode (a sleep) on the master and on selected nodes (via an RPC call). This serves no other purpose but to execute a test operation.
The -n option can be given multiple times to select the nodes
for the RPC call. By default, the delay will also be executed on
the master, unless the --no-master option is passed.
The delay argument will be interpreted as a floating point number.
SUBMIT-JOB
submit-job [--verbose] [--timing-stats] [--job-repeat N] [--op-repeat N] [--each] {opcodes_file...}
This command builds a list of opcodes from files in JSON format and submits a job per file to the master daemon. It can be used to test options that are not available via command line.
The verbose option will additionally display the corresponding
job IDs and the progress in waiting for the jobs; the
timing-stats option will show some overall statistics inluding
the number of total opcodes, jobs submitted and time spent in each
stage (submit, exec, total).
The job-repeat and op-repeat options allow to submit
multiple copies of the passed arguments; job-repeat will cause N
copies of each job (input file) to be submitted (equivalent to
passing the arguments N times) while op-repeat will cause N copies
of each of the opcodes in the file to be executed (equivalent to
each file containing N copies of the opcodes).
The each option allow to submit each job separately (using N
SubmitJob LUXI requests instead of one SubmitManyJobs request).
TEST-JOBQUEUE
test-jobqueue
Executes a few tests on the job queue. This command might generate failed jobs deliberately.
LOCKS
Shows a list of locks in the master daemon.