
Learn Linux cluster high availability through two real-life projects, covering active-active and active-passive setups, fencing, quorum, constraints, and enterprise lab architecture with vSphere, ESXi, and Red Hat Linux.
Explore Red Hat high-availability clusters, including active-active and active-passive setups, floating IPs, shared storage, and essential concepts like fencing, quorum, and resource management.
Navigate the Udemy platform, adjust video speed on desktop or mobile for clearer understanding of the instructor's accent, and explore ratings and feedback to improve Linux cluster high availability content.
Explore data center infrastructure foundations, including active and passive data centers, clustering and failover strategies for Linux, and cross-site disaster recovery to keep production apps running.
Explore how application staging fits into DevOps, moving code from developers through staging to production with testing, UAT, and multiple environments, using Jenkins, Maven, and Ansible.
Learn linux basics and lab setup across rpm and debian bases, with ssh, file transfer, and essential commands; explore infrastructure, networking, lvm-based disk management, patching, and cloud deployment.
Explore shell terminals, focusing on bash as the go-to shell for system administration, and compare it with zsh, fish, dash, and csh, highlighting autocomplete.
Explore the linux file system hierarchy, starting from the root slash, learn how mounting new disks creates subtrees and absolute paths like /home and /tmp, and navigate with cd.
Harness the pipeline concept to chain commands, filter command output, and build precise results across Linux, Unix, and Windows terminals using grep, cat, and other commands.
Build a lab architecture for a Linux cluster high availability using VMware ESXi on a workstation. Install ESXi, create Linux and Windows nodes, and practice snapshots.
Learn why Red Hat Linux is chosen for enterprise clusters, including CentOS as a free alternative, and how OpenShift, Red Hat Satellite, and Ansible enable automation and reliable support.
Install VMware Workstation 15 on Windows to support Linux cluster high availability labs, replacing VirtualBox, and complete stage one of the setup.
Create a NAT network in the virtual network editor with the 192.168.100.0 class C subnet and dynamic DHCP. Use VMnet10 sharing on the host to connect lab VMs.
Learn to install and configure VMware ESXi, set static network IPs, bridge networking, and troubleshoot host-to-VM connectivity for Linux cluster high-availability projects.
Set up an ESXi host and install two CentOS 7 nodes for a Linux cluster with high availability; configure static IPs 192.168.1.110 and 192.168.1.120, storage, and SSH access.
Set up a two-node Linux high-availability cluster using Pacemaker and fencing, configure hosts, disable firewall for lab practice, authenticate nodes, create and enable the cluster.
Explore fencing in Linux clusters, ensuring only one active writer through shared storage and heartbeat, preventing data corruption during failover, reboot, and quorum management.
Configure fencing in a linux cluster with vmware_soap, assign two fencing agents to the nodes, and verify failover using pcs status and crm-mon.
Learn how to identify VMs inside an ESXi host using command output or the web UI, compare UUIDs for accuracy, and verify VM names for patching and cluster checks.
Master the concept of quorum in Linux clusters by examining default settings, rule of majority, and how to adjust configurations for odd versus even node counts to prevent split brain.
Learn how a quorum server in a Linux cluster monitors nodes, enforces fencing to prevent split-brain, and ensures majority consensus, with high-level setup and optional deployment.
Learn how to configure cluster quorum for odd or even node counts using auto_tie_breaker, wait_for_all, and last_man_standing settings, including practical commands to update and verify quorum.
Learn how to apply location, ordering, and co-location constraints in a two-node Linux cluster using pcs constraints to control where and when applications and services run.
Add a new server to a Linux cluster and enable fencing. Install required packages, configure the DNS/hosts setup, join the node to the three-node cluster, and validate failover.
Build a two-node Linux cluster with active-passive high availability and shared storage. Explore NFS/SAMBA exports, cluster resources, floating IP, and moving resources between nodes.
Learn how to implement a high-availability nfs cluster with active-passive failover on linux, using shared storage, lvm (vg and lv), gfs2, and ip failover for reliable multi-node access.
Set up a two-node Linux cluster with NFS storage shared via iSCSI, configure fencing, LVM volumes, and VGs, create an NFS export, and activate the cluster resources for high availability.
Explore building an active-passive Linux cluster with a floating IP, configuring NFS resources, exporting shares, and testing failover between nodes to keep services available.
Explore how gfs2 enables active-active Linux cluster storage by connecting multiple servers simultaneously, contrasting with ext4 and xfs for active-passive setups, and previewing a real-world failover website project.
Build an active-active linux cluster with 2 nodes using gfs2, lvm, dlm, and clvmd, create shared storage, configure a floating IP, and deploy a clustered Apache website.
Master Linux cluster high availability by implementing active-active and active-passive failover with pcs, managing resources, constraints, fencing, and quorum, while handling SELinux and Apache and NFS.
Learn practical commands for managing a rehl high-availability cluster with pcs, including viewing and updating resources, changing ip addresses, standby nodes, cluster status and sync, and debugging.
Connect a Cisco switch or router via a console cable using a laptop and Putty to access device in data center. Confirm serial port and use USB adapters if needed.
Learn to replace a server hard disk by identifying the correct bay, removing the old drive, and installing the new one. Verify the disk status using color indicators from green healthy to orange warning and red error, confirm the correct bay and serial number, and complete data center clearance before exiting.
Master tape library storage by changing tapes in HP StorageWorks autoloaders, including left and right magazines, weekly tape rotation, and console access via Putty and command line.
Learn to access discounted Udemy courses via coupon links, including linux high availability cluster and ansible, by copying a link and applying the 12.9 discount.
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
History
The 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