Re: [openstack-dev] [Bilean][CloudKitty][Telemetry] Open discussionaround Bilean and existing OpenStack components
On Thu, Jul 07, 2016 at 09:50:02AM +0800, 吕冬兵 wrote: > Hi, > > I'm sorry to see this discussion so late:). Thanks for attention. > > I don't oppose to contribute to add trigger-based solution to > CloudKitty, I just want to know if it's possible to support > trigger-based for CloudKitty based on now arch, pls generally describe > how. And another thing I want to make sure is that if it's good to mix > two different solution in one component. Hi, At the moment we have an arch that looks like this [collector] <-> [orchestrator] <-> [rating, storage, etc] The orchestrator is responsible of polling data from different backends using collectors. We are currently working on a refactor of the internal architecture, we plan on having rating engines as drivers to ease transitions and possibility to fully integrate with other engines. And we'll add the "on demand collect" which is basically a smarter rating engine. We can easily do something like this: [events] ^ | v [collector] <-> [orchestrator] <-> [rating, storage, etc] Which is just adding notification handling to the orchestrator. Events will then be processed by the rating engine. Everything can be enabled/disabled easily using configuration so that users can choose what type they need (poll/event). I don't see what can be the blocking point here. The new rating engine is on the agenda of next Monday meeting, we can add a point to talk about collaboration on event based rating. I'm available if you need any information. Cheers, Stéphane __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Bilean][CloudKitty][Telemetry] Open discussionaround Bilean and existing OpenStack components
Hi, I'm sorry to see this discussion so late:). Thanks for attention. I don't oppose to contribute to add trigger-based solution to CloudKitty, I just want to know if it's possible to support trigger-based for CloudKitty based on now arch, pls generally describe how. And another thing I want to make sure is that if it's good to mix two different solution in one component. -- Original -- From: "Stéphan Albert"; Date: Fri, Jul 1, 2016 11:37 PM To: "openstack-dev"; Subject: [openstack-dev] [Bilean][CloudKitty][Telemetry] Open discussionaround Bilean and existing OpenStack components Hi, I would like to continue the discussion that started in the [review][1] for the Big-Tent integration of the project Bilean. In the [review][1] the Bilean team stated that a new project was needed to overcome limitations of existing components. In this thread, I would like to have an open discussion about what features are lacking in the available components and what needs to be done to integrate the Bilean use case with the current components. I'm not opposed to changes and new features in CloudKitty, and I'm pretty sure that trigger-based billing can be integrated in CloudKitty's codebase. From my perspective, CloudKitty team is a small team and having two teams working on rating/billing is just scattering contributions and is detrimental to both projects. It brings confusion to users minds about what components should be used. We can add this topic to our meeting agenda, so we can have a talk on IRC. I'm hoping we'll find a solution that benefits existing projects and enables you to implement your trigger-based billing solution. Cheers, Stéphane [1]: https://review.openstack.org/#/c/334350/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
