Hi Matt
The way I did that is, first of all ,vmdk_name is the option to use to give
the disk a name ( see below how I pass a variable to that option to give
the disk a specific name )
"vmdk_name":"{{user \`vmdk\`}}",
Secondly the way I created multiple disk is to modify the vmx data.. but
not entirely sure if *vmdk_name (string)* , if you add multiple entries like
vmdk_name : root-disk
vmdk_name : data-disk
Will be something that works.. I personally do not think so because the
option is a string and I'd expect to have an array if that option can
create more than one disk...
But is worth the shot .. if that doesn't work, I will recommend you to
modify the VMX file and add the disks there
On Wednesday, January 31, 2018 at 5:19:55 AM UTC+13, Matt Hickok wrote:
>
> So that makes sense. If I want the first disk to be named 'os' and the
> second disk to be named 'data', would I need to set the disknames then? Or
> is there a different way to do it? I have a feeling I need to modify the
> vmx data.
>
> On Tuesday, January 30, 2018 at 2:13:47 AM UTC-6, Alvaro Miranda Aguilera
> wrote:
>>
>> can you test?
>>
>> vmdk_name <https://www.packer.io/docs/builders/vmware-iso.html#vmdk_name>
>> (string) - The filename of the virtual disk that'll be created, without
>> the extension. This defaults to "packer".
>>
>> seems it will use the disk name
>>
>>
>> https://github.com/hashicorp/packer/blob/7f4112ba229309cfc0ebaa10ded2abdfaf1b22c8/builder/vmware/iso/step_create_vmx.go#L243-L247
>>
>>
>>
>> On Tue, Jan 30, 2018 at 1:07 AM, Matt Hickok <[email protected]>
>> wrote:
>>
>>> Hello,
>>>
>>> If I am producing multiple VMDKs during a vmware-iso build, is there a
>>> way to name both disks? There is a 'vmdk_name' field but I don't know how
>>> this works with multiple disks. Or would I need to edit the vmx data?
>>>
>>> Thanks!
>>>
>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/packer-tool/e979e80f-698b-4c0f-beb9-311338234ec4%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/packer-tool/e979e80f-698b-4c0f-beb9-311338234ec4%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Alvaro
>>
>>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/packer-tool/a3322556-8b02-4e20-a9f8-1fdc9310c6ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
