Zenoss Core Instlltion Guide Relese 6.1.0 Zenoss, Inc. www.zenoss.com
Zenoss Core Instlltion Guide Copyright 2018 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: 1651.18.009 Zenoss, Inc. 11305 Four Points Drive Bldg 1 - Suite 300 Austin, Texs 78726 2
Contents About this guide...5 Tested operting environments...5 Zenoss Core publictions...6 Chnge history... 6 Prt I: Applince deployments... 9 Chpter 1: Instlling mster host... 10 Creting virtul mchine... 10 Configuring the Control Center mster host... 15 Editing connection to configure sttic IPv4 ddressing...15 Setting the system hostnme... 17 Adding the mster host to resource pool... 18 Deploying Zenoss Core... 19 Chpter 2: Instlling delegte hosts... 21 Creting virtul mchine... 21 Configuring the virtul mchine...25 Editing connection to configure sttic IPv4 ddressing...26 Setting the system hostnme... 28 Editing the /etc/hosts file...29 Chpter 3: Configuring multi-host deployment... 31 Delegte host uthentiction...31 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: Adding Zenoss Core to stndrd deployment... 43 Downloding templte nd imge files...43 Instlling the Zenoss Core templte...43 Importing Zenoss Core imges...44 Deploying Zenoss Core... 44 3
4 Appendix A: Enbling NTP on Microsoft Hyper-V guests...46 Configuring NTP for public time servers... 46 Configuring n NTP mster server... 47 Configuring NTP clients...48
About this guide About this guide Zenoss Core Instlltion Guide provides detiled procedures for instlling Zenoss Core. This guide supports the following, mutully-exclusive instlltion pths: Prt I: Applince deployments: Instll Control Center nd Zenoss Core virtul pplince s guest systems on VMWre vsphere or Microsoft Hyper-V hypervisors. For more informtion bout using this prt, refer to the Zenoss Core Plnning Guide. Prt II: Non-pplince deployments: Add Zenoss Core to n existing Control Center deployment. For more informtion bout creting Control Center deployments, refer to the Control Center Plnning Guide. For the ltest informtion bout this relese of Zenoss Core, refer to the Zenoss Core Relese Notes. Tested operting environments Zenoss Core, Control Center, nd operting systems The following tble identifies the tested combintions of Zenoss Core, Control Center, nd operting system releses. Zenoss Core relese Control Center Minimum relese Host OS 6.0.1, 6.1.0 ** 1.5.0 RHEL/CentOS 7.2, 7.3, or 7.4 (64-bit) 5.3.0, 5.3.1, 5.3.2, 5.3.3 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 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) Supported clients nd browsers The following tble identifies the supported combintions of client operting systems nd web browsers. ** Version 6.0.0 - controlled vilbility. * Version 5.2.5 - withdrwn. 5
Zenoss Core Instlltion Guide Client OS Windows 7, 10 mcos 10.12.3, 10.13 Ubuntu 14.04 LTS Supported browsers Internet Explorer 11 * Firefox 56 nd lter Chrome 61 nd lter Firefox 56 nd lter Chrome 61 nd lter Firefox 56 nd lter Chrome 61 nd lter Zenoss Core publictions Title Zenoss Core Administrtion Guide Zenoss Core Configurtion Guide Zenoss Core Instlltion Guide Zenoss Core Plnning Guide Zenoss Core Relese Notes Zenoss Core Upgrde Guide Description Provides n overview of Zenoss Core rchitecture nd fetures, s well s procedures nd exmples to help use the system. Provides required nd optionl configurtion procedures for Zenoss Core, to prepre your deployment for monitoring in your environment. Provides detiled informtion nd procedures for creting deployments of Control Center nd Zenoss Core. Provides both generl nd specific informtion for prepring to deploy Zenoss Core. Describes known issues, fixed issues, nd ltebreking informtion not lredy provided in the published documenttion set. Provides detiled informtion nd procedures for upgrding deployments of Zenoss Core. Additionl informtion nd comments 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 Core Instlltion Guide) nd prt number (1651.18.009). 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 Core Relese Notes. * Enterprise mode only; comptibility mode is not tested. 6
About this guide 1651.18.009 (6.1.0) Replce Lepfile.net with delivery.zenoss.com. Updte relese numbers. 1651.17.311.1 (6.0.0) Restructure pplince instlltion procedures. Updte non-pplince procedures for offline instlltion requirements. Updte relese numbers. 1051.17.268 (5.3.2) Updte relese numbers. 1051.17.242 (5.3.1) Updte relese numbers. 1051.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. 1051.17.191 Updte relese numbers. About 5.2.5 Version 5.2.5 ws withdrwn. 1051.17.123 (5.2.4) Updte relese numbers. 1051.17.100 (5.2.3) Add chpter for high-vilbility instlltions. New procedures for instlling the pplince with Hyper-V. Updte relese numbers. 1051.17.58 (5.2.2) Remove procedure for dding storge for bckups (no longer required for pplinces). 1051.17.044 (5.2.1) Updte relese numbers. 1051.16.335 (5.2.0) Add section detiling the tested operting environments. Remove procedures for instlling Control Center. Tht informtion is now in the Control Center Instlltion Guide. 1051.16.316 Updte relese numbers. 1051.16.291 Updte relese numbers. 1051.16.277 Updte relese numbers. 1051.16.264 Updte relese numbers. 1051.16.257 Updte relese numbers. 7
Zenoss Core Instlltion Guide 1051.16.207 Updte relese numbers. 1051.16.176 Updte relese numbers. 1051.16.153 Updte relese numbers. 1051.16.146 Updte relese numbers. 1051.16.125 Refine the procedure for creting the ppliction dt thin pool. 1051.16.118 Add Zenoss Core 5.1.2. Add substep to crete the docker override directory. 1051.16.111 Add this document chnge history. Add chpters describing how to instll the Zenoss Core 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 Control Center hosts. Add step to instll the Nmp Nct pckge, which is used to check ZooKeeper ensemble sttus. 1051.16.060 Plnning informtion is now in the Zenoss Core Plnning Guide. Informtion bout how to strt nd configure Zenoss Core is now in the Zenoss Core Configurtion Guide. 8
Applince deployments Prt I: Applince deployments The chpters in this prt describe how to instll the Zenoss Core 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. 9
Zenoss Core Instlltion Guide Instlling mster host 1 This chpter describes how to instll Zenoss Core pplince pckge s Control Center mster host. All Zenoss Core deployments require Control Center mster host. Creting virtul mchine You cn crete virtul mchine for the Zenoss Core 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 An ccount on the Zenoss Community site. This procedure instlls Zenoss Core 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. 1 In web browser, nvigte to the downlod site, nd then log in. The downlod site is Zenoss Community. 2 Downlod the Zenoss Core mster host OVA file. zenoss-core-6.1.0-1-mster.vmwre.ov 3 Use the VMwre vsphere Client to log in to vcenter s root, or s user with superuser privileges, nd then disply the Home view. 10
Instlling mster host 4 Choose VMs nd Templtes. 5 In the top nvigtion br, choose Actions > Deploy OVF Templte. Figure 1: Deploy OVF Templte 6 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. 11
Zenoss Core Instlltion Guide 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. 7 Nvigte to the new virtul mchine's Getting Strted tb, nd then click Edit virtul mchine settings. 8 Edit the Virtul Hrdwre settings of the virtul mchine. Chnge the settings. For multi-host deployments: Reduce the number of CPUs from 8 to 4. Reduce the mount of memory from 32 to 16. For single-host deployments, reduce the mount of memory from 32 to 24. b Click OK. 9 On the new virtul mchine's Getting Strted tb, click Power on virtul mchine. 10 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: Microsoft Remote Desktop Connection Administrtor privileges on Microsoft Hyper-V server An ccount on the Zenoss Community site. Use this procedure to instll the Zenoss Core mster host pplince s virtul mchine mnged by Microsoft Hyper-V. 1 Use Microsoft Remote Desktop Connection to log in to Hyper-V host s Administrtor, or s user with Administrtor privileges. 2 In web browser, nvigte to the downlod site, nd then log in. The downlod site is Zenoss Community. 3 Downlod the Zenoss Core mster host ISO file. zenoss-core-6.1.0-1-mster.x86_64.iso 4 Open Hyper-V Mnger. 5 In the left nvigtion pne, choose server to host the virtul mchine. 6 From the Action menu, choose New > Virtul Mchine... The New Virtul Mchine Wizrd opens. 7 In the New Virtul Mchine Wizrd dilog, disply the Specify Nme nd Loction pnel. If the first pnel displyed is the Before You Begin pnel, click Next. 8 In the Specify Nme nd Loction pnel, provide nme for the virtul mchine, nd then click Next. 9 In the Specify Genertion pnel, choose Genertion 1, nd then click Next. 10 In the Assign Memory pnel, specify the memory for the virtul mchine. In the Strtup memory field, enter the mount of memory for the host. b For multi-host deployments, enter 16384 (16GB). For single-host deployments, enter 24576 (24GB). Optionl: Check Use Dynmic Memory for this virtul mchine, if desired. 12
Instlling mster host Zenoss Core is tested with dynmic memory enbled. c Click Next. 11 In the Configure Networking pnel, choose virtul switch, nd then click Next. 12 In the Connect Virtul Hrd Disk pnel, specify new disk on which to instll the guest operting system. Choose Crete virtul hrd disk. b Specify nme. c In the Size field, enter 30. d Click Next. 13 In the Instlltion Options pnel, specify the mster host ISO file. Choose Instll n operting system from bootble CD/DVD-ROM. b Choose Imge file (.iso). c Specify or browse to the loction of the mster host ISO file. d Click Next. 14 In the Completing the New Virtul Mchine Wizrd pnel, verify the description, nd then click Finish. Hyper-V Mnger cretes the new virtul mchine, nd then closes the wizrd. Configuring nd strting Hyper-V mster host To perform this tsk, you need: A Microsoft Remote Desktop Connection Administrtor privileges on Microsoft Hyper-V server The mster host creted in the previous procedure (Creting virtul mchine with Hyper-V on pge 12) The Zenoss Core mster host virtul mchine requires totl of 7 virtul hrd disks. The following tble identifies the purpose nd size of ech disk. Tble 1: Mster host disks Purpose Size 1 Root (/) 30GB 2 Swp 16GB 3 Temporry (/tmp) 16GB 4 Docker dt 50GB 5 Control Center internl services dt 50GB 6 Appliction dt 200GB 7 Appliction dt bckups 150GB Disk 1 ws creted when the virtul mchine ws creted, in the previous procedure. Use this procedure to configure hrdwre resources, crete disks 2-6, nd strt the mster host. 1 Use Microsoft Remote Desktop Connection to log in to Hyper-V host s Administrtor, or s user with Administrtor privileges. 2 Open Hyper-V Mnger. 3 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Settings. The Settings dilog displys. 4 In the Hrdwre re, locte the virtul hrd disk creted previously, nd then determine whether it is ttched to n IDE controller. 13
Zenoss Core Instlltion Guide Hyper-V guest mchines cn only boot from n IDE drive. 5 In the Hrdwre re, choose Processor, nd then chnge the number of processors ssigned to the mchine. In Number of virtul processors, enter the vlue for your deployment. For single-host deployments, enter 8. For multi-host deployments, enter 4. b Click Apply. 6 In the Hrdwre re on the left, choose SCSI Controller, nd then crete dditionl virtul hrd disks. Repet the following substeps to crete new disks in the following sizes: 50GB 150GB 50GB 200GB 16GB 16GB b c d e In the controller re on the right, choose Hrd Drive, nd then click Add. In the Loction field, choose n unused loction number. In the Medi re, 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 disk size from the list t the beginning of this step. c Click Next. 5 Summry/New Virtul Hrd Disk Wizrd: Verify the description, nd then click Finish. At the bottom of the Settings window, click Apply. When ll of the disks re creted, click OK. 7 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Strt. Figure 2: Strting virtul mchine 8 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Connect. 9 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. 14
Instlling mster host 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. 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. 15
Zenoss Core Instlltion Guide 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 4: Exmple: Avilble connections Note Do not use this procedure to modify the docker0 connection. 5 Select the virtul connection, nd then press Enter. 16
Instlling mster host 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. 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 core-mster for the Zenoss Core mster host nd is core-delegte for Zenoss Core 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. 17
Zenoss Core Instlltion Guide 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. 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. 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. 18
Instlling mster host b Crete new pool nmed mster. 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 deployment 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 deployment 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. Deploying Zenoss Core Use this procedure to dd the Zenoss Core ppliction to Control Center nd tg ppliction imges in the locl registry. 1 Log in to the Control Center mster host s user with serviced CLI privileges. 2 Add the Zenoss Core ppliction templte to Control Center. serviced templte dd /opt/serviced/templtes/zenoss*.json On success, the serviced commnd returns the templte ID. 3 Identify the resource pool to which the host belongs. serviced host list 4 Deploy the ppliction. Replce Templte-ID with the identifier Zenoss Core templte Replce Pool with the nme of the resource pool to which the mster host belongs (single-host system) or to which the delegte hosts belong (multi-host system) Replce Deployment-ID with nme for this deployment (for exmple, Test or Production) serviced templte deploy Templte-ID Pool Deployment-ID Control Center tgs Zenoss Core imges in the locl registry. 19
Zenoss Core Instlltion Guide If you re creting single-host deployment, proceed to the Zenoss Core Configurtion Guide. If you re creting multi-host deployment, proceed to the next chpter. 20
Instlling delegte hosts Instlling delegte hosts 2 This chpter describes how to instll Zenoss Core pplince pckge s Control Center delegte host. You cn dd s mny delegte hosts s you need to Control Center deployment. Perform the procedures in Instlling mster host on pge 10 before performing the procedures in this chpter. Creting virtul mchine You cn crete virtul mchine for the Zenoss Core 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 An ccount on the Zenoss Community site. This procedure instlls Zenoss Core 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. 1 In web browser, nvigte to the downlod site, nd then log in. The downlod site is Zenoss Community. 2 Downlod the Zenoss Core delegte host OVA file. zenoss-core-6.1.0-1-delegte.vmwre.ov 3 Use the VMwre vsphere Client to log in to vcenter s root, or s user with superuser privileges, nd then disply the Home view. 21
Zenoss Core Instlltion Guide 4 In the top nvigtion br, choose Actions > Deploy OVF Templte. Figure 7: Deploy OVF Templte 5 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. 22
Instlling delegte hosts 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. 6 Nvigte to the new virtul mchine's Getting Strted tb, nd then click Edit virtul mchine settings. 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: Microsoft Remote Desktop Connection Administrtor privileges on Microsoft Hyper-V server An ccount on the Zenoss Community site. Use this procedure to instll the Zenoss Core delegte host pplince s virtul mchine mnged by Microsoft Hyper-V. 1 Use Microsoft Remote Desktop Connection to log in to Hyper-V host s Administrtor, or s user with Administrtor privileges. 2 In web browser, nvigte to the downlod site, nd then log in. The downlod site is Zenoss Community. 3 Downlod the Zenoss Core delegte host ISO file. zenoss-core-6.1.0-1-delegte.x86_64.iso 4 Open Hyper-V Mnger. 5 In the left nvigtion pne, choose server to host the virtul mchine. 6 From the Action menu, choose New > Virtul Mchine... The New Virtul Mchine Wizrd opens. 7 In the New Virtul Mchine Wizrd dilog, disply the Specify Nme nd Loction pnel. If the first pnel displyed is the Before You Begin pnel, click Next. 8 In the Specify Nme nd Loction pnel, provide nme for the virtul mchine, nd then click Next. 9 In the Specify Genertion pnel, choose Genertion 1, nd then click Next. 10 In the Assign Memory pnel, specify the memory for the virtul mchine. b In the Strtup memory field, enter 32768 (32GB). Optionl: Check Use Dynmic Memory for this virtul mchine, if desired. Zenoss Core is tested with dynmic memory enbled. c Click Next. 11 In the Configure Networking pnel, choose virtul switch, nd then click Next. 12 In the Connect Virtul Hrd Disk pnel, specify new disk on which to instll the guest operting system. Choose Crete virtul hrd disk. b Specify nme. c In the Size field, enter 30. d Click Next. 13 In the Instlltion Options pnel, specify the delegte host ISO file. Choose Instll n operting system from bootble CD/DVD-ROM. b Choose Imge file (.iso). c Specify or browse to the loction of the delegte host ISO file. d Click Next. 14 In the Completing the New Virtul Mchine Wizrd pnel, verify the description, nd then click Finish. 23
Zenoss Core Instlltion Guide Hyper-V Mnger cretes the new virtul mchine, nd then closes the wizrd. Configuring nd strting Hyper-V delegte host To perform this tsk, you need: A Microsoft Remote Desktop Connection Administrtor privileges on Microsoft Hyper-V server The delegte host creted in the previous procedure (Creting virtul mchine with Hyper-V on pge 23) Zenoss Core delegte host virtul mchines requires totl of 4 virtul hrd disks. The following tble identifies the purpose nd size of ech disk. Tble 2: Delegte host disks Purpose Size 1 Root (/) 30GB 2 Swp 16GB 3 Temporry (/tmp) 16GB 4 Docker dt 50GB Disk 1 ws creted when the virtul mchine ws creted, in the previous procedure. Use this procedure to configure hrdwre resources, crete disks 2-4, nd strt the mster host. 1 Use Microsoft Remote Desktop Connection to log in to Hyper-V host s Administrtor, or s user with Administrtor privileges. 2 Open Hyper-V Mnger. 3 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Settings. The Settings dilog displys. 4 In the Hrdwre re, locte the virtul hrd disk creted previously, nd then determine whether it is ttched to n IDE controller. Hyper-V guest mchines cn only boot from n IDE drive. 5 In the Hrdwre re, choose Processor, nd then chnge the number of processors ssigned to the mchine. In Number of virtul processors, enter 8. b Click Apply. 6 In the Hrdwre re on the left, choose SCSI Controller, nd then crete dditionl virtul hrd disks. Repet the following substeps to crete new disks in the following sizes: 50GB 16GB 16GB b c d In the controller re on the right, choose Hrd Drive, nd then click Add. In the Loction field, choose n unused loction number. In the Medi re, 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. 24
Instlling delegte hosts e 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 disk size from the list t the beginning of this step. c Click Next. 5 Summry/New Virtul Hrd Disk Wizrd: Verify the description, nd then click Finish. At the bottom of the Settings window, click Apply. When ll of the disks re creted, click OK. 7 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Strt. Figure 8: Strting virtul mchine 8 In the Hyper-V Mnger Virtul Mchines re, right-click the new virtul mchine, nd then choose Connect. 9 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. 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. 25
Zenoss Core Instlltion Guide 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. 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: 26
Instlling delegte hosts 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 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. 27
Zenoss Core Instlltion Guide 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 core-mster for the Zenoss Core mster host nd is core-delegte for Zenoss Core 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. 28
Instlling delegte hosts 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. 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. Strt the editor. nno /etc/hosts Figure 13: Exmple nno session 29
Zenoss Core Instlltion Guide 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 core-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. 30
Configuring multi-host deployment Configuring multi-host deployment 3 This chpter describes how to configure n pplince-bsed multi-host deployment, which 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. Note If you re creting multi-host deployment on Hyper-V system, you must perform the procedures in Enbling NTP on Microsoft Hyper-V guests on pge 46, in ddition to the procedures in this chpter. Delegte host uthentiction Control Center uses RSA key pirs to crete the uthentiction tokens tht re required for ll delegte communictions. When you dd host to resource pool, the serviced instnce on the mster host cretes privte key for the delegte nd bundles it with its own public key. The serviced instnce on the delegte host uses the bundle to sign messges with its unique tokens. Key bundles re instlled by using n SSH connection or file. The commnd to dd host to pool cn initite n SSH connection with the delegte nd instll the key bundle. This option is the most secure, becuse no file is creted. However, it requires either public key uthentiction or pssword uthentiction between the mster nd delegte hosts. When no SSH connection is requested, the commnd to dd host to pool cretes file contining the key bundle. You cn move the key bundle file to the delegte host with ny file trnsfer method, nd then instll it on the delegte. The following procedures demonstrte how to dd host to resource pool nd instll its key bundle. Adding delegte host through n SSH connection To succeed, the following sttements bout the login ccount used to perform this procedure must be true: The ccount exists on both the mster host nd on the delegte host. The ccount hs serviced CLI privileges. The ccount hs either public key uthentiction or pssword uthentiction enbled on the mster host nd on the delegte host. Use this procedure to dd delegte host to resource pool through n SSH connection. Repet this procedure on ech delegte in your Zenoss Core deployment. 31
Zenoss Core Instlltion Guide 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. 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 delegte host to resource pool. If the mster nd delegte host re configured for key-bsed ccess, the following commnd does not prompt you to dd the delegte to the list of known hosts or to provide the pssword of the remote user ccount. Use the hostnme or IP ddress to identify Control Center host. If you use hostnme, ll Control Center hosts must be ble to resolve it, either through n entry in /etc/hosts or through nmeserver on the network. In the following exmple, replce Hostnme-Or-IP with the hostnme or IP ddress of delegte host, nd replce Resource-Pool with the nme of resource pool. If the host is behind router or firewll for network ddress trnsltion (NAT), include the option --ntddress to specify the NAT device's hostnme or IP ddress nd port of the delegte host. serviced host dd --register Hostnme-Or-IP:4979 Resource-Pool \ --nt-ddress==nat-hostnme-or-ip:nat-port Adding delegte host using file Use this procedure to dd delegte host to resource pool by using key bundle file. Repet this procedure on ech delegte in your Zenoss Core deployment. 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. 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 delegte host to resource pool. Use the hostnme or IP ddress to identify Control Center host. If you use hostnme, ll Control Center hosts must be ble to resolve it, either through n entry in /etc/hosts or through nmeserver on the network. In the following exmple, replce Hostnme-Or-IP with the hostnme or IP ddress of delegte host, nd replce Resource-Pool with the nme of resource pool. If the host is behind router or firewll for network ddress trnsltion (NAT), include the option --ntddress to specify the NAT device's hostnme or IP ddress nd port of the delegte host. serviced host dd Hostnme-Or-IP:4979 Resource-Pool \ --nt-ddress==nat-hostnme-or-ip:nat-port The commnd cretes unique key bundle file in the locl directory. 4 Use file trnsfer utility such s scp to copy the key bundle file to the delegte host. Once copied to the delegte host, the key bundle file is not needed on the mster host nd cn be deleted. 32
Configuring multi-host deployment 5 Log in to the Control Center delegte host s user with serviced CLI privileges. 6 Instll the key bundle. Replce Key-Bundle-Pth with the pthnme of the key bundle file: serviced host register Key-Bundle-Pth 7 Delete the key bundle file. The file is no longer needed on the delegte host. Replce Key-Bundle-Pth with the pthnme of the key bundle file: rm Key-Bundle-Pth 33
Zenoss Core 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 Control Center hosts 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 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 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 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 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 deployment. 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,\ 35
Zenoss Core Instlltion Guide 2@198.51.100.136:2888:3888,3@0.0.0.0:2888:3888 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 Core 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 tht is 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