Right now, Fuel deploys Ceilometer to use the OpenStack mySQL DB for
Ceilometer data, although we’re expecting to utilize MongoDB in the 4.1
Fuel version. This is, as you mention, primarily to address the
performance issues with a shared mySQL DB. That said, I don’t know that
it really changes th
On 01/20/2014 01:29 PM, Dmitry Iakunchikov wrote:
> David,
>
> You're completely right,
>
> The main problem is that ceilometer has possibility to create samples,
> but not to delete. Because of that there is no possibility to remove
> OSTF created data.
1) What is current DB backend for Ceilomet
David,
You're completely right,
The main problem is that ceilometer has possibility to create samples, but
not to delete. Because of that there is no possibility to remove OSTF
created data.
Actually another way is to use time_to_live, but as you sad "As an
operator, I’d expect that my data is r
I¹d like to make sure I understand the question. Is this the scenario?
* A user installs Mirantis OpenStack
* The user runs the Mirantis OpenStack Health Check (OSTF) against
Ceilometer
* The Health Check creates a VM against which ceilometer can collect data
* Ceilometer collects the data from th
On Fri, 2014-01-17 at 12:43 +0200, Dmitry Iakunchikov wrote:
> Ceilometer's tests creates some data which could not be deleted.
> For example: after creation new instance, ceilometer creates new
> meters for this instance and there is no possibility to delete them.
> Even after instance deletion
For now in Fuel we keep samples forever
In case if we will use time_to_live, how long we should keep this data?
2014/1/17 Julien Danjou
> On Fri, Jan 17 2014, Nadya Privalova wrote:
>
> > I would ask in another way.
> > Ceilometer has a mechanism to add a sample through POST. So it looks not
>
: Julien Danjou [mailto:jul...@danjou.info]
Sent: Friday, January 17, 2014 1:35 PM
To: Nadya Privalova
Cc: fuel-...@lists.launchpad.net; OpenStack Development Mailing List (not for
usage questions); Vladimir Kuklin
Subject: Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters
and
On Fri, Jan 17 2014, Nadya Privalova wrote:
> I would ask in another way.
> Ceilometer has a mechanism to add a sample through POST. So it looks not
> consistent not to allow user to delete a sample.
> IMHO, insertion and deletion through REST looks a little bit hacky: user
> always has an ability
Hi guys,
I would ask in another way.
Ceilometer has a mechanism to add a sample through POST. So it looks not
consistent not to allow user to delete a sample.
IMHO, insertion and deletion through REST looks a little bit hacky: user
always has an ability to fake data collected from OpenStack servic
On Fri, Jan 17 2014, Dmitry Iakunchikov wrote:
> Ceilometer's tests creates some data which could not be deleted.
> For example: after creation new instance, ceilometer creates new meters for
> this instance and there is no possibility to delete them. Even after
> instance deletion they would not
Hi,
Ceilometer's tests creates some data which could not be deleted.
For example: after creation new instance, ceilometer creates new meters for
this instance and there is no possibility to delete them. Even after
instance deletion they would not be deleted.
Should we take attention to this? And
11 matches
Mail list logo
