Feature #150
one.db clean up
| Status: | Closed | Start date: | 09/10/2009 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 5.4 | |||
| Resolution: | fixed | Pull request: |
Description
one.db is after over 1700 VMs full from the old vm_attributes, it would be nice if oned could implement a garbage collector on the db.
Related issues
Associated revisions
History
#1
Updated by Ruben S. Montero over 11 years ago
- Target version changed from Release 1.4 to Release 1.4.2
Just, updating the issue for its evaluation for OpenNebula 1.4.2
#2
Updated by Javi Fontan over 10 years ago
- Status changed from New to Closed
- Resolution set to wontfix
This does not happen in 2.0 series
#3
Updated by Ruben S. Montero almost 6 years ago
- Tracker changed from Feature to Backlog
- Status changed from Closed to Pending
- Priority changed from Low to High
- Target version changed from Release 1.4.2 to Release 5.0
This can be implemented in two ways, either as a script for onedb patch or as a core operation.
#4
Updated by Ruben S. Montero over 5 years ago
- Tracker changed from Backlog to Feature
#5
Updated by Ruben S. Montero about 5 years ago
- Tracker changed from Feature to Backlog
#6
Updated by Ruben S. Montero almost 5 years ago
- Target version changed from Release 5.0 to Release 5.4
#7
Updated by Ruben S. Montero over 4 years ago
- Related to Feature #4937: Database toolset enhancements added
#8
Updated by Ruben S. Montero about 4 years ago
- Tracker changed from Backlog to Feature
- Assignee set to Javi Fontan
#9
Updated by Ruben S. Montero about 4 years ago
- Status changed from Pending to Closed
- Resolution set to fixed