Wednesday, October 31, 2012

Amazon VMware Import vApp

After Amazon announced they support not only VM import into their EC2 cloud, but now customers could export their VMs, we decided to try their "EC2 VM Import Connector for VMware vCenter".

The vApp download is actually a FreeBSD based VM.

The first issue I encountered was the VM boots up and assumes DHCP is available - the docs make no mention of static IP options - but the root credentials for the VM are documented (l: root p: )
So logging in as root on the VM console and running sysinstall allowed us to assign a static IP.
The next step was to login to the web interface of the VM, but even after a reboot there were no web services listening on 80 or 443.

Some more digging showed the port 80 web services would start by calling

/var/service/web-manage/run &

We could then sign into the web UI and get the VM registered with our vCenter:



Note: I ran into an issue with the UI not parsing my DOM\dom.username vcenter credentials (invalid username or password) - on a hunch I tried escaping the '\' - and indeed DOM\\\dom.username was accepted !

The next issue was port 443 web service (Connector vCenter Web Service) was not running.

It was less obvious how to start the port 443 service - so started digging through the amazon forums and ended up posting for assistance - someone from amazon replied with "we are looking into it"

I also discovered in the forums the tool currently only supports import of Windows 2003/2008 VMs!
This was surprising, and indeed many users in the forum are clamoring for Linux VM import support going back months.

While I wait for response on the port 443 service (anyone started it manually?) I am planning to check out the VMware Cloud Connector for import/export VM functionality.

Anyone had success demonstrating workload migration Private (VMware)<->Public ? 
VMware announced Zephyr 3 months ago - are they close to accepting signups?

3 comments:

reece denne said...

Hi Scott,

Did you ever get this working? Running into the same issues vCenter Server at IPADDRESS is not responding on TCP port 443.

Have telnet to the IPADDRESS 443 from the console of the appliance and is connecting fine.

Reece

reece denne said...

Hi Scott,

Did you ever get this working? Running into the same issues vCenter Server at IPADDRESS is not responding on TCP port 443.

Have telnet to the IPADDRESS 443 from the console of the appliance and is connecting fine.

Reece

vExpert2013 said...

I did not receive a meaningful response from Amazon and back in Oct 2013 lost interest when we found out Linux workloads were not migratable (just made that a word if it was not already).

However, now with vCHS I am compelled to revisit and compare