3355 Commits (bd5692451b0987d4d28512ab4ecc10d12be2cdc3)

Author	SHA1	Message	Date
DanHam	c2437ba592	Remove the option to place the VHD files in a separate directory ... The export process now exports the VM directly from the build directory into the output directory. There are no intermediate steps or copying of files involved. This means that there is no longer any benefit in having a separate directory to house the VHD files - see #5206 for the reasoning behind the introduction of this feature. If a user wishes to house the build files on a separate disk from the output directory (perhaps for performance reasons or due to disk space limitations) they can still do so through the use of `temp_path`.	8 years ago
DanHam	d5d82c32b2	Changes to the export process have made 'inline' build of disks redundant ... PR #5631 introduced code to build/create disks directly in the output directory if `skip_export` was set in an attempt to optimise the build process. These are no longer required.	8 years ago
DanHam	35b4e87c42	Add tests for export VM step	8 years ago
DanHam	30a71da8e7	Add tests for disk compaction step	8 years ago
DanHam	09028c14a3	Reintroduce the disk compaction process as a unique step	8 years ago
DanHam	da2df69301	Remove disk compaction from the export step	8 years ago
DanHam	c6b9d9ce90	Add checks/error reporting to compaction process ... * Report compaction results * Failure to find any disks under the supplied path is treated as a 'soft' error and a warning message will be printed in place of the compaction result. Any other failure will cause the build to fail.	8 years ago
DanHam	534fc4a473	Ensure the export directory structure matches that of previous versions ... Commit 3fc2defb6 altered the directory structure associated with an exported VM. The changes mean that the export process now stores the exported machine files and folders under a folder with name 'vm_name' in the output directory. This commit restores the previous behaviour whereby the exported machine files and folders were stored directly in the output directory. This allows us to keep the efficiency improvements introduced with 3fc2defb6 while maintaining backward compatibility. By default the Export-VM command creates three folders in the specified export directory - 'Virtual Hard Disks', 'Virtual Machines' and 'Snapshots'. When a machine with no associated snapshots is exported the 'Snapshots' directory is empty. Prior to 3fc2defb6 the Snapshots folder was not copied/incorporated into the output directory at all. This was a bug. This commit preserves the legacy behaviour by not including an empty Snapshots directory in the export. However, if there *are* Snapshots associated with the VM, they are now moved into the output directory along with the usual directories containing disks and VM metadata. This prevents warnings/errors on import due to missing snapshots.	8 years ago
DanHam	dc46848f89	Remove now redundant function to copy exported VM files	8 years ago
DanHam	3fc2defb6d	Refactor the export step for Hyper-V ISO and VMCX builders ... * Fixes a bug that caused the build to error if users did not explicitly set `skip_compaction:true` when setting `skip_export: true`. See #6392. * Improves the efficiency of the compaction and export process by reordering the compaction and export steps. * Further improves the efficiency of the compacting step through compacting the vmd* file directly rather than creating and then operating on a copy. * The changes mean the export process now stores the exported machine files and folders under a folder with name 'vm_name' in the output directory. Previously the exported machine files and folders were stored directly in the output directory.	8 years ago
Matthew Hooker	814c1cf2b2	spellfix	8 years ago
Andrew Pryde	67f039509a	Merge pull request #6498 from neumayer/ocimetadata ... Allow instance metadata to be specified in config	8 years ago
xxx	7630268e1d	Incorporate review comments	8 years ago
James Nugent	9fffe4056e	Merge pull request #5452 from smaato/tag-spot-requests ... Enable tagging of spot requests	8 years ago
Sander van Harmelen	451cbd8aa9	Merge pull request #6487 from sermilrod/Honour-cloudstack-projectid ... Honour cloudstack projectid	8 years ago
Sergio Millan Rodriguez	f4020835d6	flag to setup networking without firewall rules	8 years ago
Sergio Millan Rodriguez	472a7820eb	Using UI keypair meaningful message	8 years ago
Sergio Millan Rodriguez	e729b21212	passing projectid to getRootVolumeID rather than the whole config struct	8 years ago
Mark Meyer	2fec76ea87	Check if spot price is empty, when spot_tags is set	8 years ago
Megan Marsh	b6b907f523	read in the environment variables that government wait time and polling time for the AWS wait in step_stop_ebs_volume	8 years ago
Sergio Millan Rodriguez	a41a4658ee	make packer builder honour projectid setting if provided	8 years ago
Sergio Millan Rodriguez	eae0556dc5	Add option to enable/disable create firewall/acl rules	8 years ago
Megan Marsh	1d15f09e36	Merge pull request #6440 from DanHam/simplify-vmx-find-disks ... Further simplify enumeration of attached disks for VMware VMX builder	8 years ago
Megan Marsh	8e22803099	fix loading of environment variables for managing aws waiters	8 years ago
Megan Marsh	12f1b2421d	Merge pull request #6332 from hashicorp/do_6177 ... Replace home-grown waiters with aws sdk's built in waiters	8 years ago
Megan Marsh	f657ca39c9	refactored env var code and tests so that I don't have to set env vars during tests to check logic	8 years ago
Megan Marsh	14166fdd99	update amazon import docs to include the env vars for setting aws waiter delays and timeouts	8 years ago
Megan Marsh	bfbe318727	fix the homegrown waiters ... fix image import; issue was with wait options not being evaluated	8 years ago
Megan Marsh	f49a2d8aed	move UI call to before the wait; add context to these steps	8 years ago
Megan Marsh	cf63dd10bf	replace AMIStateRefreshFunc, InstanceStateRefreshFunc, our spot instance waiter, our chroot volume waiter, and our snapshot waiters with waiters form AWS's SDK.	8 years ago
M. Marsh	62d9dcb822	Merge pull request #6477 from jabbera/fixMaxResourceGroupLength ... managed_image_resource_group_name max length change	8 years ago
Mike	5ea6429cd6	managed_image_resource_group_name max length change	8 years ago
M. Marsh	8e852af1eb	Merge pull request #6448 from DanHam/fix-esxi-displayName ... ESXi: Fix failure to discover IP or export VM when 'displayName' differs from 'vm_name'	8 years ago
Michael Gibson	7e4fb9adb5	vnc_bind_address not getting passed through to qemu ... This was mostly addressed in commit hashicorp/packer@fa273f3 Just missing vncIP from step_type_boot_command.go	8 years ago
M. Marsh	adfee4933a	Merge pull request #6437 from hashicorp/retry_convert ... make the convert retryable in case it takes a bit to release a lock	8 years ago
Mark Meyer	3dbf1cb371	Enable tagging of spot requests ... This adds a new parameter to the EBS builders named `spot_tags'. This parameter accepts a map of tags, much like `tags'. These tags will be applied to a spot request that is created. Improve visibility.	8 years ago
DanHam	a39c5887fb	Test we halt if a bad path is set in vmx_path	8 years ago
DanHam	21117e5d38	Test we fail if displayName is not stored in the statebag as 'display_name'	8 years ago
DanHam	88c43ec98d	Test we fail if the displayName key is not found in the VMX	8 years ago
DanHam	d68d26a6e5	Fix tests: We now need to set `displayName` key/val pair in the test VMX	8 years ago
DanHam	902cea0f30	ESXi: Fix failure to export VM when `displayName` differs from `vm_name` ... ovftool requires we pass in `displayName` as part of the source locator string so that it can successfully determine the VM intended for export.	8 years ago
DanHam	cd7d3812ea	ESXi: Fix failure to get VM IP when `displayName` differs from `vm_name` ... The value in the Name field returned by 'esxcli network vm list' actually returns the VMs `displayName`. As such, we need to match against `displayName` to discover the VMs 'WorldID'. 'WorldId' is ultimately used/needed as an argument in the command that returns the VMs IP.	8 years ago
DanHam	3eab3cc99b	ESXi builds require we store the value of displayName in the statebag ... The value of displayName is needed by later steps: * When determining the IP address of the build VM * When exporting the VM using ovftool By default Packer will configure the VMX so `displayName` is equal to the value defined for `vm_name` in the build template. However, it is possible (and sometimes desirable) to set a custom value for `displayName`. Users can set a custom `displayName` through use of the `vmx_data` option in their template.	8 years ago
Edouard Bonlieu	4b1f96b527	Merge pull request #6439 from jbonachera/scaleway-config-bootscript ... scaleway: add 'bootscript' configuration parameter	8 years ago
M. Marsh	8658eaf1ac	Merge pull request #6424 from DanHam/fix-esxi-export-hang ... Prevent hang on export when using VMware ISO builder on remote ESXi host	8 years ago
DanHam	939aa7e289	Add test: We shouldn't error when main remote options are unset	8 years ago
DanHam	efcdf60d96	Add tests to ensure remote_password is set when exporting with ovftool	8 years ago
DanHam	0d9134bdbc	Fix existing tests as they were not doing what they should have been ... * Fix test to check for remote_host when remote_type is set * Fix tests by including remote_password where required	8 years ago
DanHam	eee16262b6	Remove duplicate/redundant test	8 years ago
DanHam	c8199458a7	Prevent hang on export for remote ESXi build due to empty remote_password	8 years ago