Feature #591

DB Versioning and migration tool

Added by Carlos Martín about 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:04/26/2011
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 3.0
Resolution:fixed Pull request:

Description

The DB will have a new table with information about the OpenNebula version it is ready for, and possibly other control information.

The core should refuse to start until the DB is updated to the right version.
In addition, a DB migration tool will be created.

Associated revisions

Revision 8510fa56
Added by Carlos Martín about 10 years ago

Feature #591: New onedb command. Core detects wrong DB versions.

Revision 97bf19d0
Added by Carlos Martín about 10 years ago

Feature #591: Better core bootstrap. Upgrade process done. New functionality for onedb

Revision 691c9653
Added by Carlos Martín about 10 years ago

Bug #566: New control table to store the last used oid
Feature #591: Add new control table, and fix SQL syntax for MySQL

Revision 211eed32
Added by Carlos Martín about 10 years ago

Feature #407: Create default groups 'oneadmin' and 'users'. Make regular groups start from ID 100. Fix tests.
Feature #591: Add group_pool table to the DB migration script.

Revision d554bea4
Added by Carlos Martín about 10 years ago

Feature #591: Delete cluster_pool, update group_pool schema

Revision 149c5afb
Added by Carlos Martín about 10 years ago

Feature #591: add tests for onedb upgrade. For now, only the DB schema is compared

Revision d0b5c29c
Added by Carlos Martín about 10 years ago

Feature #591: Fix wrong CDATA text element

Revision 3f1cd6e5
Added by Carlos Martín about 10 years ago

Feature #591: Test for onedb upgrade now checks the objects loaded from an upgraded DB.

History

#1 Updated by Carlos Martín about 10 years ago

Needs testing and documentation.

#2 Updated by Damien Raude-Morvan about 10 years ago

Hi,

I don't know what's current status of this feature request, so please excuse me if my remarks are already specified/coded/tested :)

JFTR, I think you should also pay attention to :
- allow your DB migration tool to work on any database supported by OpenNebula (sqlite, mysql, maybe postresql soon #332 :)
- work from command-line (hint: called automaticaly by Debian maintainer-script)
- allow upgrade from previous versions (see my previous request for #181 and #415)

Regards,

#3 Updated by Carlos Martín about 10 years ago

Hi Damien, thank you for your comments.
Looks like we are in the right path:

- allow your DB migration tool to work on any database supported by OpenNebula (sqlite, mysql, maybe postresql soon #332 :)

The command works with sqlite and mysql, reading the connection parameters from the current installation's oned.conf, or from command line options.

- work from command-line (hint: called automaticaly by Debian maintainer-script)

That's a must for us, the cli comes first :)

- allow upgrade from previous versions (see my previous request for #181 and #415)

It will update databases created by 2.x versions.

Cheers

#4 Updated by Ruben S. Montero almost 10 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF