baserock/baserock/morph.git - Morph -- Baserock build tool

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove trailing \	Sam Thursfield	2014-12-18	1	-1/+1
\| \| \| \|	I meant to do this as part of the previous merge.
*	openstack.check: Be more careful when claiming credentials are invalid	Sam Thursfield	2014-12-09	1	-4/+11
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In order to check the user's credentials at the start of deployment, we try to run `glance image-list`. I found a situation where this command failed despite my credentials being correct. Morph outputted a misleading error message that said 'Wrong OpenStack credentials' The code now checks that the error returned by 'glance' does indeed look like a credentials error. If it doesn't, the full error output is displayed. The error I encountered now gets a message like this: ERROR: openstack.check failed with code 1: ERROR: Failed to connect to OpenStack instance at https://example.com:5000/v2.0: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')] (If you are curious, I fixed this by running `update-ca-certificates`.)
*	Fix openstack write/check exts to pass the tests	Pedro Alvarez	2014-09-09	1	-1/+1
\|
*	Check OpenStack credentials in openstack.checkbaserock/pedroalvarez/openstack-check-improvements	Pedro Alvarez	2014-09-05	1	-0/+48
\| \| \| \| \| \| \| \|	If the credentials are wrong, then morph will fail before attempting the OpenStack deployment. To achieve that openstack.check will attempt to run `glance image-list`.
*	Check for presence of btrfs before trying to use it	Sam Thursfield	2014-06-11	1	-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: Check the --upgrade flag has been used correctly.	Sam Thursfield	2014-03-04	1	-0/+35
	Most write extensions don't handle both initial deployments and upgrades of a system.