On Thu, May 3, 2012 at 11:59 AM, Loic Dachary l...@enovance.com wrote:
On 05/03/2012 09:58 AM, Robert Collins wrote:
On Wed, May 2, 2012 at 10:28 AM, Loic Dachary l...@enovance.com wrote:
As I wrote in a previous mail, once we manage to provide an
implementation that proves useful, we
On Fri, May 4, 2012 at 4:51 PM, Christopher MacGown
ch...@pistoncloud.comwrote:
Do you envision that writing to AMQP directly, or using the existing
notification API (which seems to be a wrapper over the RPC layer, which is
in turn a wrapper for AMQP)?
The RPC layer is not merely a wrapper
On 05/03/2012 05:25 AM, Andrew Clay Shafer wrote:
Integrating the metering agents as part of the core component, much in
the same way it's currently done in nova.
What specifically is done?
If metering is not integrated in the beginning it will likely never be.
Hi,
I'm refering to
On 05/03/2012 09:58 AM, Robert Collins wrote:
On Wed, May 2, 2012 at 10:28 AM, Loic Dachary l...@enovance.com wrote:
As I wrote in a previous mail, once we manage to provide an implementation
that proves useful, we will be in a position to approach the core OpenStack
components. Integrating
It would be better if all OpenStack core components agreed on unified
interfaces / messages for metering that would be easy to harvest without
installing agents on nodes. This is also true for many services outside of
the OpenStack eco-system. However, much in the same way munin and nagios
On 05/01/2012 09:57 PM, Andrew Clay Shafer wrote:
I'm glad to see people championing the effort to implement metering. Is there
someway to refocus the enthusiasm for solving the metering problem into
engineering a general solution in OpenStack?
I'm just going to apologize in advance, but I
6 matches
Mail list logo
