|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/linux-cluster-high-availability/
课程评论：没有评论
**课程概述：Linux集群高可用性（含两个真实项目）** 本课程（2025年）将以实际项目为导向，一步步教授您如何构建高可用性（HA）Linux集群，重点讲解使用Pacemaker实现Active-Active和Active-Passive两种模式。您将深入理解集群的工作原理及其核心组件，包括： * **集群概念与历史：** 了解Linux高可用性集群的起源和发展历程，从早期的邮件列表和HOWTOs，到首个生产客户的部署，再到版本2带来的n节点集群、资源监控、依赖关系和策略等增强功能，以及版本3中Pacemaker作为集群资源管理器（CRM）的分离。 * **核心组件解析：** * **Quorum（仲裁）：** 理解数据集群决策的关键，确保集群的稳定性。 * **Constraint（约束）：** 学习如何定义资源间的关系和限制，以实现预期的HA行为。 * **Resources（资源）：** 掌握如何配置和管理集群中的各种服务和应用程序，使其实现高可用。 * **Fencing (STONITH)：** 深入了解STONITH（Shoot The Other Node In The Head）机制，这是防止脑裂和数据损坏的关键。 * **Troubleshooting（故障排除）：** 学习诊断和解决集群环境中各类故障的实用技巧。 * **两种架构模式：** * **Active-Active：** 学习如何配置集群，使多个节点同时提供服务，提高资源利用率和响应能力。 * **Active-Passive：** 学习如何配置集群，由主节点提供服务，副节点在主节点故障时接管，实现容错。 通过本课程，您将获得构建和管理高可用Linux集群的全面知识和实践技能。
This course in 2025 will teach you how to setup a cluster step by step Will learn how to setup High Availability ( HA using Pacemaker ) ( Active - Active ) and ( Active - Passive ) Teach you how the cluster works and components like: - Quorum- Constraint - Resources - Fencing ( Stonith ) - Troubleshooting - Active - Active - Active - Passive HistoryThe project originated from a mailing list started in November 1997. Eventually Harald Milz wrote an odd sort of Linux-HA HOWTO. Unlike most HOWTOs, this was not about how to configure or use existing software, it was a collection of HA techniques which one could use if one were to write HA software for Linux.Alan Robertson was inspired by this description and thought that he could perhaps write some of the software for the project to act as a sort of initial seed crystal to help jump start the project. He got this initial software running on 18 March 1998. He created the first web site for the project on 19 October 1998, and the first version of the software was released on 15 November 1998.The first production customer of the software was Rudy Pawul of ISO-NE. The ISO-NE web site went into production in the second half of 1999.At this point, the project was limited to two nodes and very simple takeover semantics, and no resource monitoring.This was cured with version 2 of the software, which added n-node clusters, resource monitoring, dependencies, and policies. Version 2.0.0 came out on 29 July 2005.[5] This release represented another important milestone as it was the first version where very large contributions (in terms of code size) were made by the Linux-HA community at large. This series of releases brought the project to a level of feature parity-or-superiority with respect to commercial HA software.After version 2.1.4, the cluster resource manager component (responsible for starting and stopping resources and monitoring resource and node failure) was split off into a separate project called Pacemaker,[6] and the resource agents and other "glue" infrastructure were moved to separate packages. Thus with the version 3 series, the name Heartbeat should be used for the cluster messaging layer only
