So far he best method that I have found to move images about between systems is to use the ICCT server as the staging for the OVA file, coping that data there first before you move it to your other environments. First ensure that the ICCT/Staging server has sufficient space to store the image as the export job will unzip the raw disk image from the V7000 storage. So if your disk is 25Gb you will need 25G (+/-1 or 2G) to stage the raw disk before it creates the ova that you can import. In my case our server has a 100G disk that I can stage these to one at a time, but as you can imagine if you are doing multiple or larger images that container will need to be considerably larger.
From ICCT login and go to the 'Images and bundles - Build and manage images' page -
Select the image you wish to import and then click the 'export as OVA' button -
Fill in the details of where you want to stage you image -
Once it is exporting, the first step that ICCT wil take is to prep the cloud provider so that image is ready to be copied. This will involve VMControl checking the disk details and information it has from the V7000. Next the V7000 will run a 'svctask mkfcmap' and make a copy of the image ready for it to be exported. It then maps that disk to your VIOS and then that disk will be 'dd' to a file at the following location -
So while you might not see any activity on the staging server immediately, have a look at the VIOS and you will get a idea of how things are progressing. The disk is then removed and the old image cleaned up off the V7000. The required contents for the OVA are created by ICCT, such as language and ovf files containing the detail about how the OVA is made up.
Once this is completed its copied over to the requested server, in our case the ICCT server and the image deleted off of the VIOS. The image is then unzipped, creating the raw 25Gb disk file, the related files are put together and the ova file created and then zipped up. Once this is finished you should see the image on your server -
# ls -l /data/ova
-rw-r--r-- 1 root system 2063359759 08 May 14:32 icon_image_<image-name>_1_0_0.ova.zip
To import in to VMControl its a good idea to extract that image as follows -
# jar -xvf icon_image_<image-name>_1_0_0.ova.zip
Make sure you only use 'jar' to unzip and then extract the tar as other zip/tar utilities will get a incorrect size returned and the data will be useless.
Now you can import this ova into you other Flex. You need to copy it over to your FSM so you can import it direct or host the files on a http server enabling you download the image, once you have done this you can start the import.
So go to the VMControl front page, Virtual Appliances, and select import -
Put in the address/location of the OVF (/dump/ova/icon_image_iic_<image-name>_1_0_0.ovf), click next. Ensure that 'Import without digital signature' is selected, then update/review the description and search tags. Select the image repository it will be imported into, and then in my case this is a new image so 'create a new version tree'. Finally review the virtual appliance details and if your happy click 'Finish'. You can then monitor the job via the link that pops up or the 'Task Management - Active and Scheduled Jobs' task in the FSM.
Now you should find that your image is available for use via VMControl or other Cloud software like ICCT and Smart Cloud Entry.