VMware Agent PostgreSQL Configuration Steps With CMIS 11.2

Transcription

1 The IT Performance Management & Capacity Planning Company VMware Agent PostgreSQL Configuration Steps With CMIS 11.2 Author: Walter Verhoeven Doc. Ref.: vmware_pgsql_config_tq11.2_v1.0.doc Version: 1.0 Date: 25 July 2014

2 TeamQuest Tips & Tricks Page 2 of 19 I. Document History Version Date Name Description /03/2014 W. Verhoeven Intermediate copy for discussion. II. Stakeholders Company CREATIVE Associates Responsible Stakeholder Walter Verhoeven CREATIVE Associates Donderveldstraat Lot/Beersel Belgium

3 TeamQuest Tips & Tricks Page 3 of 19 III. Contents Table of Contents 1.MANAGEMENT SUMMARY Introduction TEST INFRASTRUCTURE DESCRIPTION STEP1: CREATE THE POSTGRESQL EDB STEP2: CONFIGURE THE ADMINISTRATION CONSOLE STEP3: APPLY PERFORMANCE DATA POLICY STEP4: ACTIVATE THE VMWARE INFRASTRUCTURE AGENT...16

4 TeamQuest Tips & Tricks Page 4 of Management Summary 1.1 Introduction This document describes the different configuration steps in order to set-up a PostgreSQL TeamQuest Open Enterprise Database that will act as a database for the TQ VMware Infrastructure Agent. The configuration used here is TeamQuest Manager (CMIS) 11.2 PF , PostgreSQL DB version and the console also version 11.2 PF The ITSAR version to check the collected data is 11.2 PF

5 TeamQuest Tips & Tricks Page 5 of Test Infrastructure Description We have a server RHEL 6.0 system rhlvirt5 that runs the VMware Infrastructure agent. It also hosts the PostgreSQL database. We have the Administration Console running on rhlvirtconsole. We assume that the PostgreSQL TeamQuest package and CMIS has been installed correctly on your server and that you have an Administration Console up & running.

6 TeamQuest Tips & Tricks Page 6 of Step1: Create The PostgreSQL EDB First of all check if the local PostgreSQL database cluster is running: [root@rhlvirt5 ~]# ps -ef grep postgres nobody :54? 00:00:00 /opt/teamquest/pgsql/.bin/postgres nobody :54? 00:00:00 postgres: logger process nobody :54? 00:00:00 postgres: checkpointer process nobody :54? 00:00:00 postgres: writer process nobody :54? 00:00:00 postgres: wal writer process nobody :54? 00:00:00 postgres: autovacuum launcher process nobody :54? 00:00:00 postgres: stats collector process nobody :04? 00:00:00 postgres: administrator vmware ::1(42022) idle root :34 pts/1 00:00:00 grep postgres This is the case, if not you can launch it as root via the scripts that TQ has made for you /opt/teamquest/pgsql/bin/service.sh stop/start. If you like to connect to the local PostgreSQL database cluster you should set the following environment variables: PATH=/opt/teamquest/pgsql/bin:$PATH export PATH PGDATA=/opt/teamquest/pgdata/9.2 export PGDATA Then it is possible to check if you can connect and list the current databases: [root@rhlvirt5 ~]# psql -U administrator -d postgres Password for user administrator: psql (9.2.4) Type "help" for help. postgres=# \l List of databases Name Owner Encoding Collate Ctype Access privileges postgres administrator UTF8 C C template0 administrator UTF8 C C =c/administrator + administrator=ctc/administrator template1 administrator UTF8 C C =c/administrator + administrator=ctc/administrator (3 rows) We see that there is a default database called postgres. In order to create the TQ Performance Database we use the command listed below. Remark again that the DB type is now pdb (Performance Database) as it can store both live production & harvested types of data. Also the time zone is not an option any more as this is now defined by the Performance Data Policy deployed via the Administration Console. As command option -f has not been used here, we will be asked to provide information related to the superuser, database owner etc... In our case we will create the Performance Database vmware owned by the user administrator.

7 TeamQuest Tips & Tricks Page 7 of 19 [root@rhlvirt5 wav]# tqdbu -i -t pdb -d vmware -a postgresql TQDBU 11.2 PF (Europe/Brussels) Fri 25 Jul :04:20 CEST Copyright (c) TeamQuest Corporation. All Rights Reserved. rhlvirt5 Linux x86_ el6.x86_64 Red Hat Enterprise Linux Server release 6.4 (Santia Detecting revision 5 database specification file. *Info* The PostgreSQL architecture will be used for the database. Enter the superuser account name [administrator] : Enter the superuser account password : Enter the database owner account name : administrator Enter the database owner account password : Enter the connection string [localhost] : Enter the port number for the connection string [2732] : Enter the database name [vmware] : Creating database 'vmware' in /opt/teamquest/data/vmware Database 'vmware' has been created. Database 'vmware' time zone set to 'Europe/Brussels'. End TQDBU Fri 25 Jul :04:48 CEST When connecting to TQManager we see that the new database is listed. Figure 3-1: New vmware Database Listed Checking the Database Connection screen reveals that with the user administrator we can connect to the database.

8 TeamQuest Tips & Tricks Page 8 of 19 Figure 3-2: Database Connection Screen When checking with psql we have the following: [root@rhlvirt5 ~]# psql -U administrator -d postgres Password for user administrator: psql (9.2.4) Type "help" for help. postgres=# \l List of databases Name Owner Encoding Collate Ctype Access privileges postgres administrator UTF8 C C template0 administrator UTF8 C C =c/administrator + administrator=ctc/administrator template1 administrator UTF8 C C =c/administrator + administrator=ctc/administrator vmware administrator UTF8 C C (4 rows) The database vmware has been created and we can connect to it too. postgres-# \connect vmware You are now connected to database "vmware" as user "administrator". vmware-# \dt List of relations Schema Name Type Owner public agentinterval table administrator public svctqlog table administrator public tq$aggservice table administrator public tq$clobs table administrator public tq$derivedtab table administrator public tq$field_cons_methods table administrator public tq$field_data_subtypes table administrator public tq$field_data_types table administrator public tq$field_relationship_types table administrator public tq$field_types table administrator public tq$licenses table administrator

9 TeamQuest Tips & Tricks Page 9 of 19 public tq$nodes table administrator public tq$properties table administrator public tq$related_fields table administrator public tq$table_defs table administrator public tq$table_fields table administrator public tq$table_retentions table administrator public tq$table_time_types table administrator public tq$table_types table administrator public tq$tables table administrator public tq$time_unit_types table administrator public tq$tokens table administrator public vguestinfo table administrator (23 rows) We can connect and the database has been initialized since we can find some tables. When connecting to TQManager and listing the agents we remark that most of these are in a PENDING state. Figure 3-3: Agent Manager For vmware Verifying the Database Settings reveals that you now need to pass by the Administration Console in order to define the Time Zone. We need to deploy a Performance Data Policy.

10 TeamQuest Tips & Tricks Page 10 of 19 Figure 3-4: Database Settings

11 TeamQuest Tips & Tricks Page 11 of Step2: Configure The Administration Console The system rhlvirt5, with the Performance Database vmware, should be registered with an Administration Console. Figure 4-1: Registering With Administration Console Once this is done and tqsync has been initiated, this server should appear in the managed servers list. Figure 4-2: Run tqsync Remark that the Health reveals PENDING due to the fact that there is not yet a Performance Data Policy applied to our database. Figure 4-3: Registered Nodes

12 TeamQuest Tips & Tricks Page 12 of Step3: Apply Performance Data Policy There are four new Performance Data Policies as of console version 11.2 PF Figure 5-1: Performance Data Policy Types In our case the nodes that we will harvest are all running a TeamQuest proprietary production database type with the standard intervals but with modified retentions. As such we will deploy the Open Architecture Default one. It is a good idea to make a copy of it in order to changes some settings of this policy like Time Zone etc...

13 TeamQuest Tips & Tricks Page 13 of 19 Figure 5-2: Performance Data Policy Then press Save Copy and it will appear as a new policy in your list with the name specified in the Name field a the top. Remark that the granularity of the data collection for VMware is by default set to 5 minutes. If you want to define/change retention periods of the data and others, it is in this policy that you will need to make these changes. Figure 5-3: Policy Table Filtered On Architecture Next step is to assign this policy to our vmware database by simply dragging & dropping it on the node. After tqsync has been running this policy will be applied.

14 TeamQuest Tips & Tricks Page 14 of 19 Figure 5-4: Assigned Performance Data Policy Once applied the agents that where in a PENDING state are now in a RUNNING state. Figure 5-5: Agent Manager For vmware

15 TeamQuest Tips & Tricks Page 15 of 19 This means that the production/live data is now collected into your Performance Database vmware of the type PostgreSQL. As of now you can use this Performance Database also for getting production/live data from other servers but this is not the goal of this document since we like to activate the TQ VMware Infrastructure Agent storing data into this database.

16 TeamQuest Tips & Tricks Page 16 of Step4: Activate The VMware Infrastructure Agent On the server rhlvirt5 we now activate the Vmware Infrastructure Agent. Select the option Collection Agents -> Add Agent. Figure 6-1: Add Agent Menu Then select Add Vmware Infrastructure Instance and select the Collection Type. In our case this will be Individual Host. Figure 6-2: Add Vmware Infrastructure Agent Fill-in the different fields as shown in our example below.

17 TeamQuest Tips & Tricks Page 17 of 19 Figure 6-3: Add Vmware Infrastructure Individual Host Instance In case you will install CMIS on the virtual nodes, pls. put the Use Host License field in an Enabled state. Don't forget to select the Activate Changes reference on the left of the screen. Figure 6-4: Activate Changes The new Vmware agent instance dell1_vmware is now listed in the Agent Manager screen.

18 TeamQuest Tips & Tricks Page 18 of 19 Figure 6-5: Vmware Instance dell1_vmware The log file of this new agent tqvmwarep.txt looks as following in case all is fine. Figure 6-6: Log File Entry As of now the VMware data will be collected every 5 minutes as specified in the Performance Data Policy deployed earlier. When connecting to the service database that has a reference to our Performance Database called vmware we get the following live data. Do not forget to add the license key of this VMware server into the license file on the collection host, in our case rhlvirt5.

19 TeamQuest Tips & Tricks Page 19 of 19 Figure 6-7: Live Vmware Data Example In ITSAR -END-