- Feb 02, 2011
-
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Michael Hanselmann authored
- Use constant for exit value - Configure logging from main function, not from class' “__init__” Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Michael Hanselmann authored
Instead of using its own, burnin can use cli.SetGenericOpcodeOpts. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
- Feb 01, 2011
-
-
Stephen Shirley authored
Signed-off-by:
Stephen Shirley <diamond@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Stephen Shirley authored
Signed-off-by:
Stephen Shirley <diamond@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Stephen Shirley authored
This allows calling of _UnlockedLookupNodeGroup() from within AddNodeGroup() Signed-off-by:
Stephen Shirley <diamond@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
- Jan 31, 2011
-
-
Stephen Shirley authored
Also fix type of Merger.cluster_name from list to string. This would have triggered an error in sshRunner if cluster keys were in use. Signed-off-by:
Stephen Shirley <diamond@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Stephen Shirley authored
Signed-off-by:
Stephen Shirley <diamond@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Stephen Shirley authored
flatten is the verb, flattened is the adjective. Signed-off-by:
Stephen Shirley <diamond@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
This patch adds a new log handler class based on the standard library's BaseRotatingHandler. This new class allows the log file to be re-opened, e.g. upon receiving a SIGHUP signal. The latter will be implemented in forthcoming patches. The patch does not change the behaviour regarding writing to /dev/console. Quite a bit of code had to be changed to unittest the log handlers. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Jan 28, 2011
-
-
Iustin Pop authored
This patch implements recreation of instance disk symlinks when the activate-disks operation is run. Until now, it was not possible to re-create these symlinks without stopping and starting or migrating an instance as the RPC call where this is done was in instance startup and migration. In order to do this, the blockdev_assemble rpc call needs the disk index too, which is added to the protocol. This is a change from 2.3 and makes instance startup incompatible (FYI). Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
This makes it possible to get the console information via a LUXI query. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Stephen Shirley authored
Signed-off-by:
Stephen Shirley <diamond@google.com> Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
This adds checking (in the configuration) for invalid be, nd and nic params. The code is a bit tricky as nd params are at cluster, nodegroup and node level, nicparams are at cluster and nic level, whereas beparams are at cluster and instance level. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Iustin Pop authored
This just adds a 'cluster' local variable for reducing duplication. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Guido Trotter authored
Closes issue: 130 Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Stephen Shirley authored
- Add check in ConfigWriter to prevent last node group from being removed - Tidy up error message a bit Signed-off-by:
Stephen Shirley <diamond@google.com> Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
René Nussbaumer authored
If for some reason (e.g. failed migration) one instance is running on multiple nodes the output can become inconsistent. To get that error and make it consistent between runs we make the call on the secondary too and look if it's running there. If so we report the instance as ERROR_wrongnode. Signed-off-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Add “cluster-oob” to sample configuration file. Don't run RAPI group tests if disabled. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Jan 27, 2011
-
-
Michael Hanselmann authored
* devel-2.3: Wait for master to become available on initialization Start all daemons on cluster initialization Clarify job processing order in admin guide Improve option descriptions Remove two unused variables Fix LUOSDiagnose and non-vm_capable nodes Rephrasing two error messages for auto promotion storage: Check that mapper is either used or None Fix bug in “gnt-node list-storage” Improve import/export timeout settings Increase remote import/export timeout Conflicts: lib/constants.py: Trivial lib/objects.py: Trivial qa/qa_node.py: Trivial Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
Currently, the validity of the hypervisor parameters is only checked at init/modification time, and not in the cluster verify. This is bad, as it can lead to inconsistent state that is only detected when the next modification (which can be unrelated) is made, leading to unexpected error messages. This patch adds both syntax verification (in masterd) and validity verification on remote nodes. The downside of the patch is that on clusters with many instances which have custom parameters, it will be slow. A possible improvement would be to detect duplicate, identical set of parameters, and collapse these into a single verification, but that is left as a TODO (in case it becomes problematic). An additional change is in utils.ForceDict, where we said 'key', whereas this function is always used with parameter dicts, so I changed it to "Unknown parameter". Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
- Remove the actual code - Remove mentions of it from iallocator.rst, and use hail instead - Also remove mentions of "etch-image" and use "debootstrap+default" - Mention htools as the reference implementation in iallocator.rst Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Stephen Shirley authored
Signed-off-by:
Stephen Shirley <diamond@google.com> Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Stephen Shirley authored
cli._RunWhileClusterStoppedHelper.Call passes (self, *args) to functions called via cli.RunWhileClusterStoppedHelper(). The code in cluster-merge was broken by commit d8aab233. Signed-off-by:
Stephen Shirley <diamond@google.com> Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Commit 70b0d2a2 broke unittests on Python 2.4 and 2.5. Turns out that Python 2.6 and above allow classes to be passed as custom test runners, whereas earlier versions don't. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
René Nussbaumer authored
In cases where secondary was offline and not evacuated watcher tried to activate-disks in an endless manner, but this is useless, as the secondary is offline and therefore not responding to this approach. This patch skips activation of the disk if the secondary is bad but instance up and running. Signed-off-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
- Jan 26, 2011
-
-
Iustin Pop authored
The recent work on multi-VG support has converted LUClusterVerifyDisks into doing serialised calls to each node, as each node can have different VGs. This is suboptimal, especially for big clusters, where this LU is executed by the watcher very often. This patch changes the logic based on the observation that querying a node for its VGs and then requesting a LV list for those VGs is equivalent to simply asking for all LVs, without specifying the VG name(s). So backend.py needs changes to accept an empty VG list, and the LU itself partially reverts to the previous version. Additionally, we do two other fixes to this LU: - small improvement in getting the instance list from the config - MapLVsByNode works for all disk types, hence no need to restrict to the DRBD template, especially as today we can "recreate" disks for plain volumes too (the warning message in gnt-cluster is updated too) Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
Recent multi-VG work already exports the missing LV names as vg/lv, not simply lv. So the query and addition of the VG name in gnt-cluster verify-disks is redundant, and even wrong for non-default-VG instances. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
In some cases (e.g. the hypervisor not running at all), we might want to force disk deactivation, skipping the hypervisor checks. I believe this is not a good thing to do all the time, so this patch adds the force option to allow manual selection of this operation mode. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
This is analogue to the existing check for a responsive node daemon. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
At least ganeti-confd was not started. It got started a few minutes later by ganeti-watcher. Also move one pylint disable to the effective line. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
The fact that jobs don't necessarily execute in order has been source for some confusion. Hopefully this update will clarify things. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Also replace hardcoded “xenvg” with constant. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-