Open Stack

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 services. But
maybe I don't see any valuable usecases.
Anyway, it seems reasonable to have both add_sample and delete_sample in
API or not to have neither.

Thanks,
Nadya


On Fri, Jan 17, 2014 at 3:50 PM, Julien Danjou <julien at danjou.info> wrote:

> 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 be deleted.
> >
> > Should we take attention to this? And find some way to delete all data,
> for
> > example database wipe or patch to ceilometer client...
> > Or just to skip this?
>
> Why would you delete this?
> There's a time-to-live mechanism in Ceilometer to delete old samples.
>
> --
> Julien Danjou
> // Free Software hacker / independent consultant
> // http://julien.danjou.info
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140117/1208eb25/attachment.html>