This patchset implements the support in backend to allow user to change maxMemory xml tag. It also changes the memory API from 'memory: XXX' to 'memory': {'current': XXX, 'maxmemory': YYY} maxMemory xml tag is not created by default anymore, when a guest is created. Tag will be created only when the user changes maxmemory manually, and if the value is different (higher) of 'current' memory. So in order to performe memory hotplug, an user has to stop guest, modify maxmemory and then start the guest. Tests were fixed and new ones were included. Rodrigo Trujillo (3): Add support to edit max memory in Templates Add support to edit max memory in Guest Changes and add tests to support new memory API (templates/guest) API.json | 66 +++++++++--- docs/API.md | 29 ++++-- i18n.py | 11 +- model/templates.py | 58 ++++++++++- model/vms.py | 245 ++++++++++++++++++++++++++------------------ osinfo.py | 16 ++- template.conf | 10 +- tests/test_livemigration.py | 6 +- tests/test_model.py | 22 ++-- tests/test_rest.py | 23 ++++- tests/test_template.py | 38 +++++-- tests/test_vmtemplate.py | 26 +++-- vmtemplate.py | 74 ++++++------- 13 files changed, 411 insertions(+), 213 deletions(-) -- 2.1.0