577a4b1a54
This makes the libvirt driver handle and pass trusted_certs through to the image download code that is now available. This also adds a new supports_trusted_certs compute driver capability which only the libvirt driver supports at this time. Attempts to create a server or rebuild a server on a host with a driver that does not support trusted_certs will fail if the instance is requesting image cert validation. We can also eventually expose this capability as a trait for more efficient scheduling. The nova-compute service RPC API version is incremented so that the nova-api paths for create/rebuild can determine if the deployment has been upgraded to the point of supporting trusted certs. Co-Authored-By: Dan Smith <dansmith@redhat.com> Co-Authored-By: Brianna Poulos <Brianna.Poulos@jhuapl.edu> Change-Id: Ie3130e104d7ca80289f1bd9f0fee9a7a198c263c Implements: blueprint nova-validate-certificates |
||
|---|---|---|
| .. | ||
| 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".