If you want to be able to fence when one iSCSI target server is down, you have to use three SBD devices and, therefore, three iSCSI target servers. Pacemaker can't automatically fence a cluster node if only two SBD devices are configured and one of them is unavailable. We recommend using either one SBD device or three. If you want to use more than one SBD device per Pacemaker, be sure to deploy multiple iSCSI target servers and connect one SBD from each iSCSI target server. You can use up to three SBD devices for a Pacemaker cluster to allow an SBD device to become unavailable (for example, during OS patching of the iSCSI target server). The advantage of using an SBD device is that if you're already using SBD devices on-premises, they don't require any changes to how you operate the Pacemaker cluster. These iSCSI target servers can, however, be shared with other Pacemaker clusters. The SBD device requires at least one additional virtual machine (VM) that acts as an Internet Small Computer System Interface (iSCSI) target server and provides an SBD device. You can configure the SBD device by using either of two options: You can use an Azure fence agent, which restarts a failed node via the Azure APIs, or you can use SBD device. In Azure, you have two options for setting up fencing in the Pacemaker cluster for SLES. This article discusses how to set up Pacemaker on SUSE Linux Enterprise Server (SLES) in Azure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |