Create a bucket by clicking Create Bucket, and configure the following details:

Enter a unique Name for the bucket using lower case alphanumeric characters, hyphens, and/or underscores.

Configure your location from the dropdown list.

Click Create.

Click Upload Files and browse to the location of the ManageIQ Google Compute Engine appliance you downloaded. Select the tar.gz file on your local machine, and click Open to begin the upload.

When the upload is complete, click Products & servicesCompute Engine on the left menu.

Create an image by clicking Images from the left menu, then Create Image. Fill in the following details about the image:

Enter a unique Name for the image using lower case alphanumeric characters and/or hyphens.

Add a Description if desired.

Configure Encryption if desired. This defaults to Automatic (recommended).

In Source, use the dropdown to select Cloud Storage file. This shows the Cloud Storage file field.

In Cloud Storage file, click Browse to bring up the Select object window. Select the bucket containing the image you uploaded and click the > symbol to locate the tar.gz image inside the bucket. Select the image and click Select.

Click Create. Creating the image will take a few minutes. When the image is created, the screen will refresh and the new image will appear in the Images list.

Create a virtual machine instance by navigating to VM instancesCreate Instance, and configure the following fields:

Enter a unique Name for the virtual machine instance using lower case alphanumeric characters and/or hyphens.

Select the Zone closest to your location.

Under Boot disk, click Change to bring up the Boot disk window. Click the Your Image tab and select the disk you previously created. Click Select.

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.

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.