<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><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 id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Dmitry Iakunchikov <<a href="mailto:diakunchikov@mirantis.com">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">nprivalova@mirantis.com</a>>, "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, Dmitry Iakunchikov <<a href="mailto:diakunchikov@mirantis.com">diakunchikov@mirantis.com</a>>, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>>, Vladimir Kuklin <<a href="mailto:vkuklin@mirantis.com">vkuklin@mirantis.com</a>>, "<a href="mailto:fuel-dev@lists.launchpad.net">fuel-dev@lists.launchpad.net</a>" <<a href="mailto:fuel-dev@lists.launchpad.net">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><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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">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 class="HOEnZb"><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>
--
Mailing list: <a href="https://launchpad.net/~fuel-dev">https://launchpad.net/~fuel-dev</a>
Post to : <a href="mailto:fuel-dev@lists.launchpad.net">fuel-dev@lists.launchpad.net</a>
Unsubscribe : <a href="https://launchpad.net/~fuel-dev">https://launchpad.net/~fuel-dev</a>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</span></body></html>