Show Table of Contents
2.3. Software Requirements
Important
The Red Hat Gluster Storage Console setup script (
rhsc-setup) supports the en_US.UTF-8, en_US.utf8, and en_US.utf-8 locales. Installing on a system without one of the supported locale values fails.
2.3.1. Red Hat Gluster Storage Console Operating System Requirements
The Red Hat Gluster Storage Console Management Server is supported on the Red Hat Enterprise Linux 6 64-bit version platform. Ensure complete and successful installation of the operating system before starting the installing the Red Hat Gluster Storage Console.
Important
Red Hat Gluster Storage Console must be installed on a base installation of Red Hat Enterprise Linux. Do not install any additional packages after the base installation, as it could cause dependency issues when attempting to install the packages required by the Console.
2.3.2. Red Hat Gluster Storage Console Client Requirements
Use a client with a supported web browser to access the Administration Portal. The portal support the following clients and browsers:
- Mozilla Firefox 24 or later, on Red Hat Enterprise Linux is required to access the Administration Portal.
- Internet Explorer 9 or 10 on Microsoft Windows is required to access the Administration Portal. Use the desktop version, not the touchscreen version for Internet Explorer version 10.
2.3.3. Directory Services
Directory services are a collection of software, hardware, and processes that store information about an enterprise, subscribers, or both and provide this information to users. Each directory service contains at least one instance of Directory Server and at least one directory client program. Client programs access names, phone numbers, addresses, and other data stored in the directory service.
The Red Hat Gluster Storage Console platform has a default
admin user configured. Use the domain management tool (rhsc-manage-domains) to authenticate additional users by attaching directory service domains.
Note
You do not require additional firewall rules if you use a local database server (default option) on the Console itself.
2.3.4. Firewall Configuration
The ports listed in this section are the default ports that must be accessible through your system's firewall in order for certain parts of Red Hat Gluster Storage Console to work correctly. If you specified alternative ports during installation, adjust the firewall rules to allow access to the customized port.
This section does not cover specific configuration instructions for additional network infrastructure that may exist alongside your system.
If a firewall is not yet configured, run the
rhsc-setup script to automatically set up the firewall rules required by Red Hat Gluster Storage Console. If a firewall is already configured, manually integrate the existing configuration with the Red Hat Gluster Storage requirements in this section.
Note
Firewall configuration tools differ between Red Hat Entperise Linux 6 and Red Hat Enterprise Linux 7.
For Red Hat Enterprise Linux 6, use the
iptables command to open a port:
# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 5667 -j ACCEPT
# service iptables save
For Red Hat Enterprise Linux 7, if default ports are in use, it is usually simpler to add a service rather than open a port:
# firewall-cmd --zone=zone_name --add-service=glusterfs # firewall-cmd --zone=zone_name --add-service=glusterfs --permanent
However, if the default ports are already in use, you can open a specific port with the following command:
# firewall-cmd --zone=public --add-port=5667/tcp # firewall-cmd --zone=public --add-port=5667/tcp --permanent
Table 2.1. Red Hat Gluster Storage Console Firewall Requirements
| Port(s) | Protocol | Source | Destination | Purpose |
|---|---|---|---|---|
| 22 | TCP |
|
| SSH (optional) |
| 80, 443 | TCP |
|
| Provides HTTP and HTTPS access to the console. |
2.3.5. Directory Server Firewall Requirements
Red Hat Gluster Storage Console requires a directory server to support user authentication. A number of ports need to be opened in the directory server's firewall to support the GSS-API authentication as used by the Red Hat Gluster Storage Console.
Table 2.2. Directory Firewall Requirements
| Port(s) | Protocol | Source | Destination | Purpose |
|---|---|---|---|---|
| 88, 464 | TCP, UDP | Red Hat Gluster Storage Console | Directory Server | Kerberos authentication |
| 389, 636 | TCP | Red Hat Gluster Storage Console | Directory Server | Lightweight Directory Access Protocol (LDAP) and LDAP over SSL |
2.3.6. Database Server Firewall Requirements
Red Hat Gluster Storage Console supports the use of a remote database server. If you plan to use a remote database server with Red Hat Gluster Storage Console, ensure that the remote database server allows connections from the Console
.
Table 2.3. Database Server Firewall Requirements
| Port | Protocol | Source | Destination | Purpose |
|---|---|---|---|---|
| 5432 | TCP, UDP | Red Hat Gluster Storage Console | PostgreSQL database server | Default port for PostgreSQL database connections. |
2.3.7. Red Hat Gluster Storage Server Firewall Requirements
Red Hat Gluster Storage servers require that a number of ports be opened to allow network traffic through the system's firewall.
For more information on the ports that you need to open, see chapter Planning Red Hat Gluster Storage Installation in the Red Hat Gluster Storage 3.3 Installation Guide.
Table 2.4. Server Firewall Requirements
| Port | Protocol | Source | Destination | Purpose |
|---|---|---|---|---|
| 22 | TCP | Red Hat Gluster Storage Console | Red Hat Gluster Storage Servers | Secure Shell (SSH) access. |
| 54321 | TCP | Red Hat Gluster Storage Console | Red Hat Gluster Storage Servers | VDSM communications with the Red Hat Gluster Storage Console. |
2.3.8. Red Hat Gluster Storage Console User Accounts and Groups
When the rhsc package is installed, a number of user accounts are created. The default user identifier (UID) for each account and the default group identifier (GID) for each entry are:
- The kvm group (GID 36) includes the vdsm user (UID 36)
- The ovirt group (GID 108) includes the ovirt user (UID108)
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.