search for: vm_observ

...or Vm objects. Callbacks in VmObserver also update the new total_uptime and total_uptime_timestamp attributes of Vm class, which allows easy calculation of time spent in running states for user resource use accounting. --- src/app/models/vm.rb | 34 +++++++++++ src/app/models/vm_observer.rb | 96 ++++++++++++++++++++++++++++++ src/app/models/vm_state_change_event.rb | 22 +++++++ src/config/environment.rb | 2 +- src/db/migrate/039_add_vm_state_audit.rb | 51 ++++++++++++++++ 5 files changed, 204 insertions(+), 1 deletions(-) create mode 10064...

...or Vm objects. Callbacks in VmObserver also update the new total_uptime and total_uptime_timestamp attributes of Vm class, which allows easy calculation of time spent in running states for user resource use accounting. --- src/app/models/vm.rb | 34 +++++++++++ src/app/models/vm_observer.rb | 96 ++++++++++++++++++++++++++++++ src/app/models/vm_state_change_event.rb | 22 +++++++ src/config/environment.rb | 2 +- src/db/migrate/039_add_vm_state_audit.rb | 49 +++++++++++++++ 5 files changed, 202 insertions(+), 1 deletions(-) create mode 100644...

Note that one of the 8 patches (#6) will be sent separately in reply to this email, as some of the replaced lines are too long, so git won't let me send the email. However, there is nothing wrong with that patch, and it should be applied in the sequence listed below. Note also that I assume this will be tested on a clean f11 install, rather than an upgrade of an existing ovirt server