From d56e950e8591f02e0dca29fea2630b3872b73f5c Mon Sep 17 00:00:00 2001 From: Leo Simons Date: Tue, 29 Jul 2014 10:12:00 +0200 Subject: [PATCH] CLOUDSTACK-7143: work on vagrant box export Running --export creates the .ovf and the .vmdk files referenced from that .ovf in one go. Guessing/predicting the names of the .vmdk files is not fool-proof. --- tools/appliance/build.sh | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/tools/appliance/build.sh b/tools/appliance/build.sh index 12f5f896fdf..e3197e88db8 100755 --- a/tools/appliance/build.sh +++ b/tools/appliance/build.sh @@ -459,20 +459,24 @@ function vmware_export() { function vagrant_export() { log INFO "creating vagrant export" + local machine_uuid="${1}" # this is based on veewee export logic, but, we don't want to use veewee export, # since it makes optimistic assumptions about VM shutdown/halt leading to available # disks and the like - disk="${appliance_build_name}-vmware.ovf" - image="${appliance_build_name}-vmware-disk1.vmdk" + # predicting VBoxManage disk naming seems problematic + # disk="${appliance_build_name}-vmware.ovf" + # image="${appliance_build_name}-vmware-disk1.vmdk" mkdir -p "box/${appliance_build_name}" - cp "${disk}" "box/${appliance_build_name}/box.ovf" - cp "${image}" "box/${appliance_build_name}/box-disk1.vmdk" + # cp "${disk}" "box/${appliance_build_name}/box.ovf" + # cp "${image}" "box/${appliance_build_name}/box-disk1.vmdk" cat >box/${appliance_build_name}/Vagrantfile <