
Adding a collector
18
Table 3.1.
Option Name Security Scenario Notes
root user pass-
word
• The Resource Manager administrator has
the root password of the collector host.
• After the collector is added, the zenoss
user on the master host can log in as root
on the collector host.
After the collector is added, all communica-
tions with the collector host use keys for au-
thentication. The collector host's root pass-
word is not stored or reused.
root user SSH
keys
• The Resource Manager administrator does
not have the root password of the collec-
tor host.
• After the collector is added, the zenoss
user on the master host can log in as root
on the collector host.
After the collector is added, this option
works the same way as the preceding option.
zenoss user SSH
keys
• The Resource Manager administrator does
not have the root password of the collec-
tor host.
• The zenoss user on the master host can
not log in as root on the collector host.
This is the most secure option.
Note
When Resource Manager is started for the first time, the Distributed Collector ZenPack generates a new,
unique key pair for user zenoss, with the OpenSSH ssh-keygen command. You may use the generated key
pair to deploy a collector, or replace the pair with a new or different key pair before deploying a collector.
For more information about Distributed Collector security, refer to the chapter titled "Distributed Collector"
in Zenoss Service Dynamics Extended Monitoring.
3.2.1. Preparing to install
The following items are required or recommended.
• Master and collector hosts must be able to resolve each others' fully-qualified domain names, either through entries
in /etc/hosts, or through a nameserver on their network.
• The Linux distribution installed on the collector host must be the same as the distribution installed on the master
host. The master copies binaries to the collector during installation and updates.
• Zenoss recommends using a separate filesystem for $ZENHOME/perf, and mounting it with the noatime option set,
so that inode access times are not updated. Also, Resource Manager stores performance data in individual files, and
makes 4 KB block updates. Under such a high volume/low throughput usage pattern, journaled file systems can be
detrimental to I/O performance.
Note
If you are using the zenoss user SSH keys option, skip ahead to Zenoss user SSH keys.
If you are using the root user password option or the root user SSH keys option to add a remote collector, follow
these steps to prepare a collector host.
1. Disable Security-Enhanced Linux (SELinux).
Comentarios a estos manuales