manualshive.com logo in svg

Novell PLATESPIN ORCHESTRATE 2.0.2 - HIGH AVAILABILITY CONFIGURATION GUIDE 06-17-2009, Configuration Manual

Share
Download
Novell PLATESPIN ORCHESTRATE 2.0.2 - HIGH AVAILABILITY CONFIGURATION GUIDE 06-17-2009 Configuration Manual Download Page 13

Preparing PlateSpin Orchestrate for High Availability Support

13

no

vd

ocx 

(e

n)

  

13

 Ma
y 20

09

1.2.3  Configuring Nodes with Time Synchronization and 
Installing Heartbeat 2 to Each Node

When you have installed the high availability packages to each node of the cluster, you need to 
configure the Network Timing Protocol (NTP) and Heartbeat 2 clustering environment on each 
physical machine that participates in the cluster.

Š

“Configuring Time Synchronization” on page 13

Š

“Configuring Heartbeat 2” on page 13

Configuring Time Synchronization

To configure time synchronization, you need to configure the nodes in the cluster to synchronize to a 
time server outside the cluster. The cluster nodes use the time server as their time synchronization 
source.

NTP is included as a network service in SLES 10 SP2. Use the 

time synchronization instructions 

(http://www.novell.com/documentation/sles10/heartbeat/data/b5ez1wc.html)

 in the 

SLES 10 

Heartbeat Guide

 to help you configure each cluster node with NTP.

Configuring Heartbeat 2

Heartbeat 2 is an open source server clustering system that ensures high availability and 
manageability of critical network resources including data, applications, and services. It is a 
multinode clustering product for Linux that supports failover, failback, and migration (load 
balancing) of individually managed cluster resources.

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)

.

An important value you need to specify in order for Heartbeat 2 to be enabled for high availability is 
configured in the 

Default Action Timeout

 field on the settings page of the Heartbeat 2 console 

(hb_gui).

Summary of Contents for PLATESPIN ORCHESTRATE 2.0.2 - HIGH AVAILABILITY CONFIGURATION GUIDE 06-17-2009

Page 1: ...l www novell com novdocx en 13 May 2009 AUTHORIZED DOCUMENTATION PlateSpin Orchestrate 2 0 High Availability Configuration Guide PlateSpin Orchestrate 2 0 2 June 17 2009 High Availability Configuration Guide ...

Page 2: ...or re export to entities on the current U S export exclusion lists or to any embargoed or terrorist countries as specified in the U S export laws You agree to not use deliverables for prohibited nuclear missile or chemical biological weaponry end uses See the Novell International Trade Services Web page http www novell com info exports for more information on exporting Novell software Novell assum...

Page 3: ... 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: ...4 PlateSpin Orchestrate 2 0 High Availability Configuration Guide novdocx en 13 May 2009 ...

Page 5: ... and Configuring Orchestrate Server Packages on Other Nodes in the Cluster for High Availability 28 1 2 8 Creating the Cluster Resource Group 29 1 2 9 Testing the Failover of the PlateSpin Orchestrate Server in a Cluster 31 1 2 10 Installing and Configuring other PlateSpin Orchestrate Components to the High Availability Grid 31 2 PlateSpin Orchestrate Failover Behaviors in a High Availability Envi...

Page 6: ...6 PlateSpin Orchestrate 2 0 High Availability Configuration Guide novdocx en 13 May 2009 ...

Page 7: ...in Orchestrate Administrator deploys jobs manages users and monitors distributed computing resources Administrators can also create and set policies for automating the usage of these computing resources For more information about the tasks and tools used by the Orchestrate Administrator see the PlateSpin Orchestrate 2 0 Administrator Reference User The end user of PlateSpin Orchestrate also called...

Page 8: ...st recent updates of this High Availability Guide visit the 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 TM etc denotes a Novell trademark An asterisk denotes a third party trademark When a s...

Page 9: ...ate Server itself must be highly available In PlateSpin Orchestrate high availability services are provided by a specialized set of applications that run on SUSE Linux Enterprise Server SLES10 Heartbeat 2 is high availability clustering software that provides multinode failover and service level health monitoring for Linux based services Heartbeat 2 monitors both physical servers and the services ...

Page 10: ...0 on page 12 3 Section 1 2 3 Configuring Nodes with Time Synchronization and Installing Heartbeat 2 to Each Node on page 13 4 Section 1 2 4 Setting Up OCFS2 on page 14 5 Section 1 2 5 Installing and Configuring PlateSpin Orchestrate on the First Clustered Node on page 15 6 Section 1 2 6 Running the High Availability Configuration Script on page 28 7 Section 1 2 8 Creating the Cluster Resource Grou...

Page 11: ...installed and are a key part of the high availability infrastructure A Fibre Channel or ISCSI Storage Area Network SAN A STONITH device to provide node fencing A STONITH device is a power switch that the cluster uses to reset nodes that are considered dead Resetting non heartbeating nodes is the only reliable way to ensure that no data corruption is performed by nodes that hang and only appear to ...

Page 12: ...id on page 31 1 2 2 Installing the High Availability Pattern for SLES 10 The high availability install pattern is included in the distribution of SLES 10 SP2 Use YaST2 or the command line if you prefer to install the packages that are associated with the high availability pattern to each physical node that is to participate in the PlateSpin Orchestrate cluster NOTE The high availability pattern is...

Page 13: ...at data b5ez1wc html in the SLES 10 Heartbeat Guide to help you configure each cluster node with NTP Configuring Heartbeat 2 Heartbeat 2 is an open source server clustering system that ensures high availability and manageability of critical network resources including data applications and services It is a multinode clustering product for Linux that supports failover failback and migration load ba...

Page 14: ...d lock manager helps prevent file access conflicts OCFS2 supports up to 32 000 subdirectories and millions of files in each directory The O2CB cluster service a driver runs on each node to manage the cluster To set up the high availability environment for PlateSpin Orchestrate you need to first install the High Availability pattern in YaST this includes the ocfs2 tools and ocfs2console software pa...

Page 15: ... 0 and use it in a high availability environment make sure that the requirements to do so are met For more information see Planning the Orchestrate Server Installation in the PlateSpin Orchestrate 2 0 Installation and Configuration Guide The PlateSpin Orchestrate Server Orchestrate Server is supported on SUSE Linux Enterprise Server 10 Service Pack 2 SLES 10 SP2 only To install the PlateSpin Orche...

Page 16: ...ure the PlateSpin Orchestrate Server components that you have installed You can use one of two methods to perform the configuration The PlateSpin Orchestrate product text based configuration script If you use this method continue with Running the PlateSpin Orchestrate Configuration Script on page 16 The PlateSpin Orchestrate GUI Configuration Wizard which might be more user friendly If you use thi...

Page 17: ...hestrate Server 3 no PlateSpin Orchestrate Agent not installed 4 no PlateSpin Orchestrate VM Builder not installed Select from the following 1 4 toggle selection status a all n none f finished making selections q quit exit the program Selection finish Because you installed only the Platespin Orchestrate Server and the PlateSpin Orchestrate Monitoring Service no other products need to be selected 4...

Page 18: ... or n PlateSpin Orchestrate can send audit information to a relational database RDBMS If you enable auditing you need access to an RDBMS If you use a PostgreSQL database you can configure it for use with 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...

Page 19: ...the configuration summary again Specify f if you are satisfied with the configuration and want to install using the specifications as they are 20 Continue with Checking the Configuration on page 27 Running the PlateSpin Orchestrate Configuration Wizard Use the following steps to run the Platespin Orchestrate Configuration Wizard 1 Run the script for the PlateSpin Orchestrate Configuration Wizard a...

Page 20: ... 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: ...ect the options you want On this page of the wizard you can change the default node name for this monitored node and you can also configure this computer to be the Monitoring Server Make sure that the option to configure as a Monitoring Server is selected 6 Click Next to display the high availability configuration page 7 Select Install to a High Availability clustered environment to configure the ...

Page 22: ...hat is consumed by the setup program inside the GUI Configuration Wizard TIP Select Configure advanced settings to display a page where you can specify various port settings and certificate files Details for this page are provided in Table 1 1 PlateSpin Orchestrate Configuration Information on page 25 8 Click Next to display the Xen VNC password page 9 Enter the VNC password you intend to use for ...

Page 23: ...plies the configuration settings If you deselect the check box the wizard writes out the configuration file to etc opt novell novell_zenworks_orch_install conf without starting PlateSpin Orchestrate or applying the configuration settings You can use this saved conf file to start the Orchestrate Server and apply the settings Do this either by running the configuration script manually or by using an...

Page 24: ...rate Configuration Information The following table includes the information required by the PlateSpin Orchestrate configuration config and the configuration wizard guiconfig when configuring the Orchestrate Server component for high availability The information is organized in this way to make it readily available The information is listed in the order that it is requested by the configuration scr...

Page 25: ...u access the PlateSpin Orchestrate Console or the zosadmin command line interface You should remember this password for future use Grid name Select a name for the PlateSpin Orchestrate grid Default hostname_grid A grid is an administrative domain container holding all of the objects in your network or data center PlateSpin Orchestrate monitors and manages these objects including users resources an...

Page 26: ...and client installers and product tools to help you understand and use the product Specify another port number if 8001 is reserved for another use on this server TLS Certificate and Key1 Choose whether to generate a TLS certificate and key Default yes the Orchestrate Server must generate a certificate and key for authentication A PEM encoded TLS certificate and key is needed for secure communicati...

Page 27: ...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 To do so rerun the configuration and change your responses The configuration script performs the following functions in sequence on the PlateSpin Orchestrate 1 Binds the cluster IP on this server by issuing the following ...

Page 28: ...ver is not running Copies Apache files to shared storage Copies gmond and gmetad files to shared storage Moves the PlateSpin Orchestrate files to shared storage first node of the cluster Creates symbolic links pointing to the location of shared storage all nodes of the cluster The high availability configuration script must be run on all nodes of the cluster Make sure that you follow the prompts i...

Page 29: ...al The script performs the following functions Obtains the DNS name from the PlateSpin Orchestrate configuration file Creates the cluster resource group Configures resource stickiness to avoid unnecessary failbacks The zos_server_ha_resource_group script prompts you for the IP address of the Orchestrate Server cluster The script then adds this address to a Heartbeat 2 Cluster Information Base CIB ...

Page 30: ...start operations primitive primitive id Gmond class lsb type novell gmond provider heartbeat instance_attributes id gmond_attr attributes nvpair id gmond_target_role name target_role value started attributes instance_attributes operations op id Gmond_Status name status description Monitor the status of Gmetad interval 300 timeout 15 start_delay 15 role Started on_fail restart operations primitive ...

Page 31: ...dencies All non agent PlateSpin Orchestrate components must be installed to a SLES 10 SP2 server a RHEL 4 server or a RHEL 5 server The PlateSpin Orchestrate Agent must be installed to a SLES 10 SP1 server a RHEL 4 server a RHEL 5 server or a Windows NT 2000 XP server A VM Warehouse must be installed on the same server as a VM Builder A VM Builder can be installed independent of the VM Warehouse o...

Page 32: ...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: ...estart on another Orchestrate Server in the cluster The job must have been flagged as restartable For more information see Section 1 2 9 Testing the Failover of the PlateSpin Orchestrate Server in a Cluster on page 31 2 2 Use Case 2 Agent Behavior at Orchestrate Server Failover and Failback If the primary node in the PlateSpin Orchestrate cluster fails the Orchestrate Agent sees this server go dow...

Page 34: ... 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 The Monitoring Server and the Monitoring Agent services are made highly available along with the Orchestrate Server and move between clustered machines as the Orchestrate Server does If a monitoring agent ...

Page 35: ...r situation or 2 scheduled through the Job Scheduler to run at server startup the job might fail to schedule any joblets and is easily noticeable with a 0 second run time This is because scheduleSweep by default creates joblets only for online nodes If the Job runs during failover resources might not be immediately available so the job ends immediately To keep the Job from running until a resource...

Page 36: ...36 PlateSpin Orchestrate 2 0 High Availability Configuration Guide novdocx en 13 May 2009 ...

Reviews:

No comments

Brands by name

Popular brands

Load more brands