<p dir="ltr">Hey Abel,</p>
<p dir="ltr">We would be in favor of this as well. So much so that we would definitely be willing to put some resources on it. I'll reach out once we're back from Paris.</p>
<p dir="ltr">Great suggestion,<br>
Craig</p>
<div class="gmail_quote">On Oct 31, 2014 2:52 PM, "Abel Lopez" <<a href="mailto:alopgeek@gmail.com">alopgeek@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've added the same blueprint to cinder/glance/etc. yes, the plan was for this to be ${service}-manage feature. <span></span><br><br>On Friday, October 31, 2014, Britt Houser (bhouser) <<a href="mailto:bhouser@cisco.com" target="_blank">bhouser@cisco.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That would imply some extensible plugin type architecture, b/c "all<br>
projects" changes over time and from setup to setup.  So each project<br>
would define its own cleanup routines, but those routines could be called<br>
using a common set of parameters from a single tool.<br>
<br>
Thx,<br>
britt<br>
<br>
On 10/31/14, 8:19 AM, "Maish Saidel-Keesing"<br>
<<a>maishsk+openstack@maishsk.com</a>> wrote:<br>
<br>
><br>
>On 31/10/2014 11:01, Daniele Venzano wrote:<br>
>> On 10/30/14 23:30, Abel Lopez wrote:<br>
>>> As an operator, I'd prefer to have time based criteria over number of<br>
>>> rows, too.<br>
>>> I envision something like `nova-manage db purge [days]` where we can<br>
>>> leave it up to the administrator to decide how much of their old data<br>
>>> (if any) they'd be OK losing.<br>
>> I would certainly use this feature, but please, please, please: make<br>
>> it work across all OpenStack databases, not just for Nova, but also<br>
>> for Cinder, Neutron, etc.<br>
>A Huge +1 for across all projects!!<br>
>Maish<br>
>> Let's try to get something integrated project-wide instead of having a<br>
>> number of poorly documented, slightly inconsistent commands.<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-operators mailing list<br>
>> <a>OpenStack-operators@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
>--<br>
>Maish Saidel-Keesing<br>
><br>
><br>
>_______________________________________________<br>
>OpenStack-operators mailing list<br>
><a>OpenStack-operators@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a>OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div>