Red Hat SummitCe contenu n'est pas disponible dans la langue sélectionnée.
Chapter 8. Continuing Broker Host Installation for Enterprise
This section describes how to customize your broker installation for enterprise use, and provides information beyond the basic installation of an OpenShift Enterprise broker host.
8.1. Installing and Configuring DNS Plug-ins
Copier lienLien copié sur presse-papiers!
OpenShift Enterprise must be able to make dynamic, real-time updates to a DNS domain to publish applications. A DNS plug-in on the broker handles these updates by creating or deleting CNAME records. The sample broker deployment described in Chapter 7, Manually Installing and Configuring a Broker Host installs and configures an nsupdate plug-in that modifies a name server according to RFC 2136 [2]. However, you can instead define and use a different plug-in that updates a DNS service of your choice.
To implement a different DNS plug-in, you can either develop your own or install and configure one of the supported plug-ins that are shipped with OpenShift Enterprise. If you choose to develop your own, inspect the nsupdate plug-in code as an example. The location of the gem and the source files varies depending on the version of the RPM package. Use the following command to find out the location of these files on your broker hosts:
# rpm -ql rubygem-openshift-origin-dns-nsupdate
Then see the
Gem_Location/lib/openshift/nsupdate_plugin.rb file to observe the necessary functions.
If you choose to use one of the supported DNS plug-ins, see the following sections.
8.1.1. Installing and Configuring the Fog DNS Plug-in
Copier lienLien copié sur presse-papiers!
Available starting in OpenShift Enterprise 2.2, the Fog DNS plug-in uses cloud DNS services to publish OpenShift Enterprise applications. Currently, this plug-in can only be configured for use with Rackspace® Cloud DNS.
See http://fog.io/dns for more information on Fog cloud DNS services.
See http://www.rackspace.com/cloud/dns for more information on Rackspace® Cloud DNS.
Procedure 8.1. To Install and Configure the Fog DNS Plug-in:
Perform all of the following steps on each broker host in your deployment.
- Install the Fog DNS plug-in:
# yum install rubygem-openshift-origin-dns-fog - Copy the example to create the configuration file:
# cp /etc/openshift/plugins.d/openshift-origin-dns-fog.conf.example /etc/openshift/plugins.d/openshift-origin-dns-fog.conf - Edit the
/etc/openshift/plugins.d/openshift-origin-dns-fog.conffile and set your Rackspace® Cloud DNS credentials.Example 8.1. Fog DNS Plug-in Configuration Using Rackspace® Cloud DNS
FOG_RACKSPACE_USERNAME="racker" FOG_RACKSPACE_API_KEY="apikey" FOG_RACKSPACE_REGION="ord" - Disable any other DNS plug-in that may be in use by moving its configuration file from the
/etc/openshift/plugins.d/directory or renaming it so that it does not end with a.confextension. - Restart the broker service to reload the configuration:
# service openshift-broker restart
8.1.2. Installing and Configuring the DYN® DNS Plug-in
Copier lienLien copié sur presse-papiers!
Available starting in OpenShift Enterprise 2.1.6, the DYN® DNS plug-in uses the DYN® Managed DNS service to publish OpenShift Enterprise applications.
See http://dyn.com/managed-dns for more information on DYN® Managed DNS.
Procedure 8.2. To Install and Configure the DYN® DNS Plug-in:
Perform all of the following steps on each broker host in your deployment.
- Install the DYN® DNS plug-in:
# yum install rubygem-openshift-origin-dns-dynect - Copy the example to create the configuration file:
# cp /etc/openshift/plugins.d/openshift-origin-dns-dynect.conf.example /etc/openshift/plugins.d/openshift-origin-dns-dynect.conf - Edit the
/etc/openshift/plugins.d/openshift-origin-dns-dynect.conffile and set your DYN® DNS credentials.Example 8.2. DYN® DNS Plug-in Configuration
ZONE=Cloud_Domain DYNECT_CUSTOMER_NAME=Customer_Name DYNECT_USER_NAME=Username DYNECT_PASSWORD=Password DYNECT_URL=https://api2.dynect.net - Disable any other DNS plug-in that may be in use by moving its configuration file from the
/etc/openshift/plugins.d/directory or renaming it so that it does not end with a.confextension. - Restart the broker service to reload the configuration:
# service openshift-broker restart
8.1.3. Configuring the nsupdate DNS Plug-in for Compatible DNS Services
Copier lienLien copié sur presse-papiers!
A basic installation of OpenShift Enterprise includes the default nsupdate DNS plug-in, as described in Section 7.3, “Installing and Configuring BIND and DNS”, which updates a name server according to RFC 2136 [3]. In addition to BIND, this plug-in supports integration with other compatible DNS services as well.
Using Infoblox®
Because Infoblox® supports TSIG and GSS-TSIG updates, you can configure the nsupdate DNS plug-in to use an Infoblox® service to publish OpenShift Enterprise applications. See https://www.infoblox.com for more information on Infoblox®.
Configuring your Infoblox® service with the appropriate keys is outside of the scope of this guide, but once a key has been added to your zone, the configuration requirements on your OpenShift Enterprise hosts are the same as if you were using a BIND server.
Procedure 8.3. To Configure the nsupdate DNS Plug-in to Update an Infoblox® Service:
Perform all of the following steps on each broker host in your deployment.
- The nsupdate DNS plug-in is installed by default during a basic installation of OpenShift Enterprise, but if it is not currently installed, install the rubygem-openshift-origin-dns-nsupdate package:
# yum install rubygem-openshift-origin-dns-nsupdate - Edit the
/etc/openshift/plugins.d/openshift-origin-dns-nsupdate.conffile and set values appropriate for your Infoblox® service and zone:BIND_SERVER="Infoblox_Name_Server" BIND_PORT=53 BIND_KEYNAME="Key_Name" BIND_KEYVALUE="Key_Value" BIND_KEYALGORITHM=Key_Algorithm_Type BIND_ZONE="Zone_Name" - Disable any other DNS plug-in that may be in use by moving its configuration file from the
/etc/openshift/plugins.d/directory or renaming it so that it does not end with a.confextension. - Restart the broker service to reload the configuration:
# service openshift-broker restart
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}