Re: [Openstack] [metering] Considerations and Roadmap in Ceilometer (or other component) for Financial Management
On Mon, Jun 02 2014, Lee Calcote (lecalcot) wrote: Is support for these other categories planned for Ceilometer or other components? Definitely not in Ceilometer scope. Some people started a project to handle billing, such as: https://git.openstack.org/cgit/stackforge/cloudkitty/ Cheers, -- Julien Danjou ;; Free Software hacker ;; http://julien.danjou.info signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [metering] Considerations and Roadmap in Ceilometer (or other component) for Financial Management
On Mon, Jun 02, 2014 at 02:52:15AM +, Lee Calcote (lecalcot) wrote: Hi, What support does Ceilometer provide today and what support is planned to provide for financial management? While Ceilometer provides functionality for *metering* and *billing integration* as two categories of financial management, does it provide for others (e.g. *pricing* - a method to set prices on common objects)? I consider that financial management breaks into these categories (and quite possibly others): The main goal of ceilometer is metering, and from what I understand all the billing processing is not something that fit or will in this project. Is support for these other categories planned for Ceilometer or other components? Have these use cases been successfully provided for in Ceilometer to date or have they yet to be achieved - https://wiki.openstack.org/wiki/Ceilometer/blueprints/support-for-advance-s ervice-billing-models? We've started some work around the question, the project is hosted on stackforge : https://github.com/stackforge/cloudkitty Our main goal at the moment is to create reports with billing informations. Everything is gathered directly from ceilometer. In a near future we want to add the pricing informations directly in horizon. At the moment we're not addressing accounting/financial management functions. We've only really worked on what we needed to implement. We would be happy to hear about your use cases to see where the project should head. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [metering] Considerations and Roadmap in Ceilometer (or other component) for Financial Management
On Mon, Jun 02, 2014 at 02:52:15AM +, Lee Calcote (lecalcot) wrote: Hi, What support does Ceilometer provide today and what support is planned to provide for financial management? While Ceilometer provides functionality for *metering* and *billing integration* as two categories of financial management, does it provide for others (e.g. *pricing* - a method to set prices on common objects)? I consider that financial management breaks into these categories (and quite possibly others): The main goal of ceilometer is metering, and from what I understand all the billing processing is not something that fit or will in this project. Your understanding is correct ... directly addressing the billing stage of the pipeline was explicitly a non-goal for ceilometer from the very outset IIRC. Cheers, Eoghan Is support for these other categories planned for Ceilometer or other components? Have these use cases been successfully provided for in Ceilometer to date or have they yet to be achieved - https://wiki.openstack.org/wiki/Ceilometer/blueprints/support-for-advance-s ervice-billing-models? We've started some work around the question, the project is hosted on stackforge : https://github.com/stackforge/cloudkitty Our main goal at the moment is to create reports with billing informations. Everything is gathered directly from ceilometer. In a near future we want to add the pricing informations directly in horizon. At the moment we're not addressing accounting/financial management functions. We've only really worked on what we needed to implement. We would be happy to hear about your use cases to see where the project should head. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [metering] Considerations and Roadmap in Ceilometer (or other component) for Financial Management
Hi Lee, At Rackspace we use StackTach to gather our billing/usage information (with verification and reconciliation). We are heavy into our v3 development currently. While we haven't addressed the financial aspects of billing it might be something worth talking about, though it's a little further down our run way. Gathering requirements. v2 (in production): https://github.com/stackforge/stacktach v3 (in development): https://github.com/stacktach Let me know if you'd like to chat about it with our team. Cheers! -Sandy From: Lee Calcote (lecalcot) [lecal...@cisco.com] Sent: Sunday, June 01, 2014 11:52 PM To: openstack@lists.openstack.org Subject: [Openstack] [metering] Considerations and Roadmap in Ceilometer (or other component) for Financial Management Hi, What support does Ceilometer provide today and what support is planned to provide for financial management? While Ceilometer provides functionality for *metering* and *billing integration* as two categories of financial management, does it provide for others (e.g. *pricing* - a method to set prices on common objects)? I consider that financial management breaks into these categories (and quite possibly others): 1) Pricing - a method to set prices on common objects 2) Showback - a mechanism to allow users to see the calculated cost of their purchase during the ordering process 3a) Run Rates - a mechanism for users to see the recurring cost of the items that they have purchased 3b) Run Rates - a mechanism for administrators to see the recurring cost of the items that their tenants have purchased 4) Billing Integration - real-time financial events that can be consumed by a billing system within an extension point 5) Billing - invoicing and payment transacting 6) Metering - financial management based on measured utilization Is support for these other categories planned for Ceilometer or other components? Have these use cases been successfully provided for in Ceilometer to date or have they yet to be achieved - https://wiki.openstack.org/wiki/Ceilometer/blueprints/support-for-advance-s ervice-billing-models? I expect these questions are answered by each functional category: Pricing - How do I set prices on cloud services? - How do I give one tenant a discount over another tenant? Showback - How much have I, my organization or all my organizations spent? - How much am I about to spend both as a one-time and recurring cost (run rate)? - How much is what I have purchased costing me? Revenue / Run Rates - How much are my tenants spending in my cloud? - Which cloud services are reaping the most revenue (by tenant)? Billing Integration - How do I send costs incurred to my incumbent billing system? Metering - How am I utilizing my resources? - Do I need more or less resources? Billing -What is my bill? Where is my invoice? - Where and how do I send my payment? Are these questions being addressed in Ceilometer or another component? Thanks, Lee ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
