Bug #1616

Pre/Postmigrate script runs on system datastore

Added by SZTAKI LPDS over 8 years ago. Updated over 8 years ago.

Status:ClosedStart date:10/29/2012
Priority:NormalDue date:
Assignee:-% Done:


Target version:Release 4.0
Resolution:wontfix Pull request:
Affected Versions:OpenNebula 3.8


Dear Developers,

The pre and post migrate transfer manager scripts are useful feature to help the iscsi datastore driver to live migrate a virtual machine. However in an event of live migration, the used transfer manager driver is the system datastore driver, which is typically the shared or the ssh. So the iscsi log in or log out actions would need to be implemented in the ssh or shared drvier set. Our point is that the disk image's origin transfer manager driver set should be choosen to execute the pre/post migrate script.


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

  • Status changed from New to Closed
  • Resolution set to wontfix
  • Affected Versions OpenNebula 3.8 added


Closing this as wontfix. The system datastore deals with the disks of the instantiated images, so once the iSCSI volumes are setup and "linked" to the system datastore, these are the drivers that should be used to handle them. Note that the TM action operates at the VM dir level and not per disk image.

However I see your point, IMHO pre/post-migrate scripts can be specialized for the particular use case, i.e. you may copy the iSCSI pre/post scripts to the system datastore, ssh or shared. At the cost of adding some additional logic to check nature of the disk.i, in the rare situations that a VM will be using disk images from different datastore types.


We really appreciate your input and contributions to improve the iSCSI datastore and TM

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

  • Target version set to Release 4.0

Also available in: Atom PDF