| Red Hat Docs > Manuals > Red Hat High Availability Server Manuals > |
|
| Red Hat Linux 6.2: The Official Red Hat High Availability Server Installation Guide | ||
|---|---|---|
| Prev | Chapter 9. The Piranha Web Interface — Features and Configuration | Next |
As the name implies, the Piranha Web Interface requires a Web server capable of supporting CGI. Apache 1.3.x is a good choice. In addition, PHP version 3 (or later) is required. If your system uses RPM, you can simply install the appropriate Apache and PHP RPMs.
Otherwise, please consult the Apache and PHP homepages (http://www.apache.org/, and http://www.php.net/ respectively) for downloading and installation instructions. Once Apache and PHP are installed, you should install the piranha, ipvsadm, and piranha-gui RPMs [1] .
The Piranha RPMs will create a new user on your system (user piranha) which is a system account with no login properties (ie, you cannot log into a machine with this user ID). In future releases, the piranha user ID will be used to implement additional functionality.
One major security-related implication to the use of a Web-based interface is that the design promotes potentially untrusted data (which could originate from anywhere on the Internet) as input to a root-owned process. The password protection scheme is the front line of defense; though not a 100% perfect solution, it should fend off most unwanted visitors.
If you are still concerned about who has access to the Piranha Web Interface, you can further restrict access by using Apache's acl facility. This will allow only trusted hosts or networks access to the Piranha Web Interface [2] .
| [1] | Non-RPM systems should download the latest RPM tar file from http://www.rpm.org/, and use the rpm2cpio utility to extract the contents from the Piranha RPMs. |
| [2] | Note that this approach will only work if the systems you are clustering will not require Web services with different access restrictions from those required by the Piranha Web Interface. |