Uploaded image for project: 'OpenStack Strategy'
  1. OpenStack Strategy
  2. RHOSSTRAT-963

Chargeback and Showback capabilities in RHOSO

XMLWordPrintable

    • Icon: Outcome Outcome
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • 50% To Do, 50% In Progress, 0% Done
    • Not Selected
    • 0

      Outcome Overview

      Once this outcome is complete, RHOSO should have the features to report on tenant usage of services and flavors (Chargeback). Tenants should be able to see their usage to forecast and estimate their usage (Showback)

      Success Criteria

      For chargeback to be of use there are several metrics that needs to be available some more important than others. The table bellow lists the metrics that will impact the success of this outcome and if they are important for the MVP.

      Function Metric MVP  Comment
      Compute Flavor Yes Defines the base rate for CPU/RAM bundle (flavor) selected by tenants.
      Compute Uptime Yes Billable hours while instance is in “Powered On” state; base multiplier for flavor cost.
      Compute Lifetime Yes Tracks total lifespan of an instance, even when powered off/shelved. Reflects cost of maintaining configuration & persistent dependencies.
      Compute Ephemeral Storage Yes Local non-persistent storage (ephemeral SSD/flash) tied to instance runtime.
      Network Outbound Bandwith (GB egress) Yes primary billable unit; aligns with public cloud models.
      Network Floating IPs (per allocated IP per hour Yes incentivizes release of unused addresses
      Network Load Balancers (per LB hour) Yes  
      Network Quota Constructs (bill per network/router/port/SG per hour) No Needed soon.
      Networks, subnets, routers, ports, security groups/rules (limited resources)
      Network Load Balancers: per-resource hour & processed bytes ingress No Needed soon
      Network QoS/DSCP tiers & port “speed” flavors No Needed soon
      Network Peering (Neutron-RBAC) No Needed soon
      Storage Block Volumes (GB-monthly by cinder volume type) Yes provisioned capacity; performance tiers
      Storage Snapshots/Backups (GB) Yes retained data billed separately from active volumes
      Storage ObjectStorage Capacity(GB-month) + Egress (GB) Yes  
      Storage File Shares (GB by manila backend) Yes provisioned capacity, tiered by backend
      Storage Object Storage API requests (PUT/GET/DELETE) No Needed soon
      Image Service Image Storage (GB-month by backend) Yes bill for tenant-owned images stored in Glance (backed by Swift or Cinder)
      Image Service Image Count (per image-hour) No optional per-object charge to discourage sprawl
      Image Service Image Transfers (egress GB) No downloads/export bandwidth from Glance
      Image Service Image Operations (per 1k requests) No PUT/GET/DELETE request counts
      Orchestration Stacks (per stack-hour) No  
      Orchestration Change Operations (create/update/delete count) No  
      DNSaaS Hosted Zones (per zone-hour) Yes  
      DNSaaS DNS Records (per record-hour) Yes  
      DNSaaS DNS Querries (per 1M requests) No  
      Identity API Calls / Tokens Issued (per 10k) No  
      Identity Authentication domains configured No  
      Key Management Secrets Stored (per secret-month) No  
      Key Management Certs/Containers (per object-month) No  
      Key Management API Requests (per 10k) No  
      Alarming Active Alarms (per alarm-month) No  
      Alarming Notifications Delivered (per 1k) No  

       

       

      Expected Results (what, how, when)

      What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome?  (possible examples:  unblocking sales, shifts in product metrics, etc. {}{} provide links to metrics that will be used post-completion for review & pivot decisions). {}For each expected result, list what you will measure and +when you will measure it (ex. provide links to existing information or metrics that will be used post-completion for review and specify when you will review the measurement such as 60 days after the work is complete)

       

       

      Post Completion Review – Actual Results

      After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).

       

              Unassigned Unassigned
              rh-ee-sherlofs Simon Herlofsson
              rhos-dfg-cloudops
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: