Creating vmx file to deploy onto vSphere about packer-windows HOT 10 CLOSED

I haven't tried pushing templates to vSphere from Packer yet. I've only run Packer to create the VM then manually run the ovftool. I wanted to ensure the ovftool was going to work before trying it through Packer. I'm not sure what the difference is, but I run sysprep on shutdown and then run ovftool after the box has powered off.

from packer-windows.

I'm not trying to push them from packer, I'm trying to use ovftool to manually push the intermediate .vmx file created by packer. This .vmx is configured to mount the floppy, which isn't available when I check the file with ovftool.

What file are you pushing with ovftool, are you extracting it from the .box file?

from packer-windows.

This is the command line I used:

ovftool --noSSLVerify=true --acceptAllEulas --name=patched-sso-test --datastore=esx_data1_dev --network=VLAN\ 103 ./output-vmware/packer-vmware.vmx vi://sneal:[email protected]/Daptiv\ HQ/host/IT/Resources/Packer

from packer-windows.

@kief Did you figure this out, or is this still an issue?

from packer-windows.

@joefitzgerald I ended up writing a wrapper script to run packer and then strip out the floppy configuration. This is the last bit:

for vmx in output-"${PACKER_BUILD}"/*.vmx ; do
  echo "Removing the setup floppy from the vmware image $vmx"
  perl -pi -e 's/floppy0.present = "TRUE"/floppy0.present = "FALSE"/' "${vmx}"
done

from packer-windows.

@kief It sounds like the ultimate fix here is for Packer to have a new provisioner (vmware-ovf / vmware-vsphere?): hashicorp/packer#582

Are you using the vSphere post-processor (hashicorp/packer#613 / http://www.packer.io/docs/post-processors/vsphere.html)? If so, I think this deserves a Packer issue and an associated pull request... what are your thoughts?

from packer-windows.

On Wed, Feb 26, 2014 at 6:25 AM, Joe Fitzgerald [email protected]:

@kief https://github.com/kief It sounds like the ultimate fix here is
for Packer to have a new provisioner (vmware-ovf / vmware-vsphere?):
hashicorp/packer#582 hashicorp/packer#582

Are you using the vSphere post-processor (hashicorp/packer#613hashicorp/packer#613
http://www.packer.io/docs/post-processors/vsphere.html)? If so, I think
this deserves a Packer issue and an associated pull request... what are
your thoughts?

I'd see it as a post-processor rather than a provisioner of its own. The
actual provisioning would be exactly the same, wouldn't it? It's just that
in some cases, you want to package it up into an ovf, and/or push it up to
vSphere.

I'd kind of like to be able to fire up the template locally and run tests
on it (e.g. serverspec) before pushing it up to vSphere. I also might want
to use it as an input to build other templates, e.g. have a base template,
then create a few other templates with more specific things on them (nginx,
database, etc.)

K

from packer-windows.

@kief So what are the actions to come from this? I'd like to get specific about next steps. If there are none, perhaps we should consider closing the issue?

from packer-windows.

Happy to reopen if we identify next steps.

from packer-windows.

had the same issue.
it worked after adding ovftool post-processor before vsphere.

from packer-windows.