Red Hat Training

A Red Hat training course is available for Red Hat CloudForms

Installing Red Hat CloudForms on Google Compute Engine

Red Hat CloudForms 4.7

How to install and configure Red Hat CloudForms on a Google Compute Engine environment

Red Hat CloudForms Documentation Team

Abstract

This guide provides instructions on how to install and configure Red Hat CloudForms on a Google Compute Engine environment.
If you have a suggestion for improving this guide or have found an error, please submit a Bugzilla report at http://bugzilla.redhat.com against Red Hat CloudForms Management Engine for the Documentation component. Please provide specific details, such as the section number, guide name, and CloudForms version so we can easily locate the content.

Chapter 1. Installing Red Hat CloudForms

Installing Red Hat CloudForms consists of the following steps:

  1. Downloading the appliance for your environment as a virtual machine image template.
  2. Setting up a virtual machine based on the appliance.
  3. Configuring the CloudForms appliance.

After you have completed all the procedures in this guide, you will have a working environment on which additional customizations and configurations can be performed.

1.1. Obtaining the Appliance

  1. Go to access.redhat.com and log in to the Red Hat Customer Portal using your customer account details.
  2. Click Downloads in the menu bar.
  3. Click A-Z to sort the product downloads alphabetically.
  4. Click Red Hat CloudForms to access the product download page.
  5. From the list of installers and images, click the Download Now link for Google Compute Engine.

1.2. Uploading the Appliance on Google Compute Engine

When the Red Hat CloudForms Google Compute Engine appliance has finished downloading to your system, upload the appliance to Google Compute Engine.

To upload the Red Hat CloudForms Google Compute Engine appliance file you will need: * 44 GB of storage space. * 12 GB RAM. * 4 vCPUs.

You can upload the appliance with the following steps:

  1. Log in to the Google Cloud Platform dashboard.
  2. Click Home in the top left of the screen.
  3. Click GCE products services to show the Products and Services menu. Click Storage.
  4. Create a bucket by clicking Create Bucket, and configure the following details:

    1. Enter a unique Name for the bucket using lower case alphanumeric characters, hyphens, and/or underscores.
    2. Configure your location from the dropdown list.
    3. Click Create.
  5. Click Upload Files and browse to the location of the Red Hat CloudForms Google Compute Engine appliance you downloaded. Select the tar.gz file on your local machine, and click Open to begin the upload.
  6. When the upload is complete, click GCE products services Products & servicesCompute Engine on the left menu.
  7. Create an image by clicking Images from the left menu, then Create Image. Fill in the following details about the image:

    1. Enter a unique Name for the image using lower case alphanumeric characters and/or hyphens.
    2. Add a Description if desired.
    3. Configure Encryption if desired. This defaults to Automatic (recommended).
    4. In Source, use the dropdown to select Cloud Storage file. This shows the Cloud Storage file field.
    5. 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.
    6. 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.
  8. Create a virtual machine instance by navigating to VM instancesCreate Instance, and configure the following fields:

    1. Enter a unique Name for the virtual machine instance using lower case alphanumeric characters and/or hyphens.
    2. Select the Zone closest to your location.
    3. 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.
    4. Under Firewall, select the check box for Allow HTTPS traffic.
    5. Click GCE ManagementSSHkeys Management, disk, networking, SSH keys. Then, click the SSH Keys tab, add your entire SSH public key data in the Username box.
    6. Configure any other fields as desired, and click Create.

Your new virtual machine instance, as well as the external IP address for accessing the Red Hat CloudForms interface, appears under VM instances.

Chapter 2. Logging In After Installing Red Hat CloudForms

Once Red Hat CloudForms is installed, you can log in and perform administration tasks.

Log in to Red Hat CloudForms for the first time after installing by:

  1. Navigate to the URL for the login screen. (https://xx.xx.xx.xx on the virtual machine instance)
  2. Enter the default credentials (Username: admin | Password: smartvm) for the initial login.
  3. Click Login.

2.1. Changing the Default Login Password

Change your password to ensure more private and secure access to Red Hat CloudForms.

  1. Navigate to the URL for the login screen. (https://xx.xx.xx.xx on the virtual machine instance)
  2. Click Update Password beneath the Username and Password text fields.
  3. Enter your current Username and Password in the text fields.
  4. Input a new password in the New Password field.
  5. Repeat your new password in the Verify Password field.
  6. 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).

  1. After starting the Red Hat CloudForms appliance, log in with a user name of root and the default password of smartvm. This displays the Bash prompt for the root user.
  2. 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 A.1. Database Configuration Options

OptionDescription

--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 A.2. v2_key Options

OptionDescription

--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 A.3. IPA Server Options

OptionDescription

--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

Note
  • 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.

Table A.4. Certificate Options

OptionDescription

--ca (-c)

CA name used for certmonger (default: ipa)

--postgres-client-cert (-g)

install certs for postgres client

--postgres-server-cert

install certs for postgres server

--http-cert

install certs for http server (to create certs/httpd* values for a unique key)

--extauth-opts (-x)

external authentication options

Note

The certificate options augment the functionality of the certmonger tool and enable creating a certificate signing request (CSR), and specifying certmonger the directories to store the keys.

Table A.5. Other Options

OptionDescription

--logdisk (-l)

log disk path

--tmpdisk

initialize the given device for temp storage (volume mounted at /var/www/miq_tmp)

--verbose (-v)

print more debugging info

Example Usage

$ ssh root@appliance.test.company.com

To create a new database locally on the server using /dev/sdb:

# appliance_console_cli --internal --dbdisk /dev/sdb --region 0 --password smartvm

To copy the v2_key from a host some.example.com to local machine:

# appliance_console_cli --fetch-key some.example.com --sshlogin root --sshpassword smartvm

You could combine the two to join a region where db.example.com is the appliance hosting the database:

# appliance_console_cli --fetch-key db.example.com --sshlogin root --sshpassword smartvm --hostname db.example.com --password mydatabasepassword

To configure external authentication:

# appliance_console_cli --host appliance.test.company.com
                        --ipaserver ipaserver.test.company.com
                        --ipadomain test.company.com
                        --iparealm TEST.COMPANY.COM
                        --ipaprincipal admin
                        --ipapassword smartvm1

To uninstall external authentication:

# appliance_console_cli  --uninstall-ipa