Feature Overview

Improvements to the cost model for M8, that will reflect new additions to the cost model so it is closer to the final requirements.

High-Level description of the feature

Goals

• As a price admin, I want to be able to configure my rates to reflect the main costs of OCP: subscription, OSD (both managed by RH and managed by the customer),

Requirements

Support for additional capabilities in the cost model to reflect more use cases that customer have asked for modeling costs:

• Distribution of costs include any cost (raw, markup, price list costs)
• Markups are applied to the source (i.e. markup on a OCP running on AWS will be applied to AWS)
• You can add more than one rate for each rate type (i.e. you can add more than one cluster rate per node)
• Support of different rates depending on a selection of tags
• Support for default rates and price models

Out of Scope

Requirements to support properly subscription modeling are not included here:

• Support for minimum steps and rates that are longer than a month (i.e. OpenShift subscriptions are sold by pair of sockets and year, so any usage below that will be associated to the minimum and not to a percentage of it)
• Support for tiers in rates
• Discounts

Background, and strategic fit

Although cost management does not try to cover all use cases of a rating engine, there is a minimum rating capabilities that need to be supported to properly reflect the costs of running OCP in production and performing chargeback/showback to users.
For that reason, we need to be able to model the costs in a way that at least provides support for the main cost models associated to OpenShift, so that the customer can have a reliable picture of costs and take decisions based on that.

Why is this important?:

Chargeback / showback is a key use case for cost visibility and analysis.

Examples

• The customer wants to model their costs after OSD, and wants to apply a 100% discount on the AWS costs to substitute them from the costs calculated on the cost model
• The customer wants to apply a monthly cost that models the subscription costs, and a monthly costs that is modeling the maintenance costs, as they are associated to different cost centers