Is it your assumption that there will be one metering service per
installation or one per service (i.e swift, nova)? My assumption would be
a single metering service, so the API would need to handle some additional
use cases:
-list services supported
-list metrics for a service type
-get metric
A question/comment about the scope of the schema or maybe the architecture.
Assuming the services will provide the instrumentation to populate the raw
metric data, it seems likely that you will need to define an interface
between the services/agents
that are providing the data and the metering
2 matches
Mail list logo
