Zenoss Resource Mnger Instlltion Guide Relese 5.3.2 Zenoss, Inc. www.zenoss.com
Zenoss Resource Mnger Instlltion Guide Copyright 2017 Zenoss, Inc. All rights reserved. Zenoss, Own IT, nd the Zenoss logo re trdemrks or registered trdemrks of Zenoss, Inc., in the United Sttes nd other countries. All other trdemrks, logos, nd service mrks re the property of Zenoss or other third prties. Use of these mrks is prohibited without the express written consent of Zenoss, Inc., or the third-prty owner. Amzon Web Services, AWS, nd EC2 re trdemrks of Amzon.com, Inc. or its ffilites in the United Sttes nd/or other countries. Flsh is registered trdemrk of Adobe Systems Incorported. Orcle, the Orcle logo, Jv, nd MySQL re registered trdemrks of the Orcle Corportion nd/or its ffilites. Linux is registered trdemrk of Linus Torvlds. RbbitMQ is trdemrk of Pivotl Softwre, Inc. SNMP Informnt is trdemrk of Grth K. Willims (Informnt Systems, Inc.). Sybse is registered trdemrk of Sybse, Inc. Tomct is trdemrk of the Apche Softwre Foundtion. VMwre is registered trdemrk or trdemrk of VMwre, Inc. in the United Sttes nd/or other jurisdictions. Windows is registered trdemrk of Microsoft Corportion in the United Sttes nd other countries. All other compnies nd products mentioned re trdemrks nd property of their respective owners. Prt Number: 1052.17.268 Zenoss, Inc. 11305 Four Points Drive Bldg 1 - Suite 300 Austin, Texs 78726 2
Contents About this guide...5 Supported operting environments... 5 Resource Mnger publictions...6 Chnge history... 7 Prt I: Applince deployments... 10 Chpter 1: Instlling mster host... 11 Creting virtul mchine... 11 Configuring the Control Center mster host... 15 Editing connection to configure sttic IPv4 ddressing...16 Setting the system hostnme... 18 Adding the mster host to resource pool... 19 Chpter 2: Instlling delegte hosts... 20 Creting virtul mchine... 20 Configuring the virtul mchine...23 Editing connection to configure sttic IPv4 ddressing...24 Setting the system hostnme... 26 Editing the /etc/hosts file...27 Chpter 3: Configuring multi-host cluster... 29 Enbling NTP on Microsoft Hyper-V guests...29 Adding hosts to the defult resource pool... 32 Chpter 4: Configuring ZooKeeper ensemble...34 ZooKeeper nd Control Center... 34 Understnding the configurtion process... 34 Configuring the mster host s ZooKeeper node...36 Configuring delegte host A s ZooKeeper node... 37 Configuring delegte host B s ZooKeeper node... 38 Strting ZooKeeper ensemble for the first time...39 Updting delegte hosts...40 Prt II: Non-pplince deployments... 42 Chpter 5: Downloding nd stging Resource Mnger files...43 Downloding imge files...43 Stging the service definition nd Docker imge files... 43 3
Chpter 6: Instlling Resource Mnger... 45 Instlling the Resource Mnger templte... 45 Importing Resource Mnger imges...45 Deploying Resource Mnger... 46 Chpter 7: Instlling Resource Mnger in high-vilbility cluster... 47 Instlling the Resource Mnger templte... 47 Importing Resource Mnger imges...47 Deploying Resource Mnger... 48 4
About this guide About this guide Zenoss Resource Mnger Instlltion Guide provides detiled procedures for instlling Zenoss Resource Mnger (Resource Mnger). Supported operting environments The Resource Mnger ppliction is deployed in nd mnged by Control Center. The supported operting environments of Resource Mnger re the environments tht Control Center supports t given relese. The following sections identify the supported operting environments of Resource Mnger. Resource Mnger, Control Center, nd operting systems The following tble identifies the supported combintions of Resource Mnger, Control Center, nd operting system releses. Resource Mnger relese Control Center relese 5.3.0, 5.3.1, 5.3.2 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4.0, 1.4.1 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, 1.4.1 Host OS RHEL/CentOS 7.1, 7.2, or 7.3 (64-bit) 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 (internl relese 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) Hypervisors Hypervisor Versions VMwre 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 nd 2012 R2 Public cloud pltforms Amzon Web Services (AWS) is fully supported. Microsoft Azure is supported only for collector pools. Deploying full Control Center cluster to operte Resource Mnger is NOT supported on Microsoft Azure. * Version 5.2.5 ws withdrwn. 5
Zenoss Resource Mnger Instlltion Guide Supported clients nd browsers The following tble identifies the supported combintions of client operting systems nd web browsers. Client OS Windows 7 nd 8.1 Supported Browsers Internet Explorer 11 (Enterprise mode only; comptibility mode is not supported.) Internet Explorer 10 * Windows 10 Internet Explorer 11 (Enterprise mode only; comptibility mode is not supported.) Internet Explorer 10 * Firefox 50 nd lter Chrome 54 nd lter Microsoft Edge Windows Server 2012 R2 Mcintosh OS/X 10.9 Ubuntu 14.04 LTS Red Ht Enterprise Linux 6.5, CentOS 6.5 Firefox 30 Chrome 36 Firefox 30 nd bove Chrome 36 nd bove Firefox 30 nd bove Chrome 37 nd bove Firefox 30 nd bove Chrome 37 nd bove Resource Mnger publictions Title Zenoss Resource Mnger Administrtion Guide Zenoss Resource Mnger Configurtion Guide Zenoss Resource Mnger Instlltion Guide Zenoss Resource Mnger Plnning Guide Zenoss Resource Mnger Relese Notes Description Provides n overview of Resource Mnger rchitecture nd fetures, s well s procedures nd exmples to help use the system. Provides required nd optionl configurtion procedures for Resource Mnger, to prepre your deployment for monitoring in your environment. Provides detiled informtion nd procedures for creting deployments of Control Center nd Resource Mnger. Provides both generl nd specific informtion for prepring to deploy Resource Mnger. Describes known issues, fixed issues, nd ltebreking informtion not lredy provided in the published documenttion set. * Support for Internet Explorer 10 will be withdrwn beginning with the next mjor relese of Resource Mnger. 6
About this guide Title Zenoss Resource Mnger Upgrde Guide Description Provides detiled informtion nd procedures for upgrding deployments of Resource Mnger. Additionl informtion nd comments If you hve technicl questions bout this product tht re not nswered in this guide, plese visit the Zenoss Support site or contct Zenoss Support. Zenoss welcomes your comments nd suggestions regrding our documenttion. To shre your comments, plese send n emil to docs@zenoss.com. In the emil, include the document title (Zenoss Resource Mnger Instlltion Guide) nd prt number (1052.17.268). Chnge history The following list ssocites document prt numbers nd the importnt chnges to this guide since the previous relese. Some of the chnges involve fetures or content, but others do not. For informtion bout new or chnged fetures, refer to the Zenoss Resource Mnger Relese Notes. 1052.17.268 (5.3.2) Updte relese numbers. 1052.17.242 (5.3.1) Updte relese numbers. 1052.17.229 (5.3.0) Beginning with this relese, you cn downlod nd instll the pplince rtifcts or converged set of rtifcts. This document ws reorgnized nd updted with ssocited informtion. Updte relese numbers. 1052.17.191 (5.2.6) Updte relese numbers. About 5.2.5 Version 5.2.5 ws withdrwn. 1052.17.123 (5.2.4) Updte relese numbers. 1052.17.100 (5.2.3) Add chpter for high-vilbility instlltions. New procedures for instlling the pplince with Hyper-V. Updte relese numbers. 1052.17.58 (5.2.2) Remove procedure for dding storge for bckups (no longer required for pplinces). 1052.17.044 (5.2.1) Updte relese numbers. 1052.16.335 (5.2.0) Add section detiling the supported operting environments. Remove procedures for instlling Control Center clusters. Tht informtion is now in the Control Center Instlltion Guide. Remove the high-vilbility chpters. High-vilbility instlltions re now performed by Zenoss personnel. Remove the pplince instlltion chpters. The chpters will be replced when the pplinces re vilble. 7
Zenoss Resource Mnger Instlltion Guide The instructions for downloding nd instlling the softwre rtifcts for offline deployments re now in n ppendix. 1052.16.316 Updte relese numbers. 1052.16.291 Updte relese numbers. 1052.16.277 Updte relese numbers. 1052.16.264 Updte relese numbers. 1052.16.257 Added supported operting environments nd updted relese numbers. 1052.16.207 Updte relese numbers. 1052.16.176 Updte relese numbers. 1052.16.153 Updte relese numbers. 1052.16.146 Updte relese numbers. 1052.16.125 Refine the procedure for creting the ppliction dt thin pool. 1052.16.118 Add support for Resource Mnger 5.1.2. Add substep to crete the docker override directory. 1052.16.111 Add this document chnge history. Add chpters describing how to instll the Resource Mnger pplince. Chpters re orgnized into prts. Docker configurtion steps now dd the storge driver flg (-s devicempper) to the /etc/ sysconfig/docker file. Docker needs longer strtup timeout vlue, to work round known Docker issue with the devicempper driver. Docker configurtion steps now include dding TimeoutSec=300. Rther thn editing /lib/systemd/system/docker.service, Docker configurtion steps now include dding systemd override file. Add symlink to /tmp in /vr/lib/docker. Updte the commnds for strting nd testing ZooKeeper ensemble. Add procedure for updting the SERVICED_ZK vlue on delegte hosts tht re not members of ZooKeeper ensemble. Add reference topic for the ZooKeeper vribles required on hosts in Control Center cluster. Add procedures for configuring n NTP server nd clients for offline deployments. Add step to instll the Nmp Nct pckge, which is used to check ZooKeeper ensemble sttus. 1052.16.060 Plnning informtion is now in the Zenoss Resource Mnger Plnning Guide. 8
About this guide Informtion bout how to strt nd configure Resource Mnger is now in the Zenoss Resource Mnger Configurtion Guide. New procedures re included, for instlling without internet ccess, nd for instlling high-vilbility deployments. 9
Zenoss Resource Mnger Instlltion Guide Prt I: Applince deployments The chpters in this prt describe how to instll the Resource Mnger pplince, pre-configured virtul mchine tht is redy to deploy to your hypervisor. The instructions include vriety of options for customizing your deployment for your environment. For informtion bout the lternte instlltion option, see non-pplince instlltions Scope on pge 42 10
Instlling mster host Instlling mster host 1 This chpter describes how to instll Resource Mnger pplince pckge s Control Center mster host. All Resource Mnger deployments require Control Center mster host. Creting virtul mchine You cn crete virtul mchine for the Resource Mnger pplince with VMwre vsphere or Microsoft Hyper-V. Choose one of the procedures in this section. Creting virtul mchine with vsphere To perform this tsk, you need A VMwre vsphere client Permission to downlod Resource Mnger softwre from the Zenoss Support site This procedure instlls Resource Mnger OVA pckges s virtul mchine mnged by vsphere Server version 6.5.0, using VMwre vsphere Web Client 6.5. The procedure might differ with other versions of VMwre vsphere Client. There re two seprte OVA pckges: one for the mster host nd one for delegtes. 1 Downlod the Resource Mnger mster host OVA file from the Zenoss Support site to your worksttion. 2 Use the VMwre vsphere Client to log in to vcenter s root, or s user with superuser privileges, nd then disply the Home view. 11
Zenoss Resource Mnger Instlltion Guide 3 Choose VMs nd Templtes. 4 In the top nvigtion br, choose Actions > Deploy OVF Templte. Figure 1: Deploy OVF Templte 5 Use pnels in the Deploy OVF Templte wizrd to select the OVF pckge: b c To choose the pckge from drive on your worksttion or network shre, browse to the loction nd choose the OVA file. Click Next. Select nme nd loction: Specify nme for the OVF, select dtcenter or folder s the deployment loction, nd then click Next. Select resource: Select the host, cluster, or other resource on which to run the deployed templte, nd then click Next. 12
Instlling mster host d e f g Review detils: Verify the templte detils, nd then click Next. Select storge: In Select virtul disk formt, choose Thin Provison, ccept defults for other fields, nd then click Next. Select networks: Accept defults nd click Next. Redy to Complete: Verify the deployment settings, nd then click Finish. The Recent Tsks pne displys deployment progress nd sttus informtion. 6 Nvigte to the new virtul mchine's Getting Strted tb, nd then click Edit virtul mchine settings. 7 Edit Virtul Hrdwre settings for the virtul mchine s follows. Accept defult 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 virtul mchine's Getting Strted tb, click Power on virtul mchine. 9 In the top nvigtion br, choose Actions > Open console. Proceed with Configuring the Control Center mster host on pge 15. Creting virtul mchine with Hyper-V To perform this tsk, you need: A Microsoft Remote Desktop Connection Administrtor privileges on Microsoft Hyper-V server Permission to downlod Resource Mnger softwre from the Zenoss Support site This procedure instlls the Resource Mnger pplince s virtul mchine mnged by Microsoft Hyper-V. There re seprte ISO files for the mster host nd delegtes. In this procedure, you downlod nd instll the mster ISO file. A seprte procedure provides instructions for instlling delegtes. 1 Use Microsoft Remote Desktop Connection to log in to Hyper-V host s Administrtor, or s user with Administrtor privileges. 2 Downlod the Resource Mnger ISO file from the Zenoss Support site to the Hyper-V host. Choose the mster ISO file. 3 Open Hyper-V Mnger. 4 In the left nvigtion pne, choose server to host the virtul mchine. 5 In the Actions pne, choose New > Virtul Mchine. The New Virtul Mchine Wizrd opens. 6 Use pnels in the wizrd to crete the virtul mchine: b c Specify Nme nd Loction: Provide nme for the virtul mchine, nd then click Next. Specify Genertion: Choose Genertion 1, nd then click Next. Assign Memory: Specify memory informtion s follows: Strtup memory d Multi-host deployment: 16384 (16GB). Single-host deployments: 65536 (64GB). Check Use Dynmic Memory for this virtul mchine. Click Next. Configure Networking: For Connection, choose virtul switch, nd then click Next. 13
Zenoss Resource Mnger Instlltion Guide e Connect Virtul Hrd Disk: Crete new disk on which to instll the guest operting system s follows: 1 Choose Crete virtul hrd disk. 2 Specify nme. 3 Size: Enter 30. 4 Click Next. f In lter step, you will crete dditionl disks. Instlltion Options: Access the mster ISO file s follows: g 1 Choose Instll n operting system from bootble CD/DVD-ROM. 2 Choose Imge file (.iso). 3 Specify or browse to the loction of the ISO imge file. Summry/Completing the New Virtul Mchine Wizrd: Verify the description, nd then click Finish. Hyper-V Mnger cretes the new virtul mchine, nd then closes the wizrd. 7 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Settings. 8 In the Hrdwre re on the left, configure s follows: b c Ensure tht the virtul hrd disk tht you creted is ttched to n IDE controller. A Hyper-V guest mchine cn only boot from n IDE drive. Choose Processor. In the Processor re on the right, in Number of virtul processors, enter the following vlue for your deployment type: Multi-host deployment: 4 Single-host deployment: 8 d Click Apply. 9 Crete dditionl virtul hrd disks s follows: b c d In the Hrdwre re on the left, choose ny controller nd loction tht will ccommodte the disk. In the controller re on the right, choose Hrd Drive, nd then click Add. In the re on the right, choose Virtul hrd disk, nd then click New. Complete pnels in the New Virtul Hrd Disk Wizrd s follows: 1 Choose Disk Formt: Choose VHDX, nd then click Next. 2 Choose Disk Type: Choose Dynmiclly expnding, nd then click Next. 3 Specify Nme nd Loction: Enter the disk nme, nd then click Next. 4 Configure Disk: e f Choose Crete new blnk virtul hrd disk. b Size: Enter 50. c Click Next. 5 Summry/New Virtul Hrd Disk Wizrd: Verify the description, nd then click Finish. In the Settings window, click Apply. Repet this step to crete dditionl virtul hrd disks in the following sizes (for totl of seven disks): 150GB 50GB 200GB 16GB 14
Instlling mster host 16GB When viewed from the Linux system, the disks might be reordered; however, the instlltion is not ffected by disk order. g In the Settings dilog box, click Apply, nd then click OK. 10 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Strt. Figure 2: Strting virtul mchine 11 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Connect. 12 In the Virtul Mchine Connection window, press Enter. The pplince instlltion process tkes bout 15 minutes, nd should complete with no dditionl input. If received, disregrd the Fst TSC clibrtion filure messge. Configuring the Control Center mster host Perform this procedure immeditely fter creting nd strting Control Center host. All Control Center deployments must include one system tht is configured s the mster host. 1 Gin ccess to the console interfce of the Control Center host through your hypervisor console interfce. Figure 3: Initil hypervisor console login prompt 2 Log in s the root user. The initil pssword is provided in the console. 3 The system prompts you to enter new pssword for root. Note Psswords must include minimum of eight chrcters, with t lest one chrcter from three of the following chrcter clsses: uppercse letter, lowercse letter, digit, nd specil. 4 The system prompts you to enter new pssword for ccuser. 15
Zenoss Resource Mnger Instlltion Guide The ccuser ccount is the defult ccount for gining ccess to the Control Center browser interfce. Editing connection to configure sttic IPv4 ddressing The defult configurtion for network connections is DHCP. To configure sttic IPv4 ddressing, perform this procedure. To nvigte in the text user interfce (TUI): To move forwrd or bckwrd through options, press the rrow keys. To disply menu or choose n option, press Enter. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Log in s the root user. 3 Select the NetworkMnger TUI menu s follows: In the Applince Administrtion menu, select Configure Network nd DNS, nd then press Enter. 4 On the NetworkMnger TUI menu, select Edit connection, nd then press Enter. The TUI displys the connections tht re vilble on the host. 16
Instlling mster host Figure 4: Exmple: Avilble connections Note Do not use this procedure to modify the docker0 connection. 5 Select the virtul connection, nd then press Enter. Figure 5: Exmple: Edit Connection screen 6 Optionl: If the IPv4 CONFIGURATION re is not visible, select its disply option (<Show>), nd then press Enter. 7 In the IPv4 CONFIGURATION re, select <Automtic>, nd then press Enter. Figure 6: Exmple: IPv4 Configurtion options 8 Configure sttic IPv4 networking s follows: Select Mnul, nd then press Enter. b Beside Addresses, select <Add>, nd then press Enter. 17
Zenoss Resource Mnger Instlltion Guide c In the Addresses field, enter n IPv4 ddress for the virtul mchine, nd then press Enter. d Repet the preceding two steps for the Gtewy nd DNS servers fields. 9 Tb to the bottom of the Edit Connection screen to select <OK>, nd then press Enter. 10 Return to the Applince Administrtion menu: On the NetworkMnger TUI screen, select <Quit>, nd then press Enter. 11 Reboot the operting system s follows: b c In the Applince Administrtion menu, select Reboot / Poweroff System. Select Reboot. Select OK, nd then press Enter. Setting the system hostnme The defult hostnme is zsd-mster for the Resource Mnger mster host nd is zsd-delegte for Resource Mnger delegte hosts. To chnge the defult hostnme, perform this procedure. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Select the NetworkMnger TUI menu s follows: In the Applince Administrtion menu, select Configure Network nd DNS, nd then press Enter. 3 Disply the hostnme entry field. In the NetworkMnger TUI menu, select Set system hostnme. b Select OK, nd then press Enter. 4 In the Hostnme field, enter the hostnme or fully qulified domin nme. 5 Press Tb twice to select OK, nd then press Enter. 6 In the confirmtion dilog box, press Enter. 7 Return to the Applince Administrtion menu: On the NetworkMnger TUI screen, select <Quit>, nd then press Enter. 8 Reboot the operting system s follows: b c In the Applince Administrtion menu, select Reboot / Poweroff System. Select Reboot. Select OK, nd then press Enter. 18
Instlling mster host Adding the mster host to resource pool Complete this procedure to dd the Control Center mster host to the defult resource pool or to new resource pool nmed mster. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Strt commnd-line session s root s follows: b In the Applince Administrtion menu, select Root Shell. Select Run, nd then press Enter. The menu is replced by commnd prompt similr to the following exmple: [root@hostnme ~]# 3 Optionl: Crete new resource pool, if necessry. For single-host deployments, skip this step. For multi-host deployments, perform the following substeps. Crete new pool nmed mster. b serviced pool dd mster Assign dministrtive nd distributed file system (DFS) permissions to the new resource pool. serviced pool set-permission --dmin --dfs mster 4 Add the mster host to resource pool. For single-host deployments, dd the mster host to the defult resource pool. Replce Hostnme-Or-IP with the hostnme or IP ddress of the Control Center mster host: serviced host dd Hostnme-Or-IP:4979 defult If you enter hostnme, ll hosts in your Control Center cluster must be ble to resolve the nme, either through n entry in /etc/hosts, or through nmeserver on your network. For multi-host deployments, dd the mster host to the mster resource pool nd register its uthentiction token. Replce Hostnme-Or-IP with the hostnme or IP ddress of the Control Center mster host: serviced host dd --register Hostnme-Or-IP:4979 mster If you enter hostnme, ll hosts in your Control Center cluster must be ble to resolve the nme, either through n entry in /etc/hosts, or through nmeserver on your network. 5 To exit the commnd-line session, t the commnd prompt, enter exit. 19
Zenoss Resource Mnger Instlltion Guide Instlling delegte hosts 2 This chpter describes how to instll Resource Mnger pplince pckge s Control Center delegte host. You cn dd s mny delegte hosts s you need to Control Center cluster. Perform the procedures in Instlling mster host on pge 11 before performing the procedures in this chpter. Creting virtul mchine You cn crete virtul mchine for the Resource Mnger delegte pplince with VMwre vsphere or Microsoft Hyper-V. Choose one of the procedures in this section. Creting virtul mchine with vsphere To perform this tsk, you need A VMwre vsphere client Permission to downlod Resource Mnger softwre from the Zenoss Support site This procedure instlls Resource Mnger OVA pckges s virtul mchine mnged by vsphere Server version 6.5.0, using VMwre vsphere Web Client 6.5. The procedure might differ with other versions of VMwre vsphere Client. There re two seprte OVA pckges: one for the mster host nd one for delegtes. 1 Downlod the Resource Mnger delegte OVA file from the Zenoss Support site to your worksttion, if necessry. 2 Use the VMwre vsphere Client to log in to vcenter s root, or s user with superuser privileges, nd then disply the Home view. 20
Instlling delegte hosts 3 In the top nvigtion br, choose Actions > Deploy OVF Templte. Figure 7: Deploy OVF Templte 4 Use pnels in the Deploy OVF Templte wizrd to select the OVF pckge: To choose the pckge from drive on your worksttion or network shre, browse to the loction nd choose the OVA file. Click Next. b Select nme nd loction: Specify nme for the OVF, select dtcenter or folder s the deployment loction, nd then click Next. c Select resource: Select the host, cluster, or other resource on which to run the deployed templte, nd then click Next. d Review detils: Verify the templte detils, nd then click Next. 21
Zenoss Resource Mnger Instlltion Guide e f g Select storge: In Select virtul disk formt, choose Thin Provison, ccept defults for other fields, nd then click Next. Select networks: Accept defults nd click Next. Redy to Complete: Verify the deployment settings, nd then click Finish. The Recent Tsks pne displys deployment progress nd sttus informtion. 5 Nvigte to the new virtul mchine's Getting Strted tb, nd then click Edit virtul mchine settings. 6 Updte the memory ssigned to the mchine to 32GB, nd then click OK. 7 On the new virtul mchine's Getting Strted tb, click Power on virtul mchine. Creting virtul mchine with Hyper-V To perform this tsk, you need: A Microsoft Remote Desktop Connection Administrtor privileges on Microsoft Hyper-V server Permission to downlod Resource Mnger softwre from the Zenoss Support site This procedure instlls the Resource Mnger pplince s virtul mchine mnged by Microsoft Hyper-V. There re seprte ISO files for the mster host nd delegtes. In this procedure, you downlod nd instll the delegte ISO file. A seprte procedure provides instructions for instlling the mster. 1 Use Microsoft Remote Desktop Connection to log in to Hyper-V host s Administrtor, or s user with Administrtor privileges. 2 Downlod the Resource Mnger ISO file from the Zenoss Support site to the Hyper-V host. Choose the delegte ISO file. 3 Open Hyper-V Mnger. 4 In the left nvigtion pne, choose server to host the virtul mchine. 5 In the Actions pne, choose New > Virtul Mchine. The New Virtul Mchine Wizrd opens. 6 Use pnels in the wizrd to crete the virtul mchine: b c Specify Nme nd Loction: Provide nme for the virtul mchine, nd then click Next. Specify Genertion: Choose Genertion 1, nd then click Next. Assign Memory: Specify memory informtion s follows: d e Strtup memory: Enter 32768 (32GB). Check Use Dynmic Memory for this virtul mchine. Click Next. Configure Networking: For Connection, choose virtul switch, nd then click Next. Connect Virtul Hrd Disk: Crete new disk on which to instll the guest operting system s follows: 1 Choose Crete virtul hrd disk. 2 Specify nme. 3 Size: Enter 30. 4 Click Next. f In lter step, you will crete dditionl disks. Instlltion Options: Access the delegte ISO file s follows: 1 Choose Instll n operting system from bootble CD/DVD-ROM. 2 Choose Imge file (.iso). 22
Instlling delegte hosts 3 Specify or browse to the loction of the ISO imge file. g Summry/Completing the New Virtul Mchine Wizrd: Verify the description, nd then click Finish. 7 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Settings. 8 In the Hrdwre re on the left, configure s follows: Ensure tht the virtul hrd disk tht you creted is ttched to n IDE controller. A Hyper-V guest mchine cn only boot from n IDE drive. b Choose Processor. c In Number of virtul processors, enter 8, nd then click Apply. 9 Crete dditionl virtul hrd disks s follows: b c d e f In the Hrdwre re on the left, choose ny controller nd loction tht will ccommodte the disk. In the controller re on the right, choose Hrd Drive, nd then click Add. In the re on the right, choose Virtul hrd disk, nd then click New. Complete pnels in the New Virtul Hrd Disk Wizrd s follows: 1 Choose Disk Formt: Choose VHDX, nd then click Next. 2 Choose Disk Type: Choose Dynmiclly expnding, nd then click Next. 3 Specify Nme nd Loction: Enter the disk nme, nd then click Next. 4 Configure Disk: Choose Crete new blnk virtul hrd disk. b Size: Enter 50. c Click Next. 5 Summry/New Virtul Hrd Disk Wizrd: Verify the description, nd then click Finish. In the Settings window, click Apply. Repet this step to crete two 16GB virtul hrd disks (for totl of four disks). When viewed from the Linux system, the disks might be reordered; however, the instlltion is not ffected by disk order. g In the Settings dilog box, click Apply, nd then click OK. 10 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Strt. Figure 8: Strting virtul mchine 11 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Connect. 12 In the Virtul Mchine Connection window, press Enter. The pplince instlltion process tkes bout 15 minutes, nd should complete with no dditionl input. If received, disregrd the Fst TSC clibrtion filure messge. Configuring the virtul mchine This procedure configures the new virtul mchine s delegte host. 23
Zenoss Resource Mnger Instlltion Guide 1 Gin ccess to the console interfce of the Control Center host through your hypervisor console interfce. Figure 9: Initil hypervisor console login prompt 2 Log in s the root user. The initil pssword is provided in the console. 3 The system prompts you to enter new pssword for root. Note Psswords must include minimum of eight chrcters, with t lest one chrcter from three of the following chrcter clsses: uppercse letter, lowercse letter, digit, nd specil. 4 The system prompts you to enter new pssword for ccuser. The ccuser ccount is the defult ccount for gining ccess to the Control Center browser interfce. 5 In the IP field, enter the hostnme, fully qulified domin nme, or IPv4 ddress of the mster host. Note If you enter the hostnme or fully qulified domin nme of the mster host, you need n entry in the /etc/hosts file of the delegte host or nmeserver on your network tht resolves the nme to its IPv4 ddress. Press Tb to select Ok, nd then press Enter. The system reboots. Editing connection to configure sttic IPv4 ddressing The defult configurtion for network connections is DHCP. To configure sttic IPv4 ddressing, perform this procedure. To nvigte in the text user interfce (TUI): To move forwrd or bckwrd through options, press the rrow keys. To disply menu or choose n option, press Enter. 24
Instlling delegte hosts 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Log in s the root user. 3 Select the NetworkMnger TUI menu s follows: In the Applince Administrtion menu, select Configure Network nd DNS, nd then press Enter. 4 On the NetworkMnger TUI menu, select Edit connection, nd then press Enter. The TUI displys the connections tht re vilble on the host. Figure 10: Exmple: Avilble connections 25
Zenoss Resource Mnger Instlltion Guide Note Do not use this procedure to modify the docker0 connection. 5 Select the virtul connection, nd then press Enter. Figure 11: Exmple: Edit Connection screen 6 Optionl: If the IPv4 CONFIGURATION re is not visible, select its disply option (<Show>), nd then press Enter. 7 In the IPv4 CONFIGURATION re, select <Automtic>, nd then press Enter. Figure 12: Exmple: IPv4 Configurtion options 8 Configure sttic IPv4 networking s follows: Select Mnul, nd then press Enter. b Beside Addresses, select <Add>, nd then press Enter. c In the Addresses field, enter n IPv4 ddress for the virtul mchine, nd then press Enter. d Repet the preceding two steps for the Gtewy nd DNS servers fields. 9 Tb to the bottom of the Edit Connection screen to select <OK>, nd then press Enter. 10 Return to the Applince Administrtion menu: On the NetworkMnger TUI screen, select <Quit>, nd then press Enter. 11 Reboot the operting system s follows: b c In the Applince Administrtion menu, select Reboot / Poweroff System. Select Reboot. Select OK, nd then press Enter. Setting the system hostnme The defult hostnme is zsd-mster for the Resource Mnger mster host nd is zsd-delegte for Resource Mnger delegte hosts. To chnge the defult hostnme, perform this procedure. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Select the NetworkMnger TUI menu s follows: In the Applince Administrtion menu, select Configure Network nd DNS, nd then press Enter. 26
Instlling delegte hosts 3 Disply the hostnme entry field. In the NetworkMnger TUI menu, select Set system hostnme. b Select OK, nd then press Enter. 4 In the Hostnme field, enter the hostnme or fully qulified domin nme. 5 Press Tb twice to select OK, nd then press Enter. 6 In the confirmtion dilog box, press Enter. 7 Return to the Applince Administrtion menu: On the NetworkMnger TUI screen, select <Quit>, nd then press Enter. 8 Reboot the operting system s follows: b c In the Applince Administrtion menu, select Reboot / Poweroff System. Select Reboot. Select OK, nd then press Enter. Editing the /etc/hosts file This procedure is conditionl. Perform this procedure only if you use hostnmes or fully qulified domin nmes insted of IPv4 ddresses, nd only fter ll delegte hosts re instlled nd renmed. Perform this procedure on the Control Center mster host nd on ech delegte host. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Strt commnd-line session s root s follows: b In the Applince Administrtion menu, select Root Shell. Select Run, nd then press Enter. The menu is replced by commnd prompt similr to the following exmple: [root@hostnme ~]# 3 Open the /etc/hosts file in text editor. The following steps use the nno editor. 27
Zenoss Resource Mnger Instlltion Guide Strt the editor. nno /etc/hosts Figure 13: Exmple nno session b Optionl: On delegte hosts, the file might include two entries with the sme IP ddress. Remove the first of the two entries, which mps the IP ddress to the zsd-mster hostnme. c Add entries for the Control Center mster host nd for ech delegte host. d To sve, press Control-o. e To exit, press Control-x. 4 Return to the Applince Administrtion menu. exit 5 Exit the Applince Administrtion menu. Use the down-rrow key to select Exit. b Press Tb, nd then press Enter. 28
Configuring multi-host cluster Configuring multi-host cluster 3 This chpter describes how to configure n pplince-bsed multi-host Control Center cluster. A multi-host Resource Mnger deployment includes one Control Center mster host nd one or more delegte hosts. Zenoss recommends deploying t lest two delegte hosts to enble creting ZooKeeper ensemble. Enbling NTP on Microsoft Hyper-V guests The procedures in this section re required only for multi-host deployments running s Microsoft Hyper-V guests. VMwre vsphere guests use n hourly cron job to synchronize their system clocks with the host.like most distributed pplictions, Control Center requires common time source. The procedures in this section enble NTP to synchronize the system clocks of ll hosts in your Control Center cluster. Configure NTP to rely on time source s follows, depending on internet ccess of the hosts in your Control Center cluster: If ll hosts cn ccess the internet, configure NTP to rely on public time servers. If no host cn ccess the internet, configure NTP to rely on privte mster server. Configuring NTP for public time servers (Hyper-V only) This procedure uses the defult configurtion of NTP to synchronize system clocks with public time servers. If ll hosts in the Control Center cluster cn ccess the internet, repet this procedure on ech host in the cluster, strting with the Control Center mster host. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Strt commnd-line session s root s follows: b In the Applince Administrtion menu, select Root Shell. Select Run, nd then press Enter. The menu is replced by commnd prompt similr to the following exmple: [root@hostnme ~]# 3 Stop Control Center. systemctl stop serviced 4 Synchronize the system clock nd enble the NTP demon. 29
Zenoss Resource Mnger Instlltion Guide b c d Set the system time. ntpd -gq Enble the ntpd demon. systemctl enble ntpd Configure ntpd to strt when the system strts. Currently, n unresolved issue ssocited with NTP prevents ntpd from restrting correctly fter reboot, nd the following commnds provide workround to ensure tht it does. echo "systemctl strt ntpd" >> /etc/rc.d/rc.locl chmod +x /etc/rc.d/rc.locl Strt ntpd. systemctl strt ntpd 5 Strt Control Center. systemctl strt serviced Configuring n NTP mster server (Hyper-V only) This procedure configures n NTP mster server on the Control Center mster host. Perform this procedure only if the host does not hve internet ccess. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Strt commnd-line session s root s follows: b In the Applince Administrtion menu, select Root Shell. Select Run, nd then press Enter. The menu is replced by commnd prompt similr to the following exmple: [root@hostnme ~]# 3 Crete bckup of the NTP configurtion file. cp -p /etc/ntp.conf /etc/ntp.conf.orig 4 Edit the NTP configurtion file s follows: b Open /etc/ntp.conf with text editor. Replce ll lines in the file with the following lines: # Use the locl clock server 127.127.1.0 prefer fudge 127.127.1.0 strtum 10 driftfile /vr/lib/ntp/drift brodcstdely 0.008 # Give loclhost full ccess rights restrict 127.0.0.1 30
Configuring multi-host cluster c # Grnt ccess to client hosts restrict ADDRESS_RANGE msk NETMASK nomodify notrp Replce ADDRESS_RANGE with the rnge of IPv4 network ddresses tht re llowed to query this NTP server. For exmple, the following IP ddresses re ssigned to the hosts in Control Center cluster: 203.0.113.10 203.0.113.11 203.0.113.12 203.0.113.13 For the preceding ddresses, the vlue for ADDRESS_RANGE is 203.0.113.0. d Replce NETMASK with the IPv4 network msk tht corresponds with the ddress rnge. For exmple, the network msk for 203.0.113.0 is 255.255.255.0. e Sve the file nd exit the editor. 5 Stop Control Center. systemctl stop serviced 6 Enble nd strt the NTP demon s follows: Enble the ntpd demon. b c systemctl enble ntpd Configure ntpd to strt when the system strts. Currently, n unresolved issue ssocited with NTP prevents ntpd from restrting correctly fter reboot, nd the following commnds provide workround to ensure tht it does. echo "systemctl strt ntpd" >> /etc/rc.d/rc.locl chmod +x /etc/rc.d/rc.locl Strt ntpd. systemctl strt ntpd 7 Strt Control Center. systemctl strt serviced Configuring NTP clients (Hyper-V only) This procedure configures delegtes to synchronize their clocks with the NTP server on the Control Center mster host. Perform this procedure only if the delegtes do not hve internet ccess. Repet this procedure on ech delegte in your Control Center cluster. 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Strt commnd-line session s root s follows: b In the Applince Administrtion menu, select Root Shell. Select Run, nd then press Enter. 31
Zenoss Resource Mnger Instlltion Guide The menu is replced by commnd prompt similr to the following exmple: [root@hostnme ~]# 3 Crete bckup of the NTP configurtion file. cp -p /etc/ntp.conf /etc/ntp.conf.orig 4 Edit the NTP configurtion file s follows: b Open /etc/ntp.conf with text editor. Replce ll lines in the file with the following lines: # Point to the mster time server server MASTER_ADDRESS restrict defult ignore restrict 127.0.0.1 restrict MASTER_ADDRESS msk 255.255.255.255 nomodify notrp noquery driftfile /vr/lib/ntp/drift c Replce both instnces of MASTER_ADDRESS with the IPv4 ddress of the host where the NTP server is running (the Control Center mster host). d Sve the file nd exit the editor. 5 Stop Control Center. systemctl stop serviced 6 Synchronize the clock with the mster server. ntpd -gq 7 Enble nd strt the NTP demon s follows: Enble the ntpd demon. b c systemctl enble ntpd Configure ntpd to strt when the system strts. Currently, n unresolved issue ssocited with NTP prevents ntpd from restrting correctly fter reboot, nd the following commnds provide workround to ensure tht it does. echo "systemctl strt ntpd" >> /etc/rc.d/rc.locl chmod +x /etc/rc.d/rc.locl Strt ntpd. systemctl strt ntpd 8 Strt Control Center. systemctl strt serviced Adding hosts to the defult resource pool This procedure dds one or more hosts to the defult resource pool. 32
Configuring multi-host cluster 1 Gin ccess to the Control Center host, through the console interfce of your hypervisor, or through remote shell utility such s PuTTY. 2 Strt commnd-line session s root s follows: b In the Applince Administrtion menu, select Root Shell. Select Run, nd then press Enter. The menu is replced by commnd prompt similr to the following exmple: [root@hostnme ~]# 3 Add nd register delegte host. Replce Hostnme-Or-IP with the hostnme or IP ddress of the delegte host to dd nd include the register flg to uthenticte the delegte host: serviced host dd Hostnme-Or-IP:4979 defult --register If you enter hostnme, ll hosts in your Control Center cluster must be ble to resolve the nme through n entry in /etc/hosts or through nmeserver on your network. 4 Repet the preceding commnd for ech delegte in your Control Center cluster. 33
Zenoss Resource Mnger Instlltion Guide Configuring ZooKeeper ensemble 4 This chpter describes how to crete ZooKeeper ensemble (cluster) for multi-host Control Center deployment tht includes minimum of three hosts. If your deployment includes just one host or two hosts, skip this chpter. ZooKeeper nd Control Center Control Center relies on Apche ZooKeeper to distribute nd mnge ppliction services. ZooKeeper mintins the definitions of ech service nd the list of services ssigned to ech host. The scheduler, which runs on the mster host, determines ssignments nd sends them to the ZooKeeper node tht is serving s the ensemble leder. The leder replictes the ssignments to the other ensemble nodes, so tht the other nodes cn ssume the role of leder if the leder node fils. All of the hosts in Control Center cluster retrieve ssignments nd service definitions from the ZooKeeper ensemble leder nd then strt services in Docker continers s required. So, the Control Center configurtion files of ll Control Center cluster hosts must include definition for the SERVICED_ZK vrible, which specifies the ZooKeeper endpoints of the ensemble nodes. Additionl vribles re required on ensemble nodes. A ZooKeeper ensemble requires minimum of three nodes, which is sufficient for most environments. An odd number of nodes is recommended nd n even number of nodes is strongly discourged. A five-node ensemble improves filover protection during mintennce windows but lrger ensembles yield no benefits. The Control Center mster host is lwys n ensemble node. All ensemble nodes should be on the sme subnet. Understnding the configurtion process The procedures in this chpter instruct you to crete temporry vribles tht re used s building blocks, to construct Control Center configurtion vribles ccurtely. You ppend the Control Center vribles to /etc/ defult/serviced, nd then edit the file to move the vribles to more pproprite loctions. The most importnt temporry vribles specify the IP ddress or hostnme of ech host in the ZooKeeper ensemble. The following tble identifies these importnt vribles, the nmes nd vlues of which must be identicl on every Control Center cluster host. Vrible nme Plceholder vlue Actul vlue node1 Mster The IP ddress or hostnme of the mster host. node2 Delegte-A The IP ddress or hostnme of delegte host A. 34
Configuring ZooKeeper ensemble Vrible nme Plceholder vlue Actul vlue node3 Delegte-B The IP ddress or hostnme of delegte host B. Note All ensemble hosts should be on the sme subnet. ZooKeeper vribles The vribles in the following tble re set only on ZooKeeper ensemble nodes, except SERVICED_ZK, which must be identicl on ll Control Center cluster hosts. Vrible SERVICED_ISVCS_START SERVICED_ISVCS_ZOOKEEPER_ID SERVICED_ISVCS_ZOOKEEPER_QUORUM SERVICED_ZK SERVICED_ZK_SESSION_TIMEOUT Where to set ZooKeeper ensemble nodes ZooKeeper ensemble nodes ZooKeeper ensemble nodes All Control Center cluster hosts ZooKeeper ensemble nodes Exmple multi-host ZooKeeper configurtion This exmple shows the ZooKeeper vribles in the /etc/defult/serviced configurtion file of ech host in 4-node Control Center cluster. For convenience, the relevnt settings for ech node or host re lso included in subsequent procedures. Note The vlue of the SERVICED_ISVCS_ZOOKEEPER_QUORUM vrible is formtted to fit the vilble spce. In the configurtion file, the vrible nd vlue re on the sme line. Mster host nd 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 Delegte host nd 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 Delegte host nd 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 Mnger Instlltion Guide SERVICED_ZK_SESSION_TIMEOUT=15 Delegte host, 198.51.100.138: SERVICED_ZK=198.51.100.135:2181,198.51.100.136:2181,198.51.100.137:2181 Configuring the mster host s ZooKeeper node This procedure configures the Control Center mster host s node in ZooKeeper ensemble. 1 Log in to the mster host s root, or s user with superuser privileges. 2 Define the IP ddress vribles for ech node in the ZooKeeper ensemble. Replce Mster with the IP ddress or hostnme of the Control Center mster host, nd replce Delegte-A nd Delegte-B with the IP ddresses or hostnmes of the delegte hosts to include in the ensemble: node1=mster node2=delegte-a node3=delegte-b 3 Set the ZooKeeper node ID to 1. echo "SERVICED_ISVCS_ZOOKEEPER_ID=1" >> /etc/defult/serviced 4 Specify the nodes in the ZooKeeper ensemble. You cn copy the following text nd pste it in your console: echo "SERVICED_ZK=${node1}:2181,${node2}:2181,${node3}:2181" \ >> /etc/defult/serviced 5 Specify the nodes in the ZooKeeper quorum. ZooKeeper requires unique quorum definition for ech node in its ensemble. To chieve this, replce the IP ddress or hostnme of the mster host with 0.0.0.0. You cn copy the following text nd pste 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/defult/serviced 6 Specify the timeout for inctive connections. You cn copy the following text nd pste it in your console: echo "SERVICED_ZK_SESSION_TIMEOUT=15" >> /etc/defult/serviced 7 Verify the ZooKeeper environment vribles. grep -E '^\b*serviced' /etc/defult/serviced grep -E '_Z(OO K)' The following exmple shows the environment vribles for mster host with IP ddress 198.51.100.135. 36
Configuring ZooKeeper ensemble Note The vlue of the SERVICED_ISVCS_ZOOKEEPER_QUORUM vrible is formtted to fit the vilble spce. The result of the grep commnd shows the vrible nd vlue on the sme 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 delegte host A s ZooKeeper node Use this procedure to configure the delegte host designted s Delegte-A s ZooKeeper node. 1 Log in to the delegte host s root, or s user with superuser privileges. 2 Define the IP ddress vribles for ech node in the ZooKeeper ensemble. Replce Mster with the IP ddress or hostnme of the Control Center mster host, nd replce Delegte-A nd Delegte-B with the IP ddresses or hostnmes of the delegte hosts to include in the ensemble: node1=mster node2=delegte-a node3=delegte-b 3 Set the ID of this node in the ZooKeeper ensemble. echo "SERVICED_ISVCS_ZOOKEEPER_ID=2" >> /etc/defult/serviced 4 Remove the existing definition of the SERVICED_ZK vrible, which specifies only the Control Center mster host. sed -i.bk '/SERVICED_ZK=/d' /etc/defult/serviced 5 Specify the nodes in the ZooKeeper ensemble. You cn copy the following text nd pste it in your console: echo "SERVICED_ZK=${node1}:2181,${node2}:2181,${node3}:2181" \ >> /etc/defult/serviced 6 Specify the nodes in the ZooKeeper quorum. ZooKeeper requires unique quorum definition for ech node in its ensemble. To chieve this, replce the IP ddress or hostnme of delegte host A with 0.0.0.0. You cn copy the following text nd pste 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/defult/serviced 7 Specify the timeout for inctive connections. You cn copy the following text nd pste it in your console: echo "SERVICED_ZK_SESSION_TIMEOUT=15" >> /etc/defult/serviced 8 Configure Control Center to strt the ZooKeeper service. 37
Zenoss Resource Mnger Instlltion Guide You cn copy the following text nd pste it in your console: echo "SERVICED_ISVCS_START=zookeeper" >> /etc/defult/serviced 9 Verify the ZooKeeper environment vribles. grep -E '^\b*serviced' /etc/defult/serviced \ grep -E '(CS_ZO _ZK CS_ST)' The following exmple shows the environment vribles for delegte host with IP ddress 198.51.100.136. Note The vlue of the SERVICED_ISVCS_ZOOKEEPER_QUORUM vrible is formtted to fit the vilble spce. The result of the grep commnd shows the vrible nd vlue on the sme 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 delegte host B s ZooKeeper node Use this procedure to configure the delegte host designted s Delegte-B s ZooKeeper node. 1 Log in to the delegte host s root, or s user with superuser privileges. 2 Define the IP ddress vribles for ech node in the ZooKeeper ensemble. Replce Mster with the IP ddress or hostnme of the Control Center mster host, nd replce Delegte-A nd Delegte-B with the IP ddresses or hostnmes of the delegte hosts to include in the ensemble: node1=mster node2=delegte-a node3=delegte-b 3 Set the ID of this node in the ZooKeeper ensemble. echo "SERVICED_ISVCS_ZOOKEEPER_ID=3" >> /etc/defult/serviced 4 Remove the existing definition of the SERVICED_ZK vrible, which specifies only the Control Center mster host. sed -i.bk '/SERVICED_ZK=/d' /etc/defult/serviced 5 Specify the nodes in the ZooKeeper ensemble. You cn copy the following text nd pste it in your console: echo "SERVICED_ZK=${node1}:2181,${node2}:2181,${node3}:2181" \ >> /etc/defult/serviced 6 Specify the nodes in the ZooKeeper quorum. ZooKeeper requires unique quorum definition for ech node in its ensemble. To chieve this, replce the IP ddress or hostnme of delegte host B with 0.0.0.0. You cn copy the following text nd pste it in your console: q1="1@${node1}:2888:3888" 38