18.3. The Image Uploader Tool
18.3.1. The Image Uploader Tool
Note
The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disk images, and templates can then be uploaded from the imported storage domain to the attached data center. See Section 8.6, “Importing Existing Storage Domains” for information on importing storage domains.
The
engine-image-uploader command allows you to list export storage domains and upload virtual machine images in OVF or OVA format to an export storage domain and have them automatically recognized in the Red Hat Virtualization Manager.
An OVA is a
tar archive of the OVF files.
Note
The image uploader only supports gzip-compressed OVF files, or OVA files, created by Red Hat Virtualization.
The OVF contains images and master directories in the following format:
|-- images | |-- [Image Group UUID] | |--- [Image UUID (this is the disk image)] | |--- [Image UUID (this is the disk image)].meta |-- master | |---vms | |--- [UUID] | |--- [UUID].ovf
18.3.2. Syntax for the engine-image-uploader Command
The basic syntax for the image uploader command is:
engine-image-uploader[options]listengine-image-uploader[options]upload[file].[file]...[file]
The image uploader command supports two actions -
list, and upload.
- The
listaction lists the export storage domains to which images can be uploaded. - The
uploadaction uploads images to the specified export storage domain.
You must specify one of the above actions when you use the image uploader command. Moreover, you must specify at least one local file to use the
upload action.
There are several parameters to further refine the
engine-image-uploader command. You can set defaults for any of these parameters in the /etc/ovirt-engine/imageuploader.conf file.
General Options
-h,--help- Displays information on how to use the image uploader command.
--conf-file=[PATH]- Sets [PATH] as the configuration file the command will use. The default is
etc/ovirt-engine/imageuploader.conf. --log-file=[PATH]- Sets [PATH] as the specific file name the command will use to write log output. The default is
/var/log/ovirt-engine/ovirt-image-uploader/ovirt-image-uploader-[date].log. --cert-file=[PATH]- Sets [PATH] as the certificate for validating the engine. The default is
/etc/pki/ovirt-engine/ca.pem. --insecure- Specifies that no attempt will be made to verify the engine.
--quiet- Sets quiet mode, reducing console output to a minimum.
-v,--verbose- Sets verbose mode, providing more console output.
-f,--force- Force mode is necessary when the source file being uploaded has the same file name as an existing file in the destination export domain. This option forces the existing file to be overwritten.
Red Hat Virtualization Manager Options
-u [USER],--user=[USER]- Specifies the user whose credentials will be used to execute the command. The [USER] is specified in the format [username]@[domain]. The user must exist in the specified domain and be known to the Red Hat Virtualization Manager.
-r [FQDN],--engine=[FQDN]- Specifies the IP address or fully qualified domain name of the Red Hat Virtualization Manager from which the images will be uploaded. It is assumed that the image uploader is being run from the same machine on which the Red Hat Virtualization Manager is installed. The default value is
localhost:443.
Export Storage Domain Options
The following options specify the export domain to which the images will be uploaded. These options cannot be used together; you must used either the
-e option or the -n option.
-e[EXPORT_DOMAIN],--export-domain=[EXPORT_DOMAIN]- Sets the storage domain EXPORT_DOMAIN as the destination for uploads.
-n[NFSSERVER],--nfs-server=[NFSSERVER]- Sets the NFS path [NFSSERVER] as the destination for uploads.
Import Options
The following options allow you to customize which attributes of the images being uploaded are included when the image is uploaded to the export domain.
-i,--ovf-id- Specifies that the UUID of the image will not be updated. By default, the command generates a new UUID for images that are uploaded. This ensures there is no conflict between the id of the image being uploaded and the images already in the environment.
-d,--disk-instance-id- Specifies that the instance ID for each disk in the image will not be renamed. By default, the command generates new UUIDs for disks in images that are uploaded. This ensures there are no conflicts between the disks on the image being uploaded and the disks already in the environment.
-m,--mac-address- Specifies that network components in the image will not be removed from the image. By default, the command removes network interface cards from image being uploaded to prevent conflicts with network cards on other virtual machines already in the environment. If you do not use this option, you can use the Administration Portal to add network interface cards to newly imported images and the Manager will ensure there are no MAC address conflicts.
-N [NEW_IMAGE_NAME],--name=[NEW_IMAGE_NAME]- Specifies a new name for the image being uploaded.
18.3.3. Creating an OVF Archive That is Compatible With the Image Uploader
Summary
You can create files that can be uploaded using the engine-image-uploader tool.
Procedure 18.2. Creating an OVF Archive That is Compatible With the Image Uploader
- Use the Manager to create an empty export domain. An empty export domain makes it easy to see which directory contains your virtual machine.
- Export your virtual machine to the empty export domain you just created.
- Log in to the storage server that serves as the export domain, find the root of the NFS share and change to the subdirectory under that mount point. You started with a new export domain, there is only one directory under the exported directory. It contains the
images/andmaster/directories. - Run the
tar -zcvf my.ovf images/ master/command to create the tar/gzip OVF archive. - Anyone you give the resulting OVF file to (in this example, called
my.ovf) can import it to Red Hat Virtualization Manager using theengine-image-uploadercommand.
Result
You have created a compressed OVF image file that can be distributed. Anyone you give it to can use the engine-image-uploader command to upload your image into their Red Hat Virtualization environment.
18.3.4. Basic engine-image-uploader Usage Examples
The following is an example of how to use the engine uploader command to list export storage domains:
Example 18.1. Listing export storage domains using the image uploader
# engine-image-uploader list Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): Export Storage Domain Name | Datacenter | Export Domain Status myexportdom | Myowndc | active
The following is an example of how to upload an Open Virtualization Format (OVF) file:
Example 18.2. Uploading a file using the image uploader
# engine-image-uploader -e myexportdom upload myrhel6.ovf Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort):
