openstack
/
nova
Code Issues Proposed changes
nova/nova/virt/hyperv
History
Lucian Petrut 8f20e7067f HyperV: remove instance snapshot lock 
At the moment, the instance snapshot operation is synchronized using
the instance uuid. This was added some time ago, as the instance
destroy operation was failing when an instance snapshot was in
proggress.

This is now causing a deadlock, as a similar lock was recently
introduced in the manager for the shelve operation by this change:
Id36b3b9516d72d28519c18c38d98b646b47d288d

We can safely remove the lock from the HyperV driver as we now stop
pending jobs when destroying instances.

Closes-Bug: #1611321

Change-Id: I1c2ca0d24c195ebaba442bbb7091dcecc0a7e781
(cherry picked from commit c7af24ca82)
 		2016-08-18 20:42:39 -04:00
..
README.rst Adds Hyper-V support in nova-compute (with new network_info model), including unit tests 2012-08-16 03:38:51 +03:00
__init__.py Add Hyper-V driver in the "compute_driver" option description 2014-07-24 02:47:32 -07:00
constants.py Hyper-V: os_win related updates 2016-02-19 17:47:20 +02:00
driver.py fix typo in comment 2016-02-24 21:28:40 +09:00
eventhandler.py Hyper-V: os_win related updates 2016-02-19 17:47:20 +02:00
hostops.py Hyper-V: os_win related updates 2016-02-19 17:47:20 +02:00
imagecache.py config options: Centralise 'virt.driver' options 2016-02-11 09:40:25 +00:00
livemigrationops.py objects: add HyperVLiveMigrateData stub 2016-02-29 12:28:35 +02:00
migrationops.py hyper-v: Copies back files on failed migration 2016-03-12 01:50:44 +02:00
pathutils.py Remove unused logging import and LOG global var 2015-12-25 18:01:12 +08:00
rdpconsoleops.py Hyper-V: adds os-win library 2015-12-02 16:34:24 +02:00
snapshotops.py HyperV: remove instance snapshot lock 2016-08-18 20:42:39 -04:00
vif.py Remove unused logging import and LOG global var 2015-12-25 18:01:12 +08:00
vmops.py Merge "Fix hyperv use of deprecated network_api_class" 2016-03-08 16:48:39 +00:00
volumeops.py Merge "HyperV: Fix vm disk path issue" 2016-02-25 19:15:17 +00:00

README.rst

Hyper-V Volumes Management

To enable the volume features, the first thing that needs to be done is to enable the iSCSI service on the Windows compute nodes and set it to start automatically.

sc config msiscsi start= auto net start msiscsi

In Windows Server 2012, it's important to execute the following commands to prevent having the volumes being online by default:

diskpart san policy=OfflineAll exit

How to check if your iSCSI configuration is working properly:

On your OpenStack controller:

1. Create a volume with e.g. "nova volume-create 1" and note the generated volume id

On Windows:

  1. iscsicli QAddTargetPortal <your_iSCSI_target>
  2. iscsicli ListTargets

The output should contain the iqn related to your volume: iqn.2010-10.org.openstack:volume-<volume_id>

How to test Boot from volume in Hyper-V from the OpenStack dashboard:

  1. Fist of all create a volume
  2. Get the volume ID of the created volume

3. Upload and untar to the Cloud controller the next VHD image: http://dev.opennebula.org/attachments/download/482/ttylinux.vhd.gz 4. sudo dd if=/path/to/vhdfileofstep3 of=/dev/nova-volumes/volume-XXXXX <- Related to the ID of step 2 5. Launch an instance from any image (this is not important because we are just booting from a volume) from the dashboard, and don't forget to select boot from volume and select the volume created in step2. Important: Device name must be "vda".