System requirements
From ControlTier
This page describes the system requirements for ControlTier.
Contents |
Operating System Versions
- Linux - recent distributions are likely to work. Most often tested are:
- Red Hat Enterprise Linux 4 update 2 or CentOS 4.2 or later
- Red Hat Enterprise Linux 5 update 2 or CentOS 5.2 or later
- Windows XP or Windows Server 2003 or later
- Mac OS X 10.4 or later
- Solaris 10 or OpenSolaris
Operating System Tuning
Note that on certain variants of Windows (e.g. Windows XP) it is necessary to increase the number of ephemeral ports available for socket connections in order to run the ControlTier server stably (see http://support.microsoft.com/kb/196271).
Permissions
Root (or Administrator on Windows) is not required or recommended. We recommend using a dedicated user account such as deploy.
If there is need for root access, please set up the ControlTier user to have access via sudo.
Java
ControlTier requires Java 5 or Java 6. For Java 5, only the Sun JDK is supported; for Java 6, the Sun JDK and OpenJDK are supported. We recommend that you set up a separate instance of the JDK for ControlTier. On UNIX, the recommended location is: $CTIER_ROOT/pkgs/jdk1.x.x_xx. You may use a system-installed Java, but generally, we encourage you to install a separate instance of Java to avoid version conflicts, especially on older distributions of Linux. To use a system-installed Java, simply set the JAVA_HOME environment variable.
For Java 5, download the latest Java 5 JDK from the Java 5 website. Look for the Download button next to the heading "JDK 5.0 Update 19" (or latest version). This requires email registration.
Server resources
- Core / Athlon 64 / PowerPC G5 class processor or better recommended
- 1.5GB disk space, plus free space for your package repository (4GB recommended)
- 1GB of memory, 2GB recommended
Client resources
- 200MB disk space (500MB recommended)
- 256-512MB of memory
Network access
Clients should be set up to allow the ControlTier server user to connect to the clients using SSH via public-key authentication. It should not prompt for a password. There are various ways of installing SSH on Windows; we recommend Cygwin.
TCP ports 8080 (jetty) and 1055 (log4j) need to be open on the server. In addition, TCP port 22 needs to be open on the clients for SSH.
| ||||||||||||||