Zenoss Resource Manager Installation Guide

Zenoss Resource Manager
Installation Guide
Release 5.3.1
Zenoss, Inc.
www.zenoss.com
Zenoss Resource Manager Installation Guide
Copyright © 2017 Zenoss, Inc. All rights reserved.
Zenoss, Own IT, and the Zenoss logo are trademarks or registered trademarks of Zenoss, Inc., in the United States and other countries. All other
trademarks, logos, and service marks are the property of Zenoss or other third parties. Use of these marks is prohibited without the express written
consent of Zenoss, Inc., or the third-party owner.
Amazon Web Services, AWS, and EC2 are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.
Flash is a registered trademark of Adobe Systems Incorporated.
Oracle, the Oracle logo, Java, and MySQL are registered trademarks of the Oracle Corporation and/or its affiliates.
Linux is a registered trademark of Linus Torvalds.
RabbitMQ is a trademark of Pivotal Software, Inc.
SNMP Informant is a trademark of Garth K. Williams (Informant Systems, Inc.).
Sybase is a registered trademark of Sybase, Inc.
Tomcat is a trademark of the Apache Software Foundation.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.
Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
All other companies and products mentioned are trademarks and property of their respective owners.
Part Number: 1052.17.242
Zenoss, Inc.
11305 Four Points Drive
Bldg 1 - Suite 300
Austin, Texas 78726
2
Contents
About this guide.......................................................................................................................5
Supported operating environments.............................................................................................................. 5
Resource Manager publications...................................................................................................................6
Change history............................................................................................................................................. 7
Part I: Appliance deployments....................................................................... 10
Chapter 1: Installing a master host....................................................... 11
Creating a virtual machine............................................................................................................ 11
Configuring the Control Center master host................................................................................. 15
Editing a connection to configure static IPv4 addressing............................................................. 16
Setting the system hostname......................................................................................................... 18
Adding the master host to a resource pool................................................................................... 19
Chapter 2: Installing delegate hosts...................................................... 20
Creating a virtual machine............................................................................................................ 20
Configuring the virtual machine....................................................................................................23
Editing a connection to configure static IPv4 addressing............................................................. 24
Setting the system hostname......................................................................................................... 26
Editing the /etc/hosts file...............................................................................................................27
Chapter 3: Configuring a multi-host cluster........................................ 29
Enabling NTP on Microsoft Hyper-V guests................................................................................29
Adding hosts to the default resource pool.................................................................................... 32
Chapter 4: Configuring a ZooKeeper ensemble...................................34
ZooKeeper and Control Center..................................................................................................... 34
Understanding the configuration process...................................................................................... 34
Configuring the master host as a ZooKeeper node.......................................................................36
Configuring delegate host A as a ZooKeeper node...................................................................... 37
Configuring delegate host B as a ZooKeeper node...................................................................... 38
Starting a ZooKeeper ensemble for the first time.........................................................................39
Updating delegate hosts.................................................................................................................40
Part II: Non-appliance deployments.............................................................. 42
Chapter 5: Downloading and staging Resource Manager files............43
Downloading image files...............................................................................................................43
Staging the service definition and Docker image files................................................................. 43
3
Chapter 6: Installing Resource Manager.............................................. 45
Installing the Resource Manager template.................................................................................... 45
Importing Resource Manager images............................................................................................45
Deploying Resource Manager....................................................................................................... 46
Chapter 7: Installing Resource Manager in a high-availability
cluster.................................................................................................... 47
Installing the Resource Manager template.................................................................................... 47
Importing Resource Manager images............................................................................................47
Deploying Resource Manager....................................................................................................... 48
4
About this guide
About this guide
Zenoss Resource Manager Installation Guide provides detailed procedures for installing Zenoss Resource
Manager (Resource Manager).
Supported operating environments
The Resource Manager application is deployed in and managed by Control Center. The supported operating
environments of Resource Manager are the environments that Control Center supports at a given release. The
following sections identify the supported operating environments of Resource Manager.
Resource Manager, Control Center, and operating systems
The following table identifies the supported combinations of Resource Manager, Control Center, and operating
system releases.
Resource Manager release
Control Center
release
Host OS
1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4.0
RHEL/CentOS 7.1, 7.2, or 7.3 (64-bit)
5.2.0, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.3.0, 1.3.1,
5.2.6*
1.3.2, 1.3.3, 1.3.4, 1.4.0
RHEL/CentOS 7.1, 7.2, or 7.3 (64-bit)
5.1.9, 5.1.10
1.1.9, 1.2.0
RHEL/CentOS 7.1 or 7.2 (64-bit)
5.1.8
1.1.5, 1.1.6, 1.1.7. 1.1.8, 1.1.9
RHEL/CentOS 7.1 or 7.2 (64-bit)
5.1.7
1.1.5, 1.1.6, 1.1.7, 1.1.8
RHEL/CentOS 7.1 or 7.2 (64-bit)
5.1.6 (internal release only)
(none)
(none)
5.1.4, 5.1.5
1.1.5, 1.1.6, 1.1.7
RHEL/CentOS 7.1 or 7.2 (64-bit)
5.1.3
1.1.2, 1.1.3, 1.1.5
RHEL/CentOS 7.1 or 7.2 (64-bit)
5.1.2
1.1.2, 1.1.3
RHEL/CentOS 7.1 or 7.2 (64-bit)
5.1.1
1.1.1, 1.1.2
RHEL/CentOS 7.1 or 7.2 (64-bit)
5.3.0, 5.3.1
Hypervisors
Hypervisor
Versions
VMware vSphere
5.0, 5.1, 5.5, 6.0, 6.5
Microsoft Hyper-V
Version 2.0 with Windows Server 2008 R2 SP1
Version 3.0 with Windows Server 2012 and 2012 R2
Public cloud platforms
Amazon Web Services (AWS) is fully supported.
Microsoft Azure is supported only for collector pools. Deploying a full Control Center cluster to operate
Resource Manager is NOT supported on Microsoft Azure.
*
Version 5.2.5 was withdrawn.
5
Zenoss Resource Manager Installation Guide
Supported clients and browsers
The following table identifies the supported combinations of client operating systems and web browsers.
Client OS
Supported Browsers
Windows 7 and 8.1
Internet Explorer 11 (Enterprise mode only; compatibility mode is not
supported.)
Internet Explorer 10*
Windows 10
Internet Explorer 11 (Enterprise mode only; compatibility mode is not
supported.)
Internet Explorer 10*
Firefox 50 and later
Chrome 54 and later
Microsoft Edge
Windows Server 2012 R2
Firefox 30
Chrome 36
Macintosh OS/X 10.9
Firefox 30 and above
Chrome 36 and above
Ubuntu 14.04 LTS
Firefox 30 and above
Chrome 37 and above
Red Hat Enterprise Linux 6.5,
CentOS 6.5
Firefox 30 and above
Chrome 37 and above
Resource Manager publications
*
6
Title
Description
Zenoss Resource Manager Administration Guide
Provides an overview of Resource Manager
architecture and features, as well as procedures and
examples to help use the system.
Zenoss Resource Manager Configuration Guide
Provides required and optional configuration
procedures for Resource Manager, to prepare your
deployment for monitoring in your environment.
Zenoss Resource Manager Installation Guide
Provides detailed information and procedures for
creating deployments of Control Center and Resource
Manager.
Zenoss Resource Manager Planning Guide
Provides both general and specific information for
preparing to deploy Resource Manager.
Zenoss Resource Manager Release Notes
Describes known issues, fixed issues, and latebreaking information not already provided in the
published documentation set.
Support for Internet Explorer 10 will be withdrawn beginning with the next major release of Resource Manager.
About this guide
Title
Description
Zenoss Resource Manager Upgrade Guide
Provides detailed information and procedures for
upgrading deployments of Resource Manager.
Additional information and comments
If you have technical questions about this product that are not answered in this guide, please visit the Zenoss
Support site or contact Zenoss Support.
Zenoss welcomes your comments and suggestions regarding our documentation. To share your comments,
please send an email to docs@zenoss.com. In the email, include the document title (Zenoss Resource
Manager Installation Guide) and part number (1052.17.242).
Change history
The following list associates document part numbers and the important changes to this guide since the previous
release. Some of the changes involve features or content, but others do not. For information about new or
changed features, refer to the Zenoss Resource Manager Release Notes.
1052.17.242 (5.3.1)
Update release numbers.
1052.17.229 (5.3.0)
Beginning with this release, you can download and install the appliance artifacts or a converged set of
artifacts. This document was reorganized and updated with associated information.
Update release numbers.
1052.17.191 (5.2.6)
Update release numbers.
About 5.2.5
Version 5.2.5 was withdrawn.
1052.17.123 (5.2.4)
Update release numbers.
1052.17.100 (5.2.3)
Add a chapter for high-availability installations.
New procedures for installing the appliance with Hyper-V.
Update release numbers.
1052.17.58 (5.2.2)
Remove procedure for adding storage for backups (no longer required for appliances).
1052.17.044 (5.2.1)
Update release numbers.
1052.16.335 (5.2.0)
Add a section detailing the supported operating environments.
Remove procedures for installing Control Center clusters. That information is now in the Control Center
Installation Guide.
Remove the high-availability chapters. High-availability installations are now performed by Zenoss
personnel.
Remove the appliance installation chapters. The chapters will be replaced when the appliances are available.
The instructions for downloading and installing the software artifacts for offline deployments are now in an
appendix.
7
Zenoss Resource Manager Installation Guide
1052.16.316
Update release numbers.
1052.16.291
Update release numbers.
1052.16.277
Update release numbers.
1052.16.264
Update release numbers.
1052.16.257
Added supported operating environments and updated release numbers.
1052.16.207
Update release numbers.
1052.16.176
Update release numbers.
1052.16.153
Update release numbers.
1052.16.146
Update release numbers.
1052.16.125
Refine the procedure for creating the application data thin pool.
1052.16.118
Add support for Resource Manager 5.1.2.
Add a substep to create the docker override directory.
1052.16.111
Add this document change history.
Add chapters describing how to install the Resource Manager appliance.
Chapters are organized into parts.
Docker configuration steps now add the storage driver flag (-s devicemapper) to the /etc/
sysconfig/docker file.
Docker needs a longer startup timeout value, to work around a known Docker issue with the
devicemapper driver. Docker configuration steps now include adding TimeoutSec=300.
Rather than editing /lib/systemd/system/docker.service, Docker configuration steps now
include adding a systemd override file.
Add a symlink to /tmp in /var/lib/docker.
Update the commands for starting and testing a ZooKeeper ensemble.
Add a procedure for updating the SERVICED_ZK value on delegate hosts that are not members of a
ZooKeeper ensemble.
Add a reference topic for the ZooKeeper variables required on hosts in a Control Center cluster.
Add procedures for configuring an NTP server and clients for offline deployments.
Add step to install the Nmap Ncat package, which is used to check ZooKeeper ensemble status.
1052.16.060
Planning information is now in the Zenoss Resource Manager Planning Guide.
Information about how to start and configure Resource Manager is now in the Zenoss Resource Manager
Configuration Guide.
8
About this guide
New procedures are included, for installing without internet access, and for installing high-availability
deployments.
9
Zenoss Resource Manager Installation Guide
Part I: Appliance deployments
The chapters in this part describe how to install the Resource Manager appliance, a pre-configured virtual
machine that is ready to deploy to your hypervisor. The instructions include a variety of options for customizing
your deployment for your environment.
For information about the alternate installation option, see non-appliance installations Scope on page 42
10
Installing a master host
Installing a master host
1
This chapter describes how to install a Resource Manager appliance package as a Control Center master host.
All Resource Manager deployments require a Control Center master host.
Creating a virtual machine
You can create a virtual machine for the Resource Manager appliance with VMware vSphere or Microsoft
Hyper-V. Choose one of the procedures in this section.
Creating a virtual machine with vSphere
To perform this task, you need
■
■
A VMware vSphere client
Permission to download Resource Manager software from the Zenoss Support site
This procedure installs Resource Manager OVA packages as a virtual machine managed by vSphere Server
version 6.5.0, using VMware vSphere Web Client 6.5. The procedure might differ with other versions of
VMware vSphere Client.
There are two separate OVA packages: one for the master host and one for delegates.
1 Download the Resource Manager master host OVA file from the Zenoss Support site to your workstation.
2 Use the VMware vSphere Client to log in to vCenter as root, or as a user with superuser privileges, and
then display the Home view.
11
Zenoss Resource Manager Installation Guide
3 Choose VMs and Templates.
4 In the top navigation bar, choose Actions > Deploy OVF Template.
Figure 1: Deploy OVF Template
5 Use panels in the Deploy OVF Template wizard to select the OVF package:
a To choose the package from a drive on your workstation or network share, browse to the location and
choose the OVA file. Click Next.
b Select name and location: Specify a name for the OVF, select a datacenter or folder as the deployment
location, and then click Next.
c Select a resource: Select the host, cluster, or other resource on which to run the deployed template, and
then click Next.
12
Installing a master host
d Review details: Verify the template details, and then click Next.
e Select storage: In Select virtual disk format, choose Thin Provison, accept defaults for other fields,
and then click Next.
f Select networks: Accept defaults and click Next.
g Ready to Complete: Verify the deployment settings, and then click Finish.
The Recent Tasks pane displays deployment progress and status information.
6 Navigate to the new virtual machine's Getting Started tab, and then click Edit virtual machine settings.
7 Edit Virtual Hardware settings for the virtual machine as follows. Accept default settings for other options.
■
■
■
CPU: For single-host deployments, specify 8; for multi-host deployments, specify 4.
Cores per socket: Specify 1.
Memory: For single-host deployments, specify 64GB; for multi-host deployments, specify 16GB.
Click OK.
8 On the new virtual machine's Getting Started tab, click Power on virtual machine.
9 In the top navigation bar, choose Actions > Open console.
Proceed with Configuring the Control Center master host on page 15.
Creating a virtual machine with Hyper-V
To perform this task, you need:
■
■
■
A Microsoft Remote Desktop Connection
Administrator privileges on a Microsoft Hyper-V server
Permission to download Resource Manager software from the Zenoss Support site
This procedure installs the Resource Manager appliance as a virtual machine managed by Microsoft Hyper-V.
There are separate ISO files for the master host and delegates.
In this procedure, you download and install the master ISO file. A separate procedure provides instructions for
installing delegates.
1 Use a Microsoft Remote Desktop Connection to log in to a Hyper-V host as Administrator, or as a user with
Administrator privileges.
2 Download the Resource Manager ISO file from the Zenoss Support site to the Hyper-V host.
Choose the master ISO file.
3 Open Hyper-V Manager.
4 In the left navigation pane, choose a server to host the virtual machine.
5 In the Actions pane, choose New > Virtual Machine.
The New Virtual Machine Wizard opens.
6 Use panels in the wizard to create the virtual machine:
a Specify Name and Location: Provide a name for the virtual machine, and then click Next.
b Specify Generation: Choose Generation 1, and then click Next.
c Assign Memory: Specify memory information as follows:
■
Startup memory
Multi-host deployment: 16384 (16GB).
Single-host deployments: 65536 (64GB).
■
Check Use Dynamic Memory for this virtual machine.
■
Click Next.
d Configure Networking: For Connection, choose a virtual switch, and then click Next.
■
■
13
Zenoss Resource Manager Installation Guide
e Connect Virtual Hard Disk: Create a new disk on which to install the guest operating system as
follows:
1
2
3
4
f
Choose Create a virtual hard disk.
Specify a name.
Size: Enter 30.
Click Next.
In a later step, you will create additional disks.
Installation Options: Access the master ISO file as follows:
1 Choose Install an operating system from a bootable CD/DVD-ROM.
2 Choose Image file (.iso).
3 Specify or browse to the location of the ISO image file.
g Summary/Completing the New Virtual Machine Wizard: Verify the description, and then click
Finish.
Hyper-V Manager creates the new virtual machine, and then closes the wizard.
7 In the Hyper-V Manager Virtual Machines area, right-click the new virtual machine, and then choose
Settings.
8 In the Hardware area on the left, configure as follows:
a Ensure that the virtual hard disk that you created is attached to an IDE controller.
A Hyper-V guest machine can only boot from an IDE drive.
b Choose Processor.
c In the Processor area on the right, in Number of virtual processors, enter the following value for your
deployment type:
Multi-host deployment: 4
Single-host deployment: 8
d Click Apply.
9 Create additional virtual hard disks as follows:
a In the Hardware area on the left, choose any controller and location that will accommodate the disk.
b In the controller area on the right, choose Hard Drive, and then click Add.
c In the area on the right, choose Virtual hard disk, and then click New.
d Complete panels in the New Virtual Hard Disk Wizard as follows:
■
■
1
2
3
4
Choose Disk Format: Choose VHDX, and then click Next.
Choose Disk Type: Choose Dynamically expanding, and then click Next.
Specify Name and Location: Enter the disk name, and then click Next.
Configure Disk:
a Choose Create a new blank virtual hard disk.
b Size: Enter 50.
c Click Next.
5 Summary/New Virtual Hard Disk Wizard: Verify the description, and then click Finish.
e In the Settings window, click Apply.
f Repeat this step to create additional virtual hard disks in the following sizes (for a total of seven disks):
■
■
■
■
14
150GB
50GB
200GB
16GB
Installing a master host
16GB
When viewed from the Linux system, the disks might be reordered; however, the installation is not
affected by disk order.
g In the Settings dialog box, click Apply, and then click OK.
10 In the Hyper-V Manager Virtual Machines area, right-click the new virtual machine, and then choose Start.
■
Figure 2: Starting a virtual machine
11 In the Hyper-V Manager Virtual Machines area, right-click the new virtual machine, and then choose
Connect.
12 In the Virtual Machine Connection window, press Enter.
The appliance installation process takes about 15 minutes, and should complete with no additional input.
If received, disregard the Fast TSC calibration failure message.
Configuring the Control Center master host
Perform this procedure immediately after creating and starting a Control Center host. All Control Center
deployments must include one system that is configured as the master host.
1 Gain access to the console interface of the Control Center host through your hypervisor console interface.
Figure 3: Initial hypervisor console login prompt
2 Log in as the root user.
The initial password is provided in the console.
3 The system prompts you to enter a new password for root.
Note Passwords must include a minimum of eight characters, with at least one character from three of the
following character classes: uppercase letter, lowercase letter, digit, and special.
4 The system prompts you to enter a new password for ccuser.
15
Zenoss Resource Manager Installation Guide
The ccuser account is the default account for gaining access to the Control Center browser interface.
Editing a connection to configure static IPv4 addressing
The default configuration for network connections is DHCP. To configure static IPv4 addressing, perform this
procedure.
To navigate in the text user interface (TUI):
■
■
To move forward or backward through options, press the arrow keys.
To display a menu or choose an option, press Enter.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Log in as the root user.
3 Select the NetworkManager TUI menu as follows:
a In the Appliance Administration menu, select Configure Network and DNS, and then press Enter.
4 On the NetworkManager TUI menu, select Edit a connection, and then press Enter.
The TUI displays the connections that are available on the host.
16
Installing a master host
Figure 4: Example: Available connections
Note
Do not use this procedure to modify the docker0 connection.
5 Select the virtual connection, and then press Enter.
Figure 5: Example: Edit Connection screen
6 Optional: If the IPv4 CONFIGURATION area is not visible, select its display option (<Show>), and then
press Enter.
7 In the IPv4 CONFIGURATION area, select <Automatic>, and then press Enter.
Figure 6: Example: IPv4 Configuration options
8 Configure static IPv4 networking as follows:
a Select Manual, and then press Enter.
b Beside Addresses, select <Add>, and then press Enter.
17
Zenoss Resource Manager Installation Guide
c In the Addresses field, enter an IPv4 address for the virtual machine, and then press Enter.
d Repeat the preceding two steps for the Gateway and DNS servers fields.
9 Tab to the bottom of the Edit Connection screen to select <OK>, and then press Enter.
10 Return to the Appliance Administration menu: On the NetworkManager TUI screen, select <Quit>, and
then press Enter.
11 Reboot the operating system as follows:
a In the Appliance Administration menu, select Reboot / Poweroff System.
b Select Reboot.
c Select OK, and then press Enter.
Setting the system hostname
The default hostname is zsd-master for the Resource Manager master host and is zsd-delegate for
Resource Manager delegate hosts. To change the default hostname, perform this procedure.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Select the NetworkManager TUI menu as follows:
a In the Appliance Administration menu, select Configure Network and DNS, and then press Enter.
3 Display the hostname entry field.
a In the NetworkManager TUI menu, select Set system hostname.
b Select OK, and then press Enter.
4 In the Hostname field, enter the hostname or a fully qualified domain name.
5 Press Tab twice to select OK, and then press Enter.
6 In the confirmation dialog box, press Enter.
7 Return to the Appliance Administration menu: On the NetworkManager TUI screen, select <Quit>, and
then press Enter.
8 Reboot the operating system as follows:
a In the Appliance Administration menu, select Reboot / Poweroff System.
b Select Reboot.
c Select OK, and then press Enter.
18
Installing a master host
Adding the master host to a resource pool
Complete this procedure to add the Control Center master host to the default resource pool or to a new
resource pool named master.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Start a command-line session as root as follows:
a In the Appliance Administration menu, select Root Shell.
b Select Run, and then press Enter.
The menu is replaced by a command prompt similar to the following example:
[root@hostname ~]#
3 Optional: Create a new resource pool, if necessary.
■
■
For single-host deployments, skip this step.
For multi-host deployments, perform the following substeps.
a Create a new pool named master.
serviced pool add master
b Assign administrative and distributed file system (DFS) permissions to the new resource pool.
serviced pool set-permission --admin --dfs master
4 Add the master host to a resource pool.
For single-host deployments, add the master host to the default resource pool.
Replace Hostname-Or-IP with the hostname or IP address of the Control Center master host:
serviced host add Hostname-Or-IP:4979 default
If you enter a hostname, all hosts in your Control Center cluster must be able to resolve the name, either
through an entry in /etc/hosts, or through a nameserver on your network.
For multi-host deployments, add the master host to the master resource pool and register its
authentication token.
Replace Hostname-Or-IP with the hostname or IP address of the Control Center master host:
serviced host add --register Hostname-Or-IP:4979 master
If you enter a hostname, all hosts in your Control Center cluster must be able to resolve the name, either
through an entry in /etc/hosts, or through a nameserver on your network.
5 To exit the command-line session, at the command prompt, enter exit.
19
Zenoss Resource Manager Installation Guide
Installing delegate hosts
2
This chapter describes how to install a Resource Manager appliance package as a Control Center delegate host.
You can add as many delegate hosts as you need to a Control Center cluster.
Perform the procedures in Installing a master host on page 11 before performing the procedures in this chapter.
Creating a virtual machine
You can create a virtual machine for the Resource Manager delegate appliance with VMware vSphere or
Microsoft Hyper-V. Choose one of the procedures in this section.
Creating a virtual machine with vSphere
To perform this task, you need
■
■
A VMware vSphere client
Permission to download Resource Manager software from the Zenoss Support site
This procedure installs Resource Manager OVA packages as a virtual machine managed by vSphere Server
version 6.5.0, using VMware vSphere Web Client 6.5. The procedure might differ with other versions of
VMware vSphere Client.
There are two separate OVA packages: one for the master host and one for delegates.
1 Download the Resource Manager delegate OVA file from the Zenoss Support site to your workstation, if
necessary.
2 Use the VMware vSphere Client to log in to vCenter as root, or as a user with superuser privileges, and
then display the Home view.
20
Installing delegate hosts
3 In the top navigation bar, choose Actions > Deploy OVF Template.
Figure 7: Deploy OVF Template
4 Use panels in the Deploy OVF Template wizard to select the OVF package:
a To choose the package from a drive on your workstation or network share, browse to the location and
choose the OVA file. Click Next.
b Select name and location: Specify a name for the OVF, select a datacenter or folder as the deployment
location, and then click Next.
c Select a resource: Select the host, cluster, or other resource on which to run the deployed template, and
then click Next.
d Review details: Verify the template details, and then click Next.
21
Zenoss Resource Manager Installation Guide
e Select storage: In Select virtual disk format, choose Thin Provison, accept defaults for other fields,
and then click Next.
f Select networks: Accept defaults and click Next.
g Ready to Complete: Verify the deployment settings, and then click Finish.
The Recent Tasks pane displays deployment progress and status information.
5 Navigate to the new virtual machine's Getting Started tab, and then click Edit virtual machine settings.
6 Update the memory assigned to the machine to 32GB, and then click OK.
7 On the new virtual machine's Getting Started tab, click Power on virtual machine.
Creating a virtual machine with Hyper-V
To perform this task, you need:
■
■
■
A Microsoft Remote Desktop Connection
Administrator privileges on a Microsoft Hyper-V server
Permission to download Resource Manager software from the Zenoss Support site
This procedure installs the Resource Manager appliance as a virtual machine managed by Microsoft Hyper-V.
There are separate ISO files for the master host and delegates.
In this procedure, you download and install the delegate ISO file. A separate procedure provides instructions for
installing the master.
1 Use a Microsoft Remote Desktop Connection to log in to a Hyper-V host as Administrator, or as a user with
Administrator privileges.
2 Download the Resource Manager ISO file from the Zenoss Support site to the Hyper-V host.
Choose the delegate ISO file.
3 Open Hyper-V Manager.
4 In the left navigation pane, choose a server to host the virtual machine.
5 In the Actions pane, choose New > Virtual Machine.
The New Virtual Machine Wizard opens.
6 Use panels in the wizard to create the virtual machine:
a Specify Name and Location: Provide a name for the virtual machine, and then click Next.
b Specify Generation: Choose Generation 1, and then click Next.
c Assign Memory: Specify memory information as follows:
Startup memory: Enter 32768 (32GB).
Check Use Dynamic Memory for this virtual machine.
■
Click Next.
d Configure Networking: For Connection, choose a virtual switch, and then click Next.
e Connect Virtual Hard Disk: Create a new disk on which to install the guest operating system as
follows:
■
■
1
2
3
4
f
Choose Create a virtual hard disk.
Specify a name.
Size: Enter 30.
Click Next.
In a later step, you will create additional disks.
Installation Options: Access the delegate ISO file as follows:
1 Choose Install an operating system from a bootable CD/DVD-ROM.
2 Choose Image file (.iso).
22
Installing delegate hosts
3 Specify or browse to the location of the ISO image file.
g Summary/Completing the New Virtual Machine Wizard: Verify the description, and then click
Finish.
7 In the Hyper-V Manager Virtual Machines area, right-click the new virtual machine, and then choose
Settings.
8 In the Hardware area on the left, configure as follows:
a Ensure that the virtual hard disk that you created is attached to an IDE controller.
A Hyper-V guest machine can only boot from an IDE drive.
b Choose Processor.
c In Number of virtual processors, enter 8, and then click Apply.
9 Create additional virtual hard disks as follows:
a In the Hardware area on the left, choose any controller and location that will accommodate the disk.
b In the controller area on the right, choose Hard Drive, and then click Add.
c In the area on the right, choose Virtual hard disk, and then click New.
d Complete panels in the New Virtual Hard Disk Wizard as follows:
1
2
3
4
Choose Disk Format: Choose VHDX, and then click Next.
Choose Disk Type: Choose Dynamically expanding, and then click Next.
Specify Name and Location: Enter the disk name, and then click Next.
Configure Disk:
a Choose Create a new blank virtual hard disk.
b Size: Enter 50.
c Click Next.
5 Summary/New Virtual Hard Disk Wizard: Verify the description, and then click Finish.
e In the Settings window, click Apply.
f Repeat this step to create two 16GB virtual hard disks (for a total of four disks).
When viewed from the Linux system, the disks might be reordered; however, the installation is not
affected by disk order.
g In the Settings dialog box, click Apply, and then click OK.
10 In the Hyper-V Manager Virtual Machines area, right-click the new virtual machine, and then choose Start.
Figure 8: Starting a virtual machine
11 In the Hyper-V Manager Virtual Machines area, right-click the new virtual machine, and then choose
Connect.
12 In the Virtual Machine Connection window, press Enter.
The appliance installation process takes about 15 minutes, and should complete with no additional input.
If received, disregard the Fast TSC calibration failure message.
Configuring the virtual machine
This procedure configures the new virtual machine as a delegate host.
23
Zenoss Resource Manager Installation Guide
1 Gain access to the console interface of the Control Center host through your hypervisor console interface.
Figure 9: Initial hypervisor console login prompt
2 Log in as the root user.
The initial password is provided in the console.
3 The system prompts you to enter a new password for root.
Note Passwords must include a minimum of eight characters, with at least one character from three of the
following character classes: uppercase letter, lowercase letter, digit, and special.
4 The system prompts you to enter a new password for ccuser.
The ccuser account is the default account for gaining access to the Control Center browser interface.
5 In the IP field, enter the hostname, fully qualified domain name, or IPv4 address of the master host.
Note If you enter the hostname or fully qualified domain name of the master host, you need an entry in
the /etc/hosts file of the delegate host or a nameserver on your network that resolves the name to its
IPv4 address.
a Press Tab to select Ok, and then press Enter.
The system reboots.
Editing a connection to configure static IPv4 addressing
The default configuration for network connections is DHCP. To configure static IPv4 addressing, perform this
procedure.
To navigate in the text user interface (TUI):
■
■
24
To move forward or backward through options, press the arrow keys.
To display a menu or choose an option, press Enter.
Installing delegate hosts
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Log in as the root user.
3 Select the NetworkManager TUI menu as follows:
a In the Appliance Administration menu, select Configure Network and DNS, and then press Enter.
4 On the NetworkManager TUI menu, select Edit a connection, and then press Enter.
The TUI displays the connections that are available on the host.
Figure 10: Example: Available connections
25
Zenoss Resource Manager Installation Guide
Note
Do not use this procedure to modify the docker0 connection.
5 Select the virtual connection, and then press Enter.
Figure 11: Example: Edit Connection screen
6 Optional: If the IPv4 CONFIGURATION area is not visible, select its display option (<Show>), and then
press Enter.
7 In the IPv4 CONFIGURATION area, select <Automatic>, and then press Enter.
Figure 12: Example: IPv4 Configuration options
8 Configure static IPv4 networking as follows:
a Select Manual, and then press Enter.
b Beside Addresses, select <Add>, and then press Enter.
c In the Addresses field, enter an IPv4 address for the virtual machine, and then press Enter.
d Repeat the preceding two steps for the Gateway and DNS servers fields.
9 Tab to the bottom of the Edit Connection screen to select <OK>, and then press Enter.
10 Return to the Appliance Administration menu: On the NetworkManager TUI screen, select <Quit>, and
then press Enter.
11 Reboot the operating system as follows:
a In the Appliance Administration menu, select Reboot / Poweroff System.
b Select Reboot.
c Select OK, and then press Enter.
Setting the system hostname
The default hostname is zsd-master for the Resource Manager master host and is zsd-delegate for
Resource Manager delegate hosts. To change the default hostname, perform this procedure.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Select the NetworkManager TUI menu as follows:
a In the Appliance Administration menu, select Configure Network and DNS, and then press Enter.
26
Installing delegate hosts
3 Display the hostname entry field.
a In the NetworkManager TUI menu, select Set system hostname.
b Select OK, and then press Enter.
4 In the Hostname field, enter the hostname or a fully qualified domain name.
5 Press Tab twice to select OK, and then press Enter.
6 In the confirmation dialog box, press Enter.
7 Return to the Appliance Administration menu: On the NetworkManager TUI screen, select <Quit>, and
then press Enter.
8 Reboot the operating system as follows:
a In the Appliance Administration menu, select Reboot / Poweroff System.
b Select Reboot.
c Select OK, and then press Enter.
Editing the /etc/hosts file
This procedure is conditional. Perform this procedure only if you use hostnames or fully qualified domain
names instead of IPv4 addresses, and only after all delegate hosts are installed and renamed. Perform this
procedure on the Control Center master host and on each delegate host.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Start a command-line session as root as follows:
a In the Appliance Administration menu, select Root Shell.
b Select Run, and then press Enter.
The menu is replaced by a command prompt similar to the following example:
[root@hostname ~]#
3 Open the /etc/hosts file in a text editor.
The following steps use the nano editor.
27
Zenoss Resource Manager Installation Guide
a Start the editor.
nano /etc/hosts
Figure 13: Example nano session
b Optional: On delegate hosts, the file might include two entries with the same IP address. Remove the first
of the two entries, which maps the IP address to the zsd-master hostname.
c Add entries for the Control Center master host and for each delegate host.
d To save, press Control-o.
e To exit, press Control-x.
4 Return to the Appliance Administration menu.
exit
5 Exit the Appliance Administration menu.
a Use the down-arrow key to select Exit.
b Press Tab, and then press Enter.
28
Configuring a multi-host cluster
Configuring a multi-host cluster
3
This chapter describes how to configure an appliance-based multi-host Control Center cluster. A multi-host
Resource Manager deployment includes one Control Center master host and one or more delegate hosts. Zenoss
recommends deploying at least two delegate hosts to enable creating a ZooKeeper ensemble.
Enabling NTP on Microsoft Hyper-V guests
The procedures in this section are required only for multi-host deployments running as Microsoft Hyper-V
guests. VMware vSphere guests use an hourly cron job to synchronize their system clocks with the host.Like
most distributed applications, Control Center requires a common time source. The procedures in this section
enable NTP to synchronize the system clocks of all hosts in your Control Center cluster.
Configure NTP to rely on a time source as follows, depending on internet access of the hosts in your Control
Center cluster:
■
■
If all hosts can access the internet, configure NTP to rely on public time servers.
If no host can access the internet, configure NTP to rely on a private master server.
Configuring NTP for public time servers
(Hyper-V only) This procedure uses the default configuration of NTP to synchronize system clocks with public
time servers. If all hosts in the Control Center cluster can access the internet, repeat this procedure on each host
in the cluster, starting with the Control Center master host.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Start a command-line session as root as follows:
a In the Appliance Administration menu, select Root Shell.
b Select Run, and then press Enter.
The menu is replaced by a command prompt similar to the following example:
[root@hostname ~]#
3 Stop Control Center.
systemctl stop serviced
4 Synchronize the system clock and enable the NTP daemon.
29
Zenoss Resource Manager Installation Guide
a Set the system time.
ntpd -gq
b Enable the ntpd daemon.
systemctl enable ntpd
c Configure ntpd to start when the system starts.
Currently, an unresolved issue associated with NTP prevents ntpd from restarting correctly after a
reboot, and the following commands provide a workaround to ensure that it does.
echo "systemctl start ntpd" >> /etc/rc.d/rc.local
chmod +x /etc/rc.d/rc.local
d Start ntpd.
systemctl start ntpd
5 Start Control Center.
systemctl start serviced
Configuring an NTP master server
(Hyper-V only) This procedure configures an NTP master server on the Control Center master host. Perform this
procedure only if the host does not have internet access.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Start a command-line session as root as follows:
a In the Appliance Administration menu, select Root Shell.
b Select Run, and then press Enter.
The menu is replaced by a command prompt similar to the following example:
[root@hostname ~]#
3 Create a backup of the NTP configuration file.
cp -p /etc/ntp.conf /etc/ntp.conf.orig
4 Edit the NTP configuration file as follows:
a Open /etc/ntp.conf with a text editor.
b Replace all lines in the file with the following lines:
# Use the local clock
server 127.127.1.0 prefer
fudge 127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
# Give localhost full access rights
restrict 127.0.0.1
30
Configuring a multi-host cluster
# Grant access to client hosts
restrict ADDRESS_RANGE mask NETMASK nomodify notrap
c Replace ADDRESS_RANGE with the range of IPv4 network addresses that are allowed to query this NTP
server.
For example, the following IP addresses are assigned to the hosts in a Control Center cluster:
203.0.113.10
203.0.113.11
203.0.113.12
203.0.113.13
For the preceding addresses, the value for ADDRESS_RANGE is 203.0.113.0.
d Replace NETMASK with the IPv4 network mask that corresponds with the address range.
For example, the network mask for 203.0.113.0 is 255.255.255.0.
e Save the file and exit the editor.
5 Stop Control Center.
systemctl stop serviced
6 Enable and start the NTP daemon as follows:
a Enable the ntpd daemon.
systemctl enable ntpd
b Configure ntpd to start when the system starts.
Currently, an unresolved issue associated with NTP prevents ntpd from restarting correctly after a
reboot, and the following commands provide a workaround to ensure that it does.
echo "systemctl start ntpd" >> /etc/rc.d/rc.local
chmod +x /etc/rc.d/rc.local
c Start ntpd.
systemctl start ntpd
7 Start Control Center.
systemctl start serviced
Configuring NTP clients
(Hyper-V only) This procedure configures delegates to synchronize their clocks with the NTP server on the
Control Center master host. Perform this procedure only if the delegates do not have internet access. Repeat this
procedure on each delegate in your Control Center cluster.
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Start a command-line session as root as follows:
a In the Appliance Administration menu, select Root Shell.
b Select Run, and then press Enter.
31
Zenoss Resource Manager Installation Guide
The menu is replaced by a command prompt similar to the following example:
[root@hostname ~]#
3 Create a backup of the NTP configuration file.
cp -p /etc/ntp.conf /etc/ntp.conf.orig
4 Edit the NTP configuration file as follows:
a Open /etc/ntp.conf with a text editor.
b Replace all lines in the file with the following lines:
# Point to the master time server
server MASTER_ADDRESS
restrict default ignore
restrict 127.0.0.1
restrict MASTER_ADDRESS mask 255.255.255.255 nomodify notrap noquery
driftfile /var/lib/ntp/drift
c Replace both instances of MASTER_ADDRESS with the IPv4 address of the host where the NTP server is
running (the Control Center master host).
d Save the file and exit the editor.
5 Stop Control Center.
systemctl stop serviced
6 Synchronize the clock with the master server.
ntpd -gq
7 Enable and start the NTP daemon as follows:
a Enable the ntpd daemon.
systemctl enable ntpd
b Configure ntpd to start when the system starts.
Currently, an unresolved issue associated with NTP prevents ntpd from restarting correctly after a
reboot, and the following commands provide a workaround to ensure that it does.
echo "systemctl start ntpd" >> /etc/rc.d/rc.local
chmod +x /etc/rc.d/rc.local
c Start ntpd.
systemctl start ntpd
8 Start Control Center.
systemctl start serviced
Adding hosts to the default resource pool
This procedure adds one or more hosts to the default resource pool.
32
Configuring a multi-host cluster
1 Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote
shell utility such as PuTTY.
2 Start a command-line session as root as follows:
a In the Appliance Administration menu, select Root Shell.
b Select Run, and then press Enter.
The menu is replaced by a command prompt similar to the following example:
[root@hostname ~]#
3 Add and register a delegate host.
Replace Hostname-Or-IP with the hostname or IP address of the delegate host to add and include the register
flag to authenticate the delegate host:
serviced host add Hostname-Or-IP:4979 default --register
If you enter a hostname, all hosts in your Control Center cluster must be able to resolve the name through an
entry in /etc/hosts or through a nameserver on your network.
4 Repeat the preceding command for each delegate in your Control Center cluster.
33
Zenoss Resource Manager Installation Guide
Configuring a ZooKeeper ensemble
4
This chapter describes how to create a ZooKeeper ensemble (cluster) for a multi-host Control Center
deployment that includes a minimum of three hosts. If your deployment includes just one host or two hosts, skip
this chapter.
ZooKeeper and Control Center
Control Center relies on Apache ZooKeeper to distribute and manage application services. ZooKeeper maintains
the definitions of each service and the list of services assigned to each host. The scheduler, which runs on the
master host, determines assignments and sends them to the ZooKeeper node that is serving as the ensemble
leader. The leader replicates the assignments to the other ensemble nodes, so that the other nodes can assume the
role of leader if the leader node fails.
All of the hosts in a Control Center cluster retrieve assignments and service definitions from the ZooKeeper
ensemble leader and then start services in Docker containers as required. So, the Control Center configuration
files of all Control Center cluster hosts must include a definition for the SERVICED_ZK variable, which
specifies the ZooKeeper endpoints of the ensemble nodes. Additional variables are required on ensemble nodes.
A ZooKeeper ensemble requires a minimum of three nodes, which is sufficient for most environments. An odd
number of nodes is recommended and an even number of nodes is strongly discouraged. A five-node ensemble
improves failover protection during maintenance windows but larger ensembles yield no benefits.
The Control Center master host is always an ensemble node. All ensemble nodes should be on the same subnet.
Understanding the configuration process
The procedures in this chapter instruct you to create temporary variables that are used as building blocks, to
construct Control Center configuration variables accurately. You append the Control Center variables to /etc/
default/serviced, and then edit the file to move the variables to more appropriate locations.
The most important temporary variables specify the IP address or hostname of each host in the ZooKeeper
ensemble. The following table identifies these important variables, the names and values of which must be
identical on every Control Center cluster host.
Variable name Placeholder value
34
Actual value
node1
Master
The IP address or hostname of the master host.
node2
Delegate-A
The IP address or hostname of delegate host A.
Configuring a ZooKeeper ensemble
Variable name Placeholder value
Delegate-B
node3
Note
Actual value
The IP address or hostname of delegate host B.
All ensemble hosts should be on the same subnet.
ZooKeeper variables
The variables in the following table are set only on ZooKeeper ensemble nodes, except SERVICED_ZK, which
must be identical on all Control Center cluster hosts.
Variable
Where to set
SERVICED_ISVCS_START
ZooKeeper ensemble nodes
SERVICED_ISVCS_ZOOKEEPER_ID
ZooKeeper ensemble nodes
SERVICED_ISVCS_ZOOKEEPER_QUORUM
ZooKeeper ensemble nodes
SERVICED_ZK
All Control Center cluster hosts
SERVICED_ZK_SESSION_TIMEOUT
ZooKeeper ensemble nodes
Example multi-host ZooKeeper configuration
This example shows the ZooKeeper variables in the /etc/default/serviced configuration file of each
host in a 4-node Control Center cluster. For convenience, the relevant settings for each node or host are also
included in subsequent procedures.
Note
The value of the SERVICED_ISVCS_ZOOKEEPER_QUORUM variable is formatted to fit the
available space. In the configuration file, the variable and value are on the same line.
Master host and ZooKeeper ensemble node, 198.51.100.135:
SERVICED_ISVCS_ZOOKEEPER_ID=1
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
SERVICED_ISVCS_ZOOKEEPER_QUORUM=1@0.0.0.0:2888:3888,\
2@198.51.100.136:2888:3888,3@198.51.100.137:2888:3888
SERVICED_ZK_SESSION_TIMEOUT=15
Delegate host and ZooKeeper ensemble node, 198.51.100.136:
SERVICED_ISVCS_START=zookeeper
SERVICED_ISVCS_ZOOKEEPER_ID=2
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
SERVICED_ISVCS_ZOOKEEPER_QUORUM=1@198.51.100.135:2888:3888,\
2@0.0.0.0:2888:3888,3@198.51.100.137:2888:3888
SERVICED_ZK_SESSION_TIMEOUT=15
Delegate host and ZooKeeper ensemble node, 198.51.100.137:
SERVICED_ISVCS_START=zookeeper
SERVICED_ISVCS_ZOOKEEPER_ID=3
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
SERVICED_ISVCS_ZOOKEEPER_QUORUM=1@198.51.100.135:2888:3888,\
2@198.51.100.136:2888:3888,3@0.0.0.0:2888:3888
35
Zenoss Resource Manager Installation Guide
SERVICED_ZK_SESSION_TIMEOUT=15
Delegate host, 198.51.100.138:
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
Configuring the master host as a ZooKeeper node
This procedure configures the Control Center master host as a node in a ZooKeeper ensemble.
1 Log in to the master host as root, or as a user with superuser privileges.
2 Define the IP address variables for each node in the ZooKeeper ensemble.
Replace Master with the IP address or hostname of the Control Center master host, and replace Delegate-A
and Delegate-B with the IP addresses or hostnames of the delegate hosts to include in the ensemble:
node1=Master
node2=Delegate-A
node3=Delegate-B
3 Set the ZooKeeper node ID to 1.
echo "SERVICED_ISVCS_ZOOKEEPER_ID=1" >> /etc/default/serviced
4 Specify the nodes in the ZooKeeper ensemble.
You can copy the following text and paste it in your console:
echo "SERVICED_ZK=${node1}:2181,${node2}:2181,${node3}:2181" \
>> /etc/default/serviced
5 Specify the nodes in the ZooKeeper quorum.
ZooKeeper requires a unique quorum definition for each node in its ensemble. To achieve this, replace the IP
address or hostname of the master host with 0.0.0.0.
You can copy the following text and paste it in your console:
q1="1@0.0.0.0:2888:3888"
q2="2@${node2}:2888:3888"
q3="3@${node3}:2888:3888"
echo "SERVICED_ISVCS_ZOOKEEPER_QUORUM=${q1},${q2},${q3}" \
>> /etc/default/serviced
6 Specify the timeout for inactive connections.
You can copy the following text and paste it in your console:
echo "SERVICED_ZK_SESSION_TIMEOUT=15" >> /etc/default/serviced
7 Verify the ZooKeeper environment variables.
grep -E '^\b*SERVICED' /etc/default/serviced | grep -E '_Z(OO|K)'
The following example shows the environment variables for a master host with IP address 198.51.100.135.
36
Configuring a ZooKeeper ensemble
Note The value of the SERVICED_ISVCS_ZOOKEEPER_QUORUM variable is formatted to fit the
available space. The result of the grep command shows the variable and value on the same line.
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
SERVICED_ISVCS_ZOOKEEPER_ID=1
SERVICED_ISVCS_ZOOKEEPER_QUORUM=1@0.0.0.0:2888:3888,\
2@198.51.100.136:2888:3888,3@198.51.100.137:2888:3888
SERVICED_ZK_SESSION_TIMEOUT=15
Configuring delegate host A as a ZooKeeper node
Use this procedure to configure the delegate host designated as Delegate-A as a ZooKeeper node.
1 Log in to the delegate host as root, or as a user with superuser privileges.
2 Define the IP address variables for each node in the ZooKeeper ensemble.
Replace Master with the IP address or hostname of the Control Center master host, and replace Delegate-A
and Delegate-B with the IP addresses or hostnames of the delegate hosts to include in the ensemble:
node1=Master
node2=Delegate-A
node3=Delegate-B
3 Set the ID of this node in the ZooKeeper ensemble.
echo "SERVICED_ISVCS_ZOOKEEPER_ID=2" >> /etc/default/serviced
4 Remove the existing definition of the SERVICED_ZK variable, which specifies only the Control Center
master host.
sed -i.bak '/SERVICED_ZK=/d' /etc/default/serviced
5 Specify the nodes in the ZooKeeper ensemble.
You can copy the following text and paste it in your console:
echo "SERVICED_ZK=${node1}:2181,${node2}:2181,${node3}:2181" \
>> /etc/default/serviced
6 Specify the nodes in the ZooKeeper quorum.
ZooKeeper requires a unique quorum definition for each node in its ensemble. To achieve this, replace the IP
address or hostname of delegate host A with 0.0.0.0.
You can copy the following text and paste it in your console:
q1="1@${node1}:2888:3888"
q2="2@0.0.0.0:2888:3888"
q3="3@${node3}:2888:3888"
echo "SERVICED_ISVCS_ZOOKEEPER_QUORUM=${q1},${q2},${q3}" \
>> /etc/default/serviced
7 Specify the timeout for inactive connections.
You can copy the following text and paste it in your console:
echo "SERVICED_ZK_SESSION_TIMEOUT=15" >> /etc/default/serviced
8 Configure Control Center to start the ZooKeeper service.
37
Zenoss Resource Manager Installation Guide
You can copy the following text and paste it in your console:
echo "SERVICED_ISVCS_START=zookeeper" >> /etc/default/serviced
9 Verify the ZooKeeper environment variables.
grep -E '^\b*SERVICED' /etc/default/serviced \
| grep -E '(CS_ZO|_ZK|CS_ST)'
The following example shows the environment variables for a delegate host with IP address 198.51.100.136.
Note The value of the SERVICED_ISVCS_ZOOKEEPER_QUORUM variable is formatted to fit the
available space. The result of the grep command shows the variable and value on the same line.
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
SERVICED_ISVCS_START=zookeeper
SERVICED_ISVCS_ZOOKEEPER_ID=2
SERVICED_ISVCS_ZOOKEEPER_QUORUM=1@198.51.100.135:2888:3888,\
2@0.0.0.0:2888:3888,3@198.51.100.137:2888:3888
SERVICED_ZK_SESSION_TIMEOUT=15
Configuring delegate host B as a ZooKeeper node
Use this procedure to configure the delegate host designated as Delegate-B as a ZooKeeper node.
1 Log in to the delegate host as root, or as a user with superuser privileges.
2 Define the IP address variables for each node in the ZooKeeper ensemble.
Replace Master with the IP address or hostname of the Control Center master host, and replace Delegate-A
and Delegate-B with the IP addresses or hostnames of the delegate hosts to include in the ensemble:
node1=Master
node2=Delegate-A
node3=Delegate-B
3 Set the ID of this node in the ZooKeeper ensemble.
echo "SERVICED_ISVCS_ZOOKEEPER_ID=3" >> /etc/default/serviced
4 Remove the existing definition of the SERVICED_ZK variable, which specifies only the Control Center
master host.
sed -i.bak '/SERVICED_ZK=/d' /etc/default/serviced
5 Specify the nodes in the ZooKeeper ensemble.
You can copy the following text and paste it in your console:
echo "SERVICED_ZK=${node1}:2181,${node2}:2181,${node3}:2181" \
>> /etc/default/serviced
6 Specify the nodes in the ZooKeeper quorum.
ZooKeeper requires a unique quorum definition for each node in its ensemble. To achieve this, replace the IP
address or hostname of delegate host B with 0.0.0.0.
You can copy the following text and paste it in your console:
q1="1@${node1}:2888:3888"
38
Configuring a ZooKeeper ensemble
q2="2@${node2}:2888:3888"
q3="3@0.0.0.0:2888:3888"
echo "SERVICED_ISVCS_ZOOKEEPER_QUORUM=${q1},${q2},${q3}" \
>> /etc/default/serviced
7 Specify the timeout for inactive connections.
You can copy the following text and paste it in your console:
echo "SERVICED_ZK_SESSION_TIMEOUT=15" >> /etc/default/serviced
8 Configure Control Center to start the ZooKeeper service.
You can copy the following text and paste it in your console:
echo "SERVICED_ISVCS_START=zookeeper" >> /etc/default/serviced
9 Verify the ZooKeeper environment variables.
grep -E '^\b*SERVICED' /etc/default/serviced \
| grep -E '(CS_ZO|_ZK|CS_ST)'
The following example shows the environment variables for a delegate host with IP address 198.51.100.137.
Note The value of the SERVICED_ISVCS_ZOOKEEPER_QUORUM variable is formatted to fit the
available space. The result of the grep command shows the variable and value on the same line.
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
SERVICED_ISVCS_START=zookeeper
SERVICED_ISVCS_ZOOKEEPER_ID=3
SERVICED_ISVCS_ZOOKEEPER_QUORUM=1@198.51.100.135:2888:3888,\
2@198.51.100.136:2888:3888,3@0.0.0.0:2888:3888
SERVICED_ZK_SESSION_TIMEOUT=15
Starting a ZooKeeper ensemble for the first time
Use this procedure to start a ZooKeeper ensemble.
The goal of this procedure is to restart Control Center on each ensemble node at about the same time, so that
each node can participate in electing the leader.
1 Log in to the Control Center master host as root, or as a user with superuser privileges.
2 In a separate window, log in to the second node of the ZooKeeper ensemble (Delegate-A) as root, or as a
user with superuser privileges.
3 In a different window, log in to the third node of the ZooKeeper ensemble (Delegate-B) as root, or as a
user with superuser privileges.
4 On all ensemble hosts, stop serviced.
systemctl stop serviced
5 When serviced is stopped on all ensemble hosts, start serviced on all ensemble hosts at the same time.
systemctl start serviced
6 On the master host, check the status of the ZooKeeper ensemble.
39
Zenoss Resource Manager Installation Guide
a Attach to the container of the ZooKeeper service.
docker exec -it serviced-isvcs_zookeeper /bin/bash
b Query the master host and identify its role in the ensemble.
Replace Master with the hostname or IP address of the master host:
{ echo stats; sleep 1; } | nc Master 2181 | grep Mode
The result includes leader or follower.
c Query delegate host A and identify its role in the ensemble.
Replace Delegate-A with the hostname or IP address of delegate host A:
{ echo stats; sleep 1; } | nc Delegate-A 2181 | grep Mode
d Query delegate host B and identify its role in the ensemble.
Replace Delegate-B with the hostname or IP address of delegate host B:
{ echo stats; sleep 1; } | nc Delegate-B 2181 | grep Mode
e Detach from the container of the ZooKeeper service.
exit
If none of the hosts reports that it is the ensemble leader within a few minutes of starting serviced, reboot
the hosts.
Updating delegate hosts
The default configuration of delegate hosts sets the value of the SERVICED_ZK variable to the master host only.
Use this procedure to update the setting to include all of the hosts in the ZooKeeper ensemble. Perform this
procedure on each delegate host in a Control Center cluster that is not an ensemble node.
1 Log in to the delegate host as root, or as a user with superuser privileges.
2 Define the IP address variables for each node in the ZooKeeper ensemble.
Replace Master with the IP address or hostname of the Control Center master host, and replace Delegate-A
and Delegate-B with the IP addresses or hostnames of the delegate hosts to include in the ensemble:
node1=Master
node2=Delegate-A
node3=Delegate-B
3 Remove the existing definition of the SERVICED_ZK variable, which specifies only the Control Center
master host.
sed -i.bak '/SERVICED_ZK=/d' /etc/default/serviced
4 Specify the nodes in the ZooKeeper ensemble.
You can copy the following text and paste it in your console:
echo "SERVICED_ZK=${node1}:2181,${node2}:2181,${node3}:2181" \
>> /etc/default/serviced
40
Configuring a ZooKeeper ensemble
5 Verify the setting.
grep -E '^\b*SERVICED_ZK' /etc/default/serviced
The following example shows the environment variable for a delegate host that is not a node in the
ZooKeeper ensemble:
SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181
6 Restart Control Center.
systemctl restart serviced
41
Zenoss Resource Manager Installation Guide
Part II: Non-appliance deployments
The chapters in this part describe how to download and install Resource Manager for a non-appliance
deployment. Complete the procedures in Downloading and staging Resource Manager files on page 43, and
then complete procedures in one of the following chapters:
■
■
42
standard deployment: Installing Resource Manager on page 45
high-availability deployment: Installing Resource Manager in a high-availability cluster on page 47
Downloading and staging Resource Manager files
Downloading and staging Resource
Manager files
5
This chapter contains procedures for downloading and staging Resource Manager software.
Downloading image files
To perform this procedure, you need
■
■
■
a workstation with internet access
permission to download files from the File Portal - Download Zenoss Enterprise Software site. Zenoss
customers can request permission by filing a ticket at the Zenoss Support site
a secure network copy program
Use this procedure to
■
■
download the required files to a workstation
copy the files to a Control Center master host
1 In a web browser, navigate to the File Portal - Download Zenoss Enterprise Software site.
2 Log in with the account provided by Zenoss Support.
3 Download the self-installing Docker image files for Resource Manager.
Select the files with the highest version number. The version number is represented as Version in the
following file names:
install-zenoss-hbase_vVersion.run
■
install-zenoss-opentsdb_vVersion.run
■
install-zenoss-resmgr_Version.run
4 Download the Resource Manager service definition, which is distributed as an RPM file.
Choose the file with the highest version number. The version number is represented as Version in the
following file name:
■
zenoss-resmgr-service-Version.noarch.rpm
5 Use a secure copy program to copy the files to the Control Center master host.
Staging the service definition and Docker image files
Before performing this procedure, verify that approximately 640MB of temporary space is available on the file
system where /root is located.
Perform this procedure to
43
Zenoss Resource Manager Installation Guide
■
stage the Resource Manager service definition on a Control Center master host
■
The service definition is packaged as an RPM file.
add Docker image files to a Control Center master host
The files are used when Docker is fully configured.
1
2
3
4
Log in to the master host as root, or as a user with superuser privileges.
Copy or move the RPM file to /tmp.
Copy or move the archive files to /root.
Add execute permission to the files.
chmod +x /root/*.run
44
Installing Resource Manager
Installing Resource Manager
6
Before performing the procedures in this chapter, perform the procedures in Downloading and staging Resource
Manager files on page 43.
This chapter describes how to install Resource Manager on a Control Center cluster. For more information about
creating a Control Center cluster, refer to the following documents:
■
■
■
Control Center Planning Guide
Zenoss Resource Manager Planning Guide
Control Center Installation Guide
Installing the Resource Manager template
Use this procedure to install the Resource Manager service definition template on the Control Center master
host.
1 Log in to the Control Center master host as root, or as a user with superuser privileges.
2 Install the Resource Manager template file.
yum install /tmp/zenoss-resmgr-service-5.3.1-1.noarch.rpm
The template file is stored in /opt/serviced/templates.
Importing Resource Manager images
Use this procedure to import the Resource Manager images into the local registry. For more information, see
Downloading and staging Resource Manager files on page 43.
1 Log in to the Control Center master host as root, or as a user with superuser privileges.
2 Change directory to /root.
cd /root
3 Import the images.
The images are contained in self-extracting archive files.
for image in install-*.run
do
echo -n "$image: "
45
Zenoss Resource Manager Installation Guide
./$image
done
Importing begins when you press the y key. If you press y and then press Enter, the current image is
imported, but the next one is not.
4 List the images in the registry.
docker images
The result should include one image for each archive file.
5 Optional: Delete the archive files.
rm -i ./install-*.run
Deploying Resource Manager
Use this procedure to add the Resource Manager application to Control Center, and to tag application images in
the local registry.
1 Log in to the Control Center master host as a user with serviced CLI privileges.
2 Add the Resource Manager application template to Control Center.
serviced template add /opt/serviced/templates/zenoss*.json
On success, the serviced command returns the template ID.
3 Identify the resource pool to which the host belongs.
serviced host list
4 Deploy the application.
■
■
■
Replace Template-ID with the identifier Resource Manager template
Replace Pool with the name of the resource pool to which the master host belongs (single-host system) or
to which the delegate hosts belong (multi-host system)
Replace Deployment with a name for this deployment (for example, Test or Production)
serviced template deploy Template-ID Pool Deployment
Control Center tags Resource Manager images in the local registry.
Resource Manager is ready to be configured for your environment. For more information, refer to the Zenoss
Resource Manager Configuration Guide.
46
Installing Resource Manager in a high-availability cluster
Installing Resource Manager in a highavailability cluster
7
Before performing the procedures in this chapter, perform the procedures in Downloading and staging Resource
Manager files on page 43.
This chapter describes how to install Resource Manager on a high-availability Control Center cluster. For more
information about creating a high-availability Control Center cluster, refer to the Control Center Installation
Guide for High-Availability Deployments.
Installing the Resource Manager template
Use this procedure to install the Resource Manager service definition template on a Control Center master host
node. Perform this procedure on both master host nodes.
1 Log in to the Control Center master host as root, or as a user with superuser privileges.
2 Install the Resource Manager template file.
yum install /tmp/zenoss-resmgr-service-5.3.1-1.noarch.rpm
The template file is stored in /opt/serviced/templates.
Importing Resource Manager images
Use this procedure to import the Resource Manager images into the local registry. Perform this procedure on
both master host nodes.
1 Log in to the Control Center master host as root, or as a user with superuser privileges.
2 Change directory to /root.
cd /root
3 Import the images.
The images are contained in self-extracting archive files.
for image in install-*.run
do
echo -n "$image: "
./$image
done
47
Zenoss Resource Manager Installation Guide
Importing begins when you press y. If you press y and then press Enter, the current image is imported, but
the next one is not.
4 List the images in the registry.
docker images
The result should include one image for each archive file.
5 Optional: Delete the archive files.
rm -i ./install-*.run
Deploying Resource Manager
Use this procedure to install the Resource Manager template and then deploy the application.
1 Use the virtual hostname (HA-Virtual-Name) or virtual IP address (HA-Virtual-IP) of the high-availability
cluster to start a Bash shell on the Control Center master host as root, or as a user with superuser
privileges.
2 Display the public hostname of the current node.
uname -n
The result is either Primary-Public-Name or Secondary-Public-Name.
3 Place the other node in standby mode.
This avoids potential conflicts and errors in the event of an unexpected serviced shutdown during the
initial deployment.
Replace Other-Node-Hostname with the public hostname of the other node:
pcs cluster standby Other-Node-Hostname
4 Add the Resource Manager application template to Control Center.
serviced template add /opt/serviced/templates/zenoss*.json
On success, the serviced command returns the template ID.
5 Identify the resource pool to which the master host belongs.
serviced host list
6 Deploy the application.
■
■
■
Replace Template-ID with the identifier Resource Manager template
Replace Pool with the name of the resource pool to which the master host belongs (single-host system) or
to which the delegate hosts belong (multi-host system)
Replace Deployment with a name for this deployment (for example, Test or Production)
serviced template deploy Template-ID Pool Deployment
Control Center tags the Resource Manager images.
7 Restore the cluster.
48
Installing Resource Manager in a high-availability cluster
Replace Standby-Node-Hostname with the public hostname of the node that is in standby mode:
pcs cluster unstandby Standby-Node-Hostname
Resource Manager is ready to be configured for your environment. For more information, refer to the Zenoss
Resource Manager Configuration Guide.
Note
In high-availability deployments, the mariadb-events and mariadb-model services must be in the
same resource pool as the master host nodes. A procedure for moving the services from their default pool is
provided in the Zenoss Resource Manager Configuration Guide.
49
Download PDF
Similar pages