a958dc5fcc
For a cross-cell resize, the equivalent of the "finish_resize" method on the destination compute is going to call the driver spawn() method rather than the finish_migration() method and needs to pass through the power_on value, similar to finish_migration, so that when resizing a stopped server it remains stopped once it is resized. The finish_migration method in the driver behaves very similar to spawn so the semantics are the same. This change updates the spawn method signature for all in-tree compute drivers but only implements the logic for the libvirt driver as that is the only driver (currently) which supports cross-cell resize (note the can_connect_volume method is also necessary for cross-cell resize implementation in the driver). Part of blueprint cross-cell-resize Change-Id: I6929c588dd2e0e805f2e30b2e30d29967469d756 |
||
|---|---|---|
| .. | ||
| README.rst | ||
| __init__.py | ||
| block_device_manager.py | ||
| constants.py | ||
| driver.py | ||
| eventhandler.py | ||
| hostops.py | ||
| imagecache.py | ||
| livemigrationops.py | ||
| migrationops.py | ||
| pathutils.py | ||
| rdpconsoleops.py | ||
| serialconsolehandler.py | ||
| serialconsoleops.py | ||
| serialproxy.py | ||
| snapshotops.py | ||
| vif.py | ||
| vmops.py | ||
| volumeops.py | ||
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:
- iscsicli QAddTargetPortal <your_iSCSI_target>
- 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:
- Fist of all create a volume
- 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".