Project

General

Profile

Actions
Copy link

User story #2997

closed

Clean report database v2 : Add an automatic reporting configured by properties

Added by Vincent MEMBRÉ over 11 years ago. Updated about 11 years ago.

Status:
Released
Priority:
N/A
Assignee:
Jonathan CLARKE
Category:
Web - Maintenance
Target version:
2.5.0~beta1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

To compute compliance rudder needs to store reports sent by the nodes in a database.

Those reports take a huuuge size on disk. So we added a way to archive them in 2.4.
But to actually free disk space, rudder should be able to delete those reports.

This ticket main goal is to provide an automatic database cleaner that will run at a scheduled frequency, based on rudder properties.

Implementation ticket : #2973 (pull request https://github.com/Normation/rudder/pull/9 )
Integration ticket : #2978
Documentation Ticket : not created yet.

This is blocked by #2996, which is very linked (same backend)

Subtasks 1 (0 open — 1 closed)

User story #2973: Allow to automatically clean reports from database (simple version)ReleasedNicolas CHARLESActions

Related issues 2 (0 open — 2 closed)

Blocked by Rudder - User story #2996: Clean report database v1 : Add a manual report deleting ReleasedJonathan CLARKE2012-10-30Actions
Blocks Rudder - User story #2971: Clean reports database v3 : Add a webconfigurable scheduler for automatic report database cleaningRejectedActions
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 11 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 11 years ago

  • Description updated (diff)

Pull request for the implementation issue on https://github.com/Normation/rudder/pull/9

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 11 years ago

  • Description updated (diff)

typo in url

Actions
Copy link
 #4

Updated by Jonathan CLARKE over 11 years ago

  • Status changed from New to In progress
  • Target version set to 2.5.0~beta1

The development part of this (#2973) is pending technical review, and the integration part can be started (#2978)

Actions
Copy link
 #5

Updated by François ARMAND over 11 years ago

  • Status changed from In progress to 13
Actions
Copy link
 #6

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from 13 to 10
  • Assignee changed from Vincent MEMBRÉ to Jonathan CLARKE

Jonathan, could you functionnal review this meta ticket so that we'll be able to merge it for next version ?
Thanks

Actions
Copy link
 #7

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from 10 to Pending release
Actions
Copy link
 #9

Updated by Nicolas CHARLES over 11 years ago

The attributes in the scala code where not coherent with the attributes in the configuration files, so I had to change the scala code

Actions
Copy link
 #10

Updated by Matthieu CERDA over 11 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF