
1
Chapter 1. Installation considerations
This chapter describes the Resource Manager deployment architecture considerations.
1.1. Installation packages
Resource Manager is distributed as two Red Hat Package Manager (RPM) packages:
• Resource Manager RPM - The Resource Manager software and required ZenPacks
• Windows ZenPacks RPM - (Optional) The ZenPacks that enable Windows monitoring
In addition, Resource Manager incorporates a variety of third-party packages, most of which are specified as depen-
dencies in the Resource Manager RPM package, and so are downloaded and installed automatically.
1.2. Operating system requirements
Resource Manager supports 64-bit Red Hat Enterprise Linux (RHEL) and CentOS, versions 5 and 6.
The following list identifies additional operating system requirements.
• Resource Manager is not compatible with Security-Enhanced Linux (SELinux) in enforcing mode, so the installation
instructions include steps to disable SELinux.
For more information about SELinux, see en.wikipedia.org/wiki/SELinux, or the SELinux home page at
www.nsa.gov/research/selinux/index.shtml.
• Resource Manager hosts (the master host, remote hub and collector hosts) must be able to resolve their fully-qualified
domain names, either through an entry in /etc/hosts, or through a nameserver on the network.
• The Resource Manager master host must contain an entry for localhost in its /etc/hosts file.
• In the default configuration, Resource Manager hosts must be able to download packages through the internet during
installation, and to connect to other internet resources during normal operation. To configure Resource Manager to
install and operate without an internet connection, contact Zenoss Support.
• Resource Manager hosts (master, data store, hubs, collectors) require Internet Protocol version 4 (IPv4) to commu-
nicate with one another.
1.3. Hardware requirements
Hardware requirements for Resource Manager depend on a number of factors, including I/O, memory, CPU, and the
number of managed devices.
For a deployment with a low number of managed devices and data points (low I/O), only a single master is required.
For a deployment with 1000 managed devices, assuming that:
• Each managed device averages 100 data points
• Collection maximum is 250 data points per second (measured on a 15000 RPM hard drive)
• Default cycle time is 300 seconds
You could calculate hardware requirements as:
Komentarze do niniejszej Instrukcji