Provision of Turbonomic Operator Resource Mappings for the Cloud Pak for Business Automation to allow automated resource management

IBM Turbonomic Application Resource Management is used to dynamically manage IT resources to ensure application performance while avoiding infrastructure waste. Applying the Turbonomic Kubernetes Optimization use case to the Cloud Pack for Business Automation results in resourcing decisions scaling the CP4BA workloads, scaling the underlying OpenShift cluster and optimize the workload placement in the cluster at runtime (see https://www.ibm.com/products/turbonomic/kubernetes for more details).

 IBM Turbonomic natively support updating container specs for scaling, but if a workload is operator controlled, as it is the case for CP4BA, the operator will revert any changes to the resource setting given by the operator.

 Therefore, for executing Turbonomic actions (resource decisions) wither manually by a click in the UI or automatically, it is required to provide Turbonomic with the information how to change resource settings via the operator. For this purpose, Turbonomic provides so a mean for implementing the interface to the operator the called Operator Resource Mapping (https://github.com/turbonomic/orm/tree/master).

 Operator Resource Mapping (ORM) is a map to allow assets like Kubeturbo (https://github.com/turbonomic/kubeturbo/wiki, the Turbonomic mediation POD for orchestrating Kubernetes) to manage resources in an Operator managed Kubernetes cluster, for example to vertically scale containers (https://github.com/turbonomic/kubeturbo/wiki/Action-Details#resizing-vertical-scaling-of-containerized-workloads) or horizontally scale pods (https://github.com/turbonomic/kubeturbo/wiki/Action-Details#slo-horizontal-scaling). ORM works at operand basis, user defines which operand holds the desired status of which resources so that other assets can coordinate resource changes.

 Such an operator resource mapping ideally will be provided by the development team of the operator because they know best where resource definitions are specified and when the mapping needs to be adapted to reflect changes to the operator. CloudPak for Integration was the first adopter and provides ORMs to enable resource management using IBM Turbonomic. Thus, there some ORMs for common services are already available also for the use with CP4BA. Besides that, the CloudPak team can provide recommendation for application specific Turbonomic policies.

 Please provide Operator Resource Mappings for the CP4BA workloads to enable dynamic resource management using IBM Turbonomic.