Using Easy Deployment in Serviceguard and Metrocluster environments on HP-UX 11i v3 Serviceguard Manager B.03.10 Technical white paper Table of contents Executive summary............................................................................................................................... 2 Introduction ......................................................................................................................................... 3 Purpose and intended audience .............................
Executive summary This document describes the Easy Deployment feature that is available with Serviceguard A.11.20 plus PHSS_41628 or later. Easy Deployment provides an intuitive and straightforward configuration solution to users in a clustered environment. It not only enables users to configure a cluster and cluster wide storage with a single command, but also greatly simplifies configuration of packages for popular applications.
Introduction The demand for higher levels of availability in business IT infrastructures is ever-increasing. Minimizing downtime in such environments involving vital applications is painstakingly timeconsuming, and involves considerable complexity in terms of configuration and deployment of robust clustered environments. Following traditional means of deployment requires a large lead time. It also requires user expertise in areas such as storage and network configuration.
• Automates configuration steps related to complex applications and environments like Metrocluster, Oracle RAC, and Oracle E-Business Suite, etc. – Reduces the learning curve to deploy such environments and applications. – Reduces the number of manual steps required to deploy them. • A command line user is freed from manually generating package configuration files, and editing parameters in them.
Purpose and intended audience The purpose of this white paper is to: • Introduce the reader to the Easy Deployment feature in Serviceguard and Serviceguard Manager • Describe Easy Deployment in the context of cluster configuration—cluster Easy Deployment • Describe Easy Deployment in the context of package configuration—package Easy Deployment • Help customers understand prerequisites and usage details for Easy Deployment of a cluster/package using Serviceguard Manager, in order to effortlessly meet their h
Definition of terms 6 Terms Definition CFS Cluster File System allows multi-system shared access to common file system. Complex Workload Package A multi-instance application that uses active resources across multiple nodes in a cluster. These workloads are configured using multiple inter-dependent multinode or failover packages in a cluster. The workloads need to be managed and moved collectively for disaster tolerance.
Cluster Easy Deployment Introduction Cluster Easy Deployment is targeted to simplify and speed up the process of bringing up a new cluster, with a lower level of required expertise. This cluster Easy Deployment feature is supported by both Serviceguard Manager and the Serviceguard command-line interface. In Serviceguard Manager, this feature simplifies cluster configuration with various environments, by providing an interactive wizard, bolstered with ample auto-discovery.
Specific warning messages are displayed to the user, if the above listed conditions are not met. Metrocluster Easy Deployment One of the following products needs to be pre-installed to use the Metrocluster Easy Deployment feature: • HP Metrocluster with Continuous Access for P9000 and XP A.11.00 PHSS_41664 or superseding patch • HP Metrocluster with Continuous Access EVA A.05.01 PHSS_41660 or superseding patch • HP Metrocluster with EMC SRDF A.09.
Figure 2: Choosing cluster nodes Figure 3 (a): Choosing to configure a simple Serviceguard cluster 9
Figure 3 (b): Choosing to configure Continentalclusters (primary or recovery cluster) with site awareness Figure 3 (c): Choosing to configure Continentalclusters (primary or recovery cluster) 10
Figure 3 (d): Choosing to configure a site-aware Metrocluster Figure 3 (e): Choosing to configure a Metrocluster 11
Figure 4: Configuring the network Figure 5: Choosing a cluster lock option 12
Figure 6: Choosing the cluster lock option for a Metrocluster Figure 7: Creating a cluster-wide Device Special File group Figure 8: Configuring system files 13
Figure 9: Enabling CFS/CVM for the cluster Figure 10: Specifying cluster name 14
Figure 11: Cluster configuration summary Figure 12: Operation log showing completion of cluster deployment 15
Cluster Easy Deployment command-line support Easy Deployment of a Serviceguard cluster and easy creation of clustered LVM, VxVM/CVM storage is supported using the cmdeploycl and cmpreparestg commands, respectively.
Package Easy Deployment in a Serviceguard cluster using Serviceguard Manager Introduction Modular package configuration procedures for important applications need intensive manual effort and involve several steps.
Launching package Easy Deployment from Serviceguard Manager Figure 13: Serviceguard Manager Homepage • In the Serviceguard Manager Homepage, as shown in Figure 13 above, click on the [Configuration] drop-down menu. • Click on [Package Easy Deployment] to open a second-level menu for the available deployment options. Note: These options are enabled only if the prerequisites for the corresponding applications, modules and/or toolkits are satisfied.
• Storage required for Oracle CRS and RAC DB should be configured and up on all nodes. The user can choose to use local or shared storage for Oracle CRS and RAC DB binaries. The user must use shared storage for OCR (Oracle Cluster Registry), voting disk, and RAC database. • The Oracle CRS and RAC DB must be up and running on all the nodes in the cluster.
Automatic Package Dependency configuration for Oracle Clusterware storage If there are no disk group (DG-MNP) and mount point (MP-MNP) packages already configured for the storage being used by the Oracle Clusterware files, the packages will be configured automatically. The dependency between the Oracle Clusterware package and the mount point and disk group packages will also be established.
After finding the CFS storage location of the VOTE disk/OCR disk path, the Easy Deployment operation checks whether the required mount point and disk group packages are deployed or not. If these storage packages do not already exist in the cluster, the Easy Deployment operation automatically deploys these packages. Subsequently, a dependency on the required mount point packages is configured in the Oracle Clusterware package.
Figure 16: Serviceguard Manager, Oracle RAC database package prepare screen The user is expected to input the Oracle Home path and the Oracle RAC database name and click the [Prepare] button on the screen to trigger the generation of required package configuration files for the Oracle RAC database package deployment. The generated package configuration files for the Oracle RAC database package deployment will be displayed in separate panes for the user’s review. The user can edit these configuration files.
Parameter discovery and default parameters By way of automatic package parameter discovery by the Easy Deployment operation, the following Oracle RAC database package attributes are automatically populated in the corresponding configuration file: • Cluster nodes • Oracle User • OC-MNP package name • OC-MNP toolkit directory The Oracle RAC database package name parameter is initialized in the following manner: • In a non-Metrocluster environment, this is set to rac__pkg.
Overview of SGeRAC toolkit package Easy Deployment in a site-aware Metrocluster environment In a site-aware Metrocluster environment, Oracle Clusterware and Oracle RAC database package names will be appended with site IDs. In a non site-aware environment, before deploying an Oracle Clusterware/RAC DB package, the package Easy Deployment operation checks if any Oracle Clusterware/RAC DB package(s) already exist in the cluster.
Once the user chooses to deploy an Oracle Single Instance DB package from the Serviceguard Manager Homepage, the user is presented with a simple form as shown in Figure 17.
All other attributes will either remain commented or will be initialized to default values.
• Oracle EBS—only versions supported by the abovementioned SGeEBS toolkit version The EBS applications tier must be configured and running on the node from which the user is invoking the package Easy Deployment Operation. SGeEBS applications tier toolkit package deployment To deploy a SGeEBS applications tier toolkit package, click on [Configuration] -> [Package Easy Deployment] -> [SGeEBS Applications Package] menu toolbar of the Serviceguard Manager homepage.
Parameter discovery and default parameters By way of automatic package parameter discovery by the SGeEBS Easy Deployment operation, the following package attributes are automatically populated in the SGeEBS Applications Tier Toolkit package configuration file: • Package name • Toolkit directory name • Service names • Web entry IP • Volume group, LVM, mount point, and file system If a separate storage has been used for EBS instance-specific and application tier stack file system, then the storage information
Software prerequisites The following product(s) need to be pre-installed and the listed conditions must be met to use the Easy Deployment feature to deploy a Site Controller package: • Products to be pre-installed: – Serviceguard A.11.20 plus PHSS_41628 or superseding patch – Metrocluster XPCA A.11.00 PHSS_41664 or superseding patch – Metrocluster SRDF A.09.01 PHSS_41662 or superseding patch – Metrocluster CAEVA A.05.
Figure 19: Serviceguard Manager, Site Controller package prepare screen The user is expected to input the Site Controller package name and select the packages that will make up the complex workload on both sites. Subsequently, clicking the [Prepare] button on the screen triggers the generation of required package configuration files for the Site Controller package deployment. The generated package configuration files for the Site Controller package deployment will be displayed for the user’s review.
The following workflow diagram in Figure 20 illustrates the details of the Site Controller Easy Deployment process: Figure 20: Workflow diagram for Site Controller Easy Deployment Parameter discovery and default parameters By way of automatic package parameter discovery by the Site Controller Easy Deployment script, most of the package attributes are automatically populated in the Site Controller and managed packages’ configuration files. The rest are set to recommended default values.
How is it generated? Parameter What it means Value managed_packages Indicates the name of packages that are managed by Site Controller Any package name that is already configured User input in the cluster Appropriate Metrocluster module parameters Indicates the Metrocluster This module will be dependent on the type of module that will be included in replication pair used by the complex the Site Controller package workload packages: configuration If it is XP DEVICE GROUP, then dts/mcxpca will be incl
Prerequisites and restrictions in a Metrocluster SRDF environment • Prerequisites: – The replication pair must have been created already. – The supported version of SYMCLI should have been installed. • Restriction: – If the physical disks are configured with enclosure-based naming, then Easy Deployment of Metrocluster SRDF will not be supported. Prerequisites and restrictions in a Metrocluster XPCA environment • Prerequisite: – The device group pair must have been already created.
Call to action HP recommends modular style packages for new application deployment in Serviceguard clusters. HP also urges you to convert all existing legacy packages to modular style packages in your Serviceguard clusters. Only with modular style packages can you take advantage of the new Serviceguard features explained in this white paper and many other advanced Serviceguard features.
