-
Language:
English
-
Language:
English
8.6. Using an External Routing Layer for High-Availability Applications
- Adding and deleting applications
- Scaling applications up or down
- Adding or removing aliases and custom certificates
See Also:
8.6.1. Selecting an External Routing Solution
nginx is a web and proxy server with a focus on high concurrency, performance, and low memory usage. It can be installed on a Red Hat Enterprise Linux 6 host and is currently included in Red Hat Software Collections 1.2. The Red Hat Software Collections version does not include the Nginx Plus® commercial features. If you want to use the Nginx Plus® commercial features, install Nginx Plus® using the subscription model offered directly from http://nginx.com.
server.conf
and pool_*.conf
files under the configured directory. After each update, the routing daemon reloads the configured nginx or Nginx Plus® service.
Important
#rhc alias add App_Name Custom_Domain_Alias
#rhc alias update-cert App_Name Custom_Domain_Alias --certificate Cert_File --private-key Key_File
Procedure 8.16. To Install nginx from Red Hat Software Collections:
- Register a Red Hat Enterprise Linux 6 host to Red Hat Network and ensure the
Red Hat Enterprise Linux 6 Server
andRed Hat Software Collections 1
channels are enabled. For example, after registering the host with Red Hat Subscription Management (RHSM), enable the channels with the following command:#
subscription-manager repos --enable=rhel-6-server-rpms --enable=rhel-server-rhscl-6-rpms
- Install nginx:
#
yum install nginx16
- Enable the following SELinux Boolean:
#
setsebool -P httpd_can_network_connect=true
- Start the nginx service:
#
chkconfig nginx16-nginx on
#service nginx16-nginx start
Starting in OpenShift Enterprise 2.2.4, the sample routing daemon supports integration with F5 BIG-IP LTM® (Local Traffic Manager™) version 11.6.0. See the official LTM® documentation for installation instructions.
Important
client-ssl
profile must also be configured as the default SNI client-ssl
profile. Although the naming of the default client-ssl
profile is unimportant, it must be added to the HTTPS virtual server.
Administrator
role, for example, the default admin
account. Without this role, the user that the routing daemon authenticates will not have the correct privileges or configuration to use the advanced shell. Also, the LTM® admin
user's Terminal Access
must be set to Advanced Shell
so that remote bash commands can be executed.
Procedure 8.17. To Grant a User Advanced Shell Execution:
- On the F5® console, navigate to System->Users->User List->Username.
- In the dropdown box labeled Terminal Access, choose the Advanced Shell option.
- Click on the Update button.
Note
Administrator
role, and the different options for the Terminal Access dropdown box.
BIGIP_SSHKEY
public key must be added to the LTM® admin
user's .ssh/authorized_keys
file.
- Creates pools and associated local-traffic policy rules.
- Adds profiles to the virtual servers.
- Adds members to the pools.
- Deletes members from the pools.
- Deletes empty pools and unused policy rules when appropriate.
/Common/ose-#{app_name}-#{namespace}
and creates policy rules to forward requests to pools comprising the gears of the named application. Detailed configuration instructions for the routing daemon itself are provided later in Section 8.6.3, “Configuring a Routing Daemon or Listener”.