v3.11.0.2

What's Changed

• Bugfix - constraint Azure scheduled events agent installation by @hjstam in #576

• Bump Azure.Identity from 1.10.4 to 1.11.0 in /Webapp/SDAF by @dependabot in #580

• 3.11.0.2 Release by @KimForss in #582

  • Improvements to HANA Scaleout with Standby on ANF
  • Passwordless deployments using Managed Identities
  • DevOps project SetUp improvements

Full Changelog: v3.11.0.1...v3.11.0.2

v3.11.0.1

This hotfix resolves the following.

Problem

Fixing an issue which occurs when checking for the SAP Library storage account in a multi subscription scenario.
Version labels update
SBD configuration update

Solution

Ensure that the check is done against the correct subscription.

What's Changed

• Hotfix for 3.11 by @KimForss in #564

Full Changelog: v3.11.0.0...v3.11.0.1

v3.11.0.0

Release Notes for SAP Deployment Automation Framework v3.11.0.0

This release adds support for:

• HANA Scale out with worker/stand by node using shared ANF
• Azure Monitor for SAP support
• Using MSI for the deployer
• Pre-validation script to validate the environment before SDAF deployment
• URL validation script for checking that the relevant URL's are opened
• Add a post deployment playbook for providing hooks for customers
• SystemD based SAP Startup framework for SLES and RHEL based deployments
• Support for encrypted DB2 databases
• Fix for BOM download when checksum is not present in the file.
• Az DevOps setup script now supports cross-tenant deployments.
• Disable basic authentication on the webapp
• More granular control of DNS registrations
• Support for kdump optional fencing device on RHEL deployments
• Configure SBD devices for SLES cluster during cluster init
• Update load balancer properties to use probe_threshold = 2
• General stability and functionality improvements for pipelines and scripts.

What's Changed

• Release 3.11 PR by @KimForss in #561
• Add AMS monitoring by @devanshjainms in #548
• HANA Scale out with worker/stand by node using shared ANF storage by @shekharsorot in #536
• Support DB2 encrypted restore and other fixes by @hjstam and @daradicscsaba in #532 and multiple PRs
• Add Post Configuration Actions step to DB and SAP installation pipeline by @SteffenBoThomsen in #545
• Add Kdump support and SBD enhancements by @hdamecharla

Testing

All solutions and improvements have been tested using the SDAF deployment pipelines and the command line to ensure they work effectively.

Feedback

We appreciate your feedback and are committed to continuously enhancing your experience with our product. Please feel free to reach out if you have any questions or require further assistance via issues or discussions.

Additional Notes

For troubleshooting issues with the framework, please refer to the troubleshooting document.

Full Changelog: v3.10.1.0...v3.11.0.0

Release v3.10.1.0

Release v3.10.1.0

Notes

Problem

The introduction of new more descriptive variables for the Ansible configuration caused a few of the pipelines to fail.

No support for a Linux utility VM in the workload zone deployment.

No support for systemd based SAP deployments which are default for the newer OS and Kernel

No support for configuring Ansible 2.15 on the deployer.

General improvements for the deployment of infrastructure wrapper scripts and pipelines

Solution

Refactor the code to add backward compatibility functionality that will allow for the successful execution of the pipelines.

Add support for Linux utility VM in the workload zone deployment.

Add support for systemd based SAP deployments which are default for the newer OS and Kernel

Add support for configuring Ansible 2.15 on the deployer.

General improvements for the deployment of infrastructure wrapper scripts and pipelines

Testing

All solutions and improvements have been tested using the SDAF deployment pipelines and the command line to ensure they work effectively.

Feedback

We appreciate your feedback and are committed to continuously enhancing your experience with our product.
Please feel free to reach out if you have any questions or require further assistance via issues or discussions.

Additional Notes

For troubleshooting issues with the framework, please refer to the troubleshooting document.

Full Changelog: v3.10.0.0...v3.10.1.0

Release 3.10.0.0

Release v3.10.0.0

Notes

• Support for SBD and ISCSI based stonith devices
• ACSS registration playbook
• Ability to provision separate PPG for Application and DB servers
• Ability to restore encrypted Db2 database restores
• Azure scheduled events support for RHEL
• General performance and readability improvements

Testing

All solutions and improvements have been tested using the SDAF deployment pipelines and the command line to ensure they work effectively.

Feedback

We appreciate your feedback and are committed to continuously enhancing your experience with our product.
Please feel free to reach out if you have any questions or require further assistance via issues or discussions.

Additional Notes

For troubleshooting issues with the framework, please refer to the troubleshooting document.

Release 3.9.3.0

Release Notes - Version 3.9.3.0

Overview

This release addresses several important issues and introduces enhancements to improve your experience with our product. It includes fixes, updates, and new features to make your workflows more efficient and secure.

Changes

1. Resource Tagging

• Issue: Resource tags were not consistently applied to all resources.
• Solution: We've fixed this problem to ensure that resource tags are correctly and uniformly applied, simplifying resource management.

2. Terraform Compatibility

• Issue: Compatibility issues between Terraform v1.6 and older versions.
• Solution: We've addressed these issues, ensuring smooth operations.
• ⏰ terraform version on the deployer is upgraded to v1.6 to be aligned with the latest release. Look at the Additional Notes on upgrading the deployer.

3. IP Address Management

• Issue: Complicated IP address assignment affecting Ansible integration.
• Solution: We've improved the logic for gathering IP addresses by using IMDS, making it more straightforward to work with Ansible.

4. Enhanced Security

• Issue: Pipeline permissions for variable groups and agent pools needed improvement.
• Solution: Enhanced security by assigning proper pipeline permissions, ensuring a more secure environment.

5. Deployer Extension Behavior

• Issue: Deployer extension sometimes displayed unintended configuration details in logs.
• Solution: This issue is resolved, preventing configuration exposure in logs.

6. tfvars File Management

• Issue: Centralized storage of tfvars files was missing for command-line deployments.
• Solution: We now copy tfvars files into the Terraform state storage account, providing better control and organization.

7. Code Readability Enhancements

• Issue: General deployment and code readability needed improvement for both Ansible and Terraform.
• Solution: We've made various code readability enhancements, streamlining deployment and management processes.

Testing

All solutions and improvements have been tested using the SDAF deployment pipelines and the command line to ensure they work effectively.

Additional Notes

If you encounter difficulties upgrading the control plane VM, we recommend manually removing the configure_deployer extension from the VM and then redeploy.

Feedback

We appreciate your feedback and are committed to continuously enhancing your experience with our product.

Please feel free to reach out if you have any questions or require further assistance via issues or discussions.

Release 3.9.2.0

Overview

This hotfix release focuses on enhancements, bug fixes, and general stability improvements for SAP installation.

Problems Addressed

1. Improvements to dynamic BOM processes to accommodate future code changes.
2. Format of some of the terraform modules to enhance readability.
3. Refactor of some of the scripts to improve stability.

Testing

All changes have been tested using the SDAF deployment pipelines.

Release 3.9.0.0

Overview

This release focuses on enhancements, bug fixes, and general stability improvements for SAP installation.

Problems Addressed

1. Lack of support for simple mount for SLES deployments.
2. Absence of support for susChkSrv for SLES HANA deployments. Note: susChkSrv extends the functionality of the main SAPHanaSR HA provider by executing a configurable action when a SAP HANA service is not running on a node.
3. Identified issues during runs:
   • When HANA database runs on ANF volumes, volumes are added to be managed by the pacemaker cluster.
   • Default values for "resource-stickiness" and "migration-threshold" are not set on the HANA cluster.
   • The timeout value of monitor operation for filesystem and ASCS/ERS resources differs from documentation.
   • ASCS/ERS profile changes are sometimes skipped.
4. Other general enhancements.

Solutions Implemented

1. Added new tasks under deploy/ansible/roles-sap/5.6-scsers-pacemaker to support simple mount for SLES deployments.
2. Updated 5.5.3-SAPHanaSR under deploy/ansible/roles-sap/5.5-hanadb-pacemaker to support susChkSrv for SLES HANA deployments.
3. Updated deploy/ansible/roles-sap/5.6-scsers-pacemaker to support the following:
   • Added support for resource-stickiness and migration-threshold for HANA cluster.
   • Added support for timeout value of monitor operation for filesystem and ASCS/ERS resources.
   • Added support for ASCS/ERS profile changes.
4. Updated deploy/ansible/roles-sap/5.5-hanadb-pacemaker to support the following:
   • Added support for resource-stickiness and migration-threshold for HANA cluster.
   • Added ANF volumes to pacemaker cluster.
5. Various files have been updated to support general stability improvements.

Testing

All changes have been tested using the SDAF deployment pipelines.

Release 3.8.3.5

HotFix

• When ansible code failed during the PAS installation with message server or database offline, then error message doesn't have the proper information on the error. With this code change we will be getting below error messages

Release 3.8.3.4

HotFix

• Provides graceful failover with exit code INSTALL:0023, when dynamic BOM download fails