openstack
/
nova
Code Issues Proposed changes
nova/nova/virt/hyperv
History
Dan Smith 9471282626 Ban db import from nova/virt 
This makes hacking.py complain if someone adds something like:

  from nova import db

into any of the files in nova/virt/* (aside from the fake.py file).
It also removes the rest of the dangling db imports that are no
longer needed.

Yay!

Change-Id: Iba3d53b87e65e33a55f8e5033b5d1d33b28d12f7
 		2012-11-12 12:37:33 -08: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 Adds Hyper-V support in nova-compute (with new network_info model), including unit tests 2012-08-16 03:38:51 +03:00
baseops.py Adds Hyper-V support in nova-compute (with new network_info model), including unit tests 2012-08-16 03:38:51 +03:00
constants.py Adds Hyper-V support in nova-compute (with new network_info model), including unit tests 2012-08-16 03:38:51 +03:00
driver.py Updated scheduler and compute for multiple capabilities. 2012-11-10 10:20:45 +09:00
hostops.py Make ComputeDrivers send hypervisor_hostname 2012-11-06 23:12:20 +09:00
ioutils.py Adds Hyper-V support in nova-compute (with new network_info model), including unit tests 2012-08-16 03:38:51 +03:00
livemigrationops.py Switch from FLAGS to CONF in nova.virt 2012-11-07 13:21:56 +00:00
snapshotops.py Switch from FLAGS to CONF in nova.virt 2012-11-07 13:21:56 +00:00
vmops.py Ban db import from nova/virt 2012-11-12 12:37:33 -08:00
vmutils.py Switch from FLAGS to CONF in nova.virt 2012-11-07 13:21:56 +00:00
volumeops.py Switch from FLAGS to CONF in nova.virt 2012-11-07 13:21:56 +00:00
volumeutils.py Switch from FLAGS to CONF in nova.virt 2012-11-07 13:21:56 +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".