Chapter 4. Installation
DX Content Router installs as a service on a standard server, using standard Linux installation
and package management utilities as outlined in the sections below. Note, that if running DX
Content Router from a Cluster Services Node (CSN), the required infrastructure setup, installation
and configuration are performed automatically as part of CSN configuration so the steps below
are not necessary or even supported in some cases. Please reference the CSN Installation and
Configuration Guide for information on installing and configuring DX Content Router on the CSN.
4.1. Requirements
4.1.1. Operating System
DX Content Router has been developed and tested with 64-bit Red Hat Enterprise Linux (RHEL)
version 5.5. Other RHEL versions or Linux distributions are not currently supported. Subsequent
installation instructions will assume an existing RHEL installation.
4.1.2. 3rd Party Package Pre-requisites
DX Content Router has dependencies on Python 2.5, Python Setuptools 0.6c9, and Twisted 8.2.0,
which are not available as standard RPM packages under RHEL 5.5 but are included in the DX
Content Router installation package and will be unzipped into the same location as the DX Content
Router rpm (see the 'Installing Services' section below). If installing on a Cluster Services Node
(CSN), these RPMs will already be installed. If installing without a CSN, you may need to manually
install the packages using the commands shown below (in this order):
rpm -ivh caringo-3rdparty-Python-2.5.4-x86_64.rpm
rpm -ivh caringo-3rdparty-setuptools-0.6c9-x86_64.rpm
rpm -ivh caringo-3rdparty-Twisted-8.2.0-x86_64.rpm
4.1.3. Network
The DX Storage system has been designed to work within standard TCP/IP networking
environments. This is achieved through the use of widely supported network services and protocols.
4.1.3.1. Required Communications
A DX Content Router node must be able to initiate TCP connections with all nodes in a DX Storage
cluster through the designated access port. This is typically HTTP port 80, but it is configurable by
the administrator.
Internally, DX Content Router nodes must be able to communicate with each DX Storage node
via UDP on port 7000 and through IP multicasting. The multicast address must be unique for each
cluster and is configurable by the administrator. Multicast communication is only necessary between
the DX Content Router nodes and the DX Storage nodes.
All nodes in the DX Storage cluster, including DX Content Router nodes must reside within the
same IP subnet.
4.1.3.2. Bandwidth Requirements
The expected transfer rate for two clusters communicating over a wide area network can be roughly
calculated by dividing the minimum effective bandwidth available (ex: 512 kbps) by the number
of volumes in the target cluster. By default, DX Storage requires a minimum transfer rate of 1000
bytes/sec before timing out connections. The transfer rate is not checked for the initial 20 minutes to
provide some latitude for network variability. Administrators anticipating a transfer rate below 1000
Copyright © 2010 Caringo, Inc.
All rights reserved
11
Version 2.2
December 2010
Imprimer la page