gnt-debug

ALLOCATOR

allocator [--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 (internally in the command) and on selected nodes (via an RPC call). This server 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] {opcodes_file...}

This command builds a list of opcodes from JSON-format files and submits for each file a job to the master daemon. It can be used to test some options that are not available via the command line.

The verbose option will job the job IDs of the submitted jobs and the progress in waiting for the jobs; the timing-stats option will show some overall statistics with the number of total opcodes and jobs submitted, and time time for each stage (submit, exec, total).

The job-repeat and op-repeat options allow to submit multiple copies of the passed arguments; the job repeat will cause N copies of each job (input file) to be submitted (equivalent to passing the arguments N times) while the op repeat will cause each job to contain multiple copies of the opcodes (equivalent to each file containing N copies of the opcodes).