Comparison of Red Hat Clusters with Openvms Clusters Keith Parris Thank You to Our Global, Platinum & Gold Sponsors! Global
Total Page:16
File Type:pdf, Size:1020Kb
Comparison of Red Hat Clusters with OpenVMS Clusters Keith Parris Thank you to our Global, Platinum & Gold Sponsors! Global: Platinum: Gold: OpenVMS Cluster History – VAX/VMS Version 1.0, 1978 • Includes Record Management Services (RMS) – Version 2.0, 1980 • Ethernet networking added – Version 3.0, 1982 • Lock Manager • System Communications Services (SCS) and Mass Storage Control Protocol (MSCP) • 1983: Computer Interconnect (CI) & HSC controller based clusters – Limited sharing: could mount disks for read-write access on one node and also mount them read-only on other nodes – Version 4.0, 1984 • VAXclusters: Connection Manager, Distributed Lock Manager, Cluster-wide File System – Version 4.5, 1986 • Local Area VAXcluster (LAVC) using Ethernet as a cluster interconnect OpenVMS Cluster History – Version 5.0, 1988 • Mixed-Interconnect VAXclusters – Version 5.2, 1989 • Support for 96 nodes • Lock tree remastering, based on new LOCKDIRWT parameter – Version 5.4, 1989 • MSCP Load Balancing and preferred paths • 5.4-3: Multiple-NIC support for cluster interconnect – Version 5.5, 1991 • Host-Based Volume Shadowing (HBVS) for host-based mirroring (RAID-1) • Dynamic activity-based lock tree remastering • Tape MSCP Serving – Version 6.0, 1993 • Cluster-wide Virtual I/O Cache – Version 6.2, 1995 • SCSI clusters OpenVMS Cluster History – Version 7.0, 1995 • 64-bit addressing • Fast I/O and Fast Path for optimized I/O – Version 7.1, 1996 • Memory Channel cluster interconnect – Version 7.2, 1999 • Galaxy: Shared Memory cluster interconnect, and migrate CPUs between software partitions – Version 7.3, 2001 • Improved Multiple NIC performance (simultaneous transmission over multiple paths) • XFC cluster-wide file cache – Version 8.3, 2006 • Improved activity-based lock tree remastering with new LOCKRMWT parameter – Version 8.4, 2010 • IP networks as a cluster interconnect • 6-member HBVS shadowsets Red Hat Clusters History – Version 0.01 of Linux from Linus Torvalds, 1991 – First version of Red Hat Linux, 1994 – First Red Hat Cluster Suite, circa 1996 – Red Hat acquires Sistina and open-sources GFS file system, 2003-4 – GFS2 and DLM in RHEL 5.3, 2009 – Up through RHEL 5.x: product name is Red Hat Cluster Suite – RHEL 6, 2010: • RHEL 6 as base plus “Add-Ons” – High Availability Add-On – Resilient Storage Add-On – etc. Red Hat Cluster-related Products Add-Ons for Red Hat Enterprise Linux 6 – High Availability Add-On • Provides failover services between nodes within a cluster. – Resilient Storage Add-On • CLVM (Cluster Logical Volume Manager) and GFS2 (Global File System 2) cluster-wide file system for coordinated use of a shared block device using distributed lock manager (DLM) – Load Balancer Add-On • Directs network requests to nodes within a pool of servers providing identical services – Scalable File System Add-On • XFS for support of file systems up to 100 TB in size and/or with multi- threaded parallel I/O workloads – High Performance Network Add-On • Provided remote direct memory access over Converged Ethernet (RoCE) Red Hat Definition of Clusters • Cluster Types – Storage cluster – High availability cluster – Load balancing cluster – High performance cluster – Multi-Site cluster – Stretch cluster Red Hat Definition of Clusters • Cluster Types – Storage cluster • “Storage clusters provide a consistent file system image across servers in a cluster, allowing the servers to simultaneously read and write to a single shared file system. A storage cluster simplifies storage administration by limiting the installation and patching of applications to one file system. Also, with a cluster- wide file system, a storage cluster eliminates the need for redundant copies of application data and simplifies backup and disaster recovery. The High Availability Add-On provides storage clustering in conjunction with Red Hat GFS2 (part of the Resilient Storage Add-On).” – RHEL6 HA Add-On Overview, section 1.1 – High availability cluster – Load balancing cluster – High performance cluster – Multi-Site cluster – Stretch cluster Red Hat Definition of Clusters • Cluster Types – Storage cluster – High availability cluster • “High availability clusters provide highly available services by eliminating single points of failure and by failing over services from one cluster node to another in case a node becomes inoperative. Typically, services in a high availability cluster read and write data (via read-write mounted file systems). Therefore, a high availability cluster must maintain data integrity as one cluster node takes over control of a service from another cluster node. Node failures in a high availability cluster are not visible from clients outside the cluster. (High availability clusters are sometimes referred to as Failover clusters.) The High Availability Add-On provides high availability clustering through its High Availability Service Management component, rgmanager.” – RHEL6 HA Add-On Overview, section 1.1 – Load balancing cluster – High performance cluster – Multi-Site cluster – Stretch cluster Red Hat Definition of Clusters • Cluster Types – Storage cluster – High availability cluster – Load balancing cluster • “Load-balancing clusters dispatch network service requests to multiple cluster nodes to balance the request load among the cluster nodes. Load balancing provides cost-effective scalability because you can match the number of nodes according to load requirements. If a node in a load-balancing cluster becomes inoperative, the load-balancing software detects the failure and redirects requests to other cluster nodes. Node failures in a load-balancing cluster are not visible from clients outside the cluster. Load balancing is available with the Load Balancer Add-On.” – RHEL6 HA Add-On Overview, section 1.1 – High performance cluster – Multi-Site cluster – Stretch cluster Red Hat Definition of Clusters • Cluster Types – Storage cluster – High availability cluster – Load balancing cluster – High performance cluster • “High-performance clusters use cluster nodes to perform concurrent calculations. A high-performance cluster allows applications to work in parallel, therefore enhancing the performance of the applications. (High performance clusters are also referred to as computational clusters or grid computing.) … The Red Hat Enterprise Linux High Availability Add-On contains support for configuring and managing high availability servers only. It does not support high-performance clusters.” – RHEL6 HA Add-On Overview, section 1.1 – Multi-Site cluster – Stretch cluster Red Hat Definition of Clusters • Cluster Types – Storage cluster – High availability cluster – Load balancing cluster – High performance cluster – Multi-Site cluster • “Multi-site or disaster-tolerant clusters are separate clusters that run at different physical sites, typically using SAN-based storage replication to replicate data. Multi-site clusters are usually used in an active/passive manner for disaster recovery with manual failover of the active cluster to the passive cluster.” -- Red Hat Enterprise Linux Cluster, High Availability, and GFS Deployment Best Practices, Updated 22 Feb 2013, https://access.redhat.com/knowledge/articles/40051 – Stretch cluster Red Hat Definition of Clusters • Cluster Types – Storage cluster – High availability cluster – Load balancing cluster – High performance cluster – Multi-Site cluster – Stretch cluster • “Stretch clusters are single-cluster configurations that span multiple physical sites. Additional details on the supportability of multi-site and stretch clusters can be found in Support for Red Hat Enterprise Linux Cluster and High Availability Stretch Architectures and please note that all stretch clusters require an architecture review.” -- Red Hat Enterprise Linux Cluster, High Availability, and GFS Deployment Best Practices, Updated 22 Feb 2013, https://access.redhat.com/knowledge/articles/40051 Red Hat Definition of Clusters • Cluster Types • Red Hat Clusters focus on capabilities of these types: 1. High availability cluster 2. Load balancing cluster Red Hat High Availability Add-On • Overview Source: RedHat.com Red Hat High Availability Add-On • Components – Conga: User Interface for configuration & management • luci: Runs on management server and provides web-based GUI interface • ricci: Agent which runs on each cluster node – CCS: Cluster Configuration System • Provides CLI interface for cluster management – corosync: cluster executive • Implements the Totem Single Ring Ordering and Membership Protocol • Came from OpenAIS open cluster infrastructure project from the Service Availability Forum – rgmanager: Resource Group Manager for failover/relocation of services – CMAN: Cluster Manager -- handles quorum – fenced: Fencing system – CLVM: Cluster Logical Volume Manager (clustered version of LVM2) – GFS2: shared-disk cluster file system – DLM: Distributed Lock Manager – Load Balancer based on Piranha (Linux Virtual Server, LVS) OpenVMS Cluster • Limitations • Supported Limits – Number of nodes supported: 96 – Data sharing: As many as all cluster nodes at once – Number of geographical sites supported in a cluster: Unlimited • Synchronously-replicated identical copies of data in up to 6 sites at once with Volume Shadowing and OpenVMS Version 8.4 – Distance between sites: • 150 miles out-of-the-box • 500 miles with DTCS (Disaster Tolerant Continuity Services) • >500 miles supported with Product Manager approval Red Hat High Availability Add-On • Limitations • Supported Limits – Number of nodes supported: 16 – Data sharing: 1 node at a time