As a regular user, log in to OpenShift:

$ oc login -u <user> -p <password>

Create a project with your desired parameters. The <project_name> is mandatory, but <description> and <display_name> are optional:

$ oc new-project <project_name> \
--description="<description>" \
--display-name="<display_name>"

Add the cfme-anyuid service account to the anyuid security context constraint (SCC).

Because the CloudForms image requires the root user, the cfme-anyuid service account for your namespace (project) must be added to the anyuid SCC before pods using the service account can run as root.

Add your default service account to the privileged security context. The default service account for your namespace (project) must be added to the privileged security context constraints (SCCs) before they can run privileged pods.

Prepare persistent storage for the deployment. (Skip this step if you have already configured persistent storage.)

A regular CloudForms deployment needs at least two persistent volumes (PVs) to store CloudForms data. As the admin user, create two persistent volumes: one to host the CloudForms PostgreSQL database, and one to host the application data.

Example NFS-backed volume templates are provided by cfme-pv-db-example.yaml and cfme-pv-server-example.yaml, available from GitHub.

Increase the maximum number of imported images on ImageStream.

By default, OpenShift Container Platform can import five tags per image stream, but the CloudForms repositories contain more than five images for deployments.

You can modify this setting on the master node at /etc/origin/master/master-config.yaml so OpenShift can import additional images.

As a regular user, create the Red Hat CloudForms template:

$ oc create -f templates/cfme-template.yaml
template "cloudforms" created

Verify the template is available with your project:

$ oc get templates
NAME         DESCRIPTION                                    PARAMETERS        OBJECTS
cloudforms   CloudForms appliance with persistent storage   18 (1 blank)      12

(Optional) Customize the template’s deployment parameters. Use the following command to see the available parameters and descriptions:

$ oc process --parameters -n <your-project> cloudforms

To customize the deployment configuration parameters, run:

$ oc edit dc/<deployconfig_name>

To deploy Red Hat CloudForms from template using default settings, run:

$ oc new-app --template=cloudforms

Alternatively, to deploy Red Hat CloudForms from a template using customized settings, add the -p option and the desired parameters to the command. For example:

$ oc new-app --template=cloudforms -p DATABASE_VOLUME_CAPACITY=2Gi,POSTGRESQL_MEM_LIMIT=4Gi,APPLICATION_DOMAIN=hostname

Confirm the Red Hat CloudForms pod is bound to the correct security context constraints.

Verify the persistent volumes are attached to the postgresql and cfme-app pods:

$ oc volume pods --all
pods/postgresql-1-437jg
  pvc/cfme-pgdb-claim (allocated 2GiB) as cfme-pgdb-volume
    mounted at /var/lib/pgsql/data
  secret/default-token-2se06 as default-token-2se06
    mounted at /var/run/secrets/kubernetes.io/serviceaccount
pods/cfme-1-s3bnp
  pvc/cfme (allocated 2GiB) as cfme-app-volume
    mounted at /persistent
  secret/default-token-9q4ge as default-token-9q4ge
    mounted at /var/run/secrets/kubernetes.io/serviceaccount

Check the readiness of the CloudForms pod:

$ oc describe pods <cfme_pod_name>
...
Conditions:
  Type      Status
  Ready     True
Volumes:
...

After you have successfully validated your CloudForms deployment, disable automatic image change triggers to prevent unintended upgrades.

By default, on initial deployments the automatic image change trigger is enabled. This could potentially start an unintended upgrade on a deployment if a newer image is found in the ImageStream.

Disable the automatic image change triggers for CloudForms deployment configurations (DCs) on each project with the following commands:

$ oc set triggers dc --manual -l app=cloudforms
deploymentconfig "memcached" updated
deploymentconfig "postgresql" updated

$ oc set triggers dc --from-config --auto -l app=cloudforms
deploymentconfig "memcached" updated
deploymentconfig "postgresql" updated