summaryrefslogtreecommitdiff
path: root/morphlib/exts/kvm.check
Commit message (Collapse)AuthorAgeFilesLines
* Morph build c3874f415dc6448ca28d9a01edab0948baserock/6453f312359f4317803ef7f14b58d21f/d675b946df4f456693ed211dcd2ec95eAdam Coldrick2015-04-151-3/+20
| | | | System branch: master
* Morph build 2ee8190abe87461992f5b7ed85fe2ee9Adam Coldrick2015-03-191-3/+71
| | | | System branch: master
* Check for presence of btrfs before trying to use itSam Thursfield2014-06-111-0/+2
| | | | | | | | | | | | | | | | If btrfs is not present in the kernel we end up with strange output like this: Error creating disk image2014-06-10 16:00:40 [devel-system-x86_64-generic][my-raw-disk-image][rawdisk.write]Failure to create disk image at /src/tmp/testdev.img ERROR: Command failed: mount -o loop /src/tmp/testdev.img /src/tmp/deployments/tmpQ7wXO1/tmp4lVDcu/tmpvHSzDE mount: mounting /dev/loop0 on /src/tmp/deployments/tmpQ7wXO1/tmp4lVDcu/tmpvHSzDE failed: Device or resource busy To avoid this confusing error, Morph should explicitly check first.
* deploy: Extra checks for KVM deploymentsSam Thursfield2014-04-151-0/+21
| | | | | Test that a VM with the given name does not already exist, and check that the files specified in ATTACH_DISKS do already exist.
* deploy: Share SSH connectivity check in the common writeexts.py codeSam Thursfield2014-04-151-4/+1
| | | | | Also, change it to log the real error message in morph.log before raising a more general exception to the user.
* deploy: Check SSH connection for KVM deployment before startingSam Thursfield2014-04-141-0/+29
| | | | | | Slight duplication is necessary, but it's only a few lines. We could move the duplicated code into the base class in 'morphlib.writeexts' if there was more duplication.
* deploy: Check the --upgrade flag has been used correctly.Sam Thursfield2014-03-041-0/+35
Most write extensions don't handle both initial deployments and upgrades of a system.
View Lorry Controller Status