- 21 Nov, 2008 1 commit
-
-
Michael Hanselmann authored
With the new SSL client certificate stuff it's no longer needed. Reviewed-by: iustinp
-
- 20 Nov, 2008 2 commits
-
-
Michael Hanselmann authored
This function will be used to write ssconf files from the node daemon. By creating a lock file, we synchronize different child processes of ganeti-noded to not overwrite each other's changes. Also, external processes could use this lock to make sure they don't read ssconf files while changes are going on. The socket module is not used (anymore) in ganeti.ssconf, removing it. Reviewed-by: iustinp
-
Iustin Pop authored
This patch adds support for mult-disk/multi-nic in: - instance add - burnin The start/stop/failover/cluster verify work as expected. Replace disk and grow disk are TODO. There's also a change gnt-job to allow dictionaries to be listed in gnt-job info. Reviewed-by: imsnah
-
- 21 Oct, 2008 1 commit
-
-
Iustin Pop authored
Please configure your editors to strip it, or enable your git hooks... Reviewed-by: ultrotter
-
- 20 Oct, 2008 1 commit
-
-
Guido Trotter authored
'auto' is used in multiple place in the code with a meaning similar to 'default', 'generate' will be used to force generation of mac addresses when the default would be to reuse an old one. Forward-port-of: r1884, Reviewed-by: iustinp Reviewed-by: imsnah
-
- 18 Oct, 2008 1 commit
-
-
Alexander Schreiber authored
Reviewed-by: iustinp
-
- 17 Oct, 2008 3 commits
-
-
Guido Trotter authored
Reviewed-by: iustinp
-
Guido Trotter authored
Reviewed-by: iustinp
-
Guido Trotter authored
Reviewed-by: iustinp
-
- 16 Oct, 2008 1 commit
-
-
Michael Hanselmann authored
Requests are no longer logged to a separate file. Reviewed-by: amishchenko
-
- 15 Oct, 2008 1 commit
-
-
Iustin Pop authored
We add a (per-node) queue drain flag that blocks new job submission. There is not yet an interface to add/remove the flag (will come in next patches). Reviewed-by: imsnah
-
- 14 Oct, 2008 4 commits
-
-
Iustin Pop authored
Change the constant name to match the value (autobalance -> auto_balance). Also add the auto_balance header so that gnt-instance can list it. Reviewed-by: ultrotter
-
Iustin Pop authored
Memory is renamed for easier use. Reviewed-by: ultrotter
-
Iustin Pop authored
This is just a change of the various hvm_ and pvm parameters to the hv model. Parameters are queried via hv/$name or via the whole dict as returned by hvparams. Reviewed-by: ultrotter,imsnah
-
Iustin Pop authored
Since we don't want the string values of the parameters (e.g. “kernel_path”) spread over the code, we introduce constants for these. Reviewed-by: ultrotter,schreiberal
-
- 08 Oct, 2008 1 commit
-
-
Iustin Pop authored
Since in 2.0 the user will possibly have more interaction with the hypervisor names, we sanitize them by removing the version numbers (the version can be a prerequisite for the ganeti installation, we shouldn't document it in variable names). Reviewed-by: schreiberal
-
- 07 Oct, 2008 1 commit
-
-
Iustin Pop authored
Background: when we have multiple jobs in the queue (more than just a few), many of the jobs (up to the number of threads) will be in state 'running', although many of them could be actually blocked, waiting for some locks. This is not good, as one cannot easily see what is happening. The patch extends the opcode/job possible statuses with another one, waiting, which shows that the LU is in the acquire locks phase. The mechanism for doing so is simple, we initialize (in the job queue) the opcode with OP_STATUS_WAITLOCK, and when the processor is ready to give control to the LU's Exec, it will call a notifier back into the _JobQueueWorker that sets the opcode status to OP_STATUS_RUNNING (with the proper queue locking). Because this mechanism does not save the job, all opcodes on disk will be in status WAITLOCK and not RUNNING anymore, so we also change the load sequence to consider WAITLOCK as RUNNING. With the patch applied, creating in parallel (via burnin) five instances on a five node cluster shows that only two are executing, while three are waiting for locks. Reviewed-by: imsnah
-
- 01 Oct, 2008 1 commit
-
-
Michael Hanselmann authored
These functions will be used to access config values instead of using ssconf. Reviewed-by: iustinp
-
- 29 Sep, 2008 2 commits
-
-
Iustin Pop authored
For now we only use the ‘C’ protocol so we can put it in constants.py instead of hardcoding it. Reviewed-by: imsnah
-
Iustin Pop authored
This patch enables the use of the shared secrets for DRBD8 disks, using (hardcoded in constants.py) the md5 digest algorithm. For making this more flexible, either we implement a cluster parameter (once the new model is in place), or we can make it ./configure-time selectable. Reviewed-by: imsnah
-
- 09 Sep, 2008 2 commits
-
-
Guido Trotter authored
This will be used to lock the instance's nodes in addition to some more. Reviewed-by: iustinp
-
Guido Trotter authored
This constant replaces what we used to write in recalculate_locks, and represents the lock recalculation mode. It lives in constants.py because it's used only in cmdlib, and thus doesn't deal with the locking library by itself. Reviewed-by: iustinp
-
- 29 Aug, 2008 3 commits
-
-
Alexander Schreiber authored
Add HVM device type flags 2/3 Reviewed-by: ultrotter
-
Alexander Schreiber authored
Add HVM device type flags 1/4 Reviewed-by: ultrotter
-
Iustin Pop authored
This patch alters the WaitForJobChanges luxi-RPC call to have a configurable timeout, so that the call behaves nicely with long jobs that have no update. We do this by adding a timeout parameter in the RPC call, and returning a special constant when the timeout is reached without an update. The luxi client will repeatedly call the WaitForJobChanges until it gets a real change. The timeout is hardcoded as half the RWTO value. The patch also removes an unused variable (new_state) from the WaitForJobChanges method. Reviewed-by: imsnah,ultrotter
-
- 27 Aug, 2008 1 commit
-
-
Iustin Pop authored
Seems noone ran a burnin lately :) Reviwed-by: amischenko,ultrotter
-
- 18 Aug, 2008 1 commit
-
-
Michael Hanselmann authored
By using this Linux-specific way we don't have to care about removing the socket file when quitting or starting (after an unclean shutdown). For a more detailed description, see the comment in the patch. Reviewed-by: schreiberal
-
- 13 Aug, 2008 2 commits
-
-
Guido Trotter authored
Add a new hypervisor type, HT_KVM, to constants, and register it in the HYPER_TYPES set. Reviewed-by: imsnah
-
Guido Trotter authored
This allows to configure a different path to the kvm binary. By default /usr/bin/kvm is used, which is the one found in debian and ubuntu. Reviewed-by: imsnah
-
- 30 Jul, 2008 2 commits
-
-
Iustin Pop authored
The 'old-style' info, error, debug logs do not make much sense. This patch unifies the SetupLogging and SetupDaemon functions. As a result, all the commands logs to a 'commands.log' file. The patch also changes the log setup to keep going if there's an error in setting up the file logging but we're logging to stderr. Also, burnin now logs to its own file (burnin.log). Reviewed-by: ultrotter
-
Iustin Pop authored
The patch changes the log constants by moving the slash to the end of the log dir instead of at the beginning of *each* log file name. It also adds a new LOG_COMMANDS constant (to be used in a next patch). Reviewed-by: ultrotter
-
- 29 Jul, 2008 2 commits
-
-
Iustin Pop authored
Reviewed-by: imsnah
-
Iustin Pop authored
Reviewed-by: imsnah
-
- 28 Jul, 2008 1 commit
-
-
Michael Hanselmann authored
Reviewed-by: ultrotter
-
- 24 Jul, 2008 1 commit
-
-
Michael Hanselmann authored
Reviewed-by: iustinp
-
- 23 Jul, 2008 1 commit
-
-
Guido Trotter authored
This was a TODO for 2.0 Reviewed-by: iustinp
-
- 17 Jul, 2008 1 commit
-
-
Oleksiy Mishchenko authored
Reviewed-by: imsnah
-
- 14 Jul, 2008 3 commits
-
-
Iustin Pop authored
Note that since RAPI itself doesn't use luxi.Client yet, nothing works, but at least it can startup now. Reviewed-by: imsnah
-
Iustin Pop authored
This was forgot on the forward-porting of RAPI. Reviewed-by: imsnah
-
Iustin Pop authored
This patch contains a raw version for fixing feedback_fn. The new mechanism works as follows: - instead of a per-Processor feedback_fn, there's one for each ExecOpCode, so that feedback for different opcodes go via possibly different functions - each _QueuedOpCode gets a message buffer, a method for adding feedback and a method for retrieving (parts of) the feedback - the _QueuedJob object gets a new attribute that is equal to the index of the currently executing opcode - job queries get an extra parameter called 'ticker' that will return the latest message on the current executing opcode - the cli.py job completion poll will show the new status if different from the old one Of course, quick messages will be lost, as currently only the latest one is available. Also changes between opcodes are not represented at all. Reviewed-by: imsnah
-