Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-1320

Understand the costs of running applications in OpenShift

XMLWordPrintable

    • Market Problem
    • 41% 41%

      Market Problem

      Running containers on-prem or in the cloud implies 

      Adding visibility about the costs of the different components and parts of OpenShift running on-prem or in the cloud.

      Making sure that you can map your costs to internal Kubernentes components (projects, clusters, nodes), and also to higher degree elements (using labels)

      Objective 

      Make it possible for a customer to visualize costs in different ways and integrate the information into third party applications using the API

      Why it Matters

      • Lowers the barrier to use Kubernetes / OpenShift providing back visibility about the resource utilisation
      • Enhances the capabilities of OpenShift to support multi-tenant environments, providing a better understanding of how costs are related to each initiative, department, or application
      • Helps to justify the investment in Kubernetes to groups within the customer that care about the ROI and TCO of the IT investments.

      Illustrative User Stories or Scenarios

      • As an operator, I want to be able to identify patterns in my costs
      • As a finance officer, I want to distribute the costs of the infrastructure and its support and showback the information to the different groups that are using the platform
      • As a business owner, I want to understand the costs of my application

      Expected Outcomes

       

      Effect

      This Section: Effect is the expected outcome within the market. There are two dimensions of outcomes; growth or retention. This represents part of the “why” statement for a feature.

      • Position OpenShift as a platform that not only provides rapid development cycles, but also add resource and cost optimization on top of it.
      • Reduce the 
      • ...

      Partner

      This Section: Partner is any specific delivery vehicle requirements. These are feature components that MUST be delivered in concert with or through a particular BU external product.

      This represents part of the “how” statement for a feature. This would be the optional only category.

      Additional/tangential areas for future development (TBK)

      • It will be possible to integrate with third party tools that provide costs
      • It will be possible to integrate with tools that provide information about the application performance and metrics to provide KPI based on those metrics

       

            pgarciaq@redhat.com Pau Garcia Quiles
            pgarciaq@redhat.com Pau Garcia Quiles
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: