Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-1907

Usage Metering with Cost Analysis (AWS, Azure, GCP)

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • not-targeted
    • kubernetes
    • None

    Description

      Implement Cost Analysis in Usage Metering for AWS, Azure, GCP platforms.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Need to come up with options/recommendations for Roshani Sanghavi and reassign to further decide definition of done, then scope.

            ingenthr Matt Ingenthron added a comment - Need to come up with options/recommendations for Roshani Sanghavi and reassign to further decide definition of done, then scope.

            Per meeting just now, Roshani Sanghavi is going to catch up with Anil Kumar and Jared Christensen to see what more specifically is needed.

            This could be as simple as delivering a method of usage metering (KV/N1QL/FTS/Analytics ops, storage used).

            Or it could be more complex by gathering for the same time intervals not just the above, but also the network ingress/egress cost on the cloud incurred, the instance usage occurred in the same intervals, etc.  These would then be used with autoscaling, possibly, to turn into basis for usage metering based pricing.

            ingenthr Matt Ingenthron added a comment - Per meeting just now, Roshani Sanghavi  is going to catch up with Anil Kumar  and Jared Christensen  to see what more specifically is needed. This could be as simple as delivering a method of usage metering (KV/N1QL/FTS/Analytics ops, storage used). Or it could be more complex by gathering for the same time intervals not just the above, but also the network ingress/egress cost on the cloud incurred, the instance usage occurred in the same intervals, etc.  These would then be used with autoscaling, possibly, to turn into basis for usage metering based pricing.

            Anil Kumar Assigning this to you for further discussion with DBaaS team or Jared Christensen for scope clarity.

            roshani.sanghavi Roshani Sanghavi (Inactive) added a comment - Anil Kumar  Assigning this to you for further discussion with DBaaS team or Jared Christensen  for scope clarity.
            anil Anil Kumar added a comment - - edited

            At high-level let me define the scope here, so we're all on the same page - 

            • With CAO 2.1, we already provide detailed usage metering for querying and reporting resource usage over an arbitrary period of time. 
            • This feature's scope was to add a business integration layer such as "Configure AWS Billing Data Source," which does cost analysis based on resource usage to make further use of generated reports.
            • There are use cases: 
              • [p0] Chargeback - Currently, it is a significant undertaking for a customer to determine resource usage for their Couchbase deployment. Making it easy for customers to assess fine-grained usage reports for their deployment will drive subscription expansion opportunities because many customers today want to build internal database-as-a-service
              • [p0] Cost analysis for Couchbase Service API - We need granular-level usage cost analysis for each Couchbase services request. For example - data service cost analysis on ops/sec.
              • [p1] On-Demand Pricing - As adoption of public cloud continues to increase, the demand for cloud pricing models that allow customers to pay for only what they use is accelerating. Many words are used to describe this pricing/procurement concept including in-arrears pricing, usage-based pricing, and utility pricing. The key concept underpinning this model is that customers don’t prepay for subscriptions (i.e. annual subscription). Instead, customers are billed based upon the previous billing cycles product usage (i.e. number of hours software is running on servers). Having the ability to automate the process of measuring a customer’s product usage (i.e. number of nodes, cores per node and RAM per node), collecting these measurements every hour, and storing this data in a database that can then be integrate with Salesforce so a customer can be automatically invoiced based on usage is critical for Couchbase’s long-term success. 

             

            anil Anil Kumar added a comment - - edited At high-level let me define the scope here, so we're all on the same page -  With CAO 2.1, we already provide detailed usage metering for querying and reporting resource usage over an arbitrary period of time.  This feature's scope was to add a business integration layer such as "Configure AWS Billing Data Source," which does cost analysis based on resource usage to make further use of generated reports. There are use cases:  [p0] Chargeback - Currently, it is a significant undertaking for a customer to determine resource usage for their Couchbase deployment. Making it easy for customers to assess fine-grained usage reports for their deployment will drive subscription expansion opportunities because many customers today want to build  internal database-as-a-service .  [p0] Cost analysis for Couchbase Service API - We need granular-level usage cost analysis for each Couchbase services request. For example - data service cost analysis on ops/sec. [p1] On-Demand Pricing - As adoption of public cloud continues to increase, the demand for cloud pricing models that allow customers to pay for only what they use is accelerating. Many words are used to describe this pricing/procurement concept including in-arrears pricing, usage-based pricing, and utility pricing. The key concept underpinning this model is that customers don’t prepay for subscriptions (i.e. annual subscription). Instead, customers are billed based upon the previous billing cycles product usage (i.e. number of hours software is running on servers). Having the ability to automate the process of measuring a customer’s product usage (i.e. number of nodes, cores per node and RAM per node), collecting these measurements every hour, and storing this data in a database that can then be integrate with Salesforce so a customer can be automatically invoiced based on usage is critical for Couchbase’s long-term success.   
            anil Anil Kumar added a comment -

            Roshani Sanghavi do you have what you need to scope this for future release? 

            anil Anil Kumar added a comment - Roshani Sanghavi  do you have what you need to scope this for future release? 

            People

              roshani.sanghavi Roshani Sanghavi (Inactive)
              roshani.sanghavi Roshani Sanghavi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty