one 1.6 should support other SQL backends in side of sqlite
|Assignee:||Tino Vázquez||% Done:|
|Category:||Core & System|
|Target version:||Release 2.0|
By mine experience with opennebula, the sqlite backend only brings many issues and not many advantages.
I think as example on the issue where some VMs stay as zombies after delete, simply caused by the DB beeing locked by other operations.
Of course we could resolve this issue it by other means.
As advantage of say Mysql I could name:
1) Central DB: DB can be in other host than the open master.
2) High availability.
3) Better SQL.
4) Granular access rights..
featrure #206: Abstract interface for generic DB engine. Callback interface for ObjectSQL class
feature #206: Host table creation redefinition (only Sqlite compilant), host uniqueness defined by hostname and mads)
feature #206: Isolation of INSERT and REPLACE SQL queries for VirtualMachine objects.
feature-#206: Modified return value of VM pool allocate to comply with virtual definition
feature-#206: Rolling back augmented mad name size, mysql index cannot be over 1000 bytes
feature #206: DB xml dump of VMs with history items now works for both Sqlite and MySQL.