Hi guys,
For those of you who wanted to try out HBase as the backend for Ceilometer.
Glad to let you know the document for HBase configuration is available now on
openstack docs:
http://docs.openstack.org/developer/ceilometer/configuration.html#hbase
If you had any issues or questions, feel
If Ganglia has interest in ceilometer data, we can achieve it through a
specific publisher, to put data into Gangalia.
@yunhong, So it is more like the approach to CW or Synaps, isn't it? if the
monitoring system is interested in the meters from Ceilometer, we can have
different publishers to
Hi guys,
Just out of curiosity, Have we ever had any previous threads discussing about
possibility of integrating Ceilometer with ganglia as a monitoring approach?
Didn't manage to find any from the mailing list archive.
Thanks,
Shengjie
___
Mailing
Hi Julien,
Just look at the blueprints and your post, seems like there is some effort
around synaps, also something around heat, cloudwatch. Just trying to get a
clear picture about the vision and direction around monitoring area.
Shengjie
___
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
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'.
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
Hi guys,
The blueprint is registered :
https://blueprints.launchpad.net/ceilometer/+spec/hbase-storage-backend, Any
idea what's the next step ? :)
Shengjie
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Implementing? :)
And eventually adding more blueprint to depends on if you can't implement
this one directly because of some missing stuff.
Two questions:
1. Does it need to be approved first, what's the process to get it
approved/assigned to a release? Btw, I was trying to add Julien in
Thanks Julien, I will write up a blueprint soon.
Shengjie
-Original Message-
From: Julien Danjou [mailto:jul...@danjou.info]
Sent: 07 November 2012 18:12
To: Min, Shengjie
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [ceilometer] Hbase storage backend for Ceilometer -
Hi Doug,
+1
It will be good to see if the storage API design works for other backends like
HBase.
The first glance I had on ceilometer/storage/base.py, the design of basic
storage class does look ok to work with.
The only challenge is that the Hbase schema is not as flexible as traditional
Hi,
I am looking for a way to propose a blueprint to the ceilometer team - Adding
Hbase storage backend for ceilometer. Currently we have only MongoDB and
SQLalchemy as the possible ceilometer storage backend. Given the storage
interface is clearly designed and allows us to have different
13 matches
Mail list logo
