Remove the Hyper-V driver

Nova Hyper-V driver is not tested in OpenStack upstream and no maintianers.
This driver has been marked as deprecated in Antelope release. It has dependency
on the OpenStack Winstacker project which has been retired[1].

As discussed in vPTG[2], removing the HyperV driver, tests, and its config.

[1] https://review.opendev.org/c/openstack/governance/+/886880
[2] https://etherpad.opendev.org/p/nova-caracal-ptg#L301

Change-Id: I568c79bae9b9736a20c367096d748c730ed59f0e
This commit is contained in:
Ghanshyam Mann
2024-01-25 00:45:11 -08:00
parent 6531ed6310
commit b068b04372
45 changed files with 30 additions and 10655 deletions
+1 -12
View File
@@ -39,7 +39,7 @@ compute host and image.
.. rubric:: Compute host requirements
The following virt drivers support the config drive: libvirt, Hyper-V and
The following virt drivers support the config drive: libvirt and
VMware. The Bare Metal service also supports the config drive.
- To use config drives with libvirt or VMware, you must first
@@ -49,12 +49,6 @@ VMware. The Bare Metal service also supports the config drive.
the same path as the :program:`nova-compute` service, you do not need to set
this flag.
- To use config drives with Hyper-V, you must set the
:oslo.config:option:`mkisofs_cmd` config option to the full path to an
:command:`mkisofs.exe` installation. Additionally, you must set the
:oslo.config:option:`hyperv.qemu_img_cmd` config option to the full path to an
:command:`qemu-img` command installation.
- To use config drives with the Bare Metal service, you do not need to prepare
anything.
@@ -81,11 +75,6 @@ options:
- :oslo.config:option:`force_config_drive`
- :oslo.config:option:`config_drive_format`
If using the HyperV compute driver, the following additional options are
supported:
- :oslo.config:option:`hyperv.config_drive_cdrom`
For example, to ensure nova always provides a config drive to instances but
versions ``2018-08-27`` (Rocky) and ``2017-02-22`` (Ocata) are skipped, add the
following to :file:`nova.conf`: