- 24 Jul, 2008 1 commit
-
-
Michael Hanselmann authored
Reviewed-by: iustinp
-
- 23 Jul, 2008 1 commit
-
-
Michael Hanselmann authored
Reviewed-by: iustinp
-
- 11 Jul, 2008 1 commit
-
-
Michael Hanselmann authored
"gnt-job list" was broken after my recent changes in the RPC between clients and the master. This patch makes it work again. Reviewed-by: iustinp
-
- 01 Jul, 2008 1 commit
-
-
Iustin Pop authored
This adds the same “-o +...” functionality in gnt-job as in the node and instance scripts. Reviewed-by: imsnah
-
- 13 May, 2008 3 commits
-
-
Iustin Pop authored
[Trunk version] Reviwed-by: imsnah
-
Iustin Pop authored
This reverts commit 976. Reviewed-by: ultrotter
-
Iustin Pop authored
[Forward-port of the 1.2 branch patch] This patch removes all the parameters and options from the output "gnt-X" (i.e. the subcommand list for command). This is done in order to uniformize the output, currently only some parameters are shown and they are not always consistent (e.g. required versus important parameters). Reviewed-by: ultrotter
-
- 10 Apr, 2008 1 commit
-
-
Iustin Pop authored
This patch changes the definition of a job and introduces per-opcode results. First, the result and status fields of a job are condensed into a single 'status' attribute. Then, we introduce an opcode status and one result list, that allow jobs to return values. The gnt-job script is also modified to allow these new fields to be queried. Note that the patch changes the opcode field to op_list, and it changes its return value from string to a list of (serialized) opcodes. Reviewed-by: ultrotter
-
- 04 Apr, 2008 1 commit
-
-
Iustin Pop authored
This patch adds a very basic gnt-job script that allows job querying. This goes on top of the previous master daemon patches. Currently, because of the not-changed cmd lock, you can't query the jobs as long as a job is running - you have to rm the cmd lock and then you can query the jobs. Reviewed-by: imsnah
-