7.8.8. Configuring the Broker Plug-ins
Enable the required plug-ins for authentication, DNS, and messaging in the
/etc/openshift/plugins.d directory. For example, the example.conf file enables the example plug-in. The contents of the example.conf file contain configuration settings in the form of lines containing key=value pairs. In some cases, the only requirement is to copy an example configuration. Other plug-ins, such as the DNS plug-in, require further configuration.
Change to the
/etc/openshift/plugins.d/ directory to access the files needed for the following configuration steps:
# cd /etc/openshift/plugins.dProcedure 7.14. To Configure the Required Plug-ins:
- Copy the example configuration file for the remote user authentication plug-in:
# cp openshift-origin-auth-remote-user.conf.example openshift-origin-auth-remote-user.conf - Copy the example configuration file for the MCollective messaging plug-in:
# cp openshift-origin-msg-broker-mcollective.conf.example openshift-origin-msg-broker-mcollective.conf - Configure the
dns-nsupdateplug-in:# cat << EOF > openshift-origin-dns-nsupdate.confBIND_SERVER="127.0.0.1"BIND_PORT=53BIND_KEYNAME="$domain"BIND_KEYVALUE="$KEY"BIND_KEYALGORITHM=HMAC-SHA256BIND_ZONE="$domain"EOFImportant
Verify that$domainand$KEYare configured correctly as described in Section 7.3.2, “Configuring BIND and DNS”.
Note
If you use the kickstart or bash script, the
configure_httpd_auth, configure_messaging_plugin, and configure_dns_plugin functions perform these steps.
