Project

General

Profile

Actions

User story #2973

closed

User story #2997: Clean report database v2 : Add an automatic reporting configured by properties

Allow to automatically clean reports from database (simple version)

Added by François ARMAND over 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Maintenance
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

In Rudder 2.5, we want to provide a UI to configure job frequency of report cleaning, see #2971.

But the bug is so impacting for our user that we want to try to implement a simplified version for Rudder 2.4, based on #2972 and a textfile-based configuration.

Properties of the text file will be:

- age (in days) before archiving report
- age (in days) before deleting report
- an age of 0 (or less) means "no automatic cleaning"
- frequency of the job:
- hourly + minutes when the job is executed,
- daily + hours/minutes when the job is executed,
- weekly + name of the day/hours/minutes when the job is executed.

Add in the DB management page a message: "Automatic cleaning execution can be configured thanks to parameters ... of config file."
(Even better: "Current parameters: ...")

We also have to add new event logs for automatically executed cleaning.

As for #2972, the final acceptance in Rudder 2.4 is subject to the quantity/impact of code needed to add that feature.


Related issues 1 (0 open1 closed)

Blocked by Rudder - User story #2972: Allow to delete report from databaseReleasedVincent MEMBRÉ2012-10-30Actions
Actions #1

Updated by François ARMAND over 11 years ago

  • Description updated (diff)
Actions #2

Updated by Vincent MEMBRÉ over 11 years ago

  • Status changed from 2 to Pending technical review

I added a way to provide an automatic reports cleaner by setting some properties in rudder-webapp.properties.

When this is accepted some packaging must be done (#2978).

I made a pull request about that, https://github.com/Normation/rudder/pull/5

I change this ticket status into "Technical review"

Actions #3

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.0~rc1 to 2.5.0~beta1

The new feature about automation of DB management tasks will not be included in Rudder 2.4. Then, postponed to Rudder 2.5

Actions #4

Updated by Vincent MEMBRÉ over 11 years ago

  • Parent task set to #2997

This is the implementation part of #2997

Actions #5

Updated by Vincent MEMBRÉ over 11 years ago

As we can't change pull request target, I made another pull request about that issue, https://github.com/Normation/rudder/pull/9

technical review can now be done.

Actions #6

Updated by François ARMAND over 11 years ago

  • Tracker changed from Bug to Enhancement
Actions #7

Updated by Vincent MEMBRÉ over 11 years ago

  • % Done changed from 0 to 100
Actions #8

Updated by Nicolas CHARLES over 11 years ago

  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Actions #9

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from Pending technical review to 12

This is valid, thank you Vincent !

Actions #10

Updated by Vincent MEMBRÉ over 11 years ago

  • Status changed from 12 to Pending release
Actions #11

Updated by Matthieu CERDA over 11 years ago

  • Status changed from Pending release to Released
Actions #12

Updated by Benoît PECCATTE about 9 years ago

  • Tracker changed from Enhancement to User story
Actions

Also available in: Atom PDF