User story (meta) #2363

Add a datatable to store version information

Added by François ARMAND about 2 years ago. Updated about 1 year ago.

Status:Released Start date:2012-03-06
Priority:2 Due date:
Assignee:Jonathan CLARKE % Done:

100%

Category:-
Target version:Rudder - 2.4.0~alpha6

Description

We need to have a table to store information about the current version, as detected by the migration script.

That table would at least store the current XML "fileFormat" version.

Associated revisions

Revision 21e1722e
Added by François ARMAND about 2 years ago

Issue #2363: add SQL instruction to create the MigrationEventLog table and the corresponding migration schema

Revision 797ccdbc
Added by Matthieu CERDA almost 2 years ago

Fixes #2363: Added the migrationeventlog 2.3-2.4 migration script to the rudder-webapp package

Revision f0d5679f
Added by Matthieu CERDA almost 2 years ago

Fixes #2363: Added the migrationeventlog 2.3-2.4 migration script to the rudder-webapp package

Revision 3dc9337f
Added by Nicolas PERRON almost 2 years ago

Merge branch 'branches/rudder/2.4'

  • branches/rudder/2.4:
    Refs #2475 typo on perl file name
    Fixes #2363: Added the migrationeventlog 2.3-2.4 migration script to the rudder-webapp package
    Refs #2345 Typo on /var/rudder/cfengine-community path

Conflicts:
rudder-agent/SOURCES/Makefile

History

#1 Updated by Jonathan CLARKE about 2 years ago

  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES

Nicolas, can you create a SQL migration file in the rudder project, under rudder-core/src/main/resources/Migration, similar to the other ones, to add this table?

When it's done, don't close this bug, but re-assign it to me (or NPE or MCE, with their agreement) so that we can call the script from the rudder-upgrade script in packaging.

Thanks!

#2 Updated by François ARMAND about 2 years ago

  • Status changed from 2 to In progress
  • Assignee changed from Nicolas CHARLES to François ARMAND

#3 Updated by François ARMAND about 2 years ago

  • Status changed from In progress to Discussion
  • Assignee changed from François ARMAND to Jonathan CLARKE

I created the file rudder-core/src/main/resources/Migration/dbMigration-2.3-2.4-add-MigrationEventLog-table.sql in charge to add the new table.

I also modified rudder-core/src/main/resources/reportsSchema.sql to create that table for an installation from scratch - is that the good thing to do, or do we want to always use the migration scripts ?

#4 Updated by Matthieu CERDA almost 2 years ago

  • Status changed from Discussion to Pending technical review
  • % Done changed from 0 to 100

#5 Updated by Matthieu CERDA almost 2 years ago

The migration scripts are only for migrations, during basic installations we should always rely on init files like rudder-core/src/main/resources/reportsSchema.sql. (my two cents)

#6 Updated by Jonathan CLARKE almost 2 years ago

  • Status changed from Pending technical review to Pending functional review

Looks good to me.

#7 Updated by Jonathan CLARKE almost 2 years ago

  • Status changed from Pending functional review to Released

To clarify this from a functional point of view, it's one of the steps that allows an upgrade from Rudder 2.3 to 2.4 to keep event logs from the previous version, by converting them automatically.

#8 Updated by Nicolas PERRON about 1 year ago

  • Project changed from Rudder to packages
  • Category deleted (11)

Also available in: Atom PDF