Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 2. Platform Administration

This chapter covers tasks related to the various OpenShift Enterprise platform components on broker and node hosts.
Starting with OpenShift Enterprise 2.2, the Apache Virtual Hosts front-end HTTP proxy is the default for new deployments. If your nodes are currently using the previous default, the Apache mod_rewrite plug-in, you can use the following procedure to change the front-end configuration of your existing deployment.
Configuring the HTTP front-end for an already-deployed OpenShift Enterprise instance after it has been configured is possible, but Red Hat recommends caution when doing so. You must first prevent any front-end changes made by the broker, such as creating or deleting application gears, on the node host containing the applications during this configuration change. Performing a verified backup of the node host before commencing configuration is highly recommended.
See the OpenShift Enterprise Deployment Guide for more information about installing and configuring front-end HTTP server plug-ins.

Procedure 2.1. To Change the Front-end HTTP Configuration on an Existing Deployment:

  1. To prevent the broker from making any changes to the front-end during this procedure, stop the ruby193-mcollective service on the node host: 
    # service ruby193-mcollective stop
    Copy to Clipboard Toggle word wrap
    Then set the following environment variable to prevent each front-end change from restarting the httpd service: 
    # export APACHE_HTTPD_DO_NOT_RELOAD=1
    Copy to Clipboard Toggle word wrap
  2. Back up the existing front-end configuration. You will use this backup to restore the complete state of the front end after the process is complete. Replace filename with your desired backup storage location: 
    # oo-frontend-plugin-modify --save > filenameoo-frontend-plugin-modify --save > filename
    Copy to Clipboard Toggle word wrap
  3. Delete the existing front-end configuration: 
    # oo-frontend-plugin-modify --delete
    Copy to Clipboard Toggle word wrap
  4. Remove and install the front-end plug-in packages as necessary: 
    # yum remove rubygem-openshift-origin-frontend-apache-mod-rewrite
# yum -y install rubygem-openshift-origin-frontend-apache-vhost
    Copy to Clipboard Toggle word wrap
  5. Replicate any Apache customizations reliant on the old plug-in onto the new plug-in, then restart the httpd service: 
    # service httpd restart
    Copy to Clipboard Toggle word wrap
  6. Change the OPENSHIFT_FRONTEND_HTTP_PLUGINS value in the /etc/openshift/node.conf file from openshift-origin-frontend-apache-mod-rewrite to openshift-origin-frontend-apache-vhost: 
    OPENSHIFT_FRONTEND_HTTP_PLUGINS="openshift-origin-frontend-apache-vhost"
    Copy to Clipboard Toggle word wrap
  7. Un-set the previous environment variable to restarting the httpd service as normal after any front-end changes: 
    # export APACHE_HTTPD_DO_NOT_RELOAD=""
    Copy to Clipboard Toggle word wrap
  8. Restart the MCollective service: 
    # service ruby193-mcollective restart
    Copy to Clipboard Toggle word wrap
  9. Restore the HTTP front-end configuration from the backup you created in step one: 
    # oo-frontend-plugin-modify --restore < filenameoo-frontend-plugin-modify --restore < filename
    Copy to Clipboard Toggle word wrap
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat