nova/nova/virt/hyperv
Alexandru Muresan 20196b74de Hyper-V: Perform proper cleanup after cold migration
At the moment, vif ports and volume connections are not cleaned up
on the source node after a cold migration.

This change addresses this issue by passing the network and block
device info objects when destroying the instance.

Change-Id: I4fd61a6ac09f194ad8be61e6dda092bfd402b806
Closes-Bug: #1705683
2017-08-30 17:50:11 +00: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
block_device_manager.py Merge "hyperv: Fixes Generation 2 VMs volume boot order" 2017-07-01 14:00:42 +00:00
constants.py objects: Move 'arch' to 'fields.Architecture' 2016-11-25 16:19:41 +00:00
driver.py Remove translation of log messages 2017-06-13 11:20:28 +07:00
eventhandler.py Remove translation of log messages 2017-06-13 11:20:28 +07:00
hostops.py Hyper-V PCI Passthrough 2017-01-26 15:28:06 +00:00
imagecache.py Remove translation of log messages 2017-06-13 11:20:28 +07:00
livemigrationops.py hyperv: Fixes log message in livemigrationops 2017-06-30 13:10:14 +03:00
migrationops.py Hyper-V: Perform proper cleanup after cold migration 2017-08-30 17:50:11 +00:00
pathutils.py Hyper-V: properly handle shared storage during migrations 2016-08-24 17:53:40 +03:00
rdpconsoleops.py Hyper-V: adds os-win library 2015-12-02 16:34:24 +02:00
serialconsolehandler.py Remove translation of log messages 2017-06-13 11:20:28 +07:00
serialconsoleops.py Remove translation of log messages 2017-06-13 11:20:28 +07:00
serialproxy.py HyperV: Add serial console proxy 2016-04-18 20:32:13 +03:00
snapshotops.py Remove translation of log messages 2017-06-13 11:20:28 +07:00
vif.py Adds Hyper-V OVS ViF driver 2017-01-11 22:22:13 +00:00
vmops.py hyperv: stop serial console workers while deleting vm files 2017-06-30 09:58:42 +00:00
volumeops.py Remove translation of log messages 2017-06-13 11:20:28 +07: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".