Bug 1042123 - [RFE][oslo]: Common DB purge engine (oslo)
Summary: [RFE][oslo]: Common DB purge engine (oslo)
Keywords:
Status: CLOSED DUPLICATE of bug 1177348
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Upstream M3
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/oslo...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:05 UTC by RHOS Integration
Modified: 2015-02-03 13:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-03 13:16:42 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 21:05:58 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/db-oslo-purge-engine.

Description:

There are several points:

1) Nova & other core projects never delete data from the DBs and uses only soft deleting (There is special column in each table that indicates that entry is deleted).

2) To purge soft deleted records you have to get direct access to DB and do it manually by own script. Or use db-archiving feature that allows you to move soft deleted records from main to shadow tables. But db-archiving:
a) works very slow and as there is a complex logic around moving records from one table to another (we are not able to improve this)
b) db-archiving doesn’t take in account relationships between Tables.
c) db-archiving was implemented in Grizzly, during havana we found and fixed a lot of critical bugs, and didn’t see any bug reports form other, seems like nobody use it in production.
d) We didn’t find use cases for db-archiving.

3) Everybody that use OpenStack in production have some db purge script.

Due to these facts we should implement one purge engine that will be available out of box. This purge engine will cleanup considering of tables relationship. Implementation will be based on sql requests that do all work inside DB (without downloading all DB data) to improve deletions speed.

Purge engine's part of tables relationship control could be used next time to improve shadow tables.

This functionality will be available for administrators through the REST api. And probably we should think about periodic task that will cleanup DB.

Specification URL (additional information):

None

Comment 2 Nir Yechiel 2015-02-03 13:16:42 UTC

*** This bug has been marked as a duplicate of bug 1177348 ***


Note You need to log in before you can comment on or make changes to this bug.