summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
* Use force=True for os-brick disconnect during deletemelanie witt2023-05-101-0/+11
| | | | | | | | | | | | | | | | | | | The 'force' parameter of os-brick's disconnect_volume() method allows callers to ignore flushing errors and ensure that devices are being removed from the host. We should use force=True when we are going to delete an instance to avoid leaving leftover devices connected to the compute host which could then potentially be reused to map to volumes to an instance that should not have access to those volumes. We can use force=True even when disconnecting a volume that will not be deleted on termination because os-brick will always attempt to flush and disconnect gracefully before forcefully removing devices. Closes-Bug: #2004555 Change-Id: I3629b84d3255a8fe9d8a7cea8c6131d7c40899e8
* Merge "add hypervisor version weigher"Zuul2023-05-041-0/+20
|\
| * add hypervisor version weigherSean Mooney2023-04-201-0/+20
| | | | | | | | | | implements: blueprint weigh-host-by-hypervisor-version Change-Id: I36b16a388383c26bdf432030bc9e28b2fd75d120
* | Merge "hyperv: Mark driver as experimental"Zuul2023-04-191-0/+6
|\ \ | |/ |/|
| * hyperv: Mark driver as experimentalStephen Finucane2022-11-071-0/+6
| | | | | | | | | | | | | | | | | | Cloudbase have changed priorities and will no longer be testing the Hyper-V driver. We need to mark this as experimental and consider removing it in the future. Change-Id: I823fbf660948c062581d4e0aaaadc6a6983de2a3 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* | Merge "db: Remove legacy migrations"Zuul2023-04-171-0/+5
|\ \
| * | db: Remove legacy migrationsStephen Finucane2023-02-011-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | sqlalchemy-migrate does not (and will not) support sqlalchemy 2.0. We need to drop these migrations to ensure we can upgrade our sqlalchemy version. Change-Id: I7756e393b78296fb8dbf3ca69c759d75b816376d Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | | Merge "Unbind port when offloading a shelved instance"Zuul2023-03-131-0/+6
|\ \ \
| * | | Unbind port when offloading a shelved instanceArnaud Morin2022-11-291-0/+6
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | When offloading a shelved instance, the compute needs to remove the binding so the port will appear as "unbound" in neutron. Closes-Bug: 1983471 Change-Id: Ia49271b126870c7936c84527a4c39ab96b6c5ea7 Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
* | | Merge "Update master for stable/2023.1"Zuul2023-03-092-0/+7
|\ \ \
| * | | Update master for stable/2023.1OpenStack Release Bot2023-03-062-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/2023.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2023.1. Sem-Ver: feature Change-Id: I96511e7f86a9f7be9f65e0133c8b38dade57801a
* | | | Imported Translations from ZanataOpenStack Proposal Bot2023-03-091-17/+72
|/ / / | | | | | | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I9442fd04f852986e903768f06453f2a0d9cc4dbb
* | | Add the 2023.1 Antelope prelude sectionSylvain Bauza2023-03-011-0/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First time we now use the correct release naming [1]. Shamelessly copied the bullet points from the cycle highlights [2]. [1] https://governance.openstack.org/tc/reference/release-naming.html [2] I02ed58bb5a4ecdc8171d9aa4a150be1bca214528 Change-Id: Id4e2e672e3a1a5aba7e664ba2d2f701b9be988e0
* | | Merge "Enable cpus when an instance is spawning"Zuul2023-02-181-0/+18
|\ \ \
| * | | Enable cpus when an instance is spawningSylvain Bauza2023-02-101-0/+18
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | By this patch, we now automatically power down or up cores when an instance is either stopped or started. Also, by default, we now powersave or offline dedicated cores when starting the compute service. Implements: blueprint libvirt-cpu-state-mgmt Change-Id: Id645fd1ba909683af903f3b8f11c7f06db3401cb
* | | Merge "libvirt: Add configuration options to set SPICE compression settings"Zuul2023-02-171-0/+23
|\ \ \ | |/ / |/| |
| * | libvirt: Add configuration options to set SPICE compression settingsManuel Bentele2023-01-111-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds the following SPICE-related options to the 'spice' configuration group of a Nova configuration: - image_compression - jpeg_compression - zlib_compression - playback_compression - streaming_mode These configuration options can be used to enable and set the SPICE compression settings for libvirt (QEMU/KVM) provisioned instances. Each configuration option is optional and can be set explictly to configure the associated SPICE compression setting for libvirt. If all configuration options are not set, then none of the SPICE compression settings will be configured for libvirt, which corresponds to the behavior before this change. In this case, the built-in defaults from the libvirt backend (e.g. QEMU) are used. Note that those options are only taken into account if SPICE support is enabled (and the VNC support is disabled). Implements: blueprint nova-support-spice-compression-algorithm Change-Id: Ia7efeb1b1a04504721e1a5bdd1b5fa7a87cdb810
* | | Merge "api: extend evacuate instance to support target state"Zuul2023-02-011-0/+13
|\ \ \
| * | | api: extend evacuate instance to support target stateSahid Orentino Ferdjaoui2023-01-311-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Start to v2.95 any evacuated instances will be stopped a destination Implements: bp/allowing-target-state-for-evacuate Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@industrialdiscipline.com> Change-Id: I141b6f057cc4eb9c541c2bc6eddae27270ede08d
* | | | Merge "Detect host renames and abort startup"Zuul2023-02-011-0/+19
|\ \ \ \
| * | | | Detect host renames and abort startupDan Smith2023-01-301-0/+19
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Except on ironic, if we are able to determine that our locally- configured node has a hostname other than what we expect, we should abort startup. Since we currently depend on the loose name-based association of nodes, services, and instances, we need to make sure we do not startup in an inconsistent configuration. Related to blueprint stable-compute-uuid Change-Id: I595b27a57516cffe1f172cf2fb736e1b11373a1d
* | | | Merge "Add further workaround features for qemu_monitor_announce_self"Zuul2023-01-311-0/+28
|\ \ \ \ | |/ / / |/| | |
| * | | Add further workaround features for qemu_monitor_announce_selfas02023-01-301-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some cases on Arista VXLAN fabrics, VMs are inaccessible via network after live migration, despite garps being observed on the fabric itself. This patch builds on the feature ``[workarounds]/enable_qemu_monitor_announce_self`` feature as reported in `bug 1815989 <https://bugs.launchpad.net/nova/+bug/1815989>` This patch adds the ability to config the number of times the QEMU announce_self monitor command is called, and add a new configuration option to specify a delay between calling the announce_self command multiple times, as in some cases, multiple announce_self monitor commands are required for the fabric to honor the garp packets and the VM to become accessible via the network after live migration. Closes-Bug: #1996995 Change-Id: I2f5bf7c9de621bb1dc7fae5b3374629a4fcc1f46
* | | | Merge "Fix rescue volume-based instance"Zuul2023-01-301-0/+6
|\ \ \ \
| * | | | Fix rescue volume-based instanceRajesh Tailor2022-08-261-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As of now, when attempting to rescue a volume-based instance using an image without the hw_rescue_device and/or hw_rescue_bus properties set, the rescue api call fails (as non-stable rescue for volume-based instances are not supported) leaving the instance in error state. This change checks for hw_rescue_device/hw_rescue_bus image properties before attempting to rescue and if the property is not set, then fail with proper error message, without changing instance state. Related-Bug: #1978958 Closes-Bug: #1926601 Change-Id: Id4c8c5f3b32985ac7d3d7c833b82e0876f7367c1
* | | | | Merge "libvirt: Replace usage of compareCPU() with compareHypervisorCPU()"Zuul2023-01-261-0/+12
|\ \ \ \ \
| * | | | | libvirt: Replace usage of compareCPU() with compareHypervisorCPU()Kashyap Chamarthy2023-01-241-0/+12
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The older libvirt API compareCPU() does not take into account the capabilities of the "host hypervisor" (KVM, QEMU and the details libvirt knows about the host) when comparing CPUs. This is causing unwanted failures during CPU compatibility checks. To fix this and other related problems, libvirt has introduced (in v4.4.0) a newer API, compareHypervisorCPU(), which _does_ take into account the host hypervisor's capabilities before comparing CPUs. This will help fix a range of problems, such as[1][2]. So let's switch to the newer API, which is largely a drop-in replacement. In this patch: - Introduce a wrapper method, compare_hypervisor_cpu() for libvirt's compareHypervisorCPU() API. - Update the _compare_cpu() method to use the wrapper method, compare_hypervisor_cpu(). - Update the unit tests to use the newer API, compareHypervisorCPU(). [1] https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1978064 [2] https://bugzilla.redhat.com/show_bug.cgi?id=2138381 Change-Id: Ib523753f52993cfe72e35e0309e429ca879c125c Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
* | | | | Merge "Microversion 2.94: FQDN in hostname"Zuul2023-01-211-0/+22
|\ \ \ \ \
| * | | | | Microversion 2.94: FQDN in hostnameArtom Lifshitz2023-01-171-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Extend microversion 2.90 to allow FQDNs in the hostname parameter. Multi-create with --hostname continues to be refused, returning error 400 to the user. This simplifies the code by not needing to handle any sort of suffix or prefix mangling of the FQDN to handle multiple instances. No other changes are made - not Neutron integration, metadata API changes (the FQDN will appear as-is in places where the hostname currently appears), etc. Change-Id: I47e397dc6da8263762479cc8ae4f8777a6d9d811 Implements: bp/fqdn-in-hostname
* | | | | | Merge "Enable new defaults and scope checks by default"Zuul2023-01-161-0/+23
|\ \ \ \ \ \ | |/ / / / / |/| | | | |
| * | | | | Enable new defaults and scope checks by defaultGhanshyam Mann2023-01-101-0/+23
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As discussed in PTG, we need to test the new RBAC in the integrated gate and accordingly enable the new defaults and scope check by default. A new integrated testing job has been added and results show that the new defaults and scope checks are working fine. During testing, we found a few bugs in neutron policies but all are fixed now. enforce_scope and enforce_new_defaults are oslo policy config options but they are per service level and the default value can be overridden. Oslo policy 3.11.0 version allows to override the default value for these config options[1] so upgrading the oslo policy version in requirements.txt Depends-On: https://review.opendev.org/c/openstack/devstack/+/869781 Depends-On: https://review.opendev.org/c/openstack/placement/+/869525 [1] https://github.com/openstack/oslo.policy/blob/3.11.0/oslo_policy/opts.py#L125 Change-Id: I977b2daedf880229c8d364ca011f2ea965b86e3a
* | | | | Merge "Allow enabling PCI scheduling in Placement"Zuul2023-01-121-0/+8
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | Allow enabling PCI scheduling in PlacementBalazs Gibizer2023-01-051-0/+8
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A new configuration option [filter_scheduler]pci_in_placement is added that allows enabling the scheduler logic for PCI device handling in Placement for flavor based PCI requests. blueprint: pci-device-tracking-in-placement Change-Id: I5ddf6d3cdc7e05cc4914b9b1e762fa02a5c7c550
* | | | Merge "Ironic nodes with instance reserved in placement"Zuul2022-12-141-0/+11
|\ \ \ \
| * | | | Ironic nodes with instance reserved in placementJohn Garbutt2022-11-171-0/+11
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, when you delete an ironic instance, we trigger and undeploy in ironic and we release our allocation in placement. We do this well before the ironic node is actually available. We have attempted to fix this my marking unavailable nodes as reserved in placement. This works great until you try and re-image lots of nodes. It turns out, ironic nodes that are waiting for their automatic clean to finish, are returned as a valid allocation candidates for quite some time. Eventually we mark then as reserved. This patch takes a strange approach, if we mark all nodes as reserved as soon as the instance lands, we close the race. That is, when the allocation is removed the node is still unavailable until the next update of placement is done and notices that the node has become available. That may or may not have been after automatic cleaning. The trade off is that when you don't have automatic cleaning, we wait a bit longer to notice the node is available again. Note, this is also useful when a broken Ironic node is marked as in-maintainance while it is in-use by a nova instance. In a similar way, we mark the Nova as reserved immmeidately, rather than first waiting for the instance to be deleted before reserving the resources in Placement. Closes-Bug: #1974070 Change-Id: Iab92124b5776a799c7f90d07281d28fcf191c8fe
* | | | Merge "Support multiple config file with mod_wsgi"Zuul2022-12-121-0/+14
|\ \ \ \ | |_|_|/ |/| | |
| * | | Support multiple config file with mod_wsgiSean Mooney2022-12-071-0/+14
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Unlike uwsgi, apache mod_wsgi does not support passing commandline arguments to the python wsgi script it invokes. As a result while you can pass --config-file when hosting the api and metadata wsgi applications with uwsgi there is no way to use multiple config files with mod_wsgi. This change mirrors how this is supported in keystone today by intoducing a new OS_NOVA_CONFIG_FILES env var to allow operators to optional pass a ';' delimited list of config files to load. This change also add docs for this env var and the existing undocumented OS_NOVA_CONFIG_DIR. Closes-Bug: 1994056 Change-Id: I8e3ccd75cbb7f2e132b403cb38022787c2c0a37b
* | | Merge "Don't provide MTU value in metadata service if DHCP is enabled"Zuul2022-11-291-0/+5
|\ \ \ | |/ / |/| |
| * | Don't provide MTU value in metadata service if DHCP is enabledSlawek Kaplonski2022-11-291-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For networks with subnets with enabled DHCP service don't provide mtu value in the metadata. That way cloud-init will not configure it "statically" in e.g. netplan's config file and guest OS will use MTU value provided by the DHCP service. Closes-Bug: #1899487 Change-Id: Ib775c2210349b72b3dc033554ac6d8b35b8d2d79
* | | Merge "update default overcommit"Zuul2022-10-071-0/+21
|\ \ \
| * | | update default overcommitSean Mooney2022-10-061-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change updates the cpu and ram initial allocation ratios to 4.0 and 1.0 to reflect the typical values that are suitable for non web hosting workloads. Change-Id: I283eb270a4e47da15cf01d098b4f3952f7b5b570 implements: bp/nova-change-default-overcommit-values
* | | | Merge "Handle "no RAM info was set" migration case"Zuul2022-10-061-0/+11
|\ \ \ \ | |/ / / |/| | |
| * | | Handle "no RAM info was set" migration caseBrett Milford2022-08-291-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This handles the case where the live migration monitoring thread may race and call jobStats() after the migration has completed resulting in the following error: libvirt.libvirtError: internal error: migration was active, but no RAM info was set Closes-Bug: #1982284 Change-Id: I77fdfa9cffbd44b2889f49f266b2582bcc6a4267
* | | | Merge "Update master for stable/zed"Zuul2022-09-222-0/+7
|\ \ \ \
| * | | | Update master for stable/zedOpenStack Release Bot2022-09-162-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/zed. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/zed. Sem-Ver: feature Change-Id: I19ad827588f760c4892fc613c7a44c852c4bf3a7
* | | | | Merge "Imported Translations from Zanata"Zuul2022-09-202-0/+820
|\ \ \ \ \
| * | | | | Imported Translations from ZanataOpenStack Proposal Bot2022-09-172-0/+820
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I55e31ea2f0cf43d03601ac2e32e8c7f44f8574b6
* | | | | Merge "Move uwsgi-gmr reno to the proper place"Zuul2022-09-191-0/+6
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | Move uwsgi-gmr reno to the proper placeBalazs Gibizer2022-07-181-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I605f0e40417fe9b0a383cc8b3fefa1325f9690d9 added it's reno in a wrong directory. This patch moves it to the proper place Change-Id: I48bcec93aeb75294205cd15dfb89a65d9b8e4b9d
* | | | | Prelude section for Zed releaseSylvain Bauza2022-09-141-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need it before RC1. Change-Id: Ib674ca6a13f7c5d0254b222effa20d1948a80fe5
View Lorry Controller Status