New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add functionality to specify and mount bootable vmdk #6146
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -106,11 +106,13 @@ The `windows_opt_config` block supports: | |
|
||
The `disk` block supports: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would a note about using bootable vs non-bootable disks help??? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That is a distinction I was expecting some feedback for. This PR is targeting attaching a bootable drive, but is the same functionality as attaching N number of vmdk's to a vm, which may be a valid use case. I was hoping to hear from someone with more vSphere experience (I first started with vSphere less than a month ago) to understand how this code may best serve the community, whether it simply targets a bootable vmdk, or any vmdk. If we target many vmdk I think we'd only need to refactor some variable names to make it more obvious and to document that the first disk defined with a vmdk will act as your bootable disk. This all may be a good ToDo for a future PR, since (IMO) the value add of this PR is already high. |
||
|
||
* `template` - (Required if size not provided) Template for this disk. | ||
* `template` - (Required if size and bootable_vmdk_path not provided) Template for this disk. | ||
* `datastore` - (Optional) Datastore for this disk | ||
* `size` - (Required if template not provided) Size of this disk (in GB). | ||
* `size` - (Required if template and bootable_vmdks_path not provided) Size of this disk (in GB). | ||
* `iops` - (Optional) Number of virtual iops to allocate for this disk. | ||
* `type` - (Optional) 'eager_zeroed' (the default), or 'thin' are supported options. | ||
* `vmdk` - (Required if template and size not provided) Path to a vmdk in a vSphere datastore. | ||
* `bootable` - (Optional) Set to 'true' if a vmdk was given and it should attempt to boot after creation. | ||
|
||
<a id="cdrom"></a> | ||
## CDROM | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do love it when I see all of the plus signs that add a unit test. Cookie for u!!!