Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sap_ha_pacemaker_cluster: Azure health-azure-events, pcmk_host_map #832

Open
marcelmamula opened this issue Aug 8, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@marcelmamula
Copy link
Contributor

marcelmamula commented Aug 8, 2024

  1. Implement Azure specific HA steps as documented:

@marcelmamula @ja9fuchs @sean-freeman

SLES: https://learn.microsoft.com/en-us/azure/sap/workloads/high-availability-guide-suse-pacemaker?tabs=msi#configure-pacemaker-for-azure-scheduled-events

sudo crm configure property node-health-strategy=custom
sudo crm configure location loc_azure_health \
/'!health-.*'/ rule '#health-azure': defined '#uname'

sudo crm_attribute --node prod-cl1-0 --name '#health-azure' --update 0
sudo crm_attribute --node prod-cl1-1 --name '#health-azure' --update 0

sudo crm configure primitive health-azure-events ocf:heartbeat:azure-events-az \ 
meta allow-unhealthy-nodes=true failure-timeout=120s \ 
op start start-delay=60s \ 
op monitor interval=10s

sudo crm configure clone health-azure-events-cln health-azure-events

RHEL: https://learn.microsoft.com/en-us/azure/sap/workloads/high-availability-guide-rhel-pacemaker?tabs=msi#configure-pacemaker-for-azure-scheduled-events

sudo pcs property set node-health-strategy=custom

sudo pcs constraint location 'regexp%!health-.*' \
rule score-attribute='#health-azure' \
defined '#uname'

sudo crm_attribute --node prod-cl1-0 --name '#health-azure' --update 0
sudo crm_attribute --node prod-cl1-1 --name '#health-azure' --update 0

sudo pcs resource create health-azure-events \
ocf:heartbeat:azure-events-az \
op monitor interval=10s timeout=240s \
op start timeout=10s start-delay=90s

sudo pcs resource clone health-azure-events allow-unhealthy-nodes=true failure-timeout=120s
  1. Add additional check for pcmk_host_map to remove it if VM name is equal to hostname, or generate as per documentation:
The 'pcmk_host_map' option is required in the command only if the hostnames and the Azure VM names are not identical. Specify the mapping in the format hostname:vm-name.

- name: "SAP HA Prepare Pacemaker - MS Azure VM - Assemble host mapping"

@marcelmamula marcelmamula added the enhancement New feature or request label Aug 8, 2024
@marcelmamula marcelmamula changed the title sap_ha_pacemaker_cluster: Azure health-azure-events sap_ha_pacemaker_cluster: Azure health-azure-events, pcmk_host_map Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant