Verifying candidate host resources
- Log in to the candidate host as root, or as a user with superuser privileges.
Verify that the host implements the 64-bit version of the x86 instruction set.
- If the output is x86_64, the architecture is 64-bit. Proceed to the next step
- If the output is i386/i486/i586/i686, the architecture is 32-bit. Stop this procedure and select a different host.
Determine whether the installed operating system release is one of the
releases that has been tested with Control Center.
- If the result includes 7.2, 7.3, or 7.4 proceed to the next step.
- If the result does not include 7.2, 7.3, or 7.4, select a different host, and then start this procedure again.
Determine whether the CPU resources are sufficient.
Display the total number of CPU cores.
grep -Ec '^core id' /proc/cpuinfo
Compare the available resources with the
requirements for a Control Center master host.
For more information, refer to the Resource Manager Planning Guide or the Zenoss Community Edition (Core) Planning Guide.
- Display the total number of CPU cores.
Determine whether the CPU resources support the AES instruction set.
grep -Ec '^flags.*aes' /proc/cpuinfoFor optimal performance, the result of the preceding commands must match the total number of CPU resources available on the host. If the result is 0, performance is severely degraded.
If the result is 0 and the candidate host is a virtual machine, the managing hypervisor may be configured in Hyper-V compatibility mode. Check the setting and disable it, if possible, or select a different host.
Determine whether the available memory and swap is sufficient.
If the result does not meet minimum requirements, stop this procedure and select a different host.
Display the available memory.
Compare the available memory and swap space with the
amount required for a master host in your deployment.
For more information, see Master host storage requirements.
- Display the available memory.
Ensure the host has a persistent numeric ID.
Skip this step if you are installing a single-host deployment.Each Control Center host must have a unique host ID, and the ID must be persistent (not change when the host reboots).
test -f /etc/hostid || genhostid ; hostidRecord the ID for comparison with other Control Center hosts.
Verify that name resolution works on this host.
hostname -iIf the result is not a valid IPv4 address, add an entry for the host to the network nameserver, or to /etc/hosts.
Add an entry to /etc/hosts
for localhost, if necessary.
Determine whether 127.0.0.1
is mapped to localhost.
grep 127.0.0.1 /etc/hosts | grep localhostIf the preceding commands return no result, perform the following substep.
Add an entry to /etc/hosts for localhost.
echo "127.0.0.1 localhost" >> /etc/hosts
- Determine whether 127.0.0.1 is mapped to localhost.
Update the Linux kernel, if necessary.
Determine which kernel version is installed.
uname -rIf the result is lower than 3.10.0-327.22.2.el7.x86_64, perform the following substep.
Update the kernel, and then restart the host.
The following commands require internet access or a local mirror of operating system packages.
yum makecache fast && yum update kernel && reboot
- Determine which kernel version is installed.
Display the available block storage on the candidate host.
lsblk -ap --output=NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTCompare the results with the storage requirements described in Master host storage requirements.