← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1565895] Re: The Hyper-V driver cannot handle shared storage

 

Reviewed:  https://review.openstack.org/347437
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8c40c4268be57ff2f76cf616b53992b0d32e1fd3
Submitter: Jenkins
Branch:    master

commit 8c40c4268be57ff2f76cf616b53992b0d32e1fd3
Author: Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>
Date:   Thu Jun 16 11:41:20 2016 +0300

    Hyper-V: fix image handling when shared storage is being used
    
    The image cache operation uses thread locks, for which reason it is
    prone to race conditions when using shared storage. This is avoided
    by using file locks, placed on the shared path.
    
    Change-Id: I2b002993b7ab0973960794bfdd81d4fe57bf7399
    Closes-Bug: #1565895


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1565895

Title:
  The Hyper-V driver cannot handle shared storage

Status in compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The Hyper-V driver has a few issues when attempting to use shared
  storage for the instance files.

  Migration issues
  ----------------
  In case of migrations, we attempt to move the instance files without checking whether shared storage is used. Note that the block_migration flag is completely ignored.

  During live migrations, we let Hyper-V automatically detect whether
  shared storage is used or not. This seems to be troublesome when
  instance files reside on CSVs.

  After a live migration is performed, we always try to delete the
  instance files. Also, if the migration fails, the destination node is
  not cleaned up, as the HyperVLiveMigrateData object is not used at the
  moment.

  Image/path handling issues
  --------------------------
  The image cache operation uses thread locks, for which reason it is prone to race conditions when using shared storage. Switching to file locks would solve this issue.

  Using UNC paths for the instance path does not work either. The driver
  will fail to fetch the available space. Also, it will not build the
  remote instance path properly when trying to move files during
  migrations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1565895/+subscriptions


References