Two regions case:
If you want to get the meters for TenantA from 'swift-cluster-1'
specifically. According to the API design we have now, there is no API
can do that directly unless you do some complex API calls combination.
I think you can use:
GET
On Fri, Nov 23 2012, shengjie_...@dell.com wrote:
Two regions case:
If you want to get the meters for TenantA from 'swift-cluster-1'
specifically. According to the API design we have now, there is no API
can do that directly unless you do some complex API calls combination.
I think you can
Hi,
You can deploy several ceilometer and use several databases, or just one and
use a different 'source' field for each of your region/cluster to
differentiate where meters come from.
Thanks, Julien, I didn't know source it's meant to be presenting region/cluster
info. I guess this wiki
You can deploy several ceilometer and use several databases, or just one and
use a different 'source' field for each of your region/cluster to
differentiate where meters come from.
Let's say if you deploy one ceilometer instance for two swift clusters
'swift-cluster-1' and 'swift-cluster-2'.
On Thu, Nov 22 2012, shengjie_...@dell.com wrote:
Let's say if you deploy one ceilometer instance for two swift clusters
swift-cluster-1' and 'swift-cluster-2'. According to the design, if we use
source' field for region/cluster to tell what cluster the meters come from.
The Ceilometer API
Hi,
Has anybody come across the scenario you need to deploy two or more openstack
swift or nova clusters for whatever DR or HA reasons. How Ceilometer is going
to cope with that? Just wondering is there any plans or blueprints addressing
the usage data replication/distinguish/isolation among
On Tue, Nov 20 2012, shengjie_...@dell.com wrote:
Has anybody come across the scenario you need to deploy two or more
openstack swift or nova clusters for whatever DR or HA reasons. How
Ceilometer is going to cope with that? Just wondering is there any plans or
blueprints addressing the usage
7 matches
Mail list logo