[OSEv3:vars] openshift_management_install_management=true openshift_management_install_beta=true (1)
You can choose to deploy Red Hat CloudForms either during initial OpenShift Container Platform installation or after the cluster has been provisioned:
Ensure the following are set in your inventory file under the [OSEv3:vars]
section:
[OSEv3:vars] openshift_management_install_management=true openshift_management_install_beta=true (1)
| 1 | CFME 4.6 is currently available (not in beta), however this variable must be set
to true to begin the installation. This requirement will be removed in an
upcoming release.
(BZ#1557909) |
Set any other Red Hat CloudForms role variables in your inventory file as described in Configuring Role Variables. Resources to assist in this are provided in Example Inventory Files.
Choose which playbook to run depending on whether OpenShift Container Platform is already provisioned:
If you want to install Red Hat CloudForms at the same time you install your OpenShift Container Platform cluster, call the standard config.yml playbook as described in Running the Advanced Installation to begin the OpenShift Container Platform cluster and Red Hat CloudForms installation.
If you want to install Red Hat CloudForms on an already provisioned OpenShift Container Platform cluster, call the Red Hat CloudForms playbook directly to begin the installation:
# ansible-playbook -v [-i /path/to/inventory] \
/usr/share/ansible/openshift-ansible/playbooks/openshift-management/config.yml
The following sections show example snippets of inventory files showing various configurations of Red Hat CloudForms on OpenShift Container Platform that can help you get started.
|
See Configuring Role Variables for complete variable descriptions. |
This example is the simplest, using all of the default values and choices. This results in a fully-containerized (podified) Red Hat CloudForms installation. All application components, as well as the PostgreSQL database, are created as pods in OpenShift Container Platform:
[OSEv3:vars] openshift_management_app_template=cfme-template
This is as the previous example, except that instead of using local NFS services in the cluster, it uses an existing, external NFS server (such as a storage appliance). Note the two new parameters:
[OSEv3:vars] openshift_management_app_template=cfme-template openshift_management_storage_class=nfs_external (1) openshift_management_storage_nfs_external_hostname=nfs.example.com (2)
| 1 | Set to nfs_external. |
| 2 | Set to the host name of the NFS server. |
If the external NFS host exports directories under a different parent directory, such as /exports/hosted/prod, add the following additional variable:
openshift_management_storage_nfs_base_dir=/exports/hosted/prod
This example overrides the persistent volume (PV) sizes. PV sizes must be set
via openshift_management_template_parameters, which ensures that the
application and database are able to make claims on created PVs without
interfering with each other:
[OSEv3:vars]
openshift_management_app_template=cfme-template
openshift_management_template_parameters={'APPLICATION_VOLUME_CAPACITY': '10Gi', 'DATABASE_VOLUME_CAPACITY': '25Gi'}
In a test or proof-of-concept installation, you may need to reduce the application and database memory requirements to fit within your capacity. Note that reducing memory limits can result in reduced performance or a complete failure to initialize the application:
[OSEv3:vars]
openshift_management_app_template=cfme-template
openshift_management_template_parameters={'APPLICATION_MEM_REQ': '3000Mi', 'POSTGRESQL_MEM_REQ': '1Gi', 'ANSIBLE_MEM_REQ': '512Mi'}
This example instructs the installer to process the application template with
the parameter APPLICATION_MEM_REQ set to 3000Mi, POSTGRESQL_MEM_REQ set to
1Gi, and ANSIBLE_MEM_REQ set to 512Mi.
These parameters can be combined with the parameters displayed in the previous example Override PV Sizes.
To use an external database, you must change the
openshift_management_app_template parameter value to
cfme-template-ext-db.
Additionally, database connection information must be supplied using the
openshift_management_template_parameters variable. See
Configuring Role Variables for more
details.
[OSEv3:vars]
openshift_management_app_template=cfme-template-ext-db
openshift_management_template_parameters={'DATABASE_USER': 'root', 'DATABASE_PASSWORD': 'mypassword', 'DATABASE_IP': '10.10.10.10', 'DATABASE_PORT': '5432', 'DATABASE_NAME': 'cfme'}
|
Ensure your are running PostgreSQL 9.5 or you may not be able to deploy the application successfully. |