Deployment to VMware

Note, the vmrun remoter_base is in hyper active development, so the following is likely to change.

Getting started

First, make sure your vmware instance is accessible via ssh through a keypair.

scp ~/.ssh/id_rsa.pub root@local_vmware_ip:/root/.ssh/authorized_keys

I’d make a snapshot at this point. When you want to start over, this is the snapshot you’ll return to.

Make sure the vmrun is in your PATH. For example, using VMware Fusion on Mac OSX add the following to your .profile

   export PATH=$PATH:/Library/Application\ Support/VMware\ Fusion

clouds.rb

PoolParty defaults the remoter_base to ec2, but you can change this by simply adding a using line (see below). An important point to note is that currently the vmrun remoter base requires a few specifications. To add these to the vmrun remoter_base, add them into a block, like so:

    using :vmrun do
      vmx_hash({
        "/Users/alerner/Documents/Virtual Machines.localized/one.vmwarevm/Ubuntu Linux 32bit.vmx" => "192.168.248.128"
      })
    end

So, in the above example, you’ll see that I’m listing a .vmx file as the key and pointing it to an ip address. This may change in the future, but it’s important that these are listed correctly. The .vmx file is a file located in the VMWare folder. To find this, I cd into the directory and ls *.vmx.

Make sure networking is set to NAT and type ifconfig eth0. If you get the error saying the interface isn’t found, see the next step, otherwise you’re set.

To fix the eth0 network interface not found, log onto your vmware instance:

/etc/init.d/udev stop
/etc/init.d/networking stop

	
Edit this file and comment out every line except the final one. Change the final one to interface with
	
eth0

vim /etc/init.d/udev/70-persistent-net.rules

/etc/init.d/udev start

/etc/init.d/networking start

Cloud start

Type cloud start and your cloud should be booting on vmware!