-
Notifications
You must be signed in to change notification settings - Fork 2
Examples
Make sure you have read the [system requirements](System Requirements) before you attempt these examples.
Assuming you installed simdeplower using the install instructions and have your OVA file downloaded into your ~/Downloads folder, and you were wanted the OVA extracted into ~/temp/simdeplower and wanted your VCSA named fancy-pants here is how you would do it
$ source ~/venvs/simdeplower/bin/activate
(pyenv: simdeplower) $ simdeplow --ova-path ~/Downloads/VMware-vCenter-Server-Appliance-5.5.0.10300-1945271_OVF10.ova --dest ~/temp/simdeplower --target fusion --name fancy-pants --log-level info
On my MacBook Pro this process take about 5 mins. When it is done it will tell you.
INFO:simdeplower:No ovftool_path set. Attempting to locate ovftool on file system.
INFO:simdeplower:Using /Applications/VMware OVF Tool/ovftool
INFO:simdeplower:Extracting ova to disk. This may take a while.
INFO:simdeplower:Extracted ova to disk.
INFO:simdeplower:Successful connection to vCenter made.
INFO:simdeplower:Simulator provisioning in process. This may take a while!
You can now log into your vcsa at: 192.168.88.207
vSphere user: [email protected]
vSphere password: password
I have the Retina MBP with 16G of RAM and the i7. YMMV based on system specs. When I used to use a batch script on Windows to do this same thing into Workstation it would take 30 mins but I didnt have an SSD..
If simdeplower is not able to locate vmrun and or ovftool you can provide the full path to these tools using additional args. Since you can provide this info it might be possible to get this working on Windows or Linux. If you have success doing that before I am able to test and officially claim it works please let me know.
-r VMRUN, --vmrun VMRUN
Full path to vmrun
-f OVFTOOL_PATH, --ovftool-path OVFTOOL_PATH
Full path to the ovftool to use for deployment.