, Nov 2, 2012 at 4:42 PM, Dan Dyer dan.dye...@gmail.com
mailto:dan.dye...@gmail.com wrote:
Yes, I am assuming the service controller provides a different
stream of data from the lower level VM events. So the question is
how to represent and store this additional meta data
wrote:
On Thu, Nov 1, 2012 at 10:21 AM, Dan Dyer dan.dye...@gmail.com
mailto:dan.dye...@gmail.com wrote:
In some cases, the service controller is actually running inside a
VM. It would not have access to the internals of the VM's. It
maintains its metadata separately from the Nova
to reconcile the information to handle your 2
use cases. Am I missing something?
Nick
On 10/25/2012 12:03 AM, Dan Dyer wrote:
I don't think its just a matter of adding more meters or events for a
couple of reasons:
1. In many cases the metadata I am referring to comes from a different
source than
need to be able to store
meta-data that will allow the usage processing logic to identify
relationships between VM's and provide additional context for
determining billing policy.
Dan Dyer
HP Cloud Services
aka: DanD
___
Mailing list: https
usage as well
as other metrics. Once again we need a way to characterize the
relationships so that processing can associate and filter correctly.
Dan
On 10/24/2012 3:35 PM, Julien Danjou wrote:
On Wed, Oct 24 2012, Dan Dyer wrote:
Use Case 1
Service Owned Instances
There are a set of use
5 matches
Mail list logo
