Importing VMware OVA Windows virtual machines into an AppLogic Grid
Utilities Used: ovfexport.sh and image2class
Machines Utilized: Backbone Fabric Controller and Grid Controller
Make sure there is enough space on the BFC before running the next command. An additional drive or more space may need to be added to the BFC depending on the size of the machine being exported.
- Download and install the latest OVF Linux VMWare Utility onto the BFC.
Run the following command on the BFC:
Once the ovfexport.sh utility completes, copy the created .ova file to the _impex volume on the Grid Controller with the following command:
- /opt/bfc/applogic_versions/3.0.30/ovfexport.sh vi://192.168.32.130/INFRA01 INFRA01
The address in the URL is the address of the ESX or vCenter host, and INFRA01 is the name of the machine as listed in ESX or vCenter; in this case it is an ESX host. The last INFRA01 is the name of the resultant .ova file which will be INFRA01.ova.
The following is an additional example utilizing a copy of a VMware machine copied to the BFC:
[email protected] media2 # /opt/bfc/applogic_versions/3.0.30/ovfexport.sh ITDCA01/ITDCA01.vmx ITDCA01
Notice that the current working directory is the /media2 directory as shown on the bash shell prompt.
Note: Another directory cannot be specified to place the resultant .ova file in because the utility expects the file to be in the current working directory i.e. [email protected] media2#. If another directory is specified, the utility will successfully create the .ova file; however, when the image2class utility is invoked to import the .ova file it will fail because the ovfexport.sh file wraps the files one directory too deep; i.e. it wraps the files in the /OVA/media2 directory if the /media2 folder is specified in the filename. The files need to be wrapped in the root of the /OVA directory in order for image2class to process them properly. By using the current working directory and not specifying another directory, ovfexport.sh properly places the files in the .ova file wrapped in the /OVA directory. Bottom line, run the command from the current working directory and all will be well when trying to import the .ova file on the Grid using the image2class utility.
Run the image2class utility on the Grid Controller using the following command:
Once step 5 is complete, follow the instructions to install the Windows APK and make the newly imported Singleton a fully managed AppLogic Appliance:
- 3t util image2class INFRA01:INFRA01 INFRA01.ova --unmanaged
Where INFRA01:INFRA01 = Application Name as listed on the Grid:Class Name of the resultant Singleton which will be created on the Grid.
Once the imported machine has been verified, the apk has been installed, and if the name of the machine is not expected to change, i.e. INFRA01, INFRA02, etc., add an applogic_init file to the /cygwin/etc/sysconfig directory (Windows) with the following parameter set:
Note: The CygWin utility must be downloaded and installed first and the apk-x.x.xx-windows.tar.gz file must downloaded and copied to the ** c:\cygwin\tmp folder after CygWin has been installed. To get access to both downloads, run ipconfig /all from a command prompt within the newly imported Singleton's Gui Console and locate the DHCP server address. Once located plug it into the following URL within IE on the Singleton: http://x.x.x.x:8080/download; CygWin will be listed as "Server_Windows-x.x.x-x.msi" and the APK will be listed as "apk-x.x.xx-windows.tar.gz". Also note that the instructions say to un-pack the APK file with gtar, use tar with the same parameters if gtar does not work.
If desired, add the newly imported singleton to the Catalog.
This will stop AppLogic from renaming the system once it has been added to the catalog.
You will have a running VMware VM on an AppLogic grid.