1. Proposed title of this feature request Support for the SAPStartSrv resource agent for use with running a simplified SAP Instance in Pacemaker clusters. 2. Who is the customer behind the request? Account: Chevron Services Company (745769) TAM customer: yes Joshua Coopman ( jcoopman ) SRM customer: no Strategic: yes 3. What is the nature and description of the request? Customer is requesting that we provide the SAPStartSrv resource agent and assocated tools in order to provide a simplified cluster managed process for SAP Instnaces: SUSE/SAPStartSrv-resourceAgent https://github.com/SUSE/SAPStartSrv-resourceAgent Customer's description of the issue and request: ~~~ What are you experiencing? What are you expecting to happen? We would like to see something similar to this capability created by SuSE Linux for a simplified mounting structure with SAP under Pacemaker: https://www.suse.com/c/simple-mount-structure-for-sap-application-platform/ Define the value or impact to you or the business Today, we actually implement our systems with a simplified mount structure in Azure (as a minor deviation from the documented process from RedHat + Microsoft). While this has not really been a problem functionally, it does have some confusing side effects as shown below: kz2adm> sapcontrol -nr 96 -function GetSystemInstanceList 08.08.2023 19:17:16 GetSystemInstanceList OK hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus kz2-ers, 97, 59713, 59714, 0.5, ENQREP, GRAY kz2-ascs, 96, 59613, 59614, 1, GATEWAY|MESSAGESERVER|ENQUE|WEBDISP, GREEN kz2-ascs, 96, 59613, 59614, 1, GATEWAY|MESSAGESERVER|ENQUE|WEBDISP, GRAY kz2-ers, 97, 59713, 59714, 0.5, ENQREP, GREEN sapkz2-d3pas0, 0, 50013, 50014, 3, ABAP|GATEWAY|ICMAN|IGS, GREEN sapkz2-d3sas0, 1, 50113, 50114, 3, ABAP|GATEWAY|ICMAN|IGS, GREEN We can see that both the ERS and ASCS show one GREEN record and one GRAY record. The GRAY records are on the node where the service is not active and the GREEN records are on the node where the service is active. Functionally, everything has been working fine this way for 5+ years... but we never knew the cause until recently. As we are now exploring the Microsoft ACSS capabilities (which require registering with the Message server) we cannot as that service is detecting multiple ASCS nodes. After some research, we learned that this appears to be because both nodes have access to the profile directories for both ASCS and ERS. We then learned of the SuSE implementation mentioned in the description, which we think is a much cleaner and simpler solution. ~~~ 4. Why does the customer need this? (List the business requirements here) The new RA will provide a simpler and easier manage method of running SAP instances within pacemaker, then what's currently available. 5. How would the customer like to achieve this? (List the functional requirements here) Add the "SAPStartSrv" resource agent and other needed services, for use within pacemaker. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. We would need to test the functionality of the Resource Agent and SAP instnaces running within a pacemaker cluster. This will require testing of all required functionalities, such as starting / stopping / monitoring the resource on each node, and testing of failover behaviors. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? Yes: https://github.com/SUSE/SAPStartSrv-resourceAgent 8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? None listed, and customer may already be running this config. 9. Is the sales team involved in this request and do they have any additional input? Not that I am aware of. 10. List any affected packages or components. resource-agents-sap 11. Would the customer be able to assist in testing this functionality if implemented? They should be able to, and seem to be already running this configuration.