f3d48000b1
autopep8 is a code formating tool that makes python code pep8 compliant without changing everything. Unlike black it will not radically change all code and the primary change to the existing codebase is adding a new line after class level doc strings. This change adds a new tox autopep8 env to manually run it on your code before you submit a patch, it also adds autopep8 to pre-commit so if you use pre-commit it will do it for you automatically. This change runs autopep8 in diff mode with --exit-code in the pep8 tox env so it will fail if autopep8 would modify your code if run in in-place mode. This allows use to gate on autopep8 not modifying patches that are submited. This will ensure authorship of patches is maintianed. The intent of this change is to save the large amount of time we spend on ensuring style guidlines are followed automatically to make it simpler for both new and old contibutors to work on nova and save time and effort for all involved. Change-Id: Idd618d634cc70ae8d58fab32f322e75bfabefb9d |
||
|---|---|---|
| .. | ||
| 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".