OpenNebula

Most of the problems can be summarized in this example

$ oneacct 
# User 0                                                                        

 VID HOSTNAME        REAS     START_TIME       END_TIME MEMORY CPU NET_RX NET_TX
   0 localhost       none 04/01 11:54:04 04/01 12:38:46   128M 0.1     0K     0K
   1 localhost       canc 04/01 12:38:06 04/01 12:39:13   128M 0.1     0K     0K
   2 localhost       stop 04/01 12:38:07 04/01 12:41:05   128M 0.1     0K     0K
   3 localhost       stop 04/01 12:38:09 04/01 12:41:26   128M 0.1     0K     0K
   4 localhost       none 04/01 12:38:10              -   128M 0.1     0K     0K
   5 localhost       none 04/01 12:41:48              -   128M 0.1     0K     0K
   6 localhost       user 04/01 12:41:49 04/01 12:53:49   128M 0.1     0K     0K
   6 localhost       none 04/01 12:53:48              -   128M 0.1     0K     0K

Actions performed:

0 shutdown
1 shutdown --hard
2 suspend
3 stop
4 poweroff
5 none, it is running
6 migrate

Problems:

• 0 & 1 have a different reason, but they are the same action.
• 2 & 3 are two different actions, but can't be told appart.
• 2 & 4 are similar (suspend has checkpoint, poweroff doesn't), but only one has the end time set.
• 4 & 5 have the same history, but one is running while the other is poweroff.

We will simplify the History reason to be used internally:

• None: open history record
• User: history record closed by an action
• Error: history record closed because of an error (e.g. prolog error)

And add a new field to show the actual action that closed the history record (e.g. shutdown, poweroff)