Open Stack

On Fri, Oct 31, 2014 at 8:30 AM, Abel Lopez <alopgeek at gmail.com> wrote:

> It seems that every release, there is more and more emphasis on
> upgradability. This is a good thing, I've love to see production users
> easily go from old to new.
>
> As an operator, I've seen first hand the results of neglecting the
> databases that openstack creates. If we intend to have users go
> year-over-year with upgrades, we're going to expect them to carry huge
> databases around.
>
> Just in my lab, I have over 100000 deleted instances in the last two
> months.
> Frankly, I'm not convinced that simply archiving deleted rows is the best
> idea. Sure, gets your production databases and tables to a manageable size,
> but you're simply hoarding old data.
>
> As an operator, I'd prefer to have time based criteria over number of
> rows, too.
> I envision something like `nova-manage db purge [days]` where we can leave
> it up to the administrator to decide how much of their old data (if any)
> they'd be OK losing.
>
>
Heat has something like this:
http://docs.openstack.org/developer/heat/man/heat-manage.html

heat-manage purge_deleted [-g {days,hours,minutes,seconds}] [age]

Although I am not sure it is popular:
https://bugs.launchpad.net/heat/+bug/1239377

-Angus


> Think about data destruction guidelines too, some companies require old
> data be destroyed when not needed, others require maintaining it.
> We can easily provide both here.
>
> I've drafted a simple blueprint
> https://blueprints.launchpad.net/nova/+spec/database-purge
>
> I've love some input from the community.
>
> _______________________________________________
> 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/20141031/eb882883/attachment.html>