<div dir="ltr"><div><div><div><div>David,<br><br></div>You're completely right,<br><br></div>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.<br>
<br></div>Actually another way is to use time_to_live, but as you sad "As an operator, I’d expect that my data is retained even for items that have been removed"(c)<br></div><div><div><div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014/1/17 David Easter <span dir="ltr"><<a href="mailto:deaster@mirantis.com" target="_blank">deaster@mirantis.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div>I’d like to make sure I understand the question. Is this the scenario?</div><ul><li>A user installs Mirantis OpenStack</li><li>The user runs the Mirantis OpenStack Health Check (OSTF) against Ceilometer</li>
<li>The Health Check creates a VM against which ceilometer can collect data</li><li>Ceilometer collects the data from this VM for an amount of time and stores the data in mySQL</li><li>The Health Check then ends the test, removing the VM</li>
<li>The data collected about this sample VM is retained in mySQL and is not removed.</li></ul><div>Is this basically correct?</div><div><br></div><div>If so, I’d ask if Ceilometer removes data from VM’s or nodes that have been deleted from OpenStack during normal operation or if the data is retained in the run-time scenarios as well? If so, wouldn’t this be a general requirement to remove data about entities that no longer exist in the environment vs. an issue specific to Health Check (OSTF)?</div>
<div><br></div><div>As an operator, I’d expect that my data is retained even for items that have been removed, but I agree that there should be a way for an operator to make a decision to remove stale data – either based on time or as a manually executed operation. Removing data automatically right away could lead to a loss of historical information that could be used for longer term analysis and billing.</div>
<div><br></div><div>Or am I misinterpreting the situation and Ceilometer already allows for deletion of data – and the question is just whether we should remove the data collected during the test? If that is the only question, then yes – we should remove the data after the test is done.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>-Dave Easter</div><div><br></div><span><div style="padding:3pt 0in 0in;text-align:left;font-size:11pt;border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) -moz-use-text-color -moz-use-text-color;font-family:Calibri">
<span style="font-weight:bold">From: </span> Dmitry Iakunchikov <<a href="mailto:diakunchikov@mirantis.com" target="_blank">diakunchikov@mirantis.com</a>><br><span style="font-weight:bold">Date: </span> Friday, January 17, 2014 at 5:10 AM<br>
<span style="font-weight:bold">To: </span> Nadya Privalova <<a href="mailto:nprivalova@mirantis.com" target="_blank">nprivalova@mirantis.com</a>>, "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>>, Dmitry Iakunchikov <<a href="mailto:diakunchikov@mirantis.com" target="_blank">diakunchikov@mirantis.com</a>>, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>>, Vladimir Kuklin <<a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a>>, "<a href="mailto:fuel-dev@lists.launchpad.net" target="_blank">fuel-dev@lists.launchpad.net</a>" <<a href="mailto:fuel-dev@lists.launchpad.net" target="_blank">fuel-dev@lists.launchpad.net</a>><br>
<span style="font-weight:bold">Subject: </span> Re: [Fuel-dev] [openstack-dev] [OSTF][Ceilometer] ceilometer meters and samples delete<br></div><div><div><div><br></div><div dir="ltr"><div>For now in Fuel we keep samples forever<br>
<br></div>In case if we will use time_to_live, how long we should keep this data? <br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014/1/17 Julien Danjou <span dir="ltr"><<a href="mailto:julien@danjou.info" target="_blank">julien@danjou.info</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On Fri, Jan 17 2014, Nadya Privalova wrote:<br><br>
> I would ask in another way.<br>
> Ceilometer has a mechanism to add a sample through POST. So it looks not<br>
> consistent not to allow user to delete a sample.<br>
> IMHO, insertion and deletion through REST looks a little bit hacky: user<br>
> always has an ability to fake data collected from OpenStack services. But<br>
> maybe I don't see any valuable usecases.<br>
> Anyway, it seems reasonable to have both add_sample and delete_sample in<br>
> API or not to have neither.<br><br></div>From the user PoV, that totally makes sense, agreed.<br><span><font color="#888888"><br>
--<br>
Julien Danjou<br>
# Free Software hacker # independent consultant<br>
# <a href="http://julien.danjou.info" target="_blank">http://julien.danjou.info</a><br></font></span></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><div>With Best Regards<br></div>QA engineer Dmitry Iakunchikov<br>
</div></div></div></div>
--
Mailing list: <a href="https://launchpad.net/~fuel-dev" target="_blank">https://launchpad.net/~fuel-dev</a>
Post to : <a href="mailto:fuel-dev@lists.launchpad.net" target="_blank">fuel-dev@lists.launchpad.net</a>
Unsubscribe : <a href="https://launchpad.net/~fuel-dev" target="_blank">https://launchpad.net/~fuel-dev</a>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a>
</span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><div>With Best Regards<br></div>QA engineer Dmitry Iakunchikov<br></div>
</div></div></div></div></div></div></div>