Chapter 2. Platform Administration

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

   Then set the following environment variable to prevent each front-end change from restarting the httpd service:

   # export APACHE_HTTPD_DO_NOT_RELOAD=1

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

3. Delete the existing front-end configuration:

   # oo-frontend-plugin-modify --delete

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

5. Replicate any Apache customizations reliant on the old plug-in onto the new plug-in, then restart the httpd service:

   # service httpd restart

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"

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

8. Restart the MCollective service:

   # service ruby193-mcollective restart

9. Restore the HTTP front-end configuration from the backup you created in step one:

   # oo-frontend-plugin-modify --restore < filename