44 GB of storage space on both the export domain and the local partition where /tmp resides, as the OVF archive is locally expanded into that directory.

12 GB RAM.

4 vCPUs.

1.2.1. Uploading the Appliance Using the Administration Portal

In Red Hat Virtualization 4.0 and newer, upload the QCOW2 appliance image using the Red Hat Virtualization Administration Portal.
After uploading the image, create a disk and attach it to a virtual machine.

Internet Explorer 10, Firefox 35, or Chrome 13 or greater is required to perform this upload procedure. Previous browser versions do not support the required HTML5 APIs.

You must import the required certificate authority into the web browser used to access the Administration Portal.

To import the certificate authority, browse to https://<engine_address>/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA and select all the trust settings. Refer to the instructions to install the certificate authority in Firefox, Internet Explorer, or Google Chrome.

It takes approximately 90 minutes to upload the ManageIQ appliance file to the Red Hat Enterprise Virtualization Manager. Once the OVA is uploaded and imported as a template, add a network adapter to the template itself.

1.2.3. Uploading the Appliance Manually

The following procedure provides manual upload instructions if the image uploader tool is not available or fails to upload.

Log in to a host in your Red Hat Virtualization system with a mount to the export storage domain.

Change to the export storage domain’s directory.

Copy the ManageIQ appliance OVF archive to this directory.

Run the ls command to locate the directory named after a GUID, and change to that directory.

Extract the OVF file using the tar command, substituting the .ova filename with your download. For example:

Press the number for the item you want to change, and press Enter. The options for your selection are displayed.

Follow the prompts to make the changes.

Press Enter to accept a setting where applicable.

The ManageIQ appliance console automatically logs out after five minutes of inactivity.

2.2. Configuring a Worker Appliance

You can use multiple appliances to facilitate horizontal scaling, as well as for dividing up work by roles. Accordingly, configure an appliance to handle work for one or many roles, with workers within the appliance carrying out the duties for which they are configured. You can configure a worker appliance through the terminal. The following steps demonstrate how to join a worker appliance to an appliance that already has a region configured with a database.

Start the appliance and open a terminal console.

After starting the appliance, log in with a user name of root and the default password of smartvm. This displays the Bash prompt for the root user.

You are prompted to create or fetch a security key. Since this is not the first ManageIQ appliance, choose 2) Fetch key from remote machine. For worker and multi-region setups, use this option to copy key from another appliance.

All ManageIQ appliances in a multi-region deployment must use the same key.

3.1. Changing the Default Login Password

Change your password to ensure more private and secure access to ManageIQ.

Navigate to the URL for the login screen. (https://xx.xx.xx.xx on the virtual machine instance)

Click Update Password beneath the Username and Password text fields.

Enter your current Username and Password in the text fields.

Input a new password in the New Password field.

Repeat your new password in the Verify Password field.

Click Login.

Appendix A: Appendix

A.1. Appliance Console Command-Line Interface (CLI)

Currently, the appliance_console_cli feature is a subset of the full functionality of the appliance_console itself, and covers functions most likely to be scripted using the command-line interface (CLI).

After starting the ManageIQ appliance, log in with a user name of root and the default password of smartvm. This displays the Bash prompt for the root user.

Enter the appliance_console_cli or appliance_console_cli --help command to see a list of options available with the command, or simply enter appliance_console_cli --option <argument> directly to use a specific option.

Table 1. Database Configuration Options

Option

Description

--region (-r)

region number (create a new region in the database - requires database credentials passed)

--internal (-i)

internal database (create a database on the current appliance)

--dbdisk

database disk device path (for configuring an internal database)

--hostname (-h)

database hostname

--port

database port (defaults to 5432)

--username (-U)

database username (defaults to root)

--password (-p)

database password

--dbname (-d)

database name (defaults to vmdb_production)

Table 2. v2_key Options

Option

Description

--key (-k)

create a new v2_key

--fetch-key (-K)

fetch the v2_key from the given host

--force-key (-f)

create or fetch the key even if one exists

--sshlogin

ssh username for fetching the v2_key (defaults to root)

--sshpassword

ssh password for fetching the v2_key

Table 3. IPA Server Options

Option

Description

--host (-H)

set the appliance hostname to the given name

--ipaserver (-e)

IPA server FQDN

--ipaprincipal (-n)

IPA server principal (default: admin)

--ipapassword (-w)

IPA server password

--ipadomain (-o)

IPA server domain (optional). Will be based on the appliance domain name if not specified.

--iparealm (-l)

IPA server realm (optional). Will be based on the domain name of the ipaserver if not specified.

--uninstall-ipa (-u)

uninstall IPA client

In order to configure authentication through an IPA server, in addition to using Configure External Authentication (httpd) in the appliance_console, external authentication can be optionally configured via the appliance_console_cli (command-line interface).

Specifying --host will update the hostname of the appliance. If this step was already performed via the appliance_console and the necessary updates made to /etc/hosts if DNS is not properly configured, the --host option can be omitted.