HP OSMS Blueprint: HP Manageability Value-Add Software for Open Source Middleware Stacks HP Part Number: 5992-4100 Published: February 2008 Edition: 1.
© Copyright 2008 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents Introduction............................................................................................................................................9 Executive Summary...........................................................................................................................9 Intended Audience............................................................................................................................9 Scope and Purpose......................................
List of Figures 1 2 3 4 5 6 7 8 9 OVOW Architecture......................................................................................................................11 HP OVO - Launch Tool.................................................................................................................13 HP OVO - Select Tool ...................................................................................................................13 HP OVO - SPI Deployment.........................................
List of Tables 1 2 3 Required Patches...........................................................................................................................12 Application Labels and Descriptions............................................................................................14 JBoss SPI Policies...........................................................................................................................
Introduction Executive Summary The HP Open Source Integrated Portfolio (HP OSIP) comprises a range of products and services designed to verify that customers can successfully realize the cost and feature benefits of adopting open source software in their IT environments. HP Open Source foundation components include the base components of an open source-based ecosystem. HP servers and storage are validated to run the Linux operating system together with the supported commercial Linux distribution.
Typographic Conventions This document uses the following typographical conventions. Command ComputerOut Ctrl-x ENVIRONVAR [ERRORNAME] Key Term UserInput VARIABLE \ (continuation character) ... | A command name or qualified command phrase. Text displayed by the computer. A key sequence. A sequence such as Ctrl-x indicates that you must hold down the key labeled Ctrl while you press another key or button. The name of an environment variable, for example, PATH.
Using HP OpenView Operations and Gallery Smart Plug Ins HP enhances the Open Source and Middleware Stacks (OSMS) by using HP OpenView Operations (OVO) Gallery Smart Plug-Ins (SPIs). HP OVO is a distributed, client/server software solution designed to provide service-driven event and performance management of business-critical enterprise systems, applications, and services.
Table 1 Required Patches Patch Description Version Patch Name Dependencies Msg/Act Agt A.07.31 OVOW_00187 SvnDisc Linux A.07.31 OVOW_00198 OVOW_00187 Agent Linux A.07.33 OVOW_00234 OVOW_00191 — For information about installing the HP OVOW, see the HP OpenView Operations for Windows Installation Guide located at: http://support.openview.hp.
Figure 2 HP OVO - Launch Tool 3. Select an instrumentation tool from the Select the Tool to Execute window as shown in Figure 3. Figure 3 HP OVO - Select Tool 4. Next, right-click on an SPI under the folder Policy groups, for example select SPI for Application Servers, and select All Tasks > Deploy on... as shown in Figure 4. This step will deploy the corresponding SPI to the managed node.
Figure 4 HP OVO - SPI Deployment Using the SPIs The HP OVOW SPIs support two methodologies to manage the JBoss Application Server, MySQL, Symass OpenLDAP and Tomcat: • • User-driven methods Event-driven methods User-Driven Methods The user-driven functions are accessed from the Tools menu. You can start, stop, and monitor the JBoss Application Server, MySQL, Symass OpenLDAP, and Tomcat from the OVOW console.
Event-Driven Methods The event-driven methods are used to manage events that are triggered when certain conditions are met, for example, if the JBoss Application Server process uses a greater percentage of CPU bandwidth than the threshold defined in the policy. When a threshold is exceeded, warning messages appear in the management console. Table 3 lists the JBoss SPI policy details.
MySQL High Availability Using HP Serviceguard Overview HP Serviceguard HP Serviceguard is a specialized software for protecting mission-critical applications from a wide variety of hardware and software failures. A high availability computer system allows application services to continue even in the event of a hardware or software failure. High availability systems protect users from software failures and from the failure of a system processing unit (SPU), disk, or local area network (LAN) component.
When the package fails over from one node to another, the following actions occur: • On the primary node: — The package is halted on the node where it is currently running. As a result, all package resources are halted. — The relocatable IP address is removed from this node. — The file systems are unmounted and all volume groups assigned to this package are deactivated. — The systems are going to halt when the storage or networks fail.
MySQL Configuration You have installed the MySQL database and configured it on the shared storage. For more information, see the file /usr/local/cmcluster/mysqltoolkit/README. Installing and Configuring the MySQL Toolkit On all target nodes you have installed the Serviceguard MySQL toolkit and configured the MySQL Serviceguard Cluster package with the following values: MySQL Cluster: PACKAGE Name MySQL_PKG Relocatable IP address 10.101.0.
The following test uses an x86_64 system running a fully installed version of the RHEL5 distribution. The RHEL5 distribution contains embedded mysql-bench test suite. To enable and use the mysql-bench test suite to verify the stability of the MySQL Serviceguard cluster, use the following steps: 1. Verify that the mysql-bench test suite is installed, by entering the following command: # rpm -qa | grep mysql-bench If the test suite is installed, the following message is shown: mysql-bench-5.0.22-2.
Testing Cluster Failover You can simulate some of the following cases, which cause primary-node failure, to verify the MySQL Serviceguard cluster failover function. CAUTION: You should perform the following tests with sample data before trying the tests with critical production data. In the event of a serious failure or the wrong configuration, data corruption can result. • • • • • End the primary node's MySQL processes. Pull the power cable out on the primary node to cause a power failure.
Figure 6 MySQL Replication Configuration This replication scheme can offer one key advantage, which is that backing up the database is easier and safer. A slave server can be taken off line and all of its data can be backed up without impacting the overall operation of the live database. During backup, the master server and other slave servers continue responding to queries uninterrupted.
5. Import the MySQL slave server as a client of the Data Protector Cell Manager as shown in Figure 7. Figure 7 Importing a Client Backing Up Data There are two parts to backing up your data: first, the extraction of data from the database and, second, the integration of the database back up tool into the process. To Extract Data from the Database 1. To stop the slave replication, enter the following command: mysql> STOP SLAVE SQL_THREAD; 2.
NOTE: To identify the type of storage engine used for a particular table, use the following command: mysql> show table status from osmdb like 'customer'; 4. Restart the slave replication thread after the database has been dumped by entering the following command: mysql> START SLAVE SQL_THREAD; To Integrate Data Protector 1. 2. Add the secondary storage, which is used to hold the backup data, as a device in Data Protector.
Restoring Data Restore the data file and binary log files to both the master server and slave server. All database data is recreated using the extracted data file and the binary log files. 1. Stop the replication between master server and slave servers. For more instructions, see the MySQL 5.0 Reference Manual, located at: http://dev.mysql.com/doc/refman/5.0/en/index.html 2. Restore the latest database data file and binary log files to both master server and slave server using Data Protector.
