Project

General

Profile

Actions

User story #2978

closed

Handle automatic reports cleaning properties

Added by Vincent MEMBRÉ about 12 years ago. Updated over 9 years ago.

Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

In #2973 we add an automatic report cleaner in Rudder.

To make it work we set up some new properties in rudder configuration file (/opt/rudder/etc/rudder-webapp.conf).

We should add a migration script that add the new properties and set them to the default value.

Here is the extract of the property file concerning the automatic process

###########################
# Automatic reports cleaning ###########################################################
###########################

#
# Automatic reports cleaning
# This allows you to schedule automatically clean reports (archive or delete)
#

#
# TTL are the maximum age (in days) of reports before archiving (archive.TTL)
# or deleting (delete.TTL)
#
# A value equal to 0 or lower means disable automatic archiving/deleting.
#
# If the archive TTL is greater than the delete TTL then archiving will be disabled
# as there will be no reports to archive (they would be deleted first).
#
# Defaults: archive after 30 days, delete after 90 days.
#

rudder.batch.reportscleaner.archive.TTL=30
rudder.batch.reportscleaner.delete.TTL=90

#
# Schedule option for automatic cleaning
# Automatic cleaning can be scheduled:
#  - every hour at the minute past the hour of your choice
#  - every day at the time of your choice
#  - every week on the day at the time of your choice
#
# Default frequency: daily
rudder.batch.reportscleaner.frequency=daily

# Defaults: minute=0, hour=0, day=Sunday

# Which minute the cleaner should be run on.
# Values  : [0-59]
# Default : 0
rudder.batch.databasecleaner.runtime.minute=0

# Which hour the cleaner should be run on.
# Values : [0-23]
# Default : 0
rudder.batch.databasecleaner.runtime.hour=0

# Which day the cleaner should be run on.
# Values : monday | tuesday | wednesday | thursday | friday | saturday | sunday
# Default : sunday
rudder.batch.databasecleaner.runtime.day=sunday

We should at least add the property and maybe some comments :

###########################
# Automatic reports cleaning ###########################################################
###########################

# Defaults: archive after 30 days, delete after 90 days.

rudder.batch.reportscleaner.archive.TTL=30
rudder.batch.reportscleaner.delete.TTL=90

# Default frequency: daily
rudder.batch.reportscleaner.frequency=daily

# Values  : [0-59]
# Default : 0
rudder.batch.databasecleaner.runtime.minute=0

# Values : [0-23]
# Default : 0
rudder.batch.databasecleaner.runtime.hour=0

# Values : monday | tuesday | wednesday | thursday | friday | saturday | sunday
# Default : sunday
rudder.batch.databasecleaner.runtime.day=sunday
Actions #1

Updated by Vincent MEMBRÉ about 12 years ago

This is not to be pushed until #2973 has not been accepted.

I'll update that ticket when it will be the case.

Actions #2

Updated by Nicolas PERRON about 12 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 #3

Updated by Vincent MEMBRÉ about 12 years ago

  • Target version deleted (2.5.0~beta1)
  • Parent task set to #2997

This issue is the integration part of #2997.

Actions #4

Updated by François ARMAND almost 12 years ago

  • Tracker changed from Bug to Enhancement
Actions #5

Updated by François ARMAND almost 12 years ago

  • Assignee set to Nicolas PERRON
Actions #6

Updated by François ARMAND almost 12 years ago

  • Tracker changed from Enhancement to 6
Actions #7

Updated by Jonathan CLARKE almost 12 years ago

  • Target version set to 2.5.0~beta1
Actions #8

Updated by Jonathan CLARKE almost 12 years ago

  • Status changed from New to 8
  • Assignee changed from Nicolas PERRON to Matthieu CERDA

This can be done by checking for the properties in rudder-upgrade.

Actions #9

Updated by Matthieu CERDA almost 12 years ago

  • Status changed from 8 to Pending technical review
  • Assignee changed from Matthieu CERDA to Jonathan CLARKE
  • % Done changed from 0 to 100
Actions #10

Updated by Jonathan CLARKE almost 12 years ago

  • Status changed from Pending technical review to 12

Matthieu CERDA wrote:

Ready to review here: https://github.com/Normation/rudder-packages/pull/6

Looks fine to me.

Actions #11

Updated by Matthieu CERDA almost 12 years ago

  • Status changed from 12 to Pending release

Applied in changeset commit:3e5b87bbf46993034d646ebb96d0b9390394c40e.

Actions #12

Updated by Matthieu CERDA almost 12 years ago

  • Status changed from Pending release to Released
Actions #13

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
  • Parent task deleted (#2997)
Actions #14

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions #15

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from 6 to User story
Actions

Also available in: Atom PDF