After checking all the changes needed to backport azure-events to Bionic I agree with Rafael (comment #4). Let's recommend users wanting to use azure-events to upgrade to Focal. I am removing azure-events from the scope of the proposed SRUs.
** Summary changed: - Microsoft Azure Enablement: azure-lb & azure-events missing in Bionic + Microsoft Azure Enablement: azure-lb missing in Bionic ** Description changed: [Impact] - azure-lb and azure-events are handful resources agents if one is - maintaining a cluster on Azure platform. azure-lb facilitate the - operation of a load balancer implemented by Azure and azure-events - notifies when some events in the Azure platform happens to help the - cluster to adjust itself. + azure-lb is a handful resources agent if one is maintaining a cluster on + Azure platform. azure-lb facilitate the operation of a load balancer + implemented by Azure. - In Focal, both resource agents are available, however, to keep all the - releases in the same state a patch fixing a bug in azure-lb is needed. - This is the upstream patch: + In Focal, azure-lb is available, however, to keep all the releases in + the same state a patch fixing a bug in azure-lb is needed. This is the + upstream patch: https://github.com/ClusterLabs/resource-agents/commit/d22700fc - In Bionic, those agents are not available, and the full features will be + In Bionic, the agent is not available, and the full feature will be backported as a way to better support the HA stack on Azure. The changes are self-contained since each resource agent is maintained as a separate script. [Test Case] On Azure create a Corosync/Pacemaker cluster with 3 VMs and make sure you have the following CIB: node 1: vm01 node 2: vm02 node 3: vm03 primitive lb-healthprobe azure-lb \ - params port=8000 nc="/bin/nc" \ - op monitor interval=10 timeout=20 - primitive notifier azure-events \ - op monitor interval=10 - clone clone-notifier notifier + params port=8000 nc="/bin/nc" \ + op monitor interval=10 timeout=20 property cib-bootstrap-options: \ - have-watchdog=false \ - dc-version=2.0.3-4b1f869f0f \ - cluster-infrastructure=corosync \ - cluster-name=clufocal \ - no-quorum-policy=stop \ - last-lrm-refresh=1603822692 \ - maintenance-mode=false + have-watchdog=false \ + dc-version=2.0.3-4b1f869f0f \ + cluster-infrastructure=corosync \ + cluster-name=clufocal \ + no-quorum-policy=stop \ + last-lrm-refresh=1603822692 \ + maintenance-mode=false The status of the cluster should be: $ sudo crm status Cluster Summary: - * Stack: corosync - * Current DC: vm02 (version 2.0.3-4b1f869f0f) - partition with quorum - * Last updated: Wed Dec 9 18:16:32 2020 - * Last change: Wed Dec 9 18:16:30 2020 by root via crm_attribute on vm01 - * 3 nodes configured - * 4 resource instances configured + * Stack: corosync + * Current DC: vm02 (version 2.0.3-4b1f869f0f) - partition with quorum + * Last updated: Wed Dec 9 18:16:32 2020 + * Last change: Wed Dec 9 18:16:30 2020 by root via crm_attribute on vm01 + * 3 nodes configured + * 1 resource instances configured Node List: - * Online: [ vm01 vm02 vm03 ] + * Online: [ vm01 vm02 vm03 ] Full List of Resources: - * lb-healthprobe (ocf::heartbeat:azure-lb): Started vm02 - * Clone Set: clone-notifier [notifier]: - * Started: [ vm01 vm02 vm03 ] + * lb-healthprobe (ocf::heartbeat:azure-lb): Started vm02 - To take advantage of azure-lb resource agents you need to have an Azure + To take advantage of azure-lb resource agent you need to have an Azure load balance configured. You can find information on how to do it here: https://docs.microsoft.com/en-us/azure/load-balancer/quickstart-load- balancer-standard-public-cli [Where problems could occur] As mentioned previously each resource agent is maintained as a separate - script, so for Focal where the agents are already there we can have a - problem in the existent azure-lb resource agent (the one patched). In - Bionic the risk of a regression is quite low since those agents do not - exist. + script, so for Focal where the agent is already there we can have a + problem in the existent azure-lb resource agent. In Bionic the risk of a + regression is quite low since the agent does not exist. [Original description] This bug is part of the HA enablement for Microsoft Azure Cloud. (https://discourse.ubuntu.com/t/ubuntu-ha-cluster-in-microsoft-azure-cloud/) """ Need one additional Azure package to support load balancer. If you refer the following article, we use Azure load balancer to find the active replica in availability group for SQL Server and routing connections appropriately. """ [rafaeldtinoco@focal ~]$ apt-file list resource-agents | grep -i azure resource-agents: /usr/lib/ocf/resource.d/heartbeat/azure-events resource-agents: /usr/lib/ocf/resource.d/heartbeat/azure-lb resource-agents: /usr/share/man/man7/ocf_heartbeat_azure-events.7.gz resource-agents: /usr/share/man/man7/ocf_heartbeat_azure-lb.7.gz [rafaeldtinoco@bionic ~]$ apt-file list resource-agents | grep -i azure <nothing> In Ubuntu we have: $ rmadison resource-agents resource-agents | 1:4.1.0~rc1-1ubuntu1.2 | bionic-updates resource-agents | 1:4.5.0-2ubuntu2 | focal resource-agents | 1:4.6.1-1ubuntu1 | groovy In Debian: $ rmad resource-agents resource-agents | 1:4.2.0-2+deb10u2 | stable resource-agents | 1:4.6.1-1~bpo10+1 | buster-backports resource-agents | 1:4.6.1-1 | testing resource-agents | 1:4.6.1-1 | unstable From upstream: commit 771b49a1 Author: Oyvind Albrigtsen <[email protected]> Date: Wed Nov 29 14:09:06 2017 azure-lb: new resource agent (and other commits from 2018 and 2019 as fixes) [rafaeldtinoco@upstream resource-agents]$ git describe --tags 771b49a1 v4.1.0-1-g771b49a1 [rafaeldtinoco@upstream resource-agents]$ git tag --contains 771b49a1 v4.1.1 v4.1.1rc1 Considering version in Bionic is 4.1.0~rc1, we probably lost the new resource by little. Should be easy to be backported and, after discussing with the SRU (Stable Releases Update) team member, possible to be consider as HW enablement within SRU guidelines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895343 Title: Microsoft Azure Enablement: azure-lb missing in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1895343/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
