SQL tables for templates re-design
|Assignee:||Carlos Martín||% Done:|
|Category:||Core & System|
|Target version:||Release 2.0|
Templates are stored in the DB as individual pairs of [attribute - value].
This doesn't bring any advantage, because internally all attributes are read and then managed as a complete template object.
DB schema should be re-designed to store templates as a whole, to speed up the rebuild from DB to memory and have cleaner tables.
feature #282: Templates can be now parsed from xml-formatted strings.
(cherry picked from commit 35aa6ade2c054282eca76c777c9318575a6f154d)
feature #282: Host template initialization fixed to match the old HostTemplate class.
feature #282: VirtualNetworkTemplate moved from its own table to a network_pool column.
feature #282: Template attributes are now managed by the PoolSQL objects, and then the object has to be updated to write changes to DB.
feature #282: Scheduler now builds objects from the pool dump xmls, instead of querying the core for each one individually.
feature #282: Removed unneeded try, made VirtualMachineXML constructors as HostXML