Hi Alvaro,
I think you got me wrong. I didnt explain it properly also. I am running a
vmware-iso builder only, but this is being run from a Azure VM contacting a
ESX machine.
Below is my code. My question is why image is getting exported to this
azure VM. When I run the same code from a vmware VM it creates the image in
ESX machine itself. Both cases I am not using 'format' option.
Thanks in advance
{
"variables": {
"vm_name": "packer",
"vm_description": "rhel7 base",
"iso": "/data/rhel-server-7.5-x86_64-dvd.iso",
"checksum":
"d0dd6ae5e001fb050dafefdfd871e7e648b147fb2d35f0e106e0b34a0163e8f5",
"iso_checksum_type": "sha256",
"remote_password" : "{{env `ESX_SSH_PASS`}}",
"ssh_password": "{{env `VM_SSH_PASS`}}"
},
"builders": [
{
"type": "vmware-iso",
"ssh_username": "packer",
"ssh_password": "{{ user `ssh_password` }}",
"ssh_port": 22,
"ssh_wait_timeout": "30m",
"http_directory": "./",
"vm_name": "{{ user `vm_name` }}",
"guest_os_type": "rhel7-64",
"iso_url": "{{ user `iso` }}",
"iso_checksum": "{{ user `checksum` }}",
"iso_checksum_type": "{{ user `iso_checksum_type` }}",
"tools_upload_flavor": "linux",
"remote_datastore": "datastore_name",
"remote_host": "IP_ESX",
"remote_password": "{{ user `remote_password` }}",
"remote_type": "esx5",
"remote_username": "root",
"disk_size": "32000",
"headless": false,
"vnc_port_min": 5980,
"vnc_port_max": 5990,
"vmx_data": {
"memsize": 512,
"ethernet0.networkName": "network_name",
"ethernet0.present": "TRUE",
"ethernet0.startConnected": "TRUE",
"ethernet0.virtualDev": "e1000",
"ethernet0.addressType": "generated",
"ethernet0.generatedAddressOffset": "0",
"ethernet0.wakeOnPcktRcv": "FALSE",
"numvcpus": 1
},
"boot_wait": "10s",
"boot_command": [
"<esc><wait>",
"vmlinuz initrd=initrd.img net.ifnames=0 biosdevname=0 ",
"<tab> text ks=http://{{ .HTTPIP }}:{{ .HTTPPort }}/ks4.cfg ip=IP
netmask=maske_details gateway=gatwway_details<enter><wait>"
],
"shutdown_command": "echo '{{ user `username` }}' | sudo -S shutdown
-P now"
}
]
}
Shyam
On Monday, 6 August 2018 09:20:46 UTC+5:30, Alvaro Miranda Aguilera wrote:
>
> ovftool is a vmware tool.
>
> if you share your packer template, I can sugges some filters. but you
> shouldn't be running ovftool on non vmware setups.
>
> you can add "only": ["vmware-iso"] to restrict a provisioner/post-processor
>
> alvaro
>
> On Mon, Aug 6, 2018 at 6:36 AM, Shyam J <[email protected] <javascript:>>
> wrote:
>
>> Yes when running the same packer code from a vmware VM which outputs in
>> ESX machine while when running packer code from azure VM looking for
>> ovftool.
>>
>> Thanks
>> Shyam
>>
>> On Saturday, 4 August 2018 02:10:06 UTC+5:30, Alvaro Miranda Aguilera
>> wrote:
>>>
>>> hello
>>>
>>>
>>> azure?
>>>
>>> On Fri, Aug 3, 2018 at 3:00 PM, Shyam J <[email protected]> wrote:
>>>
>>>> Hi,
>>>> If this question doesnt have an answer now its fine, I can wait.
>>>>
>>>> But can you tell me why when format is not mentioned also packer is
>>>> looking for ovftool to export in Azure VM? Why cant it keep the exports in
>>>> ESX machine?
>>>>
>>>> Thanks
>>>> Shyam
>>>>
>>>> --
>>>> 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/5b359b54-65fe-410f-8379-b4d95cd78711%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/packer-tool/5b359b54-65fe-410f-8379-b4d95cd78711%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] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/packer-tool/529f6a3c-a77b-4b10-807a-2a8f7c7574f3%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/packer-tool/529f6a3c-a77b-4b10-807a-2a8f7c7574f3%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/5b5d3b35-2d81-4f86-8366-7615615c45ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
