sap.sap_operations.quality role – Role to run SAP quality checks

Note

This role is part of the sap.sap_operations collection.

It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it use: ansible-galaxy collection install sap.sap_operations.

To use it in a playbook, specify: sap.sap_operations.quality.

Entry point main – Role to run SAP quality checks

Synopsis

  • Role to run SAP quality checks

  • Quality checks are available in Azure SAP repository https://github.com/Azure/SAP-on-Azure-Scripts-and-Utilities.git

  • How role works

  • Ansible facts are collected

  • Information from sap hostagent is collected - what databases are installed, what instances are installed, what processes are running, etc.

  • Information from Azure instance metadata service is collected instance type, data disks types, resource group, region (location), etc.

  • All collected information is available in the quality_context variable for each check.

  • A lot of checks are skipped and not executed on the host based on following rules

    1. only checks that run in local mode executed

    1. only os checks are executed (not powershell)

    1. only checks without postprocessing command are executed

    1. only checks for VMs are executed, checks for HLI are skipped

    1. if ha status collected (true or false) is in the list of ha statuses in the check - only when check is executed

    1. checks are executed for relevant os family (suse or redhat) and for relevant os versions

    1. only checks for FencingAgent as high availability agent are executed

    1. checks are executed if one of the following is true

    1. check.role contains ‘db’ and respective database is detected by sap hostagent

    1. check.role contains instance types that are detected by sap hostagent.

  • Instance types (ASCS, ERS) are determined using processes detected by sap hostagent

  • Limitations

  • Role tested only on single instance

  • Role tested only with HANA and ASE databases and works only with these databases (configuration has to be changed)

  • Role does not run checks with postprocessing commands

  • Role does not run powershell checks - only OS checks

  • User executing role should be able to sudo to root

  • Role does not yet support RHEL 9