Feature #1631

Change History reason to reflect the actual operation

Added by Carlos Martín over 8 years ago. Updated about 8 years ago.

Status:ClosedStart date:10/31/2012
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 4.0
Resolution:fixed Pull request:

Description

For example, instead of STOP_RESUME, write the reason as suspend, stop, poweroff, resubmit, etc.

Associated revisions

Revision a9428539
Added by Carlos Martín about 8 years ago

Feature #1631: Add a new ACTION filed to each History

Revision 3ddbef0a
Added by Carlos Martín about 8 years ago

Feature #1631: Use enum type in RM one.vm.action

Revision 72d3ea94
Added by Carlos Martín about 8 years ago

Feature #1631: Change history reasons to be only 3: none, user, error

Revision b483b8bb
Added by Carlos Martín about 8 years ago

Feature #1631: Fix merge

Revision 3e99db4a
Added by Carlos Martín about 8 years ago

Feature #1631: Set USER reason for any operation initiated by the user

Revision 4095acb7
Added by Carlos Martín about 8 years ago

Feature #1631: Fix history reason for migrate.

Revision ce61d6ee
Added by Carlos Martín about 8 years ago

Feature #1631: Add history close action to onevm show and oneacct output

Revision b1273bae
Added by Carlos Martín about 8 years ago

Feature #1631: Add migrator to 4.0.0

Revision 4abedb3d
Added by Carlos Martín about 8 years ago

Feature #1631: Add new action element to xsd files

Revision 002ec7e9
Added by Carlos Martín about 8 years ago

Feature #1631: Rearrange History Actions so NONE is 0

Revision 68e48b0d
Added by Carlos Martín about 8 years ago

Feature #1631: Fix change made for testing

Revision 5e160734
Added by Ruben S. Montero about 8 years ago

feautr #1631: Renamed to life-migrate.

Revision 6db5aa6c
Added by Carlos Martín about 8 years ago

Feature #1631: Rename life-migrate in cli; fix live-migration action

Revision 7c02cbe6
Added by Carlos Martín about 8 years ago

Feature #1631: Add history action to sunstone

History

#1 Updated by Carlos Martín about 8 years ago

  • Assignee set to Carlos Martín

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)

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

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF