Related Manuals for Novell PLATESPIN ORCHESTRATE 2.0.2 - HIGH AVAILABILITY CONFIGURATION GUIDE 06-17-2009
Summary of Contents for Novell PLATESPIN ORCHESTRATE 2.0.2 - HIGH AVAILABILITY CONFIGURATION GUIDE 06-17-2009
- Page 1 AUTHORIZED DOCUMENTATION High Availability Configuration Guide Novell ® PlateSpin Orchestrate ® 2.0.2 June 17, 2009 www.novell.com PlateSpin Orchestrate 2.0 High Availability Configuration Guide...
- Page 2 Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
- Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
- Page 4 PlateSpin Orchestrate 2.0 High Availability Configuration Guide...
-
Page 5: Table Of Contents
Contents About This Guide 1 Preparing PlateSpin Orchestrate for High Availability Support Overview ..............9 Installing PlateSpin Orchestrate to a High Availability Environment . - Page 6 PlateSpin Orchestrate 2.0 High Availability Configuration Guide...
-
Page 7: About This Guide
® ® PlateSpin Orchestrate 2.0 from Novell in a high availability environment. The guide provides information about the components and configuration steps necessary for preparing this environment, including instructions for configuring the PlateSpin Orchestrate Server in a cluster. The guide also provides some information regarding the behaviors you can expect from PlateSpin Orchestrate in various failover scenarios. - Page 8 PlateSpin Orchestrate 2. Web site (http://www.novell.com/documentation/pso_orchestrate20/). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
-
Page 9: Preparing Platespin Orchestrate For High Availability Support
® ® The PlateSpin Orchestrate Server from Novell is a critical component of your enterprise infrastructure. It continuously monitors and manages physical servers and virtual machines (VMs), and provides high availability for virtual machines by automatically restarting them on alternate physical servers if the server they are running on becomes unavailable because of a planned or unplanned outage. -
Page 10: Installing Platespin Orchestrate To A High Availability Environment
The Oirchestrate Server in a Clustered, High Availability Environment Figure 1-1 1.2 Installing PlateSpin Orchestrate to a High Availability Environment This section includes information to help you install PlateSpin Orchestrate Server components in a high availability environment. The sequence below is the supported method for configuring this environment. -
Page 11: Meeting The Prerequisites
SLES 10 SP2 integrates these open source storage technologies (Heartbeat 2 and OCFS) in a high availability installation pattern, which, when installed and configured, is known as the Novell High Availability Storage Infrastructure. This combined technology Preparing PlateSpin Orchestrate for High Availability Support... -
Page 12: Installing The High Availability Pattern For Sles 10
A plug-in and interface loading library used by Heartbeat 2 An interface for the STONITH device OCFS2 GUI tools OCFS2 Core tools For more information, see “Installing and Removing Software” (http://www.novell.com/ documentation/sles10/sles_admin/data/sec_yast2_sw.html) in the SLES 10 Installation and Administration Guide. PlateSpin Orchestrate 2.0 High Availability Configuration Guide... -
Page 13: Configuring Nodes With Time Synchronization And Installing Heartbeat 2 To Each
Heartbeat 2 packages are installed with the high availability pattern on the SLES 10 SP2 install source. For detailed information about configuring Heartbeat 2, see the installation and setup instructions (http://www.novell.com/documentation/sles10/heartbeat/index.html?page=/ documentation/sles10/heartbeat/data/b3ih73g.html) in the SLES 10 Heartbeat Guide (http:// www.novell.com/documentation/sles10/heartbeat/data/heartbeat.html). -
Page 14: Setting Up Ocfs2
SAN in OCFS2 where the PlateSpin Orchestrate files can be stored. For information on setting up and configuring OCFS2, see the “Oracle Cluster File System 2” (http://www.novell.com/documentation/sles10/sles_admin/data/ocfs2.html) section of the SLES 10 Administration Guide. -
Page 15: Installing And Configuring Platespin Orchestrate On The First Clustered Node
SAN configuration is beyond the scope of this document. For information about setting up a SAN, see the Oracle Cluster File System 2 (http://www.novell.com/documentation/sles10/sles_admin/ data/ocfs2.html) documentation in the SLES 10 Administration Guide. IMPORTANT: PlateSpin Orchestrate requires a specific mount point for file storage on the SAN. - Page 16 3e In the YaST2 Filter drop-down menu, select Patterns to display the install patterns available on the PlateSpin Orchestrate ISO. 3f Select the PlateSpin Orchestrate Server installation pattern for installation on the first node. When you do so, the Monitoring Server installation pattern and the Monitoring Agent pattern are also selected.
- Page 17 2 Run the script, as follows: /opt/novell/zenworks/orch/bin/config When the script runs, the following information is initially displayed: Welcome to Novell PlateSpin Orchestrate. This program will configure Novell PlateSpin Orchestrate 2.0 Select whether this is a new install or an upgrade i) install u) upgrade...
- Page 18 PlateSpin Orchestrate auditing at this time. If you use a different RDBMS, you must configure it separately for use with PlateSpin Orchestrate. 13 Specify the full path to file containing the license key you received from Novell. Example: opt/novell/zenworks/zos/server/license/key.txt...
- Page 19 Use the following steps to run the Platespin Orchestrate Configuration Wizard. 1 Run the script for the PlateSpin Orchestrate Configuration Wizard as follows: /opt/novell/zenworks/orch/bin/guiconfig The Configuration Wizard launches. IMPORTANT: If you only have a keyboard to navigate through the pages of the GUI Configuration Wizard, use the Tab key to shift the focus to a control you want to use (for example, a Next button), then press the Spacebar to activate that control.
- Page 20 3 Accept the agreement, then click Next to display the installation type page. 4 Select New Installation, then click Next to display the PlateSpin Orchestrate components page. The components page lists the PlateSpin Orchestrate components that are available for configuration. By default, only the installed components (the PlateSpin Orchestrate Server, in this case) are selected for configuration.
- Page 21 If other PlateSpin Orchestrate patterns were installed by mistake, make sure that you deselect them now. As long as these components are not configured for use, there should be no problem with the errant installation. 5 Click Next to display the Monitoring Services configuration page, then select the options you want.
- Page 22 Refer to the information in Table 1-1, “PlateSpin Orchestrate Configuration Information,” on page 25 for details about the configuration data that you need to provide. The GUI Configuration Wizard uses this information to build a response file that is consumed by the setup program inside the GUI Configuration Wizard.
- Page 23 Use the following command to run the configuration script: > /opt/novell/zenworks/orch/bin/config -rs <path_to_config_file 10 Click Next to display the following wizard page: 11 Click Next to launch the configuration script. When the configuration is finished, the following...
- Page 24 12 Click Finish to close the configuration wizard. 13 Continue with “Checking the Configuration” on page PlateSpin Orchestrate Configuration Information The following table includes the information required by the PlateSpin Orchestrate configuration ) and the configuration wizard ( ) when configuring the Orchestrate Server config guiconfig component for high availability.
- Page 25 A license key is required to use this product. You should have received this key from Novell, then you should have subsequently copied it to the network location that you specify here. Be sure to include the name of the license file in the path.
- Page 26 Configuration Explanation Information Orchestrate Agent Port Server Specify the Agent port. (continued) Default = 8100 Port 8100 is used for communication between the Orchestrate Server and the Orchestrate Agent. Specify another port number if 8100 is reserved for another use. Server Portal Specify the Server Portal port.
- Page 27 19), the first node of the Orchestrate Server cluster is set up. You then need to check the configuration. 1 Open the configuration log file ( /var/opt/novell/novell_zenworks_orch_install.log to make sure that the components were correctly configured. You can change the configuration if you change your mind about some of the parameters you provided in the configuration process.
-
Page 28: Running The High Availability Configuration Script
The high availability script, , is located in zos_server_ha_post_config /opt/novell/ with the other configuration tools. You need to run this script on the first node zenworks/orch/bin of the cluster (that is, the node where you installed PlateSpin Orchestrate Server) as the next step in setting up PlateSpin Orchestrate to work in a high availability environment. -
Page 29: Creating The Cluster Resource Group
<group id="ZOS_Server"> <primitive id="ZOS_Server_Cluster_IP" class="ocf" type="IPaddr2" provider="heartbeat"> <instance_attributes> <attributes> <nvpair name="ip" value="$CONFIG_ZOS_SERVER_CLUSTER_IP"/> </attributes> </instance_attributes> </primitive> <primitive id="ZOS_Server_Instance" class="lsb" type="novell-zosserver" provider="heartbeat"> <instance_attributes id="zos_server_instance_attrs"> <attributes> <nvpair id="zos_server_target_role" name="target_role" value="started"/> </attributes> </instance_attributes> <operations> <op id="ZOS_Server_Status" name="status" description="Monitor the status of the ZOS service" interval="60" timeout="15" start_delay="15"... - Page 30 <nvpair id="apache2_target_role" name="target_role" value="started"/> </attributes> </instance_attributes> <operations> <op id="Apache2_Status" name="status" description="Monitor the status of Apache2" interval="120" timeout="15" start_delay="15" role="Started" on_fail="restart"/> </operations> </primitive> <primitive id="Gmetad" class="lsb" type="novell-gmetad" provider="heartbeat"> <instance_attributes id="gmetad_attr"> <attributes> <nvpair id="gmetad_target_role" name="target_role" value="started"/> </attributes> </instance_attributes> <operations> <op id="Gmetad_Status" name="status" description="Monitor the status of Gmetad"...
-
Page 31: Testing The Failover Of The Platespin Orchestrate Server In A Cluster
1.2.9 Testing the Failover of the PlateSpin Orchestrate Server in a Cluster You can optionally simulate a failure of the Orchestrate Server by powering off or performing a shutdown of the server. After approximately 30 seconds, the clustering software detects that the primary node is no longer functioning, binds the IP address to the failover server, then starts the failover server in the cluster. - Page 32 It is important to understand that virtual machines under the management of PlateSpin Orchestrate are also highly available—the loss of a host causes PlateSpin Orchestrate to re-provision it elsewhere. This is true as long as the constraints in PlateSpin Orchestrate allow it to re-provision (for example, if the virtual machine image is on shared storage).
-
Page 33: Platespin Orchestrate Failover Behaviors In A High Availability Environment
® This section includes information to help you understand the failover behavior of the PlateSpin ® Orchestrate Server from Novell in a high availability environment. Section 2.1, “Use Case 1: Orchestrate Server Failover,” on page 33 Section 2.2, “Use Case 2: Agent Behavior at Orchestrate Server Failover and Failback,” on page 33 Section 2.3, “Use Case 3: VM Builder Behavior at Orchestrate Server Failover and Failback,”... -
Page 34: Use Case 4: Monitoring Behavior At Orchestrate Server Failover And Failback
2.4 Use Case 4: Monitoring Behavior at Orchestrate Server Failover and Failback The PlateSpin Orchestrate Monitoring Server and the Monitoring Agent are installed on the same server as the PlateSpin Orchestrate Server in the high availability PlateSpin Orchestrate cluster. The Monitoring Agent reports data to the PlateSpin Orchestrate Monitoring Server, and the Orchestrate VM Client provides access to the charts created from the monitoring data. -
Page 35: High Availability Best Practices
Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html (http://www.novell.com/documentation/ feedback.html) and enter your comments there. - Page 36 PlateSpin Orchestrate 2.0 High Availability Configuration Guide...