- May 12, 2011
-
-
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:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- May 11, 2011
-
-
Guido Trotter authored
These sneaked in from 2.4 during the merge, but this attribute is actually gone in the master branch. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
* devel-2.4: Use floppy disk and a second CDROM on KVM Document the selection of instance kernels Make root_path an optional hypervisor parameter Some man page updates Add 2 new variables to the OS scripts environment Add --no-wait-for-sync when converting to drbd Recreate instance disks: allow changing nodes Rename instance: only show new name when different Fix race condition in LUGroupAssignNodes Re-wrap and fix formatting issues in gnt-instance.rst Documentation for the new parameters for KVM cmdlib: Fix typo, s/nick/NIC/ A small optimisation in cluster verify A few docstring fixes luxi: do not handle KeyboardInterrupt Handle EPIPE errors while writing to the terminal Cluster verify: check for missing bridges Conflicts: lib/cmdlib.py - manually merge the 2.4 fix lib/opcodes.py - add new field from 2.4, but also describe it man/gnt-cluster.rst man/gnt-instance.rst man/gnt-node.rst - merge new attributes with general 2.4 manpage fixes Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- May 10, 2011
-
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Marco Casavecchia authored
Hi all, this patch will add 3 new KVM parameters and a new option. New Parameters: - floppy_image_path = "" -> Specify the floppy image to load as floppy disk. - cdrom2_image_path = "" -> Specify a second cdrom image to load on the system (note: this in not intended to be used as a boot device. To boot the system from cdrom you must use the "cdrom_image_path" parameter as always). - cdrom_disk_type = "" -> it can be one of the kvm supported types as "ide,scsi,paravirtual,ecc". I introduced this optional parameter to make possible to specify a different virtual device for cdroms. It is useful if you want to install a windows system New option for "boot_device" parameter: - "floppy": with this value you should be able to boot a KVM instance from floppy image. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Iustin Pop <iustin@google.com> (cherry picked from commit cc130cc7) Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
A simple doc patch to document how to configure the kernels for the instances. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
With this patch, the worker thread name is updated to include a short summary of the opcode (basically its OP_ID). The base name of job queue threads is shortened from “JobQueue” to “Jq”. Logs and the lock monitor will show a job verifying the cluster as e.g. “Jq2/Job1742/C_VERIFY”. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
This will hopefully detect potential LVM (or any other storage, when they implement it) issues before committing changes just on some nodes. Unfortunately due to the dry_run opcode handling, we can't integrate this into the usual handling (as we need to activate the disks before doing any tests, which belongs in Exec not in CheckPrereq). Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Iustin Pop authored
Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Iustin Pop authored
This is always called with False from backend for now. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Michael Hanselmann authored
Also reorder the methods to match all other LUs. 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
Also change the way “share_locks” is filled. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
When removing “acquired_locks” in commit 0d5a0b96, I didn't remember that it does not contain the Big Ganeti Lock. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Apollon Oikonomopoulos authored
Commit 52f33103 introduced lock release factorization, replacing manual lock release using utility functions. However, it broke TLMigrateInstance due to a typo (passing the Tasklet to ReleaseLocks instead of the parent LU). We fix this by passing the LU to ReleaseLocks. Thanks to Dan Eriksson for reporting this. Signed-off-by:
Apollon Oikonomopoulos <apollon@noc.grnet.gr> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
No idea where those four spaces came from, but they must've been there for a while. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
The “acquired_locks” attribute in LUs is used to keep a list of acquired locks at each lock level. This information is already known in the lock manager, which also happens to be the authoritative source. Removing the attribute and directly talking to the lock manager saves us from having to maintain the duplicate information when releasing locks. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Saves some typing and we'll use it more often in the future. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
René Nussbaumer authored
This will allow us an easy migration to pv-grub, because a set root_path confused pv-grub. Signed-off-by:
René Nussbaumer <rn@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- May 09, 2011
-
-
Michael Hanselmann authored
Depending on the opcode and its parameters, the existing “Summary” function can give a rater long summary. For displaying the summary in logs and in the lock monitor, it should be shorter. Hence this new function is added to just use the opcode ID with common prefixes replaced (e.g. “INSTANCE_” becomes “I_”). Opcode values are not used. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
When all locks contained in a set are acquired, the lockset's internal lock is acquired with the same mode. With this patch the internal lock will show up on the lock monitor, named e.g. “instances/[lockset]”. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Michael Hanselmann authored
It is always used in the locking code. Unittests are updated. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Michael Hanselmann authored
In some rare cases new shared acquires could sneak in through the condition cached in “__pending_shared” while the code was still notifying acquires. This was only working because such a condition would be on top of the queue. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Iustin Pop authored
This adds documentation for both the short and long form of many options (which was inconsistent before: in some cases only the short form was used, in others only the long form). Note that the standard this patch adopts is to document both forms as such: {-O|--os-parameters} … This makes it a bit uglier in complex situations, but the alternatives considered were not perfect either. Other suggestions (with patches) welcome. Additionally, it fixes two doc bugs: - in gnt-cluster.rst, the --prealloc-wipe-disks section was in the middle of a paragraph - in gnt-instance.rst, a list was not typed correctly, thus it was mangled as a single paragraph Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Marco Casavecchia authored
Add INSTANCE_PRIMARY_NODE and INSTANCE_SECONDARY_NODES. These new values are useful for OS scripts that needs to know the nodes where the instance lives.. or has lived. Signed-off-by:
Iustin Pop <iustin@google.com> [iustin@google.com: fixed small issue with SECONDARY_NODES] Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
Currently, when converting an instance from plain to DRBD, the instance is blocked during the entire resync period. This patch adds the --no-wait-for-sync so that the operation finishes as soon as the DRBD sync has started, without waiting for the entire sync. This makes the instance available much faster. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
This patch introduces the option of changing an instance's nodes when doing the disk recreation. The rationale is that currently if an instance lives on a node that has gone down and is marked offline, it's not possible to re-create the disks and reinstall the instance on a different node without hacking the config file. Additionally, the LU now locks the instance's nodes (which was not done before), as we most likely allocate new resources on them. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
- May 06, 2011
-
-
Iustin Pop authored
Commit 1c6e5787 removed the iallocator and target_node keyword parameters from TLMigrateInstance, but I didn't update their use in LUInstanceFailover and (not fully) in LUInstanceMigrate. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
It makes not sense to show messages like: Fri May 6 02:04:01 2011 - INFO: Resolved given name 'instance18' to 'instance18' So we'll skip the message if the resolved name is identical to the requested one. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
The original code would get all node information and their groups without before acquiring the necessary locks. With this patch the node information is only retrieved once all locks have been acquired. Groups are locked optimistically and verified after acquiring the node locks. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- May 05, 2011
-
-
Apollon Oikonomopoulos authored
Commit faaabe3c fixed failover behaviour for DTS_INT_MIRROR instances, however it broke migration for DTS_EXT_MIRROR instances, by moving iallocator and node checks from LUInstanceMigrate to TLMigrateInstance. This has the side-effect that the LU called the TL with None for both, node and iallocator when the default iallocator was being used. This patch maintains the iallocator checks in TLMigrateInstance and fixes the LU-TL integration. Signed-off-by:
Iustin Pop <iustin@google.com> [iustin@google.com: rebased patch on current HEAD] Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
This is one of the first opcodes to make use of node group locking. To get an instance's node groups, the instance's nodes need to be looked at. Due to a previous design decision nodes are locked after the group, hence there's no clean locking order. This patch works around that by first getting the instance's groups without locks, and then verifying them after actually getting all locks. Rough overview: - Lock instance - Get groups of instance's nodes - Lock groups - Lock all nodes in groups - Verify node groups - Run iallocator - Release group and unused nodes - Replace disks, etc. There are probably too many assertions in the code, but it's locking and we've been bitten in the past. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
This will be used for locking only the necessary node group(s) for per-instance operations. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Apollon Oikonomopoulos authored
Commit 77fcff4a unintentionally incorporated code from TLMigrateInstance.CheckPrereq into TLMigrateInstance._RunAllocator, presumably during a rebase from earlier versions of the patch to the 2.5 codebase. As a result all migrations running without an iallocator were performed non-live :-( This patch moves the affected code back to CheckPrereq. Signed-off-by:
Apollon Oikonomopoulos <apollon@noc.grnet.gr> Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- May 04, 2011
-
-
Michael Hanselmann authored
- Clarify some error messages - Remove unnecessary punctuation - Merge two if conditions in one place Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
This is mostly rewrapping plus fixing a few small issues in gnt-instance.rst. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Marco Casavecchia authored
Options added/updated are: cdrom2_image_path, floppy_image_path, cdrom_disk_type and boot_order. Signed-off-by:
Iustin Pop <iustin@google.com> [iustin@google.com: small formatting update] Reviewed-by:
Iustin Pop <iustin@google.com>
-
- May 03, 2011
-
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-