Feature Overview

Purpose:  This document describes the use case and proposes a technical implementation to modify an existing Red Hat product (The Cost Explorer) to fulfill critical requirements for Red Hat’s customers in the sector of Finance and Ensurances in need to comply to BAFIN regulations.

Goals

Providing functionality to cover the basic requirements from BAFIN (EMEA) regulations. The final goal shall be to provide the same functionality as other Cost services in cloud infrastructures provide.

The focus is in regards to:

• Cost Management improvement for disconnected onPrem deployments COST-2704

• Cost Management improvement for AI and GPU workloads COST-3027 COST-5109 
• Cost Management improvement for Signals (COST-todo)
• Cost Management improvement for Network I/O (COST-todo)
• Cost Management improvement for Disk I/O (COST-todo)

  Requirements

The major requirements to consuder CMMO as alternative for regulated organizations is  COST-2704

For compliance reason of PCI-DSS4.0 Signal, Network and Disk Cost management shall be provided (order of priority as written) as documenting the complete path is a mandatory item for the regulated sector.

Background, and strategic fit

The best way to treat this is that there is no internet or proxy available and everything needed by the application should be self-contained within the application.

All required Cost data sources shall come from OpenShift internals.

Assumptions

It is assumed that the image or operator will be hosted alongside OpenShift Container Platform images or operator images in the Red Hat registry or in quay.io

It is assumed that the images can be released when updates are made to the Cost Explorer

It is assumed that the On-Premise Cost Explorer can be run on an OpenShift Container Platform.

Customer Considerations

Customers should be able to host the application container images and or related operator images on the disconnected registries and are expected to be able to install and configure the application.

Documentation Considerations

Usual user guides for deploying and configuring the application will be needed.

Customers running disconnected multi-tenant clusters are able to use the on-premise cost explorer to apply chargeback to their various customers and tenants.

This feature will need new content and some update to the existing Cost Management Metrics Operator content to show customers how the two are used on disconnected clusters.

• Customers will need to understand how to install and configure this application
• Customers will use this feature to implement chargeback for the multitenant clusters and be able to apply cost models and markup to their tenants
• Similar reference to the Cost Management and Metrics Operator where this feature is the complement to have the full coverage for chargeback story
• New Content, Updates to existing content, and Release Notes

Questions

 ** 

Recommendations from the regulations are based upon Cloud provider examples