#, fuzzy msgid "" msgstr "" "Project-Id-Version: nova\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2026-07-22 15:35+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../:215 stable/2025.2>:575 msgid "" "\"When updating volumeId, this API is typically meant to only be used as " "part of a larger orchestrated volume migration operation initiated in the " "block storage service via the os-retype or os-migrate_volume volume actions. " "Direct usage of this API to update volumeId is not recommended and may " "result in needing to hard reboot the server to update details within the " "guest such as block storage serial IDs. Furthermore, updating volumeId via " "this API is only implemented by certain compute drivers.\"" msgstr "" #: ../../:148 current msgid "**Impact:**" msgstr "" #: ../../:155 current msgid "**Required Actions:**" msgstr "" #: ../../:319 msgid "31.0.0" msgstr "" #: ../../:267 msgid "31.0.1" msgstr "" #: ../../:202 msgid "31.1.0" msgstr "" #: ../../:152 msgid "31.2.0" msgstr "" #: ../../:61 msgid "31.3.0" msgstr "" #: ../../:39 msgid "31.3.1" msgstr "" #: ../../:5 msgid "31.3.1-2" msgstr "" #: ../../:165 msgid "32.0.0" msgstr "" #: ../../:145 msgid "32.1.0" msgstr "" #: ../../:61 msgid "32.2.0" msgstr "" #: ../../:39 msgid "32.2.1" msgstr "" #: ../../:5 msgid "32.2.1-2" msgstr "" #: ../../:68 msgid "33.0.0" msgstr "" #: ../../:5 current msgid "33.0.0-177" msgstr "" #: ../../:39 msgid "33.0.2" msgstr "" #: ../../:5 msgid "33.0.2-2" msgstr "" #: ../../:327 msgid "" "A few of the Nova APIs are meant only for use by other Openstack services. " "Those APIs are not supposed to be used by any non-service users (even " "admins) because they can make deployment or resources in unwanted state. To " "restrict the usage of those APIs by users, Nova now defaults those APIs to a " "policy rule of the ``service`` role. This will make sure they are allowed to " "be used by the OpenStack services only." msgstr "" #: ../../:353 msgid "" "A new ImagePropertiesWeigher is able to spread or pack instances using the " "same image properties." msgstr "" #: ../../:388 msgid "" "A new `ImagePropertiesWeigher` has been added. It will compare the number of " "image properties of the image being booted for each of the host with how " "many existing instances use them. By default this weigher is enabled but " "with a value of 0.0 for `[filter_scheduler]/image_props_weight_multiplier` " "which won't modify the existing scheduling behavior. If you want to pack " "instances having the same image properties on the same hosts, modify " "`image_props_weight_multiplier` to a positive value. If you want to spread " "instances with the same properties around all hosts, then please modify " "`image_props_weight_multiplier` to a negative value. Another configuration " "option `[filter_scheduler]/image_props_weight_setting` allows you to define " "fine-grained weights for each of the properties you actually would like to " "weigh (eg. `os_distro`). Please refer to the documentation for more details " "about how to use this configuration option." msgstr "" #: ../../:404 current msgid "" "A new ``[libvirt]live_migration_monitor_interval`` config option has been " "added to control how frequently migration stats are saved to the database " "during live migrations. The default remains 5 seconds. In environments where " "long-running live migrations produce enough database writes to overwhelm the " "message queue, this interval can be increased to reduce the frequency of RPC " "calls to nova-conductor. See `bug 2091138 `_ for details." msgstr "" #: ../../:103 current msgid "" "A new configuration option ``[DEFAULT] concurrency_backend`` has been added " "to allow operators to explicitly select the concurrency backend used by Nova " "services. Accepted values are ``auto`` (default), ``threading``, and " "``eventlet``. When set to ``auto`` each Nova binary applies its own built-in " "deployment default: in 2026.2 (Hibiscus) all services default to native " "threading except the novnc/serial/spice console proxy services and CLI entry " "points (nova-manage, nova-policy, nova-status). Setting an explicit value " "overrides the per-binary default for every service that reads the config " "file. The environment variable ``OS_NOVA_DISABLE_EVENTLET_PATCHING`` takes " "precedence over this option when both are set. See the `concurrency admin " "guide `__ for " "details." msgstr "" #: ../../:377 msgid "" "A new configuration option ``[DEFAULT]/manager_shutdown_timeout`` has been " "added with a default value of 160 seconds. This controls how long the " "service manager waits for in-progress tasks to finish during graceful " "shutdown. Operators may want to tune this value based on how long their " "typical long-running operations (e.g. live migrations) take to complete." msgstr "" #: ../../:167 msgid "" "A new configuration option ``[libvirt]use_default_aio_mode_for_volumes`` has " "been added to enable use of QEMU default AIO modes for NFS, FC, and iSCSI " "Cinder volumes. By default, Nova explicitly sets AIO mode ``io=native`` in " "the Libvirt guest XML for NFS, FC, and iSCSI Cinder volumes. Operators may " "set this option to ``True`` in order to defer AIO mode selection to QEMU if " "forcing ``io=native`` is not desired." msgstr "" #: ../../:406 msgid "" "A new microversion has been added that allows users to retrieve server's " "associated scheduler hints in ``GET /servers/{server_id}``, ``GET /servers/" "detail``, ``PUT /servers/{server_id}`` and ``POST /server/{server_id}/" "action`` (rebuild) responses." msgstr "" #: ../../:148 msgid "" "A new microversion has been added to allow fully-asynchronous attachment of " "volumes to a server. Previously, calling ``POST /servers/{server_id}/os-" "volume_attachments`` to attach a volume would return HTTP 200 containing a " "``volumeAttachment`` object, returning a device name. With API version 2.101 " "this changes to HTTP 202. The reason is, that the device name could not be " "assured by any of the current drivers and reserving the device name could " "block the API thread for some time." msgstr "" #: ../../:65 current msgid "" "A new microversion has been added to allow unpinning and re-pinning the " "availability zone for an instance. By doing a ``PUT /servers/{server_id}`` " "containing a value for ``pinned_availability_zone``, a user can remove the " "AZ or add it back. For re-pinning, only the current AZ of the instance is " "allowed to be set (i.e. equal to the ``OS-EXT-AZ:availability_zone``) value." msgstr "" #: ../../:216 msgid "" "Added support for AMD Secure Encrypted Virtualization – Encrypted State (SEV-" "ES) with libvirt, extending confidential computing capabilities in Nova to " "protect guest memory and CPU register state." msgstr "" #: ../../:184 stable/2025.2>:673 msgid "" "Adding uptime information to the periodic resource updates sent by nova-" "compute to the database, eliminating the need for synchronous RPC calls " "during API requests" msgstr "" #: ../../:357 msgid "" "Additional attributes relating to the image metadata an instance is " "configured with have been added to the libvirt domain metadata under the " "```` element. This allows downstream services that read libvirt " "domain metadata, such as Ceilometer, to use and expose more information " "about an instance without needing to perform additional API queries " "(potentially to multiple services) to get that information." msgstr "" #: ../../:348 msgid "" "Additional information regarding an instance's flavor (the ID and the " "defined extra specs at the time the instance was launched) has been added to " "the libvirt domain metadata for instances. This allows downstream clients " "that queries libvirt domain metadata, such as Ceilometer, to avoid " "performing additional Nova API queries to get this information." msgstr "" #: ../../:225 stable/2025.2>:585 msgid "" "As an admin only api, direct usage has always been limited to admins or " "service like ``watcher``. This longstanding recommendation is now enforced " "as a security hardening measure and restricted to only cinder. The prior " "warning alluded to the fact that directly using this api can result in a " "guest with a de-synced definition of the volume serial. Before this change " "it was possible for an admin to unknowingly put a VM in an inconsistent " "state such that a future live migration may fail or succeed and break tenant " "isolation. This could not happen when the api was called by cinder so Nova " "has restricted that api exclusively to that use-case. see: https://bugs." "launchpad.net/nova/+bug/2112187 for details." msgstr "" #: ../../:552 msgid "" "As we have learned over the years per compute periodic tasks that call other " "services do not scale well as the number of compute nodes increases. In " "``ce936ea5f3ae0b4d3b816a7fe42d5f0100b20fca`` the os-server-external-events " "API was introduced. The server external events API allows external systems " "such as Neutron to trigger cache refreshes on demand, this was part of the " "Icehouse release. With the introduction of this API, neutron was modified to " "send network-changed events on a per-port basis as API actions are performed " "on neutron ports. When that was introduced the default value of " "``[compute]heal_instance_info_cache_interval`` was not changed to ensure " "there was no upgrade impact." msgstr "" #: ../../:204 current stable/2025.1>:31 #: stable/2025.2>:31 stable/2026.1>:31 msgid "" "Bug #2158919 is fixed, which involved an authenticated user able to poison " "the server-side allowed origins list (and potentially exhaust memory by " "extending it until failure)." msgstr "" #: ../../:212 current #: stable/2025.1>:44 stable/2025.1>:88 stable/2025.1>:157 stable/2025.1>:242 #: stable/2025.1>:272 stable/2025.1>:645 stable/2025.2>:44 stable/2025.2>:88 #: stable/2025.2>:150 stable/2025.2>:602 stable/2026.1>:44 stable/2026.1>:484 msgid "Bug Fixes" msgstr "" #: ../../:225 msgid "Cold migration" msgstr "" #: ../../:209 msgid "" "Completes SPICE direct consoles with USB controller config and sound device " "support." msgstr "" #: ../../:222 msgid "Currently below operations are using second RPC server:" msgstr "" #: ../../:280 stable/2025.2>:294 #: stable/2025.2>:308 stable/2025.2>:311 msgid "Default: ``ADMIN``" msgstr "" #: ../../:274 stable/2025.2>:288 #: stable/2025.2>:302 msgid "Default: ``PROJECT_MANAGER_OR_ADMIN``" msgstr "" #: ../../:181 current stable/2025.1>:624 #: stable/2025.2>:532 stable/2026.1>:422 msgid "Deprecation Notes" msgstr "" #: ../../:656 msgid "" "During the Caracal cycle the libvirt driver was enhanced to support using " "device aliases to detach devices from a domain. " "I1dfe4ad3df81bc810835af9b09cfc6c06e9a5388 This introduced a regression for " "instance with vgpus. A prior bugfix https://bugs.launchpad.net/nova/+bug/" "1942345 addressed the symptom without correcting the underlying problem. A " "related bug for mdev devices was later reported. https://bugs.launchpad.net/" "nova/+bug/2074219 When this feature was added nova introduced a helper " "method to get device via the alias because the libvirt api does not provide " "one natively. That helper function assumed all devices would have an alias " "attribute. That assumption was not valid and had now been corrected. As a " "result detaching a volume from an instance with vgpus should now be possible " "and this class of bug should no longer happen." msgstr "" #: ../../:190 msgid "Enable IOThread for Virtual Machines, for now 1 per VM." msgstr "" #: ../../:185 current msgid "" "Eventlet based concurrency mode is now deprecated and will be removed in a " "future release, not earlier than 2027.2. Nova services that are still " "configured to run with eventlet will log a deprecation warning at startup. " "Operators should migrate to native threading mode. All Nova services except " "the console proxy services (nova-novncproxy, nova-serialproxy, nova-" "spicehtml5proxy) already run in native threading mode by default. The " "console proxy services still default to eventlet mode and require explicit " "configuration to enable native threading. Please read the `concurrency " "`__ guide for " "details on how to configure native threading mode." msgstr "" #: ../../:152 current msgid "" "Existing instances using Linux bridge VIFs cannot be managed by upgraded " "compute nodes until migrated to supported VIF types." msgstr "" #: ../../:98 current msgid "" "Existing instances with AMD SEV-ES memory encryption should be migrated or " "deleted from the host before SEV-SNP is enabled in the hardware." msgstr "" #: ../../:284 stable/2025.2>:298 msgid "Existing policy is used to list live migrations without host info:" msgstr "" #: ../../:269 msgid "" "Existing policy is used when live migrating server without specifying host:" msgstr "" #: ../../:442 msgid "Existing policy:" msgstr "" #: ../../:220 msgid "" "Experimental feature: Nova API, metadata, and scheduler services can run in " "native threading mode as an alternative to eventlet. Please try it in non-" "production environment and share your success or failure with us on the " "openstack-discuss mailing list or via the Nova bug tracker." msgstr "" #: ../../:135 msgid "" "Experimental feature: Nova services can run in native threading mode as an " "alternative to eventlet. Please try it in non-production environment and " "share your success or failure with us on the openstack-discuss mailing list " "or via the Nova bug tracker." msgstr "" #: ../../:128 msgid "" "Experimental feature: Nova services now supports graceful shutdown (part 1 " "of a larger effort). A second RPC server is introduced in compute service to " "handle in-progress operations during shutdown. The configurable timeouts " "controls how long the service waits for ongoing tasks to complete before " "fully stopping, preventing operations from being left in an unrecoverable " "state." msgstr "" #: ../../:291 stable/2025.2>:689 msgid "" "Fix displaying the reason messages from the Ironic validate node operation " "that is called just before the instance is deployed on the bare metal node. " "The message from Ironic is now correctly logged. Fixes `bug 2100009 _`." msgstr "" #: ../../:108 #: stable/2025.2>:606 msgid "" "Fixed an issue where certain server actions could fail for servers with " "ephemeral disks due to filesystem label name length limitations (VFAT, XFS, ." "..). Filesystem label name generation has been fixed for these cases. See " "https://launchpad.net/bugs/2061701 for more details." msgstr "" #: ../../:673 msgid "" "Fixed an issue where the instance rebuild option failed for Ironic instances." " The problem was caused by an incorrect parameter order in the " "``add_instance_info_to_node`` function, which was introduced by commit " "`93b90d2b` . For more " "details, see `bug 2092570` ." msgstr "" #: ../../:177 stable/2025.2>:666 msgid "" "Fixed performance issue with the ``/os-hypervisors/detail`` API endpoint " "when using microversion 2.88 or higher. The API was making sequential RPC " "calls to each compute node to gather uptime information, causing significant " "delays in environments with many compute nodes (LP#2122036)." msgstr "" #: ../../:293 current msgid "" "Fixed slow nova-compute startup caused by lazy-loading instance attributes. " "During init_host(), the _validate_vtpm_configuration() method accesses " "instance.flavor and instance.image_meta, which triggered 2*N sequential " "database queries for N instances. These attributes are now pre-loaded in the " "initial InstanceList query, reducing startup time significantly for hosts " "with many instances." msgstr "" #: ../../:323 current msgid "" "Fixed the `bug #2152697`_ that prevented pre-existing VMs with dedicated " "CPUs to be live migrated after Gazpacho." msgstr "" #: ../../:161 #: stable/2025.2>:154 stable/2026.1>:524 msgid "" "Fixed the issue `bug 2044235 `__ where Nova Conductor puts an instance into an error state if any " "errors occur during execution of the 'check_can_live_migrate_source()' " "method in an RPC call. Now, any error is caught and a MigrationPreCheckError " "exception is re-raised to reset the instance state." msgstr "" #: ../../:246 stable/2025.2>:628 msgid "" "Fixed the issue `bug 2098496 `__ where nova assigned more PCI hostdevs to a VM than the flavor " "requested via the pci_passthrough:alias extra_spec. This only affected " "systems where both ``[filter_scheduler]pci_in_placement`` and " "``[pci]report_in_placement`` were set to True. This only affected systems " "where the PCI alias requested type-VF devices and a single PF device on the " "compute node supported more than one VFs and ``[pci]device_spec`` " "configuration allowed nova to use multiple VFs from a single PF." msgstr "" #: ../../:604 msgid "" "Fixes `bug 2137673`_ where details about the fact that the user specified an " "incorrect configuration by requesting to attach to an external network are " "masked by \"Failure prepping block device\" since they do not have access to " "the whole backtrace." msgstr "" #: ../../:338 current msgid "" "Fixes `bug 2154495`_ by limiting vTPM and pCPU startup validation to the " "libvirt driver. Drivers that cannot support vTPM, such as Ironic, no longer " "inspect every local instance's flavor and image metadata during ``nova-" "compute`` startup to check for persisted vTPM requests." msgstr "" #: ../../:227 current msgid "" "Fixes an bug where deleting a volume backed server during the creation " "phase(building) could leave its cinder volume attachment behind. We will now " "check for already created BDMs during this deletion phase and will call/" "notify cinder for deleting these attachments." msgstr "" #: ../../:649 msgid "" "Fixes an issue seen when using bare metal (Ironic) instances where an " "instance could fail to delete. See `Bug 2019977`_ for more details." msgstr "" #: ../../:687 msgid "" "Fixes an issue when serial console for baremetal instances is not available. " "`See bug 2099872 `__" msgstr "" #: ../../:476 msgid "" "For backward compatibility, Nova continue allow ``admin`` role token to " "access service APIs but in future release, ``admin`` access will be removed." msgstr "" #: ../../:229 msgid "Get Console output" msgstr "" #: ../../:414 current msgid "" "However, nova metadata handler rejects a proxied metadata request if wrong " "signature was used for the request, but it logged the expected signature. " "This is now fixed and the expected signature is not present in the warning " "anymore. In case of concerns regarding the logged signature, it is advised " "to replace ``metadata_proxy_shared_secret`` in nova and neutron " "configuration. See `bug #2150094`_ description for more details." msgstr "" #: ../../:472 msgid "" "If you are allowing these APIs to be accessed by admin or non-admin users " "then it is highly recommended to remove that permission and make sure those " "APIs are not accessible by any non-service users." msgstr "" #: ../../:129 current msgid "" "If you are not upgrading the oslo.policy to 6.0.0, then there will not be " "any change in scope enforcement behaviour." msgstr "" #: ../../:360 msgid "" "Image properties and scheduler hints are now returned as part of the " "instance show API response." msgstr "" #: ../../:205 msgid "" "Implemented parallel live migrations for libvirt driver, which can be " "enabled by defining ``[libvirt] live_migration_parallel_connections`` to a " "value higher than 1. By default parallel migrations are not used to " "preserve existing behavior. Also note that QEMU prior to 10.1.0 was not able " "to support multifd with postcopy migrations, so enabling these two features " "together on older QEMU versions is disallowed." msgstr "" #: ../../:264 msgid "" "In addition, a number of new, more granular policies are introduced to allow " "us to use the ``project_manager`` persona in migration APIs:" msgstr "" #: ../../:182 msgid "" "In addition, the ``rxtx_factor`` and ``OS-FLV-DISABLED:disabled`` fields " "have been removed from all flavors responses, while the ``rxtx_factor`` " "field can no longer be provided when creating a server. Finally, all APIs " "now reject unknown query string parameters with a HTTP 400 (Bad Request) " "error, building upon work first started in microversion 2.75." msgstr "" #: ../../:526 msgid "" "In all cases, the replacement is the same option in the ``[api]`` group." msgstr "" #: ../../:341 msgid "" "In native threading mode the limit expressed by " "``[DEFAULT]max_concurrent_builds`` and ``[DEFAULT]max_concurrent_snapshots`` " "configuration options are shared across the two operation types as they are " "executed by the same Executor. Therefore the two config options need to be " "set to the same value. If not then nova will use the bigger value as the " "shared limit. The shared limit also means that one operation type can " "consume the whole limit." msgstr "" #: ../../:541 msgid "" "In the early days of Nova, all networking was internal, then ``quantum``, " "now known as ``neutron`` was introduced. When the networking subsystem was " "being externalized and neutron was optional Nova still needed to keep track " "of the ports associated with an instance. To that end, to avoid these " "expensive calls to an optional service the instance info cache was extended " "to include network information and a periodic task was introduced to update " "it in ``08fa534a0d28fa1be48aef927584161becb936c7`` as part of the ``Essex`` " "release." msgstr "" #: ../../:570 msgid "" "In this release, the default behaviour of Nova has been changed to disable " "the periodic, optimizing for performance, scale, power consumption and " "typical deployment topologies, where the instance network information is " "updated by neutron via the external event API as ports are modified. This " "should significantly reduce the background neutron API load in medium to " "large clouds. If you have a neutron backend that does not reliably send " "network-changed event notifications to Nova you can re-enable this periodic " "task by setting ``[compute]heal_instance_info_cache_interval`` to a value " "greater than 0." msgstr "" #: ../../:563 msgid "" "In``ba44c155ce1dcefede9741722a0525820d6da2b8`` as part of bug #1751923 the " "_heal_instance_info_cache periodic task was modified to pass a " "\"force_refresh\" forcing Nova to lookup the current state of all ports for " "the instance from neutron and fully rebuild the info_cache. This has the " "side effect of making the already poor scaling of this optional periodic " "task even worse." msgstr "" #: ../../:150 current msgid "" "Instances with ``binding:vif_type=bridge`` ports will fail to start on " "upgraded compute nodes with a clear error message." msgstr "" #: ../../:197 msgid "Ironic is configured to enable graphical consoles" msgstr "" #: ../../:140 current msgid "" "Linux bridge VIF support has been removed from Nova. The ``VIF_TYPE_BRIDGE`` " "VIF type is no longer supported by the libvirt virt driver." msgstr "" #: ../../:296 msgid "List migration:" msgstr "" #: ../../:282 msgid "List server migration:" msgstr "" #: ../../:224 msgid "Live migration" msgstr "" #: ../../:267 msgid "Live migration:" msgstr "" #: ../../:466 msgid "" "Make sure the configured nova service user in other services has the " "``service`` role otherwise communication from the other services to Nova " "will fail. For example, user configured as ``username`` option in ``neutron." "conf`` file under ``[nova]`` section has the ``service`` role." msgstr "" #: ../../:350 msgid "" "Manila shares can now be directly attached to instances by a new Nova shares " "API." msgstr "" #: ../../:157 current msgid "" "Migrate workloads from Neutron Linux bridge backend to a supported backend " "before upgrading Nova compute nodes." msgstr "" #: ../../:143 stable/2025.2>:136 #: stable/2026.1>:613 msgid "" "NVRAM variable store is preserved during stop/start, hard reboot, and live " "migration by passing the corresponding flag to libvirt." msgstr "" #: ../../:10 current stable/2025.1>:10 stable/2025.1>:378 stable/2025.2>:10 #: stable/2025.2>:229 stable/2026.1>:10 stable/2026.1>:144 msgid "New Features" msgstr "" #: ../../:36 current msgid "" "New configuration options ``[libvirt]images_cpu_time_limit`` and " "``[libvirt]images_address_space_limit`` have been added to enable tuning of " "process limits for qemu-img. The default for " "``[libvirt]images_address_space_limit`` is increased from a hard-coded 1G to " "2G in order to accommodate larger image requirements in newer versions of " "Ceph. For more details, see bug `#2116852`_." msgstr "" #: ../../:14 stable/2025.2>:14 stable/2026.1>:14 msgid "" "New configuration options ``[libvirt]images_cpu_time_limit`` and " "``[libvirt]images_address_space_limit`` have been added to enable tuning of " "process limits for qemu-img. The default for " "``[libvirt]images_address_space_limit`` is unchanged from the hard-coded 1G " "limit in order to maintain existing behavior. If you are using newer " "versions of Ceph this should be increased. For more details, see bug " "`#2116852`_." msgstr "" #: ../../:495 msgid "" "New configuration options ``[quota]unified_limits_resource_strategy`` and " "``[quota]unified_limits_resource_list`` have been added to enable operators " "to specify a list of resources that are either required or ignored to have " "registered limits set. The default strategy is ``require`` and the default " "resource list contains ``servers``. The configured list is only used when " "``[quota]driver`` is set to the ``UnifiedLimitsDriver``." msgstr "" #: ../../:346 msgid "" "New kernel vfio-PCI variant drivers like nvidia GRID on Ubuntu 24.04 are now " "supported by our PCI passthrough feature. You can create instances using " "those specific PCI devices but also live migrate them." msgstr "" #: ../../:437 msgid "" "New policies are added to the live migration APIs with the same default. If " "you are using default policy, then no action is needed, but if you have " "overridden the existing live migration policies in your deployment, you must " "include the new policy with the same permissions." msgstr "" #: ../../:290 stable/2025.2>:304 msgid "New policy is used to host info in live migrations list:" msgstr "" #: ../../:276 msgid "New policy is used when live migrate server to a specific host:" msgstr "" #: ../../:448 msgid "New policy:" msgstr "" #: ../../:363 msgid "Nova added support for the IGB VIF model." msgstr "" #: ../../:231 msgid "" "Nova added two new configuration options which will control this behavior:" msgstr "" #: ../../:457 msgid "" "Nova changed the default access for the service-to-service APIs which are " "meant to be used by the OpenStack services only and not by any users. The " "below service-to-service APIs access default to the ``service`` role:" msgstr "" #: ../../:211 stable/2025.2>:571 msgid "" "Nova has documented that the ``update volume attachment`` API PUT /servers/" "{server_id}/os-volume_attachments/{volume_id} should not be called directly " "for a very long time." msgstr "" #: ../../:680 msgid "" "Nova now allows to use a hyphen in the ``[cinder]catalog_info`` service-type " "field, so in particular the official ``block-storage`` type is now valid. " "`Bug 2092194 `_" msgstr "" #: ../../:98 msgid "" "Nova now enables one IOThread per QEMU instance by default, offloading disk " "I/O processing from vCPU threads to improve performance. For real-time " "instances, the IOThread is pinned to the same cores as the emulator thread " "to avoid impacting dedicated vCPUs." msgstr "" #: ../../:124 msgid "" "Nova now has full OpenAPI schema coverage, with JSON Schema for request and " "response bodies across all API endpoints, enabling future auto-generation of " "OpenAPI specifications." msgstr "" #: ../../:211 msgid "" "Nova now supports QEMU’s memory balloon autodeflate and free page reporting " "features with the libvirt driver. These allow unused guest memory to be " "automatically released back to the hypervisor, improving memory efficiency " "and reducing the risk of the Out-of-Memory killer activating." msgstr "" #: ../../:370 msgid "" "Nova now supports a new console type called `spice-direct`  if you define a " "specific SPICE protocol native proxy URL (eg. a kerbside URL). Direct SPICE " "VDI consoles enable a much richer virtual desktop experience." msgstr "" #: ../../:194 msgid "" "Nova now supports a new default role ``manager`` which is scoped to the " "project level. This role is part of the standard role hierarchy supported by " "Keystone and allows trusted project users to perform project-level " "management tasks (e.g., live migration) without requiring full admin rights." msgstr "" #: ../../:233 msgid "" "Nova now supports a new default role ``manager``. This role is part of the " "standard role hierarchy supported by keystone. A new persona, the " "``project_manager``, is denoted by someone with the ``manager`` role on a " "specific project. The ``project_manager`` persona is intended to perform " "more privileged operations than a ``project_member`` while granting less " "access than the global admin role. This brings the total set of personas " "currently supported by Nova to:" msgstr "" #: ../../:103 msgid "" "Nova now supports live migration of instances with vTPM devices when using " "``host`` secret security mode. A new ``hw:tpm_secret_security`` extra spec " "allows operators to select this mode, where the TPM secret is persisted in " "libvirt and transferred over RPC to the destination during migration. " "Instance owners can resize existing legacy vTPM instances to a flavor with " "``hw:tpm_secret_security=host`` to opt in to live migration. Note that this " "resize must be performed by the instance owner due to Barbican secret " "ownership constraints, unless the admin has been granted appropriate ACLs in " "Barbican. The legacy ``user`` secret security mode does not yet support live " "migration but may do so in a future release once additional deployment and " "API changes are completed." msgstr "" #: ../../:203 msgid "" "Nova now supports one-time use passthrough devices. Such devices are " "allocated to a single instance, and when the instance is deleted, the device " "stays in a reserved state instead of becoming automatically available. This " "ensures operators can perform necessary security checks or hardware resets " "before reusing the device." msgstr "" #: ../../:93 msgid "" "Nova now supports parallel live migrations via a new ``[libvirt] " "live_migration_parallel_connections`` config option, enabling multiple " "connections for memory transfer during live migration to improve speed." msgstr "" #: ../../:92 #: stable/2025.2>:92 stable/2026.1>:508 msgid "" "Nova operation with VIF type TAP was broken by a libvirt change (in 9.5.0) " "to treat TAP interface specifications as \"managed\" by default. This means " "that libvirt expects to create the TAP interface itself, which is " "incompatible with how Nova works, because Nova creates the TAP interface " "before telling libvirt about it. In particular this broke OpenStack with " "Calico as the network plugin, because Calico uses VIF type TAP." msgstr "" #: ../../:214 msgid "" "Nova services now support graceful shutdown on ``SIGTERM``. When a service " "receives ``SIGTERM``, it will stop accepting new RPC requests and wait for " "in-progress tasks to reach a safe termination point." msgstr "" #: ../../:119 msgid "" "Nova's libvirt driver now delegates UEFI firmware selection to libvirt " "instead of handling it internally. Libvirt's built-in auto-selection picks " "the best firmware file based on requested features (including Secure Boot " "and AMD SEV), and supports additional firmware types like ROM." msgstr "" #: ../../:158 msgid "" "Now the libvirt virt driver uses firmware auto-selection by libvirt, which " "is capable to select the appropriate firmware files according to the " "requested features. This built-in auto-selection extends the existing " "firmware selection capability within nova, and checks a few more feature " "flags such as amd-sev and also supports new firmware types such as rom " "firmware." msgstr "" #: ../../:443 msgid "" "On HCI deployments where Nova is collocated with the Cinder service or the " "Glance using Cinder backend service, an os-brick shared location can be " "configured using the ``lock_path`` in the ``[os_brick]`` configuration " "section." msgstr "" #: ../../:187 stable/2025.2>:676 msgid "" "Only attempting RPC-based uptime retrieval for hypervisor types that " "actually support it (libvirt and z/VM), avoiding unnecessary calls to other " "hypervisor types that would always return NotImplementedError" msgstr "" #: ../../:143 current msgid "" "Operators using Neutron's Linux bridge mechanism driver must migrate their " "deployments to a supported backend such as Open vSwitch (OVS) or OVN before " "upgrading Nova. Note that neutron removed support for the Linux bridge in " "2025.1 (epoxy)." msgstr "" #: ../../:440 current msgid "" "Optimized the discovery of PCI passthrough devices and added caching. " "Previously libvirt was called 3 times per device, this has been reduced to a " "single call." msgstr "" #: ../../:458 msgid "" "Option ``novncproxy_base_url`` does now respect supplied custom query which " "might be used to move NoVNC to a subdirectory or pass an extra argument to " "NoVNC." msgstr "" #: ../../:428 current msgid "Other Notes" msgstr "" #: ../../:321 msgid "" "Please refer `Policy New Defaults`_ for detail about policy new defaults." msgstr "" #: ../../:190 stable/2025.2>:679 msgid "" "Preferring cached uptime data from the database over RPC calls when " "available, this updates at the cadence specified by " "`[DEFAULT]update_resources_interval` which is the same interval the other " "hypervisor stats update." msgstr "" #: ../../:324 stable/2025.2>:170 #: stable/2026.1>:73 msgid "Prelude" msgstr "" #: ../../:115 stable/2025.2>:108 #: stable/2026.1>:564 msgid "" "Previously the ImagePropertiesWeigher was not running correctly as it wasn't " "targeting the correct cell context for getting the system metadata of the " "instances. This was fixed in bug `#2125935`_." msgstr "" #: ../../:119 current msgid "" "Python 3.10 support has been dropped. The minimum version of Python now " "supported by nova is Python 3.11." msgstr "" #: ../../:637 msgid "Quobyte" msgstr "" #: ../../:161 current msgid "Remove any Nova-specific Linux bridge configuration options." msgstr "" #: ../../:226 msgid "Resize" msgstr "" #: ../../:227 msgid "Revert resize" msgstr "" #: ../../:497 msgid "" "Running API services (nova-osapi_compute or nova-metadata) with eventlet is " "removed. Deploy with a WSGI server such as uwsgi or mod_wsgi." msgstr "" #: ../../:638 msgid "SMBFS" msgstr "" #: ../../:313 msgid "" "Scope checks and new defaults are enabled by default and it is recommended " "to use new defaults. However, if your deployment needs more time then you " "can disable them by switching the below config option in ``nova.conf`` file.:" "" msgstr "" #: ../../:200 current stable/2025.1>:27 stable/2025.1>:66 stable/2025.1>:207 #: stable/2025.2>:27 stable/2025.2>:66 stable/2025.2>:567 stable/2026.1>:27 #: stable/2026.1>:462 msgid "Security Issues" msgstr "" #: ../../:102 #: stable/2025.2>:102 stable/2026.1>:518 msgid "See `bug 2033681`_ for more details." msgstr "" #: ../../:631 msgid "See `bug 2069718 `_." msgstr "" #: ../../:146 stable/2025.2>:139 #: stable/2026.1>:616 msgid "See https://bugs.launchpad.net/nova/+bug/1633447 for more details." msgstr "" #: ../../:445 current msgid "" "Separately, please be aware of an upstream bug in libvirt (< 10.5) that " "caused an leak of GSource objects, which slowed down queries over time. " "https://gitlab.com/libvirt/libvirt/-/commit/" "98f1cf88fa7e0f992d93f376418fbfb3996a9690" msgstr "" #: ../../:228 msgid "Server external Event" msgstr "" #: ../../:200 msgid "" "Service-to-service APIs now use the ``service`` role, reducing unnecessary " "privileges for cross-service communication." msgstr "" #: ../../:115 msgid "" "Starting from microversion 2.101, the volume-attach API is now asynchronous, " "returning HTTP 202 instead of blocking until completion. This reduces API " "response time by offloading the operation to nova-conductor." msgstr "" #: ../../:473 msgid "" "Support creating servers with RBAC shared security groups by using the new " "``shared`` filter for security groups. See `blueprint shared-security-" "groups`_ for more details." msgstr "" #: ../../:608 msgid "" "Support for Python 3.8 has been removed. Now the minimum python version " "supported is 3.9 ." msgstr "" #: ../../:433 msgid "" "The 2.98 microversion has been added. This microversion adds support for " "including image properties as new ``properties`` subkey under the struct at " "the existing ``image`` key in the response for ``GET /servers/{server_id}`` " "(server show), ``PUT /servers/{server_id}`` (server update), and ``GET /" "servers/detail`` (list server --long) APIs. Also the same is included in " "rebuild case of ``POST /server/{server_id}/action`` (server rebuild) API " "response." msgstr "" #: ../../:194 msgid "" "The Ironic driver now supports VNC consoles when available. The pre-" "requesites for this being available for a node is:" msgstr "" #: ../../:328 msgid "" "The OpenStack 2025.1 Epoxy (Nova 31.0.0) release includes many new features " "and bug fixes. Please be sure to read the upgrade section which describes " "the required actions to upgrade your cloud from 30.0.0 (2024.2) to 31.0.0 " "(2025.1). As a reminder, OpenStack 2025.1 is a `Skip-Level-Upgrade " "Release`__ (starting from now, we name it a `SLURP release`) meaning that " "you can do rolling-upgrades from 2024.1 Caracal directly by skipping to " "upgrade to 2024.2 Dalmatian release." msgstr "" #: ../../:174 msgid "" "The OpenStack 2025.2 (Nova 32.0.0) release includes many new features and " "bug fixes. Please be sure to read the upgrade section which describes the " "required actions to upgrade your cloud from 31.0.0 (2025.1) to 32.0.0 (2025." "2). As a reminder, OpenStack 2025.2 is not a `Skip-Level-Upgrade Release " "`_ (starting from now, we name it a `SLURP release`) meaning " "that you can't do rolling-upgrade from 2024.2, you first need to upgrade to " "2025.1." msgstr "" #: ../../:77 msgid "" "The OpenStack 2026.1 Gazpacho (Nova 33.0.0) release includes many new " "features and bug fixes. Please be sure to read the upgrade section which " "describes the required actions to upgrade your cloud from 32.0.0 (2025.2) to " "33.0.0 (2026.1). As a reminder, OpenStack 2026.1 is a `Skip-Level-Upgrade " "Release `_ (starting from now, we name it a `SLURP release`) " "meaning that you can do rolling-upgrades from 2025.1 Epoxy directly by " "skipping to upgrade to 2025.2 Flamingo release." msgstr "" #: ../../:397 msgid "" "The WSGI scripts, ``nova-api-wsgi`` and ``nova-metadata-wsgi``, have been " "removed. Deployment tooling should instead reference the Python module paths " "for these services, ``nova.wsgi.osapi_compute`` and ``nova.wsgi.metadata``, " "if their chosen WSGI server supports this (gunicorn, uWSGI) or implement a " "``.wsgi`` script themselves if not (mod_wsgi)." msgstr "" #: ../../:502 msgid "" "The ``[api] neutron_default_tenant_id`` option has been renamed to ``[api] " "neutron_default_project_id`` and the legacy ``[DEFAULT] " "neutron_default_tenant_id`` alias removed." msgstr "" #: ../../:447 msgid "" "The ``[filter_scheduler] aggregate_image_properties_isolation_namespace`` " "and ``[filter_scheduler] aggregate_image_properties_isolation_separator`` " "config options have been deprecated for removal. These have been effectively " "unusable since the 12.0.0 (Liberty) release, which removed the ability for " "the ``AggregateImagePropertiesIsolation`` scheduler filter to filter on any " "non-standard image metadata property. Users who require this functionality " "should consider enforcing `aggregate isolation using placement traits`__." msgstr "" #: ../../:556 msgid "" "The ``[libvirt] num_memory_encrypted_guests`` option has been deprecated and " "will be removed in a future release. The option will be completely replaced " "by the number of SEV-encrypted guests presented by domain capabilities API " "in libvirt, which is available since version 8.0.0 . The libvirt's API is " "more feature complete and supports detecting the limit for SEV-ES-encrypted " "guests." msgstr "" #: ../../:628 msgid "" "The ``[wsgi] secure_proxy_ssl_header`` parameter has been deprecated. Use " "the ``http_proxy_to_wsgi`` middleware from ``oslo.middleware`` instead." msgstr "" #: ../../:385 msgid "" "The ``hw:sound_model`` flavor extra spec and the matching ``hw_sound_model`` " "image property were added to allow the configuration of a sound device " "within an instance. This is useful with the new spice-direct console type. " "The default remains no sound device, but when using the libvirt hypervisor " "driver you can select from ``sb16``, ``es1370``, ``pcspk``, ``ac97``, " "``ich6``, ``ich9``, ``usb``, and ``virtio``. For most use-cases ``usb`` is " "likely to be the best choice unless you have at least libvirt 8.2.0 and " "libvirt 10.4.0." msgstr "" #: ../../:418 msgid "" "The ``hw:usb_model`` flavor extra spec and the matching ``hw_usb_model`` " "image property were added to allow the configuration of a USB controller " "within an instance. This is useful with the new spice-direct console type " "which supports passing through USB devices from the client to the instance, " "such as a smart card reader. There is also an additional ``hw:" "redirected_usb_ports`` / ``hw_redirected_usb_ports`` pair which controls how " "many ports the USB controller has. This number will vary based on the USB " "controller selected. The default remains no USB controller, but when using " "the libvirt hypervisor driver you can now also select from ``qemu_xhci`` and " "``nec_xhci``." msgstr "" #: ../../:482 msgid "" "The ``nova-manage limits migrate_to_unified_limits`` command will now scan " "the API and cell databases to detect resource classes that do not have " "registered limits set in Keystone and report them to the console." msgstr "" #: ../../:25 current msgid "" "The ``nova-manage`` and ``nova-status`` CLI commands now support native " "threading mode via the ``OS_NOVA_DISABLE_EVENTLET_PATCHING`` environment " "variable. This allows CLI commands that perform cross-cell operations using " "scatter-gather patterns (e.g., ``nova-manage cell_v2 list_hosts``, ``nova-" "status upgrade check``, ``nova-manage placement heal_allocations``) to " "benefit from concurrent execution with native threading. For more details, " "see the concurrency guide: ``__" msgstr "" #: ../../:378 msgid "" "The ``one_time_use`` tag was added to the PCI ``device_spec`` description, " "which allows leaving devices in reserved state after they have been assigned " "to an instance. This is useful for data cleaning, firmware updates, and " "other operator-specific workflows." msgstr "" #: ../../:520 msgid "" "The ``unified_limits_resource_list`` list can also be set to an empty list." msgstr "" #: ../../:497 msgid "" "The `bug 1856329`_ is fixed where the ``fault`` field was empty in the " "response of ``GET /servers/detail`` when instances were located in a nova " "cell DB. The ``InstanceList.fill_faults()`` method has been updated to use " "``scatter_gather_all_cells()`` to properly retrieve faults from all cells, " "ensuring fault information is consistently returned regardless of which cell " "contains the instance." msgstr "" #: ../../:536 msgid "" "The below service-to-service APIs policy rule default value ``role:admin or " "role:service`` is deprecated and will be changed to ``role:service`` in " "future release:" msgstr "" #: ../../:218 msgid "" "The compute service creates a second RPC server on an ``compute-alt`` topic " "which remains active during graceful shutdown, allowing compute service to " "finish the in-progress tasks." msgstr "" #: ../../:385 msgid "" "The compute service now creates a second RPC server on the ``compute-alt`` " "topic. This means each compute worker will create an additional RabbitMQ " "queue." msgstr "" #: ../../:47 current msgid "" "The default concurrency mode is now switched from eventlet to native " "threading for nova-conductor, and nova-compute services. The concurrency " "mode can still be switched back to eventlet if needed per service. Please " "read the `concurrency `__ guide for more details." msgstr "" #: ../../:268 msgid "" "The default concurrency mode is now switched from eventlet to native " "threading for nova-scheduler, nova-api, and nova-metadata services. The " "concurrency mode can still be switched back to eventlet if needed per " "service. Please read the `concurrency `__ guide for more details." msgstr "" #: ../../:364 msgid "" "The default value of ``[DEFAULT]/graceful_shutdown_timeout`` has been " "changed from 60 to 180 seconds for all Nova services. This means that when a " "Nova service receives ``SIGTERM``, it will now wait up to 180 seconds for a " "graceful shutdown before being forcefully terminated. Operators using " "external system (e.g. k8s, systemd) to manage the Nova serviecs should " "ensure that their service stop timeouts are set to at least " "``graceful_shutdown_timeout`` to avoid forcefully killing service before " "Nova finish its graceful shutdown. For example, the systemd " "``TimeoutStopSec`` should be set to at least 180 seconds (or greater) for " "Nova services." msgstr "" #: ../../:309 msgid "" "The default value of the configuration option " "``[DEFAULT]sync_power_state_thread_pool_size`` is changed from 1000 to 5 to " "have a value that is safe to use in native threading mode. If you are still " "using the eventlet mode and relying on a higher value then configure that " "higher value explicitly before the upgrade. Please read the `concurrency " "`__ guide for " "more details." msgstr "" #: ../../:134 current msgid "" "The deprecated ``[libvirt] num_memory_encrypted_guests`` option has been " "removed. Now the maximum memory encrypted guests is detected automatically " "using libvirt API." msgstr "" #: ../../:124 current msgid "" "The deprecated ``[oslo_policy] enforce_scope`` configuration option has been " "removed in oslo.policy version 6.0.0 which will impact Nova as there is no " "longer any way to disable RBAC policy scope enforcement; scope checks are " "now always enforced regardless of configuration." msgstr "" #: ../../:182 stable/2025.2>:671 msgid "The fix optimizes uptime retrieval by:" msgstr "" #: ../../:508 msgid "" "The following aliases for ``[api]`` options have been removed. They have " "been deprecated since the 15.0.0 (Ocata) release." msgstr "" #: ../../:464 msgid "" "The following share attach and share detach versioned notifications have " "been added to the nova-compute service: * instance.share_attach.start * " "instance.share_attach.end * instance.share_detach.start * instance." "share_detach.end" msgstr "" #: ../../:633 msgid "" "The following volume drivers of the libvirt virt driver have been deprecated " "and will be removed in a future release. The corresponding volume drivers in " "cinder were all marked unsupported and will be removed." msgstr "" #: ../../:216 current msgid "" "The instance info cache now preserves the existing interface network MTU " "metadata when an interface from a new network is attached to an instance. " "Previously the MTU for already-attached interfaces could be dropped from the " "cache, which could cause live migration to fail with a source and " "destination network card MTU mismatch. See `Bug 2080531`_ for more details." msgstr "" #: ../../:258 current msgid "" "The ironic virt driver now overrides ``get_num_instances`` to use the node " "cache instead of the default implementation which calls ``list_instances`` " "and loads each instance via a database call. This improves the performance " "of the ``sync_power_states`` periodic task for deployments with a large " "number of baremetal nodes. See `bug 2117700`_ for details." msgstr "" #: ../../:342 msgid "" "The latest Compute API microversion supported for 2024.2 is `v2.100`__." msgstr "" #: ../../:186 msgid "" "The latest Compute API microversion supported for 2025.2 is `v2.100 `_." msgstr "" #: ../../:90 msgid "" "The latest Compute API microversion supported for 2026.1 is `v2.103 `_." msgstr "" #: ../../:547 msgid "" "The legacy v2 API is now deprecated for removal, and the status in the root " "version document (``/``) has been changed from ``SUPPORTED`` to " "``DEPRECATED``. This will cause some clients like keystoneauth to ignore the " "endpoint by default. Users are encouraged to switch the v2.1 API, which is " "functionally identical to the v2 API when using the ``2.1`` API microversion." "" msgstr "" #: ../../:336 msgid "" "The libvirt driver can now support requests for guest RAM to be encrypted " "using the AMD SEV-ES(Secure Encrypted Virtualization-Encrypted State), " "instead of AMD SEV." msgstr "" #: ../../:14 current msgid "" "The libvirt driver can now support requests for guest RAM to be encrypted " "using the AMD SEV-SNP(Secure Nested Paging), in addition to AMD SEV and AMD " "SEV-ES." msgstr "" #: ../../:367 msgid "" "The libvirt driver now automatically enables ``autodeflate`` and " "``freePageReporting`` features for virtio memory balloon devices. The " "``autodeflate`` feature allows the QEMU virtio memory balloon to release " "memory at the last moment before a guest process is killed by the Out of " "Memory killer. The ``freePageReporting`` feature enables the memory balloon " "to return unused pages back to the hypervisor for use by other guests or " "processes, improving overall memory efficiency on the compute host." msgstr "" #: ../../:382 msgid "" "The libvirt driver now supports hw_vif_model=igb image property if the " "hypervisor has libvirt version 9.3.0 and qemu version 8.0.0 or higher." msgstr "" #: ../../:277 msgid "" "The libvirt driver now supports live migration of servers with virtual " "emulated TPM (vTPM) when the ``hw:tpm_secret_security`` flavor extra spec is " "set to ``host``. Operators must create flavors which set ``hw:" "tpm_secret_security`` in order to enable servers to select a particular TPM " "secret security mode. Pre-existing servers can opt-in to the ``host`` TPM " "secret security mode by resizing to a flavor which has set ``hw:" "tpm_secret_security`` to ``host``. Operators may choose which TPM security " "modes they want to support by setting the " "``[libvirt]supported_tpm_secret_security`` configuration option on compute " "hosts. See the documentation for details: https://docs.openstack.org/nova/" "latest/admin/emulated-tpm.html" msgstr "" #: ../../:189 msgid "" "The libvirt guest XML now includes additional flavor and image metadata " "fields so that it can be used during troubleshooting or services like " "Ceilometer can retrieve accurate instance information directly, without " "performing extra Nova API calls." msgstr "" #: ../../:319 msgid "" "The meaning of the 0 value of the config option " "``[DEFAULT]max_concurrent_builds`` has been changed. In the past it meant " "\"unlimited\" but actually it was limited by the oslo.messaging's " "``executor_thread_pool_size`` config option. For eventlet mode \"unlimited\" " "now means 1000 concurrent builds. For the native threading mode it is now " "reduced to 10 native threads. Please also read the `concurrency `__ guide for more " "details." msgstr "" #: ../../:297 msgid "" "The meaning of the 0 value of the config option " "``[DEFAULT]max_concurrent_live_migrations`` has been changed. In the past " "the implementation of the meaning of \"unlimited\" used maximum 1000 " "concurrent worker greenthreads. For eventlet mode this behavior is kept but " "for the native threading mode it is now reduced to 5 native threads. It is " "almost always a bad idea to change this config option from its default " "value, 1. Please read the `concurrency `__ guide for more details." msgstr "" #: ../../:330 msgid "" "The meaning of the 0 value of the config option " "``[DEFAULT]max_concurrent_snapshots`` has been changed. In the past it meant " "\"unlimited\" but actually it was limited by the oslo.messaging's " "``executor_thread_pool_size`` config option. For eventlet mode \"unlimited\" " "now means 1000 concurrent snapshots. For the native threading mode it is now " "reduced to 5 native threads. Please also read the `concurrency `__ guide for more details." msgstr "" #: ../../:582 msgid "" "The minimum required version of libvirt by the `nova-compute` service is now " "8.0.0, and the minimum required version of QEMU is 6.2.0. Failing to meet " "these minimum versions when using the libvirt compute driver will result in " "the `nova-compute` service not starting. The next minimum required version " "of libvirt to be used in a future release is 10.0.0, while the next minimum " "QEMU is 8.2.2." msgstr "" #: ../../:524 msgid "" "The new ``[libvirt] volume_enforce_multipath`` option has been added. When " "this option is set to ``True``, attachment of volumes is aborted when " "multipathd is not running in the host. Otherwise it falls back to single " "path. This option also makes the libvirt driver to check multipathd during " "initialization, and the compute service fails to start if mulitipathd is not " "running." msgstr "" #: ../../:198 msgid "" "The node ``console_interface`` is a graphical driver such as ``redfish-" "graphical`` or ``fake-graphical``" msgstr "" #: ../../:298 #: stable/2025.2>:696 msgid "" "The nova (metadata)api wsgi application will now detect fatal errors " "(configuration, et al) on startup and lock into a permanent error state " "until fixed and restarted. This solves a problem with some wsgi runtimes " "ignoring initialization errors and continuing to send requests to the half-" "initialized service. See https://bugs.launchpad.net/nova/+bug/2103811 for " "more details." msgstr "" #: ../../:413 msgid "" "The nova scheduler now supports enabling the nova cell discover hosts " "perodic task on multiple schedulers. In prior release enabling this feature " "required setting the discover_hosts_in_cells_interval option to a value " "greater than 0 in at most one scheduler, with the 2025.1 release it was " "possible to enable the feature on multiple schedulers via the introduction " "of leader election. This simplifies deployment of nova in kubernetes by " "allowing the operator to deploy multiple schedulers and have them elect a " "single leader that will run the discover hosts perodic task." msgstr "" #: ../../:397 msgid "" "The nova-api and nova-metadata services now can be run in native threading " "mode instead of with eventlet. This is an experimental feature that is " "disabled by default. Please test the native threading mode in pre-production " "before enabling it in production. If you do so please let us now how it went " "on the mailing list openstack-discuss@lists.openstack.org. Please read the " "`concurrency `__ guide for more details." msgstr "" #: ../../:92 current msgid "" "The nova-compute service with libvirt driver now fails to start if any " "instance in its host requires the memory encryption feature by AMD SEV-ES " "but it also detects AMD SEV-SNP enabled in the host hardware. The detection " "is based on the sev_snp parameter of the kvm_amd kernel module, exposed at " "``/sys/module/kvm_amd/parameters/sev_snp``." msgstr "" #: ../../:250 msgid "" "The nova-compute services now can be run in native threading mode instead of " "with eventlet. This is an experimental feature that is disabled by default. " "Please test the native threading mode in pre-production before enabling it " "in production. Please read the `concurrency `__ guide for more details." msgstr "" #: ../../:259 msgid "" "The nova-conductor services now can be run in native threading mode instead " "of with eventlet. This is an experimental feature that is disabled by " "default. Please test the native threading mode in pre-production before " "enabling it in production. Please read the `concurrency `__ guide for more details." msgstr "" #: ../../:408 msgid "" "The nova-scheduler now can be run in native threading mode instead of with " "eventlet. This is an experimental feature that is disabled by default. " "Please test the native threading mode in pre-production before enabling it " "in production. If you do so please let us now how it went on the mailing " "list openstack-discuss@lists.openstack.org. Please read the `concurrency " "`__ guide for " "more details." msgstr "" #: ../../:356 msgid "" "The nova-scheduler service now does leader election in an attempt to have " "only one run host discovery periodically (if configured) instead of all of " "them running it all the time in parallel." msgstr "" #: ../../:515 msgid "" "The options should be configured for the :program:`nova-api` and :program:" "`nova-conductor` services. The :program:`nova-conductor` service performs " "quota enforcement when ``[quota]recheck_quota`` is ``True`` (the default)." msgstr "" #: ../../:435 msgid "" "The possible 0 value of the configuration option " "``[DEFAULT]max_concurrent_builds`` is deprecated and will be removed in a " "future release." msgstr "" #: ../../:426 msgid "" "The possible 0 value of the configuration option " "``[DEFAULT]max_concurrent_live_migrations`` is deprecated and will be " "removed in a future release. It is almost always a bad idea to change the " "default value, 1, of this config option. If more performant live migration " "is needed, use the ``live_migration_parallel_connections`` config option " "instead." msgstr "" #: ../../:441 msgid "" "The possible 0 value of the configuration option " "``[DEFAULT]max_concurrent_snapshots`` is deprecated and will be removed in a " "future release." msgstr "" #: ../../:486 msgid "" "The purpose of the flavor scan is to assist operators who are migrating from " "legacy quotas to unified limits quotas. The current behavior with unified " "limits is to fail quota checks if resources requested are missing registered " "limits in Keystone. With flavor scanning in ``migrate_to_unified_limits``, " "operators can easily determine what resource classes for which they need to " "create registered limits." msgstr "" #: ../../:488 msgid "" "The remote debugger has been removed from the codebase. If you were using " "it, you will need to find an alternative solution. The remote debugger was " "un-maintained and was first introduced in the early days of OpenStack when " "we used python 2.7. While it was useful at the time, it has not been " "maintained and updated to work with new versions of python and eventlet. As " "a result it is being removed until we complete the eventlet removal." msgstr "" #: ../../:351 msgid "" "The server-shares API policies have been updated to allow admin users (those " "with the role admin) to access them. There are no changes to the permissions " "for project users with the role reader/member. The following API policies " "have been updated from PROJECT_READER/PROJECT_MEMBER to " "PROJECT_READER_OR_ADMIN/PROJECT_MEMBER_OR_ADMIN to facilitate this change." msgstr "" #: ../../:177 msgid "" "The v2.102 microversion has been introduced. This allows users to search " "flavors by name, e.g.::" msgstr "" #: ../../:391 msgid "" "The v2.103 microversion has been introduced. This deprecates the hitherto " "undocumented ``/os-volumes_boot`` API. HTTP 404 will be returned for all " "requests starting with this API microversion." msgstr "" #: ../../:432 current msgid "" "The virt driver API has been extended with a new " "``process_instances_at_startup`` function. Drivers can optionally override " "its default no-op implementation to process instances during ``nova-" "compute`` startup and perform any driver-specific initialization or " "validation they require." msgstr "" #: ../../:56 current msgid "" "The websocketproxy (``nova-novncproxy``, ``nova-serialproxy``, and ``nova-" "spicehtml5proxy``) can now be run in native threading mode instead of with " "eventlet. This is an experimental feature that is disabled by default. " "Please read the ``concurrency`` guide for more details: ``__" msgstr "" #: ../../:339 stable/2025.2>:183 #: stable/2026.1>:87 msgid "" "There are a few major changes worth mentioning. This is not an exhaustive " "list:" msgstr "" #: ../../:195 stable/2025.2>:684 msgid "" "This change significantly reduces response times for the hypervisor detail " "API in large deployments while maintaining backward compatibility." msgstr "" #: ../../:99 stable/2025.2>:99 stable/2026.1>:515 msgid "" "This is now fixed, by Nova adding the `managed=\"no\"` attribute to TAP " "interface XML specifications." msgstr "" #: ../../:279 current msgid "" "This patch addresses this by adding the ``-y`` flag, which runs ``lvcreate`` " "in non-interactive mode with the default option being ``yes``." msgstr "" #: ../../:425 msgid "" "This release adds support for SR-IOV devices using the new kernel VFIO SR-" "IOV variant driver interface. See the `OpenStack pci-passthrough " "documentation`__ for more details." msgstr "" #: ../../:450 msgid "" "This release adds support for migrating SR-IOV devices using the new kernel " "VFIO SR-IOV variant driver interface. See the `OpenStack configuration " "documentation`__ for more details." msgstr "" #: ../../:246 msgid "" "To avoid any change in ``admin`` permissions, Nova uses " "``PROJECT_MANAGER_OR_ADMIN`` as a default where manager access is granted. " "In this release, the below APIs policy are newly defaulted to " "``PROJECT_MANAGER_OR_ADMIN``:" msgstr "" #: ../../:482 msgid "" "To expose the newly added attributes in the libvirt domain metadata in an " "upgraded environment, already running instances will need to be shutdown, " "restarted, cold migrated or shelved and unshelved." msgstr "" #: ../../:80 current msgid "" "Two indexes were added to the ``migrations`` table: " "``migrations_by_src_host_nodes_and_status_idx`` and " "``migrations_by_dest_host_nodes_and_status_idx``. These indexes optimize " "migration lookups for a specific compute node by source or destination host/" "node and are used by the ``_cleanup_incomplete_migrations`` periodic task " "(run every 5 minutes by default on each compute service). In environments " "with large migration tables, this significantly reduces query latency and " "improves the nova-conductor performance. See `bug 2121465 `__ for details." msgstr "" #: ../../:592 msgid "" "Ubuntu 24.04 does not support the QXL video model or spice. Operators using " "instances with this video model will be unable to start them if moving to " "Ubuntu 24.04. CentOS 9 and RHEL 9 previously compiled out support for spice, " "and as QXL was implemented in libspice, support for QXL was removed as a " "result for the removal of support for spice. The QXL model was a spice " "optimized video model and is no longer supported by several distros. To " "avoid issues with starting instances, operators should change the spice " "video model from QXL to virtio and replace the spice console with vnc. For " "existing instances the video model can be updated with the ``nova-manage " "image_property set`` command. When updating the embedded image properties, " "operators should evaluate if any glance images request the QXL video model " "and update them or work with the image owner to have them move to a modern " "video model." msgstr "" #: ../../:365 msgid "" "Unified limits are no longer experimental since we added a nova-manage tool " "for migrating existing quota limits to Keystone automatically and given we " "added new configuration options for telling which resource classes are " "either required or ignored." msgstr "" #: ../../:159 current msgid "" "Update Neutron configuration to use supported mechanism drivers (OVS, OVN, " "SR-IOV, etc.)." msgstr "" #: ../../:620 msgid "" "Updated nova to support os-vif TAP device pre-creation for OVN ports. When " "Neutron sets ``ovs_create_tap`` in vif_details (enabled via the ``[ovn]/" "ovs_create_tap`` config option in the ML2 driver config), Nova propagates " "this to os-vif which creates the TAP device before libvirt starts the VM. " "Nova then configures libvirt with ``managed=\"no\"`` so it uses the pre-" "created TAP device instead of creating a new one. This allows nova via os-" "vif to pre create the tap device in pre live migration allowing ovn to " "install openflow rules before nova starts the live migration. This reduces " "network connectivity downtime when ovn is overloaded." msgstr "" #: ../../:76 #: current stable/2025.1>:535 stable/2025.2>:433 stable/2026.1>:293 msgid "Upgrade Notes" msgstr "" #: ../../:340 msgid "" "Usage of AMD SEV-ES for memory encryption can be required either via a " "flavor which has the ``hw:mem_encryption_model`` extra spec set to ``amd-sev-" "es``, or via an image which has the ``hw_mem_encryption_model`` property set " "to ``amd-sev-es``. In case the extra spec and the property are unset or set " "to ``amd-sev``, then AMD SEV is used for memory encryption." msgstr "" #: ../../:18 current msgid "" "Usage of AMD SEV-SNP for memory encryption can be required either via a " "flavor which has the ``hw:mem_encryption_model`` extra spec set to ``amd-sev-" "snp``, or via an image which has the ``hw_mem_encryption_model`` property " "set to ``amd-sev-snp``." msgstr "" #: ../../:639 msgid "Virtuozzo Storage" msgstr "" #: ../../:244 msgid "" "We plan to improve the graceful shutdown in future releases by task tracking " "and transitioning resources to a recoverable state. Until then, this feature " "is experimental." msgstr "" #: ../../:509 msgid "" "When ``unified_limits_resource_strategy = ignore``, if a resource in " "``unified_limits_resource_list`` is requested and has no registered limit " "set, the quota limit for that resource will be considered to be unlimited " "and all requests to allocate that resource will be accepted. Any resource " "not in the list will be considered to have 0 quota." msgstr "" #: ../../:503 msgid "" "When ``unified_limits_resource_strategy = require``, if a resource in " "``unified_limits_resource_list`` is requested and has no registered limit " "set, the quota limit for that resource will be considered to be 0 and all " "requests to allocate that resource will be rejected for being over quota. " "Any resource not in the list will be considered to have unlimited quota." msgstr "" #: ../../:640 msgid "" "When an instance booted from local storage is unshelved, the image ID " "published to the libvirt domain metadata was the ID for the temporary Glance " "image generated to store the instance state, instead of the original image " "as intended. Since the temporary image is removed after the instance is " "unshelved, this results in an invalid image ID being stored in the libvirt " "domain metadata. This issue has now been fixed. Affected instances will need " "to be shutdown, restarted, cold migrated or shelved-and-unshelved to update " "the metadata." msgstr "" #: ../../:533 msgid "" "When deleting multiple instances that share the same multi-attach volume on " "the same compute host in parallel, the volume connection could be left " "attached to the host even after all instances were deleted, preventing the " "volume from being properly detached and reused. Nova now correctly cleans up " "multi-attach volume connections when deleting instances, including when " "multiple instances sharing the same volume are deleted concurrently. For " "more details, see `bug 2048837 `__." msgstr "" #: ../../:307 stable/2025.2>:705 msgid "" "When live migration fails during pre_live_migration on the destination, " "during rollback Cinder volumes will now be disconnected from the destination " "locally instead of remotely over RPC from the source. This should ensure " "that only connection_info for the destination will be used to disconnect " "volumes from the destination. See `bug #1899835 `_ for more details." msgstr "" #: ../../:613 msgid "" "When the ``[quota]driver`` configuration option is set to the " "``UnifiedLimitsDriver``, a limit of ``-1`` in Keystone will now be " "considered as unlimited and the ``servers`` resource will be considered to " "be required to have a registered limit set in Keystone because of the values " "for ``[quota]unified_limits_resource_strategy`` and " "``unified_limits_resource_strategy``." msgstr "" #: ../../:693 msgid "" "When the default video model for libvirt was updated to virtio in Yoga the " "default for hosts using spice was not changed. This lead to issues when " "starting instances on hosts that had spice configured with QXL as the " "default video model on modern distros. To address this, the default spice " "video model is now virtio. See https://bugs.launchpad.net/nova/+bug/2097529 " "for more details." msgstr "" #: ../../:406 msgid "" "When you are upgrading to 2026.1 (Gazpacho) or newer the default " "configuration of nova-scheduler, nova-api, and nova-metadata services change " "to run these services with native threading mode by default instead of the " "legacy eventlet mode. We recommend to decouple the upgrade from the " "concurrency mode change to reduce the risk of issues. To do that either test " "the native threading mode of these services already in 2025.2 (Flamingo) or " "ensure that your service configuration is explicitly using the eventlet mode " "before you upgrade and only change to threading mode after the upgrade was " "successful. Please read the `concurrency `__ guide for more details on how to configure " "the mode." msgstr "" #: ../../:165 current msgid "" "When you are upgrading to 2026.2 (Hibiscus) or newer the default " "configuration of nova-conductor, and nova-compute services change to run " "these services with native threading mode by default instead of the legacy " "eventlet mode. We recommend to decouple the upgrade from the concurrency " "mode change to reduce the risk of issues. To do that either test the native " "threading mode of these services already in 2026.1 (Gazpacho) or ensure that " "your service configuration is explicitly using the eventlet mode before you " "upgrade and only change to threading mode after the upgrade was successful. " "Please read the `concurrency `__ guide for more details on how to configure the mode." msgstr "" #: ../../:702 msgid "" "With this change, operators can now resize the instance flavor swap to a " "smaller swap size, it can be expand and shrunk down to 0 using the same " "resize API. For more details see: `bug 1552777`_" msgstr "" #: ../../:241 msgid "" "You can increase these timeouts based on the traffic and how long the long-" "running (e.g. live migrations) tasks take in your deployment." msgstr "" #: ../../:488 msgid "" "You can now request different resource groups in your flavor for VGPU or " "generic mediated device custom resource classes. Previously, only the first " "resource request group was honored. See `bug #1758086`_ for more details." msgstr "" #: ../../:543 msgid "" "[`bug 2098514 _`] Fixed the " "per-service configuration directories for the API wsgi modules (``nova.wsgi." "osapi_compute`` and ``nova.wsgi.metadata``), unexpectedly affected by the " "application servers hosting these. Now these modules use the following per-" "service configuration directories regardless of the application server used." msgstr "" #: ../../:170 stable/2025.2>:659 msgid "" "[`bug 2117170 `_] Libvirt " "driver no longer enables VMCoreInfo device when an instance has memory " "encryption is enabled, to avoid kernel crash caused by fw_cfg device in " "guest requiring DMA." msgstr "" #: ../../:384 current msgid "" "[`bug 2123895 `__] Fixed " "service endpoint discovery with ``[oslo_limit]`` configuration when unified " "limits quotas are enabled." msgstr "" #: ../../:123 #: stable/2025.2>:116 stable/2026.1>:584 msgid "" "[`bug 2131960 `_] Fixed a bug " "where Ironic nodes in servicing-related provision states (``deploy hold``, " "``servicing``, ``service wait``, ``service hold``, ``service failed``) were " "not properly unprovisioned when instances were destroyed. The Nova Ironic " "virt driver now correctly triggers unprovisioning for nodes in these states, " "preventing orphaned node configurations in Ironic." msgstr "" #: ../../:70 #: stable/2025.2>:70 stable/2026.1>:466 msgid "" "[`bug 2131960 `_] Fixed " "improper teardown of Ironic nodes in servicing states. Previously, when " "Nova's virt driver called ``destroy()`` on Ironic nodes in certain states " "(``deploy hold``, ``servicing``, ``service wait``, ``service hold``, " "``service failed``), these nodes would fail to undergo proper teardown, " "resulting in orphaned instances where instance metadata was removed but " "nodes remained unprovisioned in Ironic. In flat networking configurations, " "this could allow nodes traversing servicing states to briefly access tenant " "networks. In Neutron networking configurations, while VIFs would detach " "correctly, nodes would remain in Ironic with a shutdown IPA, and future " "deprovisioning attempts would fail due to missing networking metadata. These " "states are now properly handled to ensure complete node deprovisioning." msgstr "" #: ../../:133 #: stable/2025.2>:126 stable/2026.1>:594 msgid "" "[`bug 2133416 `_] Libvirt virt " "driver now ignores the OVMF firmware files of the following types. " "Previously nova failed to start instances with UEFI boot when it attempts to " "check such firmware files." msgstr "" #: ../../:347 current msgid "" "[`bug 2157891 `__] Fixed AMD " "SEV-ES support reported when AMD SEV-SNP is enabled. This is aligned with " "recent firmware update, which disables AMD SEV-ES when AMD SEV-SNP is " "enabled." msgstr "" #: ../../:317 msgid "[oslo_policy] enforce_new_defaults=False enforce_scope=False" msgstr "" #: ../../:711 msgid "" "`Bug #2091033`_: Fixed calls to libvirt ``listDevices()`` and " "``listAllDevices()`` from potentially blocking all other greenthreads in " "``nova-compute``. Under certain circumstances, it was possible for the " "``nova-compute`` service to freeze with all other greenthreads blocked and " "unable to perform any other activities including logging. This issue has " "been fixed by wrapping the libvirt ``listDevices()`` and " "``listAllDevices()`` calls with ``eventlet.tpool.Proxy``." msgstr "" #: ../../:276 stable/2025.2>:613 msgid "" "`Bug #2095364`_: Fixed the List Server API and the List Server Detail API " "500 Internal Server Error issue in v2.96 or later API microversion if one or " "more instance has no request spec object. One usecase was when cloud user " "tried to create instance which exceeded their quota, the request does not " "create instance request spec. Once the no request spec instance is created " "in cloud user project, the server list API and the list server details API " "return 500 Internal Server Error for the project until the cloud user " "deletes the no request spec object instance. After this fix, the v2.96 or " "later returns `null` at the `pinned_availability_zone` value if not " "specified." msgstr "" #: ../../:236 current stable/2025.1>:48 #: stable/2025.2>:48 stable/2026.1>:48 msgid "" "`Bug #2105896`_: Fix error when multiple security groups in a project share " "the same name. The security group resolution now checks UUIDs before names, " "ensuring that a request using a specific UUID is never blocked by a naming " "collision. When a security group is requested by name and multiple groups " "share that name, a ``NoUniqueMatch`` error is raised prompting the user to " "use a UUID instead." msgstr "" #: ../../:247 current msgid "" "`Bug #2108974`_: Fix keypairs lost during cross-cell resize. When an " "instance was resized across cells, the keypairs stored in the " "``instance_extra`` table were not loaded from the source cell before cloning " "the instance to the destination cell. As a result, the keypairs column was " "written as NULL in the target cell database, effectively losing the server's " "keypair data after confirming the resize." msgstr "" #: ../../:555 msgid "" "`Bug #2122109`_: Fix API performance when getting multiple server groups. We " "now pre-fetch the not-deleted members of all requested server groups in a " "single query per cell instead of executing a query per server group per cell." "" msgstr "" #: ../../:269 current msgid "" "`Bug #2129678 `_: Setting " "``volume_clear = none`` in `nova.conf`_ configures Nova to not clear a " "deleted volume and to let a external tool to do so. By using this " "configuration and LVM volume type, when a previous image is deleted and a " "new one is created, the command ``lvcreate`` detects that a image still " "exists and asks for interactively wipe the old image in order to create a " "new one, which the default option is ``no``, e.g., to abort the operation. " "If a user is creating a new virtual machine this leads to an error and the " "VM is not created." msgstr "" #: ../../:286 current stable/2026.1>:59 msgid "" "`Bug #2134375`_: Fix ports remain during creating instance with multiple " "network when error occurs updating first port." msgstr "" #: ../../:302 current msgid "" "`Bug #2144660`_: Fix NUMA cell sorting for non-PCI VMs with pack strategy. " "When using the ``pack`` NUMA cell allocation strategy, the compute claim was " "not passing ``pci_stats`` to ``numa_fit_instance_to_host`` for VMs without " "PCI requests. This caused the PCI-aware NUMA cell sort to be skipped, " "allowing non-PCI VMs to land on NUMA nodes holding PCI devices instead of " "being steered away from them." msgstr "" #: ../../:313 current msgid "" "`Bug #2152581`_: Fixed swap disk creation being skipped during resize or " "cold migration when the instance directory is on NFS shared storage. The NFS " "client attribute cache could retain stale lookup results after the instance " "directory rename, causing Nova to incorrectly determine that the swap file " "already existed." msgstr "" #: ../../:330 current msgid "" "`Bug #2153425`_: Fix scheduler limits not being honored during live " "migration compute claims, causing allocation ratios to be ignored." msgstr "" #: ../../:354 current msgid "" "`Bug #2158967 `_: Fixed wrong " "validation of the ``hw_firmware_stateless`` image property. Now creating a " "server with BIOS boot and the ``hw_firmware_stateless`` property set to " "``True`` is accepted and succeeds, because BIOS is always stateless and this " "request is valid. Note that ``hw_firmware_statelsss=True`` in image " "properties is effectively ignored when a server is created with BIOS boot, " "to preserve the existing behavior." msgstr "" #: ../../:365 current msgid "" "`Bug #2158972 `_: Fixed the " "wrong status code returned by API when an instance is created with locked " "memory enabled but mem_page_size unset. It now returns 400 instead of 403." msgstr "" #: ../../:372 current msgid "" "`Bug #2160224 `_: Fixed the " "`GET servers//os-volume_attachments/` and `GET servers/" "/os-volume_attachments` not to intermittently return an empty " "attachment_id (or return HTTP 400 if response body schema validation is " "enabled) while the volume is being attached to the server in microversion 2." "89 or newer. The show API will keep returning 404 until the attachment_id is " "populated. The list API will keep filtering out the attachment from the " "response until the attachment_id is populated." msgstr "" #: ../../:572 msgid "" "`Bug 2127196`_ is fixed where Nova incorrectly generated a ```` " "element in libvirt XML for LUN volumes when Cinder reported disk geometry " "(logical and physical block size). QEMU's ``scsi-block`` device driver does " "not support ``physical_block_size`` and ``logical_block_size`` properties, " "causing instance spawn to fail with the error ``Property 'scsi-block." "physical_block_size' not found``. The ```` element is now omitted " "for LUN devices." msgstr "" #: ../../:390 current msgid "" "`Bug 2140631`_ has been fixed. When using unified limits, the quota check " "now includes resource groups requested through PCI aliases " "(``pci_passthrough:alias`` extra specs), neutron port bandwidth resources " "(``NET_BW_IGR_KILOBIT_PER_SEC``, ``NET_BW_EGR_KILOBIT_PER_SEC``), and Cyborg " "device profile resources (for example, ``FPGA``). Simple custom resources " "requested directly from flavor ``resources:`` extra specs, such as GPU " "resources, were already included. The enforcement chain now uses a full " "``RequestSpec`` so these additional resource groups are counted in unified-" "limits quota checks." msgstr "" #: ../../:258 stable/2025.2>:652 msgid "" "``Nova`` now strictly enforces that only ``cinder`` can call the ``update " "volume attachment`` aka ``swap volume`` api. This is part of addressing a " "security hardening gap identified as part of bug: https://bugs.launchpad.net/" "nova/+bug/2112187" msgstr "" #: ../../:521 msgid "``[DEFAULT] compute_link_prefix``" msgstr "" #: ../../:511 msgid "``[DEFAULT] config_drive_skip_versions``" msgstr "" #: ../../:518 msgid "``[DEFAULT] dhcp_domain``" msgstr "" #: ../../:524 msgid "``[DEFAULT] enable_instance_password``" msgstr "" #: ../../:522 msgid "``[DEFAULT] glance_link_prefix``" msgstr "" #: ../../:520 msgid "``[DEFAULT] max_limit``" msgstr "" #: ../../:517 msgid "``[DEFAULT] metadata_cache_expiration``" msgstr "" #: ../../:523 msgid "``[DEFAULT] use_neutron_default_nets``" msgstr "" #: ../../:515 msgid "``[DEFAULT] vendordata_dynamic_connect_timeout``" msgstr "" #: ../../:516 msgid "``[DEFAULT] vendordata_dynamic_read_timeout``" msgstr "" #: ../../:514 msgid "``[DEFAULT] vendordata_dynamic_ssl_certfile``" msgstr "" #: ../../:513 msgid "``[DEFAULT] vendordata_dynamic_targets``" msgstr "" #: ../../:519 msgid "``[DEFAULT] vendordata_jsonfile_path``" msgstr "" #: ../../:512 msgid "``[DEFAULT] vendordata_providers``" msgstr "" #: ../../:233 msgid "" "``[DEFAULT]/graceful_shutdown_timeout`` - The overall time the service waits " "before forcefully exit. This is defaults to 180 seconds for each Nova " "services." msgstr "" #: ../../:236 msgid "" "``[DEFAULT]/manager_shutdown_timeout`` - The time the service manager waits " "for in-progress tasks to complete during graceful shutdown. This is defaults " "to 160 seconds for each service manager. This must be less than " "``graceful_shutdown_timeout``." msgstr "" #: ../../:539 msgid "``[compute]heal_instance_info_cache_interval`` now defaults to -1." msgstr "" #: ../../:241 msgid "``admin``" msgstr "" #: ../../:200 msgid "" "``nova-novncproxy`` can make network connections to the VNC servers which " "run adjacent to ``ironic-conductor``" msgstr "" #: ../../:551 msgid "``nova.wsgi.metadata``: ``/etc/nova/nova-api-metadata.d``" msgstr "" #: ../../:550 msgid "``nova.wsgi.osapi_compute``: ``/etc/nova/nova-api-os-compute.d``" msgstr "" #: ../../:450 msgid "``os_compute_api:os-migrate-server:migrate_live:host``" msgstr "" #: ../../:278 msgid "" "``os_compute_api:os-migrate-server:migrate_live:host`` (live migrate server " "to a specific host)" msgstr "" #: ../../:444 msgid "``os_compute_api:os-migrate-server:migrate_live``" msgstr "" #: ../../:253 stable/2025.2>:272 msgid "" "``os_compute_api:os-migrate-server:migrate_live`` (live migrate server " "without specifying host)" msgstr "" #: ../../:251 msgid "" "``os_compute_api:os-migrate-server:migrate`` (Cold migrate a server without " "specifying a host)" msgstr "" #: ../../:452 msgid "``os_compute_api:os-migrations:index:all_projects``" msgstr "" #: ../../:306 msgid "" "``os_compute_api:os-migrations:index:all_projects`` (List migrations for all " "or cross projects)" msgstr "" #: ../../:453 msgid "``os_compute_api:os-migrations:index:host``" msgstr "" #: ../../:309 msgid "" "``os_compute_api:os-migrations:index:host`` (List migrations with host info)" msgstr "" #: ../../:446 msgid "``os_compute_api:os-migrations:index``" msgstr "" #: ../../:255 stable/2025.2>:300 msgid "" "``os_compute_api:os-migrations:index`` (List migrations without host info)" msgstr "" #: ../../:358 msgid "" "``os_compute_api:os-server-shares:create`` → ``PROJECT_MEMBER_OR_ADMIN``" msgstr "" #: ../../:360 msgid "" "``os_compute_api:os-server-shares:delete`` → ``PROJECT_MEMBER_OR_ADMIN``" msgstr "" #: ../../:357 msgid "" "``os_compute_api:os-server-shares:index`` → ``PROJECT_READER_OR_ADMIN``" msgstr "" #: ../../:359 msgid "``os_compute_api:os-server-shares:show`` → ``PROJECT_READER_OR_ADMIN``" msgstr "" #: ../../:445 msgid "``os_compute_api:servers:migrations::index``" msgstr "" #: ../../:261 msgid "" "``os_compute_api:servers:migrations:delete`` (Delete(Abort) an in-progress " "live migration)" msgstr "" #: ../../:259 msgid "" "``os_compute_api:servers:migrations:force_complete`` (Force an in-progress " "live migration for a given server)" msgstr "" #: ../../:451 msgid "``os_compute_api:servers:migrations:index:host``" msgstr "" #: ../../:292 msgid "" "``os_compute_api:servers:migrations:index:host`` (Lists in-progress live " "migrations for a given server with host info)" msgstr "" #: ../../:286 msgid "``os_compute_api:servers:migrations:index`` (Lists in-progress live" msgstr "" #: ../../:257 msgid "" "``os_compute_api:servers:migrations:index`` (Lists in-progress live " "migrations for a given server without host info)" msgstr "" #: ../../:242 msgid "``project_manager``" msgstr "" #: ../../:243 msgid "``project_member``" msgstr "" #: ../../:244 msgid "``project_reader``" msgstr "" #: ../../:139 #: stable/2025.2>:132 stable/2026.1>:600 msgid "memory device" msgstr "" #: ../../:287 msgid "migrations for a given server)" msgstr "" #: ../../:461 stable/2025.2>:540 msgid "os_compute_api:os-assisted-volume-snapshots:create" msgstr "" #: ../../:462 stable/2025.2>:541 msgid "os_compute_api:os-assisted-volume-snapshots:delete" msgstr "" #: ../../:463 stable/2025.2>:542 msgid "os_compute_api:os-server-external-events:create" msgstr "" #: ../../:464 stable/2025.2>:543 msgid "os_compute_api:os-volumes-attachments:swap" msgstr "" #: ../../:138 #: stable/2025.2>:131 stable/2026.1>:599 msgid "stateless mode" msgstr "" #: ../source/2023.1.rst:3 msgid "2023.1 Series Release Notes" msgstr "" #: ../source/2023.1.rst:8 msgid "27.5.1" msgstr "" #: ../source/2023.1.rst:17 ../source/2023.2.rst:39 ../source/2024.1.rst:214 #: ../source/2024.2.rst:485 msgid "" "Fixes a regression for live migration on shared storage that was removing " "the backing disk and instance folder during the cleanup of a virtual machine " "post live migration. `bug 2080436 `__ for details." msgstr "" #: ../source/2023.1.rst:25 ../source/2023.2.rst:424 msgid "" "`Bug #2024258`_: Fixes an issue with performance degradation archiving " "databases with large numbers of foreign key related records." msgstr "" #: ../source/2023.1.rst:28 ../source/2023.2.rst:427 msgid "" "Previously, deleted rows were archived in batches of max_rows parents + " "their child rows in a single database transaction. It limited how high a " "value of max_rows could be specified by the user because of the size of the " "database transaction it could generate. Symptoms of the behavior were " "exceeding the maximum configured packet size of the database or timing out " "due to a deadlock." msgstr "" #: ../source/2023.1.rst:35 ../source/2023.2.rst:434 msgid "" "The behavior has been changed to archive batches of complete parent + child " "rows trees while limiting each batch when it has reached >= max_rows records." " This allows the size of the database transaction to be controlled by the " "user and enables more rows to be archived per invocation of ``nova-manage db " "archive_deleted_rows`` when there are a large number of foreign key related " "records." msgstr "" #: ../source/2023.1.rst:48 msgid "27.4.0" msgstr "" #: ../source/2023.1.rst:57 ../source/2023.2.rst:92 ../source/2024.1.rst:557 msgid "" "Ironic virt driver now uses the node cache and respects partition keys, such " "as conductor group, for list_instances and list_instance_uuids calls. This " "fix will improve performance of the periodic queries which use these driver " "methods and reduce API and DB load on the backing Ironic service." msgstr "" #: ../source/2023.1.rst:63 msgid "27.3.0" msgstr "" #: ../source/2023.1.rst:72 ../source/2023.2.rst:417 msgid "" "The `CPU power management`_ feature has been fixed to use privsep to avoid a " "FileNotFound error when offlining CPUs." msgstr "" #: ../source/2023.1.rst:79 ../source/2023.2.rst:107 ../source/2024.1.rst:530 msgid "" "Some OS platforms don't provide by default cpufreq resources in sysfs, so " "they don't have CPU scaling governors. That's why we should let the governor " "strategy to be optional for `CPU power management`_." msgstr "" #: ../source/2023.1.rst:87 ../source/2023.2.rst:115 ../source/2024.1.rst:548 msgid "" "With the change from ml2/ovs DHCP agents towards OVN implementation in " "neutron there is no port with device_owner ``network:dhcp`` anymore. Instead " "DHCP is provided by ``network:distributed`` port. Fix relies on enable_dhcp " "provided by neutron-api if no port with ``network:dhcp`` owner is found. See " "`bug 2055245 `__ for details." msgstr "" #: ../source/2023.1.rst:96 ../source/2023.2.rst:124 ../source/2024.1.rst:561 #: ../source/zed.rst:17 msgid "" "Bug 2009280 has been fixed by no longer enabling the evmcs enlightenment in " "the libvirt driver. evmcs only works on Intel CPUs, and domains with that " "enlightenment cannot be started on AMD hosts. There is a possible future " "feature to enable support for generating this enlightenment only when " "running on Intel hosts." msgstr "" #: ../source/2023.1.rst:106 msgid "27.2.0" msgstr "" #: ../source/2023.1.rst:115 ../source/2023.2.rst:399 msgid "" "The hyperv driver is marked as experimental and may be removed in a future " "release. The driver is not tested by the OpenStack project and does not have " "a clear maintainer." msgstr "" #: ../source/2023.1.rst:127 ../source/2023.2.rst:143 ../source/2024.1.rst:538 msgid "" "Relaxed the config option checking of the cpu_power_management feature of " "the libvirt driver. The nova-compute service will start with " "[libvirt]cpu_power_management=True and an empty [compute]cpu_dedicated_set " "configuration. The power management is still only applied to dedicated CPUs. " "So the above configuration only allowed to ensure that cpu_power_management " "can be enabled independently for configuring cpu_dedicated_set during " "deployment." msgstr "" #: ../source/2023.1.rst:137 ../source/2023.2.rst:445 msgid "" "[`bug 1983471 `_] When " "offloading a shelved instance, the compute will now remove the binding so " "instance ports will appear as \"unbound\" in neutron." msgstr "" #: ../source/2023.1.rst:143 ../source/2023.2.rst:451 msgid "" "`Bug #2003991`_: Fixes an issue where quota was not properly enforced during " "unshelve of a ``SHELVED_OFFLOADED`` server when " "``[quota]count_usage_from_placement = true`` or ``[quota]driver = nova.quota." "UnifiedLimitsDriver`` are configured." msgstr "" #: ../source/2023.1.rst:152 ../source/2023.2.rst:153 ../source/2024.1.rst:569 #: ../source/zed.rst:36 msgid "" "Previously ``switchdev`` capabilities should be configured manually by a " "user with admin privileges using port's binding profile. This blocked " "regular users from managing ports with Open vSwitch hardware offloading as " "providing write access to a port's binding profile to non-admin users " "introduces security risks. For example, a binding profile may contain a " "``pci_slot`` definition, which denotes the host PCI address of the device " "attached to the VM. A malicious user can use this parameter to passthrough " "any host device to a guest, so it is impossible to provide write access to a " "binding profile to regular users in many scenarios." msgstr "" #: ../source/2023.1.rst:162 ../source/2023.2.rst:163 ../source/2024.1.rst:579 #: ../source/zed.rst:46 msgid "" "This patch fixes this situation by translating VF capabilities reported by " "Libvirt to Neutron port binding profiles. Other VF capabilities are " "translated as well for possible future use." msgstr "" #: ../source/2023.1.rst:170 msgid "27.1.0" msgstr "" #: ../source/2023.1.rst:179 ../source/2023.2.rst:357 ../source/wallaby.rst:17 #: ../source/xena.rst:17 ../source/yoga.rst:61 ../source/zed.rst:74 msgid "" "Configuration of service user tokens is now **required** for all Nova " "services to ensure security of block-storage volume data." msgstr "" #: ../source/2023.1.rst:182 ../source/2023.2.rst:360 ../source/wallaby.rst:20 #: ../source/xena.rst:20 ../source/yoga.rst:64 ../source/zed.rst:77 msgid "" "All Nova configuration files must configure the ``[service_user]`` section " "as described in the `documentation`__." msgstr "" #: ../source/2023.1.rst:185 ../source/2023.2.rst:363 ../source/wallaby.rst:23 #: ../source/xena.rst:23 ../source/yoga.rst:67 ../source/zed.rst:80 msgid "See https://bugs.launchpad.net/nova/+bug/2004555 for more details." msgstr "" #: ../source/2023.1.rst:193 msgid "27.0.0" msgstr "" #: ../source/2023.1.rst:202 msgid "" "The OpenStack 2023.1 (Nova 27.0.0) release includes many new features and " "bug fixes. Please be sure to read the upgrade section which describes the " "required actions to upgrade your cloud from 26.0.0 (Zed) to 27.0.0 (2023.1). " "As a reminder, OpenStack 2023.1 is our first `Skip-Level-Upgrade Release`__ " "(starting from now, we name it a ``SLURP release``) where you can rolling-" "upgrade your compute services from OpenStack Yoga as an experimental feature." " Next SLURP release will be 2024.1." msgstr "" #: ../source/2023.1.rst:215 msgid "The latest Compute API microversion supported for 2023.1 is `v2.95`__." msgstr "" #: ../source/2023.1.rst:219 msgid "" "`PCI devices can now be scheduled `_ by Nova using the " "Placement API on a opt-in basis. This will help the nova-scheduler service " "to better schedule flavors that use PCI (non-Neutron related) resources, " "will generate less reschedules if an instance cannot be created on a " "candidate and will help the nova-scheduler to not miss valid candidates if " "the list was too large." msgstr "" #: ../source/2023.1.rst:226 msgid "" "Operators can now ask Nova to `manage the power consumption of dedicated " "CPUs `_ so as to either " "offline them or change their governor if they're currently not in use by any " "instance or if the instance is stopped." msgstr "" #: ../source/2023.1.rst:231 msgid "" "Nova will prevent unexpected compute service renames by `persisting a unique " "compute UUID on local disk `_. This stored UUID will be considered the " "source of truth for knowing whether the compute service hostame has been " "modified or not. As a reminder, changing a compute hostname is forbidden, " "particularly when this compute is currently running instances on top of it." msgstr "" #: ../source/2023.1.rst:238 msgid "" "`SPICE consoles `_ can now be configured with compression settings " "which include choices of the compression algorithm and the compression mode." msgstr "" #: ../source/2023.1.rst:242 msgid "" "Fully-Qualified Domain Names are now considered valid for an instance " "hostname if you use the 2.94 API microversion." msgstr "" #: ../source/2023.1.rst:245 msgid "" "By opting into 2.95 API microversion, evacuated instances will remain " "stopped on the destination host until manually started." msgstr "" #: ../source/2023.1.rst:248 msgid "" "Nova APIs now `by default support new RBAC policies `_ and scopes. See our `Policy " "Concepts documentation `_ for further details." msgstr "" #: ../source/2023.1.rst:260 msgid "" "The following SPICE-related options are added to the ``spice`` configuration " "group of a Nova configuration:" msgstr "" #: ../source/2023.1.rst:263 msgid "``image_compression``" msgstr "" #: ../source/2023.1.rst:264 msgid "``jpeg_compression``" msgstr "" #: ../source/2023.1.rst:265 msgid "``zlib_compression``" msgstr "" #: ../source/2023.1.rst:266 msgid "``playback_compression``" msgstr "" #: ../source/2023.1.rst:267 msgid "``streaming_mode``" msgstr "" #: ../source/2023.1.rst:269 msgid "" "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 explicitly 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." msgstr "" #: ../source/2023.1.rst:278 msgid "" "Note that those options are only taken into account if SPICE support is " "enabled (and the VNC support is disabled)." msgstr "" #: ../source/2023.1.rst:283 msgid "" "Starting with v2.95 any evacuated instance will be stopped at destination. " "The required minimum version for Nova computes is 27.0.0 (antelope 2023.1). " "Operator can still continue using previous behavior by selecting " "microversion below v2.95." msgstr "" #: ../source/2023.1.rst:290 msgid "" "This is now possible to configure nova-compute services using libvirt driver " "by setting ``[libvirt]cpu_power_management`` to ``True`` in order to let the " "service to powering down or up physical CPUs depending on whether those CPUs " "are pinned or not to instances. In order on to support this feature, the " "compute service needs to be set with ``[compute]cpu_dedicated_set``. If so, " "all the related CPUs will be powering down until they are used by an " "instance where the related pinned CPU will be powering up just before " "starting the guest. If ``[compute]cpu_dedicated_set`` isn't set, then the " "compute service will refuse to start. By default the power strategy will " "offline CPUs when powering down and online the CPUs on powering up but " "another strategy is possible by using " "``[libvirt]cpu_power_management_strategy=governor`` which will rather modify " "the related CPU governor using ``[libvirt]cpu_power_governor_low`` and " "``[libvirt]cpu_power_governor_high`` configuration values (respective " "defaults being ``powersave`` and ``performance``)" msgstr "" #: ../source/2023.1.rst:308 msgid "" "Since 26.0.0 (Zed) Nova supports tracking PCI devices in Placement. Now Nova " "also supports scheduling flavor based PCI device requests via Placement. " "This support is disable by default. Please read `documentation `_ for more details on what is supported how this feature can be " "enabled." msgstr "" #: ../source/2023.1.rst:316 msgid "" "The 2.94 microversion has been added. This microversion extends microversion " "2.90 by allowing Fully Qualified Domain Names (FQDN) wherever the " "``hostname`` is able to be specified. This consists of creating an instance " "(``POST /servers``), updating an instance (``PUT /servers/{id}``), or " "rebuilding an instance (``POST /servers/{server_id}/action (rebuild)``). " "When using an FQDN as the instance hostname, the ``[api]dhcp_domain`` " "configuration option must be set to the empty string in order for the " "correct FQDN to appear in the ``hostname`` field in the metadata API." msgstr "" #: ../source/2023.1.rst:328 msgid "" "The compute manager now uses a local file to provide node uuid persistence " "to guard against problems with renamed services, among other things. " "Deployers wishing to ensure that *new* compute services get a predictable " "uuid before initial startup may provision that file and nova will use it, " "otherwise nova will generate and write one to a ``compute_id`` file in " "``CONF.state_path`` the first time it starts up. Accidental renames of a " "compute node's hostname will be detected and the manager will exit to avoid " "database corruption. Note that none of this applies to Ironic computes, as " "they manage nodes and uuids differently." msgstr "" #: ../source/2023.1.rst:340 msgid "" "Guru Meditation Reports can now be generated for the Nova API service when " "running under uWSGI. Note that uWSGI intercepts SIGUSR2 signals, so a file " "trigger should be used instead." msgstr "" #: ../source/2023.1.rst:352 msgid "" "Operators will have to consider upgrading compute hosts to Nova 27.0.0 " "(antelope 2023.1) in order to take advantage of the new (microversion v2.95) " "evacuate API behavior. An exception will be raised for older versions." msgstr "" #: ../source/2023.1.rst:359 msgid "" "The Nova service enable the API policies (RBAC) new defaults and scope by " "default. The Default value of config options ``[oslo_policy] enforce_scope`` " "and ``[oslo_policy] oslo_policy.enforce_new_defaults`` have been changed to " "``True``." msgstr "" #: ../source/2023.1.rst:364 msgid "" "This means if you are using system scope token to access Nova API then the " "request will be failed with 403 error code. Also, new defaults will be " "enforced by default. To know about the new defaults of each policy rule, " "refer to the `Policy New Defaults`_. For more detail about the Nova API " "policies changes, refer to `Policy Concepts`_." msgstr "" #: ../source/2023.1.rst:370 msgid "" "If you want to disable them then modify the below config options value in " "``nova.conf`` file::" msgstr "" #: ../source/2023.1.rst:382 msgid "" "In order to make use of microversion's 2.94 FQDN hostnames, the " "``[api]dhcp_domain`` config option must be set to the empty string. If this " "is not done, the ``hostname`` field in the metadata API will be incorrect, " "as it will include the value of ``[api]dhcp_domain`` appended to the " "instance's FQDN. Note that simply not setting ``[api]dhcp_domain`` is not " "enough, as it has a default value of ``novalocal``. It must explicitly be " "set to the empty string." msgstr "" #: ../source/2023.1.rst:392 msgid "" "Existing compute nodes will, upon upgrade, persist the uuid of the compute " "node assigned to their hostname at first startup. Since this must match what " "is currently in the database, it is important to let nova provision this " "file from its database. Nova will only persist to a ``compute_id`` file in " "the ``CONF.state_path`` directory, which should already be writable." msgstr "" #: ../source/2023.1.rst:400 msgid "" "In this release the default values for the initial ram and cpu allocation " "ratios have been updated to 1.0 and 4.0 respectively. This will not affect " "any existing compute node resource providers but the new default will take " "effect on the creation of new resource providers." msgstr "" #: ../source/2023.1.rst:413 msgid "" "Fixes `bug 1996995`_ in which VMs live migrated on certain VXLAN Arista " "network fabrics were inaccessible until the switch arp cache expired." msgstr "" #: ../source/2023.1.rst:416 msgid "" "A Nova workaround option of ``enable_qemu_monitor_announce_self`` was added " "to fix `bug 1815989`_ which when enabled would interact with the QEMU " "monitor and force a VM to announce itself." msgstr "" #: ../source/2023.1.rst:420 msgid "" "On certain network fabrics, VMs that are live migrated remain inaccessible " "via the network despite the QEMU monitor announce_self command successfully " "being called." msgstr "" #: ../source/2023.1.rst:424 msgid "" "It was noted that on Arista VXLAN fabrics, testing showed that it required " "several attempts of running the QEMU announce_self monitor command before " "the switch would acknowledge a VM's new location on the fabric." msgstr "" #: ../source/2023.1.rst:428 msgid "" "This fix introduces two operator configurable options. The first option sets " "the number of times the QEMU monitor announce_self command is called - " "``qemu_announce_self_count``" msgstr "" #: ../source/2023.1.rst:432 msgid "" "The second option allows operators to set the delay between the QEMU " "announce_self commands in seconds for subsequent announce_self commands with " " ``qemu_announce_self_interval``" msgstr "" #: ../source/2023.1.rst:441 ../source/zed.rst:114 msgid "" "Fixed when placement returns ironic nodes that have just started automatic " "cleaning as possible valid candidates. This is done by marking all ironic " "nodes with an instance on them as reserved, such that nova only makes them " "available once we have double checked Ironic reports the node as available. " "If you don't have automatic cleaning on, this might mean it takes longer " "than normal for Ironic nodes to become available for new instances. If you " "want the old behaviour use the following workaround config: " "``[workarounds]skip_reserve_in_use_ironic_nodes=true``" msgstr "" #: ../source/2023.1.rst:452 msgid "" "apache mod_wsgi does not support passing commandline arguments to the wsgi " "application that it hosts. As a result when the nova api or metadata api " "where run under mod_wsgi it was not possible to use multiple config files or " "non-default file names i.e. nova-api.conf This has been addressed by the " "introduction of a new, optional, environment variable " "``OS_NOVA_CONFIG_FILES``. ``OS_NOVA_CONFIG_FILES`` is a ``;`` separated list " "of file path relitive to ``OS_NOVA_CONFIG_DIR``. When unset the default " "``api-paste.ini`` and ``nova.conf`` will be used form ``/etc/nova``. This is " "supported for the nova api and nova metadata wsgi applications." msgstr "" #: ../source/2023.1.rst:465 ../source/xena.rst:48 ../source/yoga.rst:97 #: ../source/zed.rst:97 msgid "" "Fix rescuing volume based instance by adding a check for 'hw_rescue_disk' " "and 'hw_rescue_device' properties in image metadata before attempting to " "rescue instance." msgstr "" #: ../source/2023.1.rst:471 msgid "" "Nova's use of libvirt's compareCPU() API has become error-prone as it " "doesn't take into account host hypervisor's capabilities. With QEMU >=2.9 " "and libvirt >= 4.4.0, libvirt will do the right thing in terms of CPU " "comparison checks via a new replacement API, compareHypervisorCPU(). Nova " "satisfies the said minimum version requirements of QEMU and libvirt by a " "good margin." msgstr "" #: ../source/2023.1.rst:478 msgid "" "This change replaces the usage of older API, compareCPU(), with the new one, " "compareHypervisorCPU()." msgstr "" #: ../source/2023.1.rst:489 ../source/zed.rst:58 msgid "" "For networks which have any subnets with enabled DHCP, MTU value is not send " "in the metadata. In such case MTU is configured through the DHCP server." msgstr "" #: ../source/2023.1.rst:494 ../source/xena.rst:139 ../source/yoga.rst:197 #: ../source/zed.rst:144 msgid "" "A workaround has been added to the libvirt driver to catch and pass " "migrations that were previously failing with the error:" msgstr "" #: ../source/2023.1.rst:497 ../source/xena.rst:142 ../source/yoga.rst:200 #: ../source/zed.rst:147 msgid "" "``libvirt.libvirtError: internal error: migration was active, but no RAM " "info was set``" msgstr "" #: ../source/2023.1.rst:499 ../source/xena.rst:144 ../source/yoga.rst:202 #: ../source/zed.rst:149 msgid "See `bug 1982284`_ for more details." msgstr "" #: ../source/2023.1.rst:505 msgid "" "The default initial allocation ratios enabled ram over commit by default " "with a factor of ``1.5``. This value was chosen early in nova's history as " "the predominant workload was web hosting or other light weight " "virtualization. Similarly the default initial cpu allocation ratio defaulted " "to 16. As more demanding workload from telco, enterprise, scientific and " "governmental users became the norm the initial values we had chosen became " "less and less correct overtime. These have now been updated to reflect a " "more reasonable default for the majority of our users. As of this release " "the initial ram allocation value is 1.0 disabling overcommit by default for " "new compute nodes and the initial cpu allocation ratio is now 4.0 which is a " "more reasonable overcommit for non idle workloads." msgstr "" #: ../source/2023.2.rst:3 msgid "2023.2 Series Release Notes" msgstr "" #: ../source/2023.2.rst:8 msgid "2023.2-eol" msgstr "" #: ../source/2023.2.rst:17 ../source/2024.1.rst:185 ../source/2024.2.rst:443 msgid "" "In the victoria release, the instance_numa_topology object was extended to " "enabled mix cpus (pinned and unpinned cpus) in the same instance. This " "change added a new field pcpuset to the instance_numa_topology object. While " "the change included object conversion code to handle the upgrade, it did not " "account for instances that have a numa_topology but were not pinned. i.e. a " "flavor with hw:mem_page_size or hw:numa_nodes set but without hw:cpu_policy " "set to dedicated. As a result, instances created between liberty and " "victoria releases with such a flavor cannot be started after upgrade to " "victoria. This has now been fixed. instances created post victoria are not " "affected by this issue. see: https://bugs.launchpad.net/nova/+bug/2080556 " "for more details." msgstr "" #: ../source/2023.2.rst:54 ../source/2024.1.rst:236 ../source/2024.2.rst:493 msgid "" "Before the `Bug 2078999 `_ was " "fixed, the ``nova-manage image_property set`` command would update the image " "properties embedded in the instance but would not update the ones in the " "request specs. This led to an unexpected rollback of the image properties " "that were updated by the command after an instance migration." msgstr "" #: ../source/2023.2.rst:62 ../source/2024.1.rst:244 ../source/2024.2.rst:529 msgid "" "Introduced a new compute configuration option " "``sharing_providers_max_uuids_per_request`` and applied a fix to handle the " "\"Request-Too-Long\" error that can occur when querying the placement API " "with a large number of aggregate UUIDs." msgstr "" #: ../source/2023.2.rst:83 msgid "28.2.0" msgstr "" #: ../source/2023.2.rst:98 msgid "28.1.0" msgstr "" #: ../source/2023.2.rst:134 msgid "28.0.1" msgstr "" #: ../source/2023.2.rst:171 msgid "28.0.0" msgstr "" #: ../source/2023.2.rst:180 msgid "" "The OpenStack 2023.2 (Nova 28.0.0) release includes many new features and " "bug fixes. Please be sure to read the upgrade section which describes the " "required actions to upgrade your cloud from 27.0.0 (2023.1) to 28.0.0 (2023." "2). As a reminder, OpenStack 2023.2 is a non-`Skip-Level-Upgrade Release`__ " "(starting from now, we name it a ``non-SLURP release``) meaning that you can " "only do rolling-upgrade from 2023.1. Next SLURP release will be 2024.1 where " "you will be able to upgrade from 2023.1 directly by skipping this release." msgstr "" #: ../source/2023.2.rst:194 msgid "The latest Compute API microversion supported for 2023.2 is `v2.95`__." msgstr "" #: ../source/2023.2.rst:198 msgid "" "The Ironic driver ``[ironic]/peer_list`` configuration option has been " "deprecated. The Ironic driver now more closely models other Nova drivers by " "having a single compute have exclusive control over assigned nodes. If high " "availability of a single compute service is required, operators should use " "active/passive failover." msgstr "" #: ../source/2023.2.rst:204 msgid "" "The legacy quota driver is now deprecated and a `nova-manage limits command " "`_ is provided in order to migrate the legacy limits into " "Keystone. We plan to change the default quota driver to the unified limits " "driver in an upcoming release (hopefully 2024.1 Caracal). It is recommended " "that you begin planning and executing a migration to unified limits as soon " "as possible." msgstr "" #: ../source/2023.2.rst:212 msgid "" "QEMU in its TCG mode (i.e. full system emulation) uses a translation block " "(TB) cache as an optimization during dynamic code translation. The libvirt " "driver can now configure the tb-cache size when the virt type is ``qemu``. " "This helps running VMs with small memory size. In order to use this feature, " "a configuration option ``[libvirt]/tb_cache_size`` has been introduced." msgstr "" #: ../source/2023.2.rst:219 msgid "" "Two new scheduler weighers have been introduced. One helps `sorting the " "nodes by the number of active instances they run `_, the other helps `sorting by the " "hypervisor version each compute runs `_. Accordingly, you can place your " "instances with different strategies, eg. by allocating them to more recent " "nodes or by reducing the number of noisy instance neighbors." msgstr "" #: ../source/2023.2.rst:226 msgid "" "It is now possible to define different authorization policies for migration " "with and without a target host." msgstr "" #: ../source/2023.2.rst:229 msgid "" "A couple of other improvements target reducing the number of bugs we have, " "one `checking at reboot if stale volume attachments still reside `_ and another one ensuring a `strict " "linkage between a compute, a service and the instances it runs `_." msgstr "" #: ../source/2023.2.rst:242 msgid "" "A new ``os_compute_api:os-migrate-server:migrate:host`` policy is created, " "being by default only an admin-only policy. This will help operators to have " "different policies between cold-migrate without providing a host or not." msgstr "" #: ../source/2023.2.rst:246 msgid "" "A new ``num_instances_weigher`` weigher has been added. This weigher will " "compare the number of instances between each node and order the list of " "filtered results by its number, By default, this weigher is enabled but with " "a default of 0.0 which doesn't change the current behavior. In order to use " "it, please change the value of ``[filter_scheduler]/" "num_instances_weight_multiplier`` config option where a positive value will " "favor the host with the higher number of instances (ie. packing strategy) vs." " a negative value that will spread instances between hosts. As a side note, " "this weigher will count *all* of the existing instances on the host, even " "the stopped or shelved ones." msgstr "" #: ../source/2023.2.rst:259 msgid "" "This change ensures the synchronization of volume attachments between Nova " "and Cinder, by deleting any dangling volume attachments and maintaining " "consistency between two databases." msgstr "" #: ../source/2023.2.rst:263 msgid "" "Block device mapping (BDM) table in the Nova database, stores information " "about volume attachments, image attachments and swap attachments. Similarly, " "each volume attachment had a corresponding entry in the Cinder database " "volume attachment table." msgstr "" #: ../source/2023.2.rst:268 msgid "" "With this change, on instance reboot, Nova will checks for all volume " "attachments associated with the instance and verifies their availability in " "the Cinder database. If attachments are not found they will get deleted from " "Nova database too." msgstr "" #: ../source/2023.2.rst:273 msgid "" "After Nova database cleanup, similarly Cinder database is checked for " "attachments related to instance. If attachments found in Cinder DB that are " "not present in Nova DB, they will get deleted from Cinder database." msgstr "" #: ../source/2023.2.rst:277 msgid "See `spec`__ for more details." msgstr "" #: ../source/2023.2.rst:283 msgid "" "A new hypervisor version weigher has been added to prefer selecting hosts " "with newer hypervisors installed. For the libvirt driver, this is the " "version of libvirt on the compute node not the version of qemu. As with all " "weighers this is enabled by default and its behavior can be modified using " "the new ``hypervisor_version_weight_multiplier`` config option in the " "``filter_scheduler`` section." msgstr "" #: ../source/2023.2.rst:292 msgid "" "Qemu>=5.0.0 bumped the default tb-cache size to 1GiB(from 32MiB) and this " "made it difficult to run multiple guest VMs on systems running with lower " "memory. With Libvirt>=8.0.0 it's possible to configure lower tb-cache size. " "A new config option is introduced:" msgstr "" #: ../source/2023.2.rst:297 msgid "``[libvirt]tb_cache_size``" msgstr "" #: ../source/2023.2.rst:299 msgid "" "This config option can be used to configure tb_cache size for guest VMs, " "it's only applicable with ``virt_type=qemu``." msgstr "" #: ../source/2023.2.rst:304 msgid "" "A new command ``nova-manage limits migrate_to_unified_limits`` has been " "added to make migration from the ``nova.quota.DbQuotaDriver`` to the ``nova." "quota.UnifiedLimitsDriver`` easier. This will enable operators to have their " "existing quota limits copied from the Nova database to Keystone " "automatically." msgstr "" #: ../source/2023.2.rst:318 msgid "" "The ``AvailabilityZoneFilter`` was deprecated for removal in 24.0.0 (Xena) " "and has now been removed. The functionality of the " "``AvailabilityZoneFilter`` has been replaced by the " "``map_az_to_placement_aggregate`` pre-filter. The pre-filter was introduced " "in 18.0.0 (Rocky) and enabled by default in 24.0.0 (Xena). This pre-filter " "is now always enabled and the ``[scheduler] " "query_placement_for_availability_zone`` config option has been removed." msgstr "" #: ../source/2023.2.rst:329 msgid "" "The minimum required version of libvirt by the ``nova-compute`` service is " "now 7.0.0, and the minimum required version of QEMU is 5.2.0. Failing to " "meet these minimum versions when using the libvirt compute driver will " "result in the ``nova-compute`` service not starting." msgstr "" #: ../source/2023.2.rst:335 msgid "" "The next minimum required version of libvirt to be used in a future release " "is 8.0.0, while the next minimum QEMU is 6.2.0." msgstr "" #: ../source/2023.2.rst:340 msgid "" "A new hypervisor version weigher has been added that will prefer selecting " "hosts with a newer hypervisor installed. This can help simplify rolling " "upgrades by preferring the already upgraded hosts when moving workloads " "around using live or cold migration. To restore the old behavior either " "remove the weigher from the list of enabled weighers or set " "``[filter_scheduler] hypervisor_version_weight_multiplier=0``. The default " "value of the hypervisor_version_weight_multiplier is 1 so only a mild " "preference is given to new hosts, higher values will make the effect more " "pronounced and negative values will prefer older hosts." msgstr "" #: ../source/2023.2.rst:352 msgid "" "The legacy ``sqlalchemy-migrate`` migrations, which have been deprecated " "since Wallaby, have been removed. There should be no end-user impact." msgstr "" #: ../source/2023.2.rst:375 msgid "" "We have renamed ``[ironic]partition_key`` to ``[ironic]conductor_group``. " "The config option is still used to specify which Ironic conductor group the " "ironic driver in the nova compute process should target." msgstr "" #: ../source/2023.2.rst:381 msgid "" "We have deprecated the configuration ``[ironic]peer_list``, along with our " "support for a group of ironic nova-compute processes targeting a shared set " "of Ironic nodes. There are so many bugs in this support we now prefer " "statically sharding the nodes between multiple nova-compute processes. Note " "that the ironic nova-compute process is stateless, and the identity of the " "service is defined by the config option ``[DEFAULT]host``. As such, you can " "use an active-passive HA solution to ensure at most one nova-compute process " "is running for each Ironic node shard." msgstr "" #: ../source/2023.2.rst:393 msgid "" "The ``nova.quota.DbQuotaDriver`` is marked as deprecated and the default " "quota driver configuration is planned to be changed to the ``nova.quota." "UnifiedLimitsDriver`` in the 29.0.0 (2024.1 Caracal) release." msgstr "" #: ../source/2023.2.rst:405 msgid "" "The vmwareapi driver is marked as experimental and may be removed in a " "future release. The driver is not tested by the OpenStack project and does " "not have a clear maintainer." msgstr "" #: ../source/2024.1.rst:3 msgid "2024.1 Series Release Notes" msgstr "" #: ../source/2024.1.rst:8 msgid "2024.1-eom" msgstr "" #: ../source/2024.1.rst:49 ../source/2024.2.rst:145 msgid "" "Preferring cached uptime data from the database over RPC calls when " "available, this updates at the cadence specified by " "``[DEFAULT]update_resources_interval`` which is the same interval the other " "hypervisor stats update." msgstr "" #: ../source/2024.1.rst:70 msgid "29.3.0" msgstr "" #: ../source/2024.1.rst:114 ../source/2024.2.rst:241 msgid "" "`Bug #2095364`_: Fixed the List Server API and the List Server Detail API " "500 Internal Server Error issue in v2.96 or later API microversion if one or " "more instance has no request spec object. One usecase was when cloud user " "tried to create instance which exceeded their quota, the request does not " "create instance request spec. Once the no request spec instance is created " "in cloud user project, the server list API and the list server details API " "return 500 Internal Server Error for the project until the cloud user " "deletes the no request spec object instance. After this fix, the v2.96 or " "later returns ``null`` at the ``pinned_availability_zone`` value if not " "specified." msgstr "" #: ../source/2024.1.rst:138 msgid "29.2.2" msgstr "" #: ../source/2024.1.rst:176 msgid "29.2.1" msgstr "" #: ../source/2024.1.rst:229 ../source/2024.2.rst:270 msgid "" "Fix displaying the reason messages from the Ironic validate node operation " "that is called just before the instance is deployed on the bare metal node. " "The message from Ironic is now correctly logged. Fixes `bug 2100009 `_." msgstr "" #: ../source/2024.1.rst:265 msgid "29.0.2" msgstr "" #: ../source/2024.1.rst:274 ../source/2024.2.rst:507 msgid "" "Nova now ensures that an instance cannot move between availability zones " "when the host of the instance is added or removed to an aggregate that is " "part of another availability zone. Moving from or to the default " "availability zone is also rejected." msgstr "" #: ../source/2024.1.rst:279 ../source/2024.2.rst:512 msgid "" "This resolves `bug 1907775`_ where after such move the instance become stuck " "in between availability zones." msgstr "" #: ../source/2024.1.rst:288 msgid "29.0.1" msgstr "" #: ../source/2024.1.rst:297 msgid "" "The OpenStack 2024.1 (Nova 29.0.0) release includes many new features and " "bug fixes. Please be sure to read the upgrade section which describes the " "required actions to upgrade your cloud from 28.0.0 (2023.2) to 29.0.0 (2024." "1). As a reminder, OpenStack 2024.1 is a `Skip-Level-Upgrade Release`__ " "(starting from now, we name it a ``SLURP release``) meaning that you can do " "rolling-upgrade from 2023.1 and skip 2023.2." msgstr "" #: ../source/2024.1.rst:310 msgid "The latest Compute API microversion supported for 2024.1 is `v2.96`__." msgstr "" #: ../source/2024.1.rst:314 msgid "" "The Ironic driver ``[ironic]/peer_list`` configuration option has been " "deprecated. The Ironic driver now more closely models other Nova drivers " "where compute nodes do not move between compute service instances. If high " "availability of a single compute service is required, operators should use " "active/passive failover between 2 compute service agents configured to share " "the same compute service host value ``[DEFAULT]/host``. Ironic nova-compute " "services can now be configured to target a specific shard of ironic nodes by " "setting the ``[ironic]/shard`` configuration option and a new ``nova-manage " "db ironic_compute_node_move`` command can help the operators when upgrading " "their computes to specify which shard they should manage." msgstr "" #: ../source/2024.1.rst:326 msgid "" "Instances using `vGPUs can now be live-migrated `_ if both of the compute nodes " "support libvirt-8.6.0 and QEMU-8.1.0, as the source mediated device will " "migrate the GPU memory to another target mediated device automatically. In " "order to do this, ``[libvirt/live_migration_downtime`` config option needs " "to be modified according to the aforementioned documentation." msgstr "" #: ../source/2024.1.rst:334 msgid "" "As of the new 2.96 microversion, the ``server show`` and ``server list`` " "APIs now return a new parameter called ``pinned_availability_zone`` that " "indicates whether the instance is confined to a specific AZ. This field " "supplements the existing ``availability_zone`` field which reports the " "availability zone of the host where the service resides. The two values may " "be different if the service is shelved or is not pinned to an AZ which can " "help operators plan maintenance and better understand the workload " "constraints." msgstr "" #: ../source/2024.1.rst:343 msgid "" "Instances using virtio-net will see an increase in performance between 10% " "and 20% if their image uses a new ``hw_virtio_packed_ring=true`` property or " "their flavor contains ``hw:virtio_packed_ring=true`` extra spec, provided " "libvirt version is >= 6.3 and QEMU >= 4.2." msgstr "" #: ../source/2024.1.rst:348 msgid "" "As a security mechanism, a new ``[consoleauth]/enforce_session_timeout`` " "configuration option provides the ability to automatically close a server " "console session when the token expires. This is disabled by default to " "preserve the existing behaviour for upgrades." msgstr "" #: ../source/2024.1.rst:353 msgid "" "The libvirt driver now supports requesting a configurable memory address " "space for the instances. This allows `instances with large RAM requirements " "`_ to be created by " "specifying either ``hw:maxphysaddr_mode=emulate`` and ``hw:" "maxphysaddr_bits`` flavor extra specs or ``hw_maxphysaddr_mode`` and " "``hw_maxphysaddr_bits`` image properties. The ``ImagePropertiesFilter`` and " "``ComputeCapabilitiesFilter`` filters are required to support this " "functionality." msgstr "" #: ../source/2024.1.rst:363 msgid "" "The Hyper-V virt driver has been removed. It was deprecated in the Nova 27.2." "0 (Antelope) release. This driver was untested and has no maintainers. In " "addition, it had a dependency on the OpenStack Winstacker project that also " "has been retired." msgstr "" #: ../source/2024.1.rst:368 msgid "" "A couple of other improvements target reducing the number of bugs we have: " "one automatically detecting the maximum number of instances with memory " "encryption which can run concurrently, another one allows specifying a " "specific IP address or hostname for incoming move operations (by setting " "``[libvirt]/migration_inbound_addr``) and yet another one that improves " "stability of block device management using libvirt device aliases." msgstr "" #: ../source/2024.1.rst:384 msgid "" "Added new flavor extra_specs and image properties to control the physical " "address bits of vCPUs in Libvirt guests. This option is used to boot a guest " "with large RAM." msgstr "" #: ../source/2024.1.rst:390 msgid "" "Instances using vGPUs can now be correctly live-migrated by the libvirt " "driver between compute nodes supporting the same mediated device types used " "by the instance. In order to be able to do this, the compute hosts need to " "support at least the minimum versions of libvirt-8.6.0, QEMU-8.1.0 and Linux " "kernel 5.18.0. If operators use multiple vGPU types per compute, they need " "to make sure they already use custom traits or custom resource classes for " "the GPUs resource providers and that the instance was created with a flavor " "using either a custom resource class or asking for a custom trait in order " "to make sure that Placement API will provide the right target GPU using the " "same mdev type for the instance." msgstr "" #: ../source/2024.1.rst:403 msgid "" "The new config option ``[libvirt]migration_inbound_addr`` is now used to " "determine the address for incoming move operations (cold migrate, resize, " "evacuate). This config is defaulted to [DEFAULT]my_ip to keep the " "configuration backward compatible. However it allows an explicit hostname or " "FQDN to be specified, or allows to specify '%s' that is then resolved to the " "hostname of compute host. Note that this config should only be changed from " "its default after every compute is upgraded." msgstr "" #: ../source/2024.1.rst:414 msgid "" "This is a security-enhancing feature that automatically closes console " "sessions exceeding a defined timeout period. To enable this functionality, " "operators are required to set the 'enforce_session_timeout' boolean " "configuration option to True." msgstr "" #: ../source/2024.1.rst:418 msgid "" "The enforcement is implemented via a timer mechanism, initiating when users " "access the console and concluding upon the expiration of the set console " "token." msgstr "" #: ../source/2024.1.rst:421 msgid "" "This ensures the graceful closure of console sessions on the server side, " "aligning with security best practices." msgstr "" #: ../source/2024.1.rst:426 msgid "" "Now the libvirt driver is capable to detect maximum number of guests with " "memory encrypted which can run concurrently in its compute host using the " "new fields in libvirt API available since version 8.0.0." msgstr "" #: ../source/2024.1.rst:432 msgid "" "The 2.96 microversion has been added. This microversion adds " "pinned_availability_zone in ``server show`` and ``server list --long`` " "responses." msgstr "" #: ../source/2024.1.rst:438 msgid "" "Handling packed virtqueue requests for an instance is now supported on the " "nodes with Qemu v4.2 and Libvirt v6.3." msgstr "" #: ../source/2024.1.rst:441 msgid "" "VMs using virtio-net will see an increase in performance. The increase can " "be anywhere between 10/20% (see DPDK Intel Vhost/virtio perf. reports) and " "75% (using Napatech SmartNICs)." msgstr "" #: ../source/2024.1.rst:445 msgid "" "Packed Ring can be requested via image property or flavor extra spec. " "hw_virtio_packed_ring=true|false (default false) hw:virtio_packed_ring=" "true|false (default false)" msgstr "" #: ../source/2024.1.rst:449 msgid "" "Useful references: https://libvirt.org/formatdomain.html#virtio-related-" "options https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-" "csprd01.html https://specs.openstack.org/openstack/nova-specs/specs/2023.2/" "approved/virtio_packedring_configuration_support.html" msgstr "" #: ../source/2024.1.rst:462 msgid "" "The ``HyperV`` virt driver has been removed. It was deprecated in the Nova " "27.2.0 (Antelope) release. This driver was untested and has no maintainers. " "In addition, it has a dependency on the OpenStack Winstacker project that " "also has been retired." msgstr "" #: ../source/2024.1.rst:467 msgid "" "The RDP console was only available for the HyperV driver, therefore the RDP " "console related APIs below will return HTTP ``400 (BadRequest)`` error:" msgstr "" #: ../source/2024.1.rst:470 msgid "GET RDP console:" msgstr "" #: ../source/2024.1.rst:472 msgid "" "Server Action Get RDP Console: POST /servers/{server_id}/action (os-" "getRDPConsole Action)" msgstr "" #: ../source/2024.1.rst:475 msgid "" "RDP protocol support from remote console API: POST /servers/{server_id}/" "remote-consoles" msgstr "" #: ../source/2024.1.rst:478 msgid "GET RDP console connection information:" msgstr "" #: ../source/2024.1.rst:480 msgid "" "Show Console Connection Information: GET /os-console-auth-tokens/" "{console_token}" msgstr "" #: ../source/2024.1.rst:483 msgid "" "The following config options which only apply for the ``HyperV`` virt driver " "or RDP console APIs also have been removed:" msgstr "" #: ../source/2024.1.rst:486 msgid "``[hyperv] dynamic_memory_ratio``" msgstr "" #: ../source/2024.1.rst:487 msgid "``[hyperv] enable_instance_metrics_collection``" msgstr "" #: ../source/2024.1.rst:488 msgid "``[hyperv] instances_path_share``" msgstr "" #: ../source/2024.1.rst:489 msgid "``[hyperv] limit_cpu_features``" msgstr "" #: ../source/2024.1.rst:490 msgid "``[hyperv] mounted_disk_query_retry_count``" msgstr "" #: ../source/2024.1.rst:491 msgid "``[hyperv] mounted_disk_query_retry_interval``" msgstr "" #: ../source/2024.1.rst:492 msgid "``[hyperv] power_state_check_timeframe``" msgstr "" #: ../source/2024.1.rst:493 msgid "``[hyperv] power_state_event_polling_interval``" msgstr "" #: ../source/2024.1.rst:494 msgid "``[hyperv] qemu_img_cmd``" msgstr "" #: ../source/2024.1.rst:495 msgid "``[hyperv] vswitch_name``" msgstr "" #: ../source/2024.1.rst:496 msgid "``[hyperv] wait_soft_reboot_seconds``" msgstr "" #: ../source/2024.1.rst:497 msgid "``[hyperv] config_drive_cdrom``" msgstr "" #: ../source/2024.1.rst:498 msgid "``[hyperv] config_drive_inject_password``" msgstr "" #: ../source/2024.1.rst:499 msgid "``[hyperv] volume_attach_retry_count``" msgstr "" #: ../source/2024.1.rst:500 msgid "``[hyperv] volume_attach_retry_interval``" msgstr "" #: ../source/2024.1.rst:501 msgid "``[hyperv] enable_remotefx``" msgstr "" #: ../source/2024.1.rst:502 msgid "``[hyperv] use_multipath_io``" msgstr "" #: ../source/2024.1.rst:503 msgid "``[hyperv] iscsi_initiator_list``" msgstr "" #: ../source/2024.1.rst:504 msgid "``[rdp] enabled``" msgstr "" #: ../source/2024.1.rst:505 msgid "``[rdp] html5_proxy_base_url``" msgstr "" #: ../source/2024.1.rst:507 msgid "" "The following extra specs which only apply for the ``HyperV`` virt driver " "have been removed." msgstr "" #: ../source/2024.1.rst:510 msgid "``os:resolution``" msgstr "" #: ../source/2024.1.rst:511 msgid "``os:monitors``" msgstr "" #: ../source/2024.1.rst:512 msgid "``os:vram``" msgstr "" #: ../source/2024.1.rst:516 msgid "The deprecated ``[upgrade_levels] cert`` option has been removed." msgstr "" #: ../source/2024.1.rst:520 msgid "The deprecated ``[api] use_forwarded_for`` option has been removed." msgstr "" #: ../source/2024.2.rst:3 msgid "2024.2 Series Release Notes" msgstr "" #: ../source/2024.2.rst:8 msgid "30.3.0" msgstr "" #: ../source/2024.2.rst:36 msgid "30.2.1" msgstr "" #: ../source/2024.2.rst:74 msgid "" "This is now fixed, by Nova adding the ``managed=\"no\"`` attribute to TAP " "interface XML specifications." msgstr "" #: ../source/2024.2.rst:104 msgid "30.2.0" msgstr "" #: ../source/2024.2.rst:166 msgid "30.1.0" msgstr "" #: ../source/2024.2.rst:234 msgid "" "Fixed an issue where the instance rebuild option failed for Ironic instances." " The problem was caused by an incorrect parameter order in the " "``add_instance_info_to_node`` function, which was introduced by commit " "``93b90d2b`` . For " "more details, see ``bug 2092570`` ." msgstr "" #: ../source/2024.2.rst:310 msgid "30.0.0" msgstr "" #: ../source/2024.2.rst:319 msgid "" "The OpenStack 2024.2 (Nova 30.0.0) release includes many new features and " "bug fixes. Please be sure to read the upgrade section which describes the " "required actions to upgrade your cloud from 29.0.0 (2024.1) to 30.0.0 (2024." "2). As a reminder, OpenStack 2024.2 is not a `Skip-Level-Upgrade Release`__ " "(starting from now, we name it a ``SLURP release``) meaning that you can't " "do rolling-upgrade from 2023.2, you first need to upgrade to 2024.1." msgstr "" #: ../source/2024.2.rst:332 msgid "The latest Compute API microversion supported for 2024.2 is `v2.96`__." msgstr "" #: ../source/2024.2.rst:336 ../source/2024.2.rst:404 msgid "" "With the libvirt driver and libvirt version 7.3.0 or newer, mediated devices " "for vGPUs are now persisted across reboots of a compute host." msgstr "" #: ../source/2024.2.rst:339 msgid "" "Instances with UEFI firmware can now be launched with stateless firmware if " "their image has the ``hw_firmware_stateless`` property and if the compute " "services have libvirt 8.6.0 or later." msgstr "" #: ../source/2024.2.rst:343 msgid "" "Nova now automatically detects vTPM support for compute services if libvirt " "version is above 8.0.0 and if ``swtpm`` is installed on the node. It will " "also automatically get the TPM models that are supported." msgstr "" #: ../source/2024.2.rst:347 msgid "" "You can now require TLS connections for SPICE consoles if you set the " "``[spice]/require_secure`` configuration option to ``True``." msgstr "" #: ../source/2024.2.rst:350 msgid "" "``AggregateMultitenancyIsolation`` scheduler filter now supports multiple " "aggregate keys prefixed by ``filter_tenant_id`` which removes the limitation " "on the number of tenants an aggregate of hosts can relate to." msgstr "" #: ../source/2024.2.rst:354 msgid "" "A couple of other improvements target reducing the number of bugs we have: " "one is changing how the Ironic driver sends metadata to the Ironic API, and " "another one created a new ``nova.wsgi`` WSGI module that allows different " "WSGI servers to set their WSGI application the same way (using module " "instead of a binary)." msgstr "" #: ../source/2024.2.rst:368 msgid "" "A new module, ``nova.wsgi``, has been added as a place to gather WSGI " "``application`` objects. This is intended to ease deployment by providing a " "consistent location for these objects. For example, if using uWSGI then " "instead of:" msgstr "" #: ../source/2024.2.rst:378 msgid "You can now use:" msgstr "" #: ../source/2024.2.rst:385 msgid "" "This also simplifies deployment with other WSGI servers that expect module " "paths such as gunicorn." msgstr "" #: ../source/2024.2.rst:390 msgid "" "A new configuration option, ``[api] response_validation``, has been added. " "This allows operators to configure the behavior of ``nova-api`` when a " "response fails schema validation." msgstr "" #: ../source/2024.2.rst:396 msgid "" "Libvirt virt driver now supports launching instances with stateless firmware." " The new ``hw_firmware_stateless`` image property can be used to enable this " "feature. Note that the feature can be used only for the instances with UEFI " "firmware. This feature requires libvirt v8.6.0 or later." msgstr "" #: ../source/2024.2.rst:409 msgid "" "After a compute host reboots, if you have a GPU that supports SR-IOV, then " "the virtual functions for the GPU must be enabled again before instances " "will be able to use their vGPUs. Please see https://docs.openstack.org/nova/" "latest/admin/virtual-gpu.html for more information." msgstr "" #: ../source/2024.2.rst:417 msgid "" "This release removes the limit of the number of tenants that can be " "specified for an aggregate and honored by the " "``AggregateMultitenancyIsolation`` filter. It now respects multiple keys " "prefixed by ``filter_tenant_id`` like the request filter implementation. " "You can use ``filter_tenant_id`` as a prefix to set an infinite number of " "properties for tenant IDs on the aggregate. This change has been implemented " "in a manner that preserves backward compatibility. Existing configurations " "using ``filter_tenant_id`` will continue to function as expected." msgstr "" #: ../source/2024.2.rst:429 msgid "" "This release adds a new config option require_secure to the spice " "configuration group. Defaulting to false to match the previous behavior, if " "set to true the SPICE consoles will require TLS protected connections. " "Unencrypted connections will be gracefully redirected to the TLS port via " "the SPICE protocol." msgstr "" #: ../source/2024.2.rst:465 msgid "" "AMI, AKI, and ARI image formats are now deprecated in Nova. The special-case " "handling for them will be removed in a future release, and Nova will stop " "being able to boot from them at that time. The kernel-id and ramdisk-id " "linkages will continue to be honored from base images and are unaffecfted by " "this deprecation." msgstr "" #: ../source/2024.2.rst:479 msgid "" "The libvirt driver now ensures the ``swtpm_ioctl`` binary, which is used to " "terminate swtpm processes, is present when ``[libvirt] swtpm_enabled`` is " "set to ``True``." msgstr "" #: ../source/2024.2.rst:501 msgid "" "`Bug #2035375 `_: Fixed " "leftover NVMe-oF subsystems when disconnecting multiple NVMe-oF volumes on " "the same host from storage sharing the subsystem for different volumes." msgstr "" #: ../source/2024.2.rst:519 msgid "" "`Bug #2002606`_: Previously, server rescue in stable device mode had a " "dependency on the original image used to create or rebuild the server. If " "the original image was deleted from Glance, the server could not be rescued. " "The issue has been fixed by falling back to the instance image metadata if " "the original image is not found in Glance." msgstr "" #: ../source/2025.1.rst:3 msgid "2025.1 Series Release Notes" msgstr "" #: ../source/2025.2.rst:3 msgid "2025.2 Series Release Notes" msgstr "" #: ../source/2026.1.rst:3 msgid "2026.1 Series Release Notes" msgstr "" #: ../source/index.rst:3 msgid "Nova Release Notes" msgstr "" #: ../source/liberty.rst:3 msgid "Liberty Series Release Notes" msgstr "" #: ../source/liberty.rst:8 msgid "12.0.5" msgstr "" #: ../source/liberty.rst:17 msgid "" "The qemu-img tool now has resource limits applied which prevent it from " "using more than 1GB of address space or more than 2 seconds of CPU time. " "This provides protection against denial of service attacks from maliciously " "crafted or corrupted disk images. oslo.concurrency>=2.6.1 is required for " "this fix." msgstr "" #: ../source/liberty.rst:23 msgid "12.0.4" msgstr "" #: ../source/liberty.rst:32 ../source/mitaka.rst:98 ../source/newton.rst:670 msgid "" "The ``record`` configuration option for the console proxy services (like " "VNC, serial, spice) is changed from boolean to string. It specifies the " "filename that will be used for recording websocket frames." msgstr "" #: ../source/liberty.rst:42 ../source/mitaka.rst:687 ../source/newton.rst:1108 msgid "" "When plugging virtual interfaces of type vhost-user the MTU value will not " "be applied to the interface by nova. vhost-user ports exist only in " "userspace and are not backed by kernel netdevs, for this reason it is not " "possible to set the mtu on a vhost-user interface using standard tools such " "as ifconfig or ip link." msgstr "" #: ../source/liberty.rst:48 msgid "12.0.3" msgstr "" #: ../source/liberty.rst:57 ../source/mitaka.rst:670 msgid "" "[OSSA 2016-007] Host data leak during resize/migrate for raw-backed " "instances (CVE-2016-2140)" msgstr "" #: ../source/liberty.rst:59 ../source/mitaka.rst:672 msgid "`Bug 1548450 `_" msgstr "" #: ../source/liberty.rst:60 ../source/mitaka.rst:673 msgid "" "`Announcement `__" msgstr "" #: ../source/liberty.rst:66 msgid "12.0.1" msgstr "" #: ../source/liberty.rst:75 msgid "The 12.0.1 release contains fixes for two security issues." msgstr "" #: ../source/liberty.rst:85 ../source/mitaka.rst:660 msgid "[OSSA 2016-001] Nova host data leak through snapshot (CVE-2015-7548)" msgstr "" #: ../source/liberty.rst:87 ../source/mitaka.rst:662 msgid "`Bug 1524274 `_" msgstr "" #: ../source/liberty.rst:88 ../source/mitaka.rst:663 msgid "" "`Announcement `__" msgstr "" #: ../source/liberty.rst:90 ../source/mitaka.rst:665 msgid "" "[OSSA 2016-002] Xen connection password leak in logs via StorageError (CVE-" "2015-8749)" msgstr "" #: ../source/liberty.rst:92 ../source/mitaka.rst:667 msgid "`Bug 1516765 `_" msgstr "" #: ../source/liberty.rst:93 ../source/mitaka.rst:668 msgid "" "`Announcement `__" msgstr "" #: ../source/liberty.rst:103 msgid "" "Fixes a bug where Nova services won't recover after a temporary DB " "connection issue, when service group DB driver is used together with local " "conductor, as the driver only handles RPC timeout errors." msgstr "" #: ../source/liberty.rst:107 msgid "For more info see https://bugs.launchpad.net/nova/+bug/1505471" msgstr "" #: ../source/liberty.rst:111 msgid "" "Fixes a bug where Nova services won't recover after a temporary DB / MQ " "connection issue, when service group DB driver is used together with remote " "conductor, as the driver only handles RPC timeout errors and does not " "account for other types of errors (e.g. wrapped DB errors on the remote " "conductor transported over RPC)" msgstr "" #: ../source/liberty.rst:117 msgid "For more info see https://bugs.launchpad.net/nova/+bug/1517926" msgstr "" #: ../source/liberty.rst:127 msgid "Start using reno to manage release notes." msgstr "" #: ../source/mitaka.rst:3 msgid "Mitaka Series Release Notes" msgstr "" #: ../source/mitaka.rst:8 msgid "13.1.4" msgstr "" #: ../source/mitaka.rst:17 ../source/newton.rst:141 ../source/ocata.rst:154 #: ../source/ocata.rst:410 ../source/pike.rst:223 ../source/pike.rst:587 msgid "This release includes fixes for security vulnerabilities." msgstr "" #: ../source/mitaka.rst:27 ../source/newton.rst:170 ../source/ocata.rst:420 #: ../source/pike.rst:1744 msgid "" "[CVE-2017-7214] Failed notification payload is dumped in logs with auth " "secrets" msgstr "" #: ../source/mitaka.rst:29 ../source/newton.rst:172 ../source/ocata.rst:422 #: ../source/pike.rst:1746 msgid "`Bug 1673569 `_" msgstr "" #: ../source/mitaka.rst:35 msgid "13.1.3" msgstr "" #: ../source/mitaka.rst:44 ../source/newton.rst:220 ../source/ocata.rst:1578 #: ../source/pike.rst:1781 msgid "" "Fixes `bug 1662699`_ which was a regression in the v2.1 API from the " "``block_device_mapping_v2.boot_index`` validation that was performed in the " "legacy v2 API. With this fix, requests to create a server with ``boot_index=" "None`` will be treated as if ``boot_index`` was not specified, which " "defaults to meaning a non-bootable block device." msgstr "" #: ../source/mitaka.rst:56 msgid "13.1.2" msgstr "" #: ../source/mitaka.rst:65 ../source/newton.rst:1085 msgid "" "Fixed bug #1579706: \"Listing nova instances with invalid status raises 500 " "InternalServerError for admin user\". Now passing an invalid status as a " "filter will return an empty list. A subsequent patch will then correct this " "to raise a 400 Bad Request when an invalid status is received." msgstr "" #: ../source/mitaka.rst:74 msgid "13.1.1" msgstr "" #: ../source/mitaka.rst:79 ../source/newton.rst:147 ../source/newton.rst:183 #: ../source/newton.rst:247 ../source/newton.rst:608 ../source/ocata.rst:248 #: ../source/ocata.rst:443 ../source/ocata.rst:920 ../source/pike.rst:375 #: ../source/pike.rst:994 ../source/queens.rst:266 ../source/queens.rst:1158 #: ../source/rocky.rst:1440 ../source/stein.rst:234 ../source/stein.rst:821 #: ../source/train.rst:881 ../source/ussuri.rst:162 ../source/ussuri.rst:625 #: ../source/victoria.rst:92 ../source/victoria.rst:218 #: ../source/victoria.rst:456 ../source/wallaby.rst:197 #: ../source/wallaby.rst:567 ../source/xena.rst:223 ../source/xena.rst:458 #: ../source/yoga.rst:110 ../source/yoga.rst:491 ../source/zed.rst:375 msgid "Known Issues" msgstr "" #: ../source/mitaka.rst:83 ../source/newton.rst:616 msgid "" "When using Neutron extension 'port_security' and booting an instance on a " "network with 'port_security_enabled=False' the Nova API response says there " "is a 'default' security group attached to the instance which is incorrect. " "However when listing security groups for the instance there are none listed, " "which is correct. The API response will be fixed separately with a " "microversion." msgstr "" #: ../source/mitaka.rst:89 msgid "13.1.0" msgstr "" #: ../source/mitaka.rst:108 ../source/newton.rst:1071 msgid "" "The qemu-img tool now has resource limits applied which prevent it from " "using more than 1GB of address space or more than 2 seconds of CPU time. " "This provides protection against denial of service attacks from maliciously " "crafted or corrupted disk images." msgstr "" #: ../source/mitaka.rst:114 msgid "13.0.0" msgstr "" #: ../source/mitaka.rst:139 msgid "" "Nova 13.0.0 release is including a lot of new features and bugfixes. It can " "be extremely hard to mention all the changes we introduced during that " "release but we beg you to read at least the upgrade section which describes " "the required modifications that you need to do for upgrading your cloud from " "12.0.0 (Liberty) to 13.0.0 (Mitaka)." msgstr "" #: ../source/mitaka.rst:145 msgid "" "That said, a few major changes are worth to notice here. This is not an " "exhaustive list of things to notice, rather just important things you need " "to know :" msgstr "" #: ../source/mitaka.rst:149 msgid "Latest API microversion supported for Mitaka is v2.25" msgstr "" #: ../source/mitaka.rst:150 msgid "Nova now requires a second database (called 'API DB')." msgstr "" #: ../source/mitaka.rst:151 msgid "" "A new nova-manage script allows you to perform all online DB migrations once " "you upgrade your cloud" msgstr "" #: ../source/mitaka.rst:153 msgid "EC2 API support is fully removed." msgstr "" #: ../source/mitaka.rst:175 msgid "" "Enables NUMA topology reporting on PowerPC architecture from the libvirt " "driver in Nova but with a caveat as mentioned below. NUMA cell affinity and " "dedicated cpu pinning code assumes that the host operating system is exposed " "to threads. PowerPC based hosts use core based scheduling for processes. Due " "to this, the cores on the PowerPC architecture are treated as threads. Since " "cores are always less than or equal to the threads on a system, this leads " "to non-optimal resource usage while pinning. This feature is supported from " "libvirt version 1.2.19 for PowerPC." msgstr "" #: ../source/mitaka.rst:188 msgid "" "A new REST API to cancel an ongoing live migration has been added in " "microversion 2.24. Initially this operation will only work with the libvirt " "virt driver." msgstr "" #: ../source/mitaka.rst:192 msgid "" "It is possible to call attach and detach volume API operations for instances " "which are in shelved and shelved_offloaded state. For an instance in " "shelved_offloaded state Nova will set to None the value for the device_name " "field, the right value for that field will be set once the instance will be " "unshelved as it will be managed by a specific compute manager." msgstr "" #: ../source/mitaka.rst:196 msgid "" "It is possible to block live migrate instances with additional cinder " "volumes attached. This requires libvirt version to be >=1.2.17 and does not " "work when live_migration_tunnelled is set to True." msgstr "" #: ../source/mitaka.rst:200 msgid "" "Project-id and user-id are now also returned in the return data of os-server-" "groups APIs. In order to use this new feature, user have to contain the " "header of request microversion v2.13 in the API request." msgstr "" #: ../source/mitaka.rst:208 msgid "Add support for enabling uefi boot with libvirt." msgstr "" #: ../source/mitaka.rst:212 msgid "" "A new host_status attribute for servers/detail and servers/{server_id}. In " "order to use this new feature, user have to contain the header of request " "microversion v2.16 in the API request. A new policy ``os_compute_api:servers:" "show:host_status`` added to enable the feature. By default, this is only " "exposed to cloud administrators." msgstr "" #: ../source/mitaka.rst:220 msgid "" "A new server action trigger_crash_dump has been added to the REST API in " "microversion 2.17." msgstr "" #: ../source/mitaka.rst:224 msgid "" "When RBD is used for ephemeral disks and image storage, make snapshot use " "Ceph directly, and update Glance with the new location. In case of failure, " "it will gracefully fallback to the \"generic\" snapshot method. This " "requires changing the typical permissions for the Nova Ceph user (if using " "authx) to allow writing to the pool where vm images are stored, and it also " "requires configuring Glance to provide a v2 endpoint with direct_url support " "enabled (there are security implications to doing this). See http://docs." "ceph.com/docs/master/rbd/rbd-openstack/ for more information on configuring " "OpenStack with RBD." msgstr "" #: ../source/mitaka.rst:228 msgid "" "A new option \"live_migration_inbound_addr\" has been added in the " "configuration file, set None as default value. If this option is present in " "pre_migration_data, the ip address/hostname provided will be used instead of " "the migration target compute node's hostname as the uri for live migration, " "if it's None, then the mechanism remains as it is before." msgstr "" #: ../source/mitaka.rst:238 msgid "" "Added support for CPU thread policies, which can be used to control how the " "libvirt virt driver places guests with respect to CPU SMT \"threads\". These " "are provided as instance and image metadata options, 'hw:cpu_thread_policy' " "and 'hw_cpu_thread_policy' respectively, and provide an additional level of " "control over CPU pinning policy, when compared to the existing CPU policy " "feature. These changes were introduced in commits '83cd67c' and 'aaaba4a'." msgstr "" #: ../source/mitaka.rst:242 msgid "" "Add support for enabling discard support for block devices with libvirt. " "This will be enabled for Cinder volume attachments that specify support for " "the feature in their connection properties. This requires support to be " "present in the version of libvirt (v1.0.6+) and qemu (v1.6.0+) used along " "with the configured virtual drivers for the instance. The virtio-blk driver " "does not support this functionality." msgstr "" #: ../source/mitaka.rst:246 msgid "" "A new ``auto`` value for the configuration option ``upgrade_levels.compute`` " "is accepted, that allows automatic determination of the compute service " "version to use for RPC communication. By default, we still use the newest " "version if not set in the config, a specific version if asked, and only do " "this automatic behavior if 'auto' is configured. When 'auto' is used, " "sending a SIGHUP to the service will cause the value to be re-calculated. " "Thus, after an upgrade is complete, sending SIGHUP to all services will " "cause them to start sending messages compliant with the newer RPC version." msgstr "" #: ../source/mitaka.rst:258 msgid "Libvirt driver in Nova now supports Cinder DISCO volume driver." msgstr "" #: ../source/mitaka.rst:262 msgid "" "A disk space scheduling filter is now available, which prefers compute nodes " "with the most available disk space. By default, free disk space is given " "equal importance to available RAM. To increase the priority of free disk " "space in scheduling, increase the disk_weight_multiplier option." msgstr "" #: ../source/mitaka.rst:266 msgid "" "A new REST API to force live migration to complete has been added in " "microversion 2.22." msgstr "" #: ../source/mitaka.rst:270 msgid "" "The os-instance-actions methods now read actions from deleted instances. " "This means that 'GET /v2.1/{tenant-id}/servers/{server-id}/os-instance-" "actions' and 'GET /v2.1/{tenant-id}/servers/{server-id}/os-instance-actions/" "{req-id}' will return instance-action items even if the instance " "corresponding to '{server-id}' has been deleted." msgstr "" #: ../source/mitaka.rst:274 msgid "" "When booting an instance, its sanitized 'hostname' attribute is now used to " "populate the 'dns_name' attribute of the Neutron ports the instance is " "attached to. This functionality enables the Neutron internal DNS service to " "know the ports by the instance's hostname. As a consequence, commands like " "'hostname -f' will work as expected when executed in the instance. When a " "port's network has a non-blank 'dns_domain' attribute, the port's 'dns_name' " "combined with the network's 'dns_domain' will be published by Neutron in an " "external DNS as a service like Designate. As a consequence, the instance's " "hostname is published in the external DNS as a service. This functionality " "is added to Nova when the 'DNS Integration' extension is enabled in Neutron. " "The publication of 'dns_name' and 'dns_domain' combinations to an external " "DNS as a service additionally requires the configuration of the appropriate " "driver in Neutron. When the 'Port Binding' extension is also enabled in " "Neutron, the publication of a 'dns_name' and 'dns_domain' combination to the " "external DNS as a service will require one additional update operation when " "Nova allocates the port during the instance boot. This may have a noticeable " "impact on the performance of the boot process." msgstr "" #: ../source/mitaka.rst:278 msgid "" "The libvirt driver now has a live_migration_tunnelled configuration option " "which should be used where the VIR_MIGRATE_TUNNELLED flag would previously " "have been set or unset in the live_migration_flag and block_migration_flag " "configuration options." msgstr "" #: ../source/mitaka.rst:282 msgid "" "For the libvirt driver, by default hardware properties will be retrieved " "from the Glance image and if such haven't been provided, it will use a " "libosinfo database to get those values. If users want to force a specific " "guest OS ID for the image, they can now use a new glance image property " "``os_distro`` (eg. ``--property os_distro=fedora21``). In order to use the " "libosinfo database, you need to separately install the related native " "package provided for your operating system distribution." msgstr "" #: ../source/mitaka.rst:286 msgid "" "Add support for allowing Neutron to specify the bridge name for the OVS, " "Linux Bridge, and vhost-user VIF types." msgstr "" #: ../source/mitaka.rst:290 msgid "" "Added a ``nova-manage db online_data_migrations`` command for forcing online " "data migrations, which will run all registered migrations for the release, " "instead of there being a separate command for each logical data migration. " "Operators need to make sure all data is migrated before upgrading to the " "next release, and the new command provides a unified interface for doing it." msgstr "" #: ../source/mitaka.rst:294 msgid "" "Provides API 2.18, which makes the use of project_ids in API urls optional." msgstr "" #: ../source/mitaka.rst:298 msgid "" "Libvirt with Virtuozzo virtualisation type now supports snapshot operations" msgstr "" #: ../source/mitaka.rst:302 msgid "" "Remove ``onSharedStorage`` parameter from server's evacuate action in " "microversion 2.14. Nova will automatically detect if the instance is on " "shared storage. Also adminPass is removed from the response body which makes " "the response body empty. The user can get the password with the server's os-" "server-password action." msgstr "" #: ../source/mitaka.rst:306 msgid "" "Add two new list/show API for server-migration. The list API will return the " "in progress live migratons information of a server. The show API will return " "a specified in progress live migration of a server. This has been added in " "microversion 2.23." msgstr "" #: ../source/mitaka.rst:314 msgid "" "A new service.status versioned notification has been introduced. When the " "status of the Service object is changed nova will send a new service.update " "notification with versioned payload according to bp versioned-notification-" "api. The new notification is documented in http://docs.openstack.org/" "developer/nova/notifications.html" msgstr "" #: ../source/mitaka.rst:318 msgid "" "Two new policies soft-affinty and soft-anti-affinity have been implemented " "for the server-group feature of Nova. This means that POST /v2.1/" "{tenant_id}/os-server-groups API resource now accepts 'soft-affinity' and " "'soft-anti-affinity' as value of the 'policies' key of the request body." msgstr "" #: ../source/mitaka.rst:322 msgid "" "In Nova Compute API microversion 2.19, you can specify a \"description\" " "attribute when creating, rebuilding, or updating a server instance. This " "description can be retrieved by getting server details, or list details for " "servers. Refer to the Nova Compute API documentation for more information. " "Note that the description attribute existed in prior Nova versions, but was " "set to the server name by Nova, and was not visible to the user. So, " "servers you created with microversions prior to 2.19 will return the " "description equals the name on server details microversion 2.19." msgstr "" #: ../source/mitaka.rst:328 msgid "" "As part of refactoring the notification interface of Nova a new config " "option 'notification_format' has been added to specifies which notification " "format shall be used by nova. The possible values are 'unversioned' (e.g. " "legacy), 'versioned', 'both'. The default value is 'both'. The new versioned " "notifications are documented in http://docs.openstack.org/developer/nova/" "notifications.html" msgstr "" #: ../source/mitaka.rst:332 msgid "" "For the VMware driver, the flavor extra specs for quotas has been extended " "to support:" msgstr "" #: ../source/mitaka.rst:335 msgid "" "quota:cpu_limit - The cpu of a virtual machine will not exceed this limit, " "even if there are available resources. This is typically used to ensure a " "consistent performance of virtual machines independent of available " "resources. Units are MHz." msgstr "" #: ../source/mitaka.rst:339 msgid "quota:cpu_reservation - guaranteed minimum reservation (MHz)" msgstr "" #: ../source/mitaka.rst:340 msgid "" "quota:cpu_shares_level - the allocation level. This can be 'custom', 'high', " "'normal' or 'low'." msgstr "" #: ../source/mitaka.rst:342 msgid "" "quota:cpu_shares_share - in the event that 'custom' is used, this is the " "number of shares." msgstr "" #: ../source/mitaka.rst:344 msgid "" "quota:memory_limit - The memory utilization of a virtual machine will not " "exceed this limit, even if there are available resources. This is typically " "used to ensure a consistent performance of virtual machines independent of " "available resources. Units are MB." msgstr "" #: ../source/mitaka.rst:348 msgid "quota:memory_reservation - guaranteed minimum reservation (MB)" msgstr "" #: ../source/mitaka.rst:349 msgid "" "quota:memory_shares_level - the allocation level. This can be 'custom', " "'high', 'normal' or 'low'." msgstr "" #: ../source/mitaka.rst:351 msgid "" "quota:memory_shares_share - in the event that 'custom' is used, this is the " "number of shares." msgstr "" #: ../source/mitaka.rst:353 msgid "" "quota:disk_io_limit - The I/O utilization of a virtual machine will not " "exceed this limit. The unit is number of I/O per second." msgstr "" #: ../source/mitaka.rst:355 msgid "" "quota:disk_io_reservation - Reservation control is used to provide " "guaranteed allocation in terms of IOPS" msgstr "" #: ../source/mitaka.rst:357 msgid "" "quota:disk_io_shares_level - the allocation level. This can be 'custom', " "'high', 'normal' or 'low'." msgstr "" #: ../source/mitaka.rst:359 msgid "" "quota:disk_io_shares_share - in the event that 'custom' is used, this is the " "number of shares." msgstr "" #: ../source/mitaka.rst:361 msgid "" "quota:vif_limit - The bandwidth limit for the virtual network adapter. The " "utilization of the virtual network adapter will not exceed this limit, even " "if there are available resources. Units in Mbits/sec." msgstr "" #: ../source/mitaka.rst:364 msgid "" "quota:vif_reservation - Amount of network bandwidth that is guaranteed to " "the virtual network adapter. If utilization is less than reservation, the " "resource can be used by other virtual network adapters. Reservation is not " "allowed to exceed the value of limit if limit is set. Units in Mbits/sec." msgstr "" #: ../source/mitaka.rst:369 msgid "" "quota:vif_shares_level - the allocation level. This can be 'custom', 'high', " "'normal' or 'low'." msgstr "" #: ../source/mitaka.rst:371 msgid "" "quota:vif_shares_share - in the event that 'custom' is used, this is the " "number of shares." msgstr "" #: ../source/mitaka.rst:382 msgid "" "All noVNC proxy configuration options have been added to the 'vnc' group. " "They should no longer be included in the 'DEFAULT' group." msgstr "" #: ../source/mitaka.rst:386 msgid "" "All VNC XVP configuration options have been added to the 'vnc' group. They " "should no longer be included in the 'DEFAULT' group." msgstr "" #: ../source/mitaka.rst:390 msgid "" "Upon first startup of the scheduler service in Mitaka, all defined " "aggregates will have UUIDs generated and saved back to the database. If you " "have a significant number of aggregates, this may delay scheduler start as " "that work is completed, but it should be minor for most deployments." msgstr "" #: ../source/mitaka.rst:394 msgid "" "During an upgrade to Mitaka, operators must create and initialize a database " "for the API service. Configure this in [api_database]/connection, and then " "run ``nova-manage api_db sync``" msgstr "" #: ../source/mitaka.rst:398 msgid "" "We can not use microversion 2.25 to do live-migration during upgrade, nova-" "api will raise bad request if there is still old compute node in the cluster." "" msgstr "" #: ../source/mitaka.rst:402 msgid "" "The option ``scheduler_driver`` is now changed to use entrypoint instead of " "full class path. Set one of the entrypoints under the namespace 'nova." "scheduler.driver' in 'setup.cfg'. Its default value is 'host_manager'. The " "full class path style is still supported in current release. But it is not " "recommended because class path can be changed and this support will be " "dropped in the next major release." msgstr "" #: ../source/mitaka.rst:411 msgid "" "The option ``scheduler_host_manager`` is now changed to use entrypoint " "instead of full class path. Set one of the entrypoints under the namespace " "'nova.scheduler.host_manager' in 'setup.cfg'. Its default value is " "'host_manager'. The full class path style is still supported in current " "release. But it is not recommended because class path can be changed and " "this support will be dropped in the next major release." msgstr "" #: ../source/mitaka.rst:420 msgid "" "The local conductor mode is now deprecated and may be removed as early as " "the 14.0.0 release. If you are using local conductor mode, plan on deploying " "remote conductor by the time you upgrade to the 14.0.0 release." msgstr "" #: ../source/mitaka.rst:427 msgid "" "The Extensible Resource Tracker is deprecated and will be removed in the 14." "0.0 release. If you use this functionality and have custom resources that " "are managed by the Extensible Resource Tracker, please contact the Nova " "development team by posting to the openstack-dev mailing list. There is no " "future planned support for the tracking of custom resources." msgstr "" #: ../source/mitaka.rst:436 msgid "" "For Liberty compute nodes, the disk_allocation_ratio works as before, you " "must set it on the scheduler if you want to change it. For Mitaka compute " "nodes, the disk_allocation_ratio set on the compute nodes will be used only " "if the configuration is not set on the scheduler. This is to allow, for " "backwards compatibility, the ability to still override the disk allocation " "ratio by setting the configuration on the scheduler node. In Newton, we plan " "to remove the ability to set the disk allocation ratio on the scheduler, at " "which point the compute nodes will always define the disk allocation ratio, " "and pass that up to the scheduler. None of this changes the default disk " "allocation ratio of 1.0. This matches the behaviour of the RAM and CPU " "allocation ratios." msgstr "" #: ../source/mitaka.rst:440 msgid "" "(Only if you do continuous deployment) " "1337890ace918fa2555046c01c8624be014ce2d8 drops support for an instance major " "version, which means that you must have deployed at least commit " "713d8cb0777afb9fe4f665b9a40cac894b04aacb before deploying this one." msgstr "" #: ../source/mitaka.rst:447 msgid "nova now requires ebtables 2.0.10 or later" msgstr "" #: ../source/mitaka.rst:451 msgid "nova recommends libvirt 1.2.11 or later" msgstr "" #: ../source/mitaka.rst:455 msgid "" "Filters internal interface changed using now the RequestSpec NovaObject " "instead of an old filter_properties dictionary. In case you run out-of-tree " "filters, you need to modify the host_passes() method to accept a new " "RequestSpec object and modify the filter internals to use that new object. " "You can see other in-tree filters for getting the logic or ask for help in " "#openstack-nova IRC channel." msgstr "" #: ../source/mitaka.rst:464 msgid "" "The ``force_config_drive`` configuration option provided an ``always`` value " "which was deprecated in the previous release. That ``always`` value is now " "no longer accepted and deployments using that value have to change it to " "``True`` before upgrading." msgstr "" #: ../source/mitaka.rst:471 msgid "" "Support for Windows / Hyper-V Server 2008 R2 has been deprecated in Liberty " "(12.0.0) and it is no longer supported in Mitaka (13.0.0). If you have " "compute nodes running that version, please consider moving the running " "instances to other compute nodes before upgrading those to Mitaka." msgstr "" #: ../source/mitaka.rst:475 msgid "" "The libvirt driver will now correct unsafe and invalid values for the " "live_migration_flag and block_migration_flag configuration options. The " "live_migration_flag must not contain VIR_MIGRATE_SHARED_INC but " "block_migration_flag must contain it. Both options must contain the " "VIR_MIGRATE_PEER2PEER, except when using the 'xen' virt type this flag is " "not supported. Both flags must contain the VIR_MIGRATE_UNDEFINE_SOURCE flag " "and not contain the VIR_MIGRATE_PERSIST_DEST flag." msgstr "" #: ../source/mitaka.rst:479 msgid "" "The libvirt driver has changed the default value of the 'live_migration_uri' " "flag, that now is dependent on the 'virt_type'. The old default 'qemu+tcp://" "%s/system' now is adjusted for each of the configured hypervisors. For Xen " "this will be 'xenmigr://%s/system', for kvm/qemu this will be 'qemu+tcp://%s/" "system'." msgstr "" #: ../source/mitaka.rst:483 msgid "" "The minimum required libvirt is now version 0.10.2. The minimum libvirt for " "the N release has been set to 1.2.1." msgstr "" #: ../source/mitaka.rst:487 msgid "" "In order to make project_id optional in urls, we must constrain the set of " "allowed values for project_id in our urls. This defaults to a regex of ``[0-" "9a-f\\-]+``, which will match hex uuids (with / without dashes), and " "integers. This covers all known project_id formats in the wild. If your site " "uses other values for project_id, you can set a site specific validation " "with ``project_id_regex`` config variable." msgstr "" #: ../source/mitaka.rst:492 msgid "" "The old neutron communication options that were slated for removal in Mitaka " "are no longer available. This means that going forward communication to " "neutron will need to be configured using auth plugins." msgstr "" #: ../source/mitaka.rst:496 msgid "" "All code and tests for Nova's EC2 and ObjectStore API support which was " "deprecated in Kilo (https://wiki.openstack.org/wiki/ReleaseNotes/" "Kilo#Upgrade_Notes_2) has been completely removed in Mitaka. This has been " "replaced by the new ec2-api project (http://opendev.org/openstack/ec2-api/)." msgstr "" #: ../source/mitaka.rst:502 msgid "" "Some installation tools (such as ``packstack``) hardcode the value of " "``enabled_apis`` in your nova.conf. While the defaults for ``enabled_apis`` " "dropped ``ec2`` as a value, if that is hard coded in your nova.conf, you " "will need to remove it before restarting Nova's API server, or it will not " "start." msgstr "" #: ../source/mitaka.rst:510 msgid "" "The commit with change-id Idd4bbbe8eea68b9e538fa1567efd304e9115a02a requires " "that the nova_api database is setup and Nova is configured to use it. " "Instructions on doing that are provided below." msgstr "" #: ../source/mitaka.rst:514 msgid "" "Nova now requires that two databases are available and configured. The " "existing nova database needs no changes, but a new nova_api database needs " "to be setup. It is configured and managed very similarly to the nova " "database. A new connection string configuration option is available in the " "api_database group. An example::" msgstr "" #: ../source/mitaka.rst:523 msgid "" "And a new nova-manage command has been added to manage db migrations for " "this database. \"nova-manage api_db sync\" and \"nova-manage api_db " "version\" are available and function like the parallel \"nova-manage db ..." "\" version." msgstr "" #: ../source/mitaka.rst:529 msgid "" "A new ``use_neutron`` option is introduced which replaces the obtuse " "``network_api_class`` option. This defaults to 'False' to match existing " "defaults, however if ``network_api_class`` is set to the known Neutron value " "Neutron networking will still be used as before." msgstr "" #: ../source/mitaka.rst:533 msgid "" "The FilterScheduler is now including disabled hosts. Make sure you include " "the ComputeFilter in the ``scheduler_default_filters`` config option to " "avoid placing instances on disabled hosts." msgstr "" #: ../source/mitaka.rst:537 msgid "" "Upgrade the rootwrap configuration for the compute service, so that patches " "requiring new rootwrap configuration can be tested with grenade." msgstr "" #: ../source/mitaka.rst:541 msgid "" "For backward compatible support the setting ``CONF.vmware." "integration_bridge`` needs to be set when using the Neutron NSX|MH plugin. " "The default value has been set to ``None``." msgstr "" #: ../source/mitaka.rst:545 msgid "" "XenServer hypervisor type has been changed from ``xen`` to ``XenServer``. It " "could impact your aggregate metadata or your flavor extra specs if you " "provide only the former." msgstr "" #: ../source/mitaka.rst:549 msgid "" "The glance xenserver plugin has been bumped to version 1.3 which includes " "new interfaces for referencing glance servers by url. All dom0 will need to " "be upgraded with this plugin before upgrading the nova code." msgstr "" #: ../source/mitaka.rst:559 msgid "" "It is now deprecated to use [glance] api_servers without a protocol scheme " "(http / https). This is required to support urls throughout the system. " "Update any api_servers list with fully qualified https / http urls." msgstr "" #: ../source/mitaka.rst:563 msgid "" "The conductor.manager configuration option is now deprecated and will be " "removed." msgstr "" #: ../source/mitaka.rst:567 msgid "" "Deprecate ``compute_stats_class`` config option. This allowed loading an " "alternate implementation for collecting statistics for the local compute " "host. Deployments that felt the need to use this facility are encoraged to " "propose additions upstream so we can create a stable and supported interface " "here." msgstr "" #: ../source/mitaka.rst:571 msgid "" "Deprecate the ``db_driver`` config option. Previously this let you replace " "our SQLAlchemy database layer with your own. This approach is deprecated. " "Deployments that felt the need to use the facility are encourage to work " "with upstream Nova to address db driver concerns in the main SQLAlchemy code " "paths." msgstr "" #: ../source/mitaka.rst:575 msgid "" "The host, port, and protocol options in the [glance] configuration section " "are deprecated, and will be removed in the N release. The api_servers value " "should be used instead." msgstr "" #: ../source/mitaka.rst:579 msgid "" "Deprecate the use of nova.hooks. This facility used to let arbitrary out of " "tree code be executed around certain internal actions, but is unsuitable for " "having a well maintained API. Anyone using this facility should bring " "forward their use cases in the Newton cycle as nova-specs." msgstr "" #: ../source/mitaka.rst:583 msgid "" "Nova used to support the concept that ``service managers`` were replaceable " "components. There are many config options where you can replace a manager by " "specifying a new class. This concept is deprecated in Mitaka as are the " "following config options." msgstr "" #: ../source/mitaka.rst:588 msgid "[cells] manager" msgstr "" #: ../source/mitaka.rst:589 msgid "metadata_manager" msgstr "" #: ../source/mitaka.rst:590 msgid "compute_manager" msgstr "" #: ../source/mitaka.rst:591 msgid "console_manager" msgstr "" #: ../source/mitaka.rst:592 msgid "consoleauth_manager" msgstr "" #: ../source/mitaka.rst:593 msgid "cert_manager" msgstr "" #: ../source/mitaka.rst:594 msgid "scheduler_manager" msgstr "" #: ../source/mitaka.rst:596 msgid "" "Many of these will be removed in Newton. Users of these options are " "encouraged to work with Nova upstream on any features missing in the default " "implementations that are needed." msgstr "" #: ../source/mitaka.rst:602 msgid "" "Deprecate ``security_group_api`` configuration option. The current values " "are ``nova`` and ``neutron``. In future the correct security_group_api " "option will be chosen based on the value of ``use_neutron`` which provides a " "more coherent user experience." msgstr "" #: ../source/mitaka.rst:606 msgid "" "Deprecate the ``vendordata_driver`` config option. This allowed creating a " "different class loader for defining vendordata metadata. The default driver " "loads from a json file that can be arbitrarily specified, so is still quite " "flexible. Deployments that felt the need to use this facility are encoraged " "to propose additions upstream so we can create a stable and supported " "interface here." msgstr "" #: ../source/mitaka.rst:610 msgid "" "The configuration option ``api_version`` in the ``ironic`` group was marked " "as deprecated and will be removed in the future. The only possible value for " "that configuration was \"1\" (because Ironic only has 1 API version) and the " "Ironic team came to an agreement that setting the API version via " "configuration option should not be supported anymore. As the Ironic driver " "in Nova requests the Ironic v1.8 API, that means that Nova 13.0.0 " "(\"Mitaka\") requires Ironic 4.0.0 (\"Liberty\") or newer if you want to use " "the Ironic driver." msgstr "" #: ../source/mitaka.rst:614 msgid "" "The libvirt live_migration_flag and block_migration_flag config options are " "deprecated. These options gave too fine grained control over the flags used " "and, in some cases, misconfigurations could have dangerous side effects. " "Please note the availability of a new live_migration_tunnelled configuration " "option." msgstr "" #: ../source/mitaka.rst:623 msgid "" "The ``network_device_mtu`` option in Nova is deprecated for removal since " "network MTU should be specified when creating the network with nova-network. " "With Neutron networks, the MTU value comes from the ``segment_mtu`` " "configuration option in Neutron." msgstr "" #: ../source/mitaka.rst:627 msgid "" "The old top-level resource ``/os-migrations`` is deprecated, it won't be " "extended anymore. And migration_type for /os-migrations, also add ref link " "to the /servers/{uuid}/migrations/{id} for it when the migration is an in-" "progress live-migration. This has been added in microversion 2.23." msgstr "" #: ../source/mitaka.rst:631 msgid "" "Deprecate ``volume_api_class`` and ``network_api_class`` config options. We " "only have one sensible backend for either of these. These options will be " "removed and turned into constants in Newton." msgstr "" #: ../source/mitaka.rst:635 msgid "" "Option ``memcached_servers`` is deprecated in Mitaka. Operators should use " "oslo.cache configuration instead. Specifically ``enabled`` option under " "[cache] section should be set to True and the url(s) for the memcached " "servers should be in [cache]/memcache_servers option." msgstr "" #: ../source/mitaka.rst:639 msgid "The Zookeeper Service Group driver has been removed." msgstr "" #: ../source/mitaka.rst:641 msgid "" "The driver has no known users and is not actively maintained. A warning log " "message about the driver's state was added for the Kilo release. Also, " "evzookeeper library that the driver depends on is unmaintained and " "`incompatible with recent eventlet releases`_." msgstr "" #: ../source/mitaka.rst:646 msgid "" "A future release of Nova will `use the Tooz library to track service " "liveliness`_, and Tooz supports Zookeeper." msgstr "" #: ../source/mitaka.rst:683 msgid "" "In a race condition if base image is deleted by ImageCacheManager while " "imagebackend is copying the image to instance path, then the instance goes " "in to error state. In this case when libvirt has changed the base file " "ownership to libvirt-qemu while imagebackend is copying the image, then we " "get permission denied error on updating the file access time using os.utime. " "Fixed this issue by updating the base file access time with root user " "privileges using 'touch' command." msgstr "" #: ../source/mitaka.rst:697 msgid "Conductor RPC API no longer supports v2.x." msgstr "" #: ../source/mitaka.rst:701 msgid "" "The service subcommand of nova-manage is deprecated. Use the nova service-* " "commands from python-novaclient instead or the os-services REST resource. " "The service subcommand will be removed in the 14.0 release." msgstr "" #: ../source/mitaka.rst:705 msgid "" "The Neutron network MTU value is now used when plugging virtual interfaces " "in nova-compute. If the value is 0, which is the default value for the " "``segment_mtu`` configuration option in Neutron before Mitaka, then the " "(deprecated) ``network_device_mtu`` configuration option in Nova is used, " "which defaults to not setting an MTU value." msgstr "" #: ../source/mitaka.rst:709 msgid "" "The sample policy file shipped with Nova contained many policies set to " "\"\"(allow all) which was not the proper default for many of those checks. " "It was also a source of confusion as some people thought \"\" meant to use " "the default rule. These empty policies have been updated to be explicit in " "all cases. Many of them were changed to match the default rule of " "\"admin_or_owner\" which is a more restrictive policy check but does not " "change the restrictiveness of the API calls overall because there are " "similar checks in the database already. This does not affect any existing " "deployment, just the sample file included for use by new deployments." msgstr "" #: ../source/mitaka.rst:715 msgid "" "Nova's EC2 API support which was deprecated in Kilo (https://wiki.openstack." "org/wiki/ReleaseNotes/Kilo#Upgrade_Notes_2) is removed from Mitaka. This has " "been replaced by the new ec2-api project (http://opendev.org/openstack/ec2-" "api/)." msgstr "" #: ../source/newton.rst:3 msgid "Newton Series Release Notes" msgstr "" #: ../source/newton.rst:8 msgid "14.1.0" msgstr "" #: ../source/newton.rst:17 ../source/ocata.rst:268 ../source/pike.rst:336 msgid "" "This release contains a schema migration for the ``nova_api`` database in " "order to address bug 1738094:" msgstr "" #: ../source/newton.rst:20 ../source/ocata.rst:271 ../source/pike.rst:339 msgid "https://bugs.launchpad.net/nova/+bug/1738094" msgstr "" #: ../source/newton.rst:22 ../source/ocata.rst:273 ../source/pike.rst:341 msgid "" "The migration is optional and can be postponed if you have not been affected " "by the bug. The bug manifests itself through \"Data too long for column " "'spec'\" database errors." msgstr "" #: ../source/newton.rst:34 ../source/ocata.rst:285 ../source/pike.rst:413 #: ../source/queens.rst:1684 msgid "" "The fix for `OSSA-2017-005`_ (CVE-2017-16239) was too far-reaching in that " "rebuilds can now fail based on scheduling filters that should not apply to " "rebuild. For example, a rebuild of an instance on a disabled compute host " "could fail whereas it would not before the fix for CVE-2017-16239. " "Similarly, rebuilding an instance on a host that is at capacity for vcpu, " "memory or disk could fail since the scheduler filters would treat it as a " "new build request even though the rebuild is not claiming *new* resources." msgstr "" #: ../source/newton.rst:42 ../source/ocata.rst:293 ../source/pike.rst:421 #: ../source/queens.rst:1692 msgid "" "Therefore this release contains a fix for those regressions in scheduling " "behavior on rebuild while maintaining the original fix for CVE-2017-16239." msgstr "" #: ../source/newton.rst:45 ../source/ocata.rst:296 ../source/pike.rst:424 #: ../source/queens.rst:1695 msgid "" "The fix relies on a ``RUN_ON_REBUILD`` variable which is checked for all " "scheduler filters during a rebuild. The reasoning behind the value for that " "variable depends on each filter. If you have out-of-tree scheduler filters, " "you will likely need to assess whether or not they need to override the " "default value (False) for the new variable." msgstr "" #: ../source/newton.rst:54 ../source/ocata.rst:314 ../source/pike.rst:433 #: ../source/queens.rst:1744 msgid "" "This release includes a fix for `bug 1733886`_ which was a regression " "introduced in the 2.36 API microversion where the ``force`` parameter was " "missing from the ``PUT /os-quota-sets/{tenant_id}`` API request schema so " "users could not force quota updates with microversion 2.36 or later. The bug " "is now fixed so that the ``force`` parameter can once again be specified " "during quota updates. There is no new microversion for this change since it " "is an admin-only API." msgstr "" #: ../source/newton.rst:68 msgid "14.0.10" msgstr "" #: ../source/newton.rst:77 ../source/ocata.rst:337 ../source/pike.rst:456 #: ../source/queens.rst:1632 msgid "`OSSA-2017-005`_: Nova Filter Scheduler bypass through rebuild action" msgstr "" #: ../source/newton.rst:79 ../source/ocata.rst:339 ../source/pike.rst:458 #: ../source/queens.rst:1634 msgid "" "By rebuilding an instance, an authenticated user may be able to circumvent " "the FilterScheduler bypassing imposed filters (for example, the " "ImagePropertiesFilter or the IsolatedHostsFilter). All setups using the " "FilterScheduler (or CachingScheduler) are affected." msgstr "" #: ../source/newton.rst:84 ../source/ocata.rst:344 ../source/pike.rst:463 #: ../source/queens.rst:1639 msgid "The fix is in the ``nova-api`` and ``nova-conductor`` services." msgstr "" #: ../source/newton.rst:92 msgid "14.0.7" msgstr "" #: ../source/newton.rst:101 ../source/ocata.rst:380 ../source/pike.rst:1800 msgid "" "Includes the fix for `bug 1673613`_ which could cause issues when upgrading " "and running ``nova-manage cell_v2 simple_cell_setup`` or ``nova-manage " "cell_v2 map_cell0`` where the database connection is read from config and " "has special characters in the URL." msgstr "" #: ../source/newton.rst:110 ../source/ocata.rst:389 ../source/pike.rst:1809 msgid "" "Fixes `bug 1691545`_ in which there was a significant increase in database " "connections because of the way connections to cell databases were being " "established. With this fix, objects related to database connections are " "cached in the API service and reused to prevent new connections being " "established for every communication with cell databases." msgstr "" #: ../source/newton.rst:120 ../source/ocata.rst:1592 msgid "" "The ``nova-manage cell_v2 simple_cell_setup`` command now creates the " "default cell0 database connection using the ``[database]`` connection " "configuration option rather than the ``[api_database]`` connection. The " "cell0 database schema is the ``main`` database, i.e. the ``instances`` " "table, rather than the ``api`` database schema. In other words, the cell0 " "database would be called something like ``nova_cell0`` rather than " "``nova_api_cell0``." msgstr "" #: ../source/newton.rst:132 msgid "14.0.5" msgstr "" #: ../source/newton.rst:151 msgid "" "The live-migration progress timeout controlled by the configuration option " "``[libvirt]/live_migration_progress_timeout`` has been discovered to " "frequently cause live-migrations to fail with a progress timeout error, even " "though the live-migration is still making good progress. To minimize " "problems caused by these checks we recommend setting the value to 0, which " "means do not trigger a timeout. (This has been made the default in Ocata " "and Pike.) To modify when a live-migration will fail with a timeout error, " "please now look at ``[libvirt]/live_migration_completion_timeout`` and " "``[libvirt]/live_migration_downtime``." msgstr "" #: ../source/newton.rst:178 msgid "14.0.4" msgstr "" #: ../source/newton.rst:187 msgid "" "When generating Libvirt XML to attach network interfaces for the ``tap``, " "``ivs``, ``iovisor``, ``midonet``, and ``vrouter`` virtual interface types " "Nova previously generated an empty path attribute to the script element " "(``