Backlog #1967

Revisit XML metadata structure

Added by Ruben S. Montero almost 8 years ago. Updated about 6 years ago.

Status:ClosedStart date:04/25/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-

History

#1 Updated by Ruben S. Montero almost 8 years ago

quote from email by Simon:


I'm looking at scaling OpenNebula and adding some caching, having the TEMPLATE section to be static  where the information would change only ex. when a VM resize operation is done (or at least, not being updated each time the VM is monitored). One could identify each sections "lifetime" ex. :

USER_TEMPLATE = updated on vm.update or when a VM action fails (and the ERROR attribute is updated)
TEMPLATE = updated on vm.resize, attach, detach, etc. operation
MONITOR = updated on each poll (typically LASTPOLL + MONITORING_INTERVAL in oned.conf.. perhaps add a NEXTPOLL attribute to make caching lifetime easier)
HISTORY_RECORDS = updated on VM state changes (one.vm.action) etc.

Then perhaps vm.vmpool could return only the base <VM> attributes (nothing below the USER_TEMPLATE, TEMPLATE, MONITOR) and one would have to call one.vm.info to retrieve the full VM XML.

I understand that would break backward compatibility. But I think it would be a huge improvement to ease caching of the OpenNebula information.

#2 Updated by Ruben S. Montero almost 8 years ago

  • Target version deleted (Release 4.2)

#3 Updated by Ruben S. Montero almost 8 years ago

  • Tracker changed from Feature to Backlog
  • Priority changed from Normal to High

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

  • Status changed from New to Pending

#5 Updated by Ruben S. Montero over 7 years ago

  • Priority changed from High to Normal

#6 Updated by Ruben S. Montero about 6 years ago

  • Status changed from Pending to Closed

This has been partially implemented

Also available in: Atom PDF