#, fuzzy msgid "" msgstr "" "Project-Id-Version: nova\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-05-06 18:10+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../:1077 msgid "**Filtering**" msgstr "" #: ../../:688 msgid "**New Defaults(Admin, Member and Reader)**" msgstr "" #: ../../:1168 msgid "**Other**" msgstr "" #: ../../:694 msgid "**Policies granularity**" msgstr "" #: ../../:662 msgid "**Ports**" msgstr "" #: ../../:677 msgid "**Scope**" msgstr "" #: ../../:1132 msgid "**Sorting**" msgstr "" #: ../../:656 msgid "**Volumes**" msgstr "" #: ../../:692 msgid "/etc/nova/placement-policy.yaml" msgstr "" #: ../../:691 msgid "/etc/nova/policy.yaml" msgstr "" #: ../../:698 msgid "/etc/placement/policy.yaml" msgstr "" #: ../../:506 msgid "15.0.0" msgstr "" #: ../../:425 msgid "15.0.1" msgstr "" #: ../../:398 msgid "15.0.2" msgstr "" #: ../../:368 msgid "15.0.5" msgstr "" #: ../../:349 msgid "15.0.7" msgstr "" #: ../../:325 msgid "15.0.8" msgstr "" #: ../../:240 msgid "15.1.0" msgstr "" #: ../../:142 msgid "15.1.1" msgstr "" #: ../../:120 msgid "15.1.3" msgstr "" #: ../../:89 msgid "15.1.4" msgstr "" #: ../../:53 msgid "15.1.5" msgstr "" #: ../../:5 msgid "15.1.5-28" msgstr "" #: ../../:575 msgid "16.0.0" msgstr "" #: ../../:521 msgid "16.0.1" msgstr "" #: ../../:488 msgid "16.0.2" msgstr "" #: ../../:444 msgid "16.0.3" msgstr "" #: ../../:367 msgid "16.0.4" msgstr "" #: ../../:289 msgid "16.1.0" msgstr "" #: ../../:266 msgid "16.1.1" msgstr "" #: ../../:211 msgid "16.1.2" msgstr "" #: ../../:116 msgid "16.1.5" msgstr "" #: ../../:97 msgid "16.1.7" msgstr "" #: ../../:61 msgid "16.1.8" msgstr "" #: ../../:5 msgid "16.1.8-57" msgstr "" #: ../../:576 msgid "17.0.0" msgstr "" #: ../../:177 msgid "17.0.10" msgstr "" #: ../../:125 msgid "17.0.11" msgstr "" #: ../../:75 msgid "17.0.12" msgstr "" #: ../../:59 msgid "17.0.13" msgstr "" #: ../../:5 msgid "17.0.13-73" msgstr "" #: ../../:533 msgid "17.0.2" msgstr "" #: ../../:501 msgid "17.0.3" msgstr "" #: ../../:481 msgid "17.0.4" msgstr "" #: ../../:403 msgid "17.0.5" msgstr "" #: ../../:258 msgid "17.0.6" msgstr "" #: ../../:243 msgid "17.0.8" msgstr "" #: ../../:224 msgid "17.0.9" msgstr "" #: ../../:494 msgid "18.0.0" msgstr "" #: ../../:479 msgid "18.0.1" msgstr "" #: ../../:455 msgid "18.0.3" msgstr "" #: ../../:369 msgid "18.1.0" msgstr "" #: ../../:269 msgid "18.2.0" msgstr "" #: ../../:243 msgid "18.2.1" msgstr "" #: ../../:167 msgid "18.2.2" msgstr "" #: ../../:149 msgid "18.2.3" msgstr "" #: ../../:110 msgid "18.3.0" msgstr "" #: ../../:5 msgid "18.3.0-55" msgstr "" #: ../../:396 msgid "19.0.0" msgstr "" #: ../../:370 msgid "19.0.1" msgstr "" #: ../../:313 msgid "19.0.2" msgstr "" #: ../../:226 msgid "19.0.3" msgstr "" #: ../../:157 msgid "19.1.0" msgstr "" #: ../../:125 msgid "19.2.0" msgstr "" #: ../../:86 msgid "19.3.0" msgstr "" #: ../../:56 msgid "19.3.2" msgstr "" #: ../../:5 msgid "19.3.2-19" msgstr "" #: ../../:448 msgid "20.0.0" msgstr "" #: ../../:383 msgid "20.1.0" msgstr "" #: ../../:346 msgid "20.1.1" msgstr "" #: ../../:295 msgid "20.2.0" msgstr "" #: ../../:274 msgid "20.3.0" msgstr "" #: ../../:256 msgid "20.4.0" msgstr "" #: ../../:207 msgid "20.4.1" msgstr "" #: ../../:146 msgid "20.5.0" msgstr "" #: ../../:126 msgid "20.6.1" msgstr "" #: ../../:5 msgid "20.6.1-41" msgstr "" #: ../../:733 msgid "204 NoContent on success" msgstr "" #: ../../:324 msgid "21.0.0" msgstr "" #: ../../:275 msgid "21.1.0" msgstr "" #: ../../:218 msgid "21.1.1" msgstr "" #: ../../:154 msgid "21.1.2" msgstr "" #: ../../:114 msgid "21.2.0" msgstr "" #: ../../:92 msgid "21.2.2" msgstr "" #: ../../:51 msgid "21.2.3" msgstr "" #: ../../:5 msgid "21.2.4-19" msgstr "" #: ../../:278 msgid "22.0.0" msgstr "" #: ../../:245 msgid "22.0.1" msgstr "" #: ../../:210 msgid "22.1.0" msgstr "" #: ../../:176 msgid "22.2.1" msgstr "" #: ../../:154 msgid "22.2.2" msgstr "" #: ../../:113 msgid "22.3.0" msgstr "" #: ../../:84 msgid "22.4.0" msgstr "" #: ../../:5 msgid "22.4.0-24" msgstr "" #: ../../:375 msgid "23.0.0" msgstr "" #: ../../:305 msgid "23.0.2" msgstr "" #: ../../:246 msgid "23.1.0" msgstr "" #: ../../:189 msgid "23.2.0" msgstr "" #: ../../:157 msgid "23.2.1" msgstr "" #: ../../:103 msgid "23.2.2" msgstr "" #: ../../:5 msgid "23.2.2-33" msgstr "" #: ../../:281 msgid "24.0.0" msgstr "" #: ../../:201 msgid "24.1.0" msgstr "" #: ../../:149 msgid "24.1.1" msgstr "" #: ../../:53 msgid "24.2.0" msgstr "" #: ../../:5 msgid "24.2.1-18" msgstr "" #: ../../:235 msgid "25.0.0" msgstr "" #: ../../:207 msgid "25.0.1" msgstr "" #: ../../:102 msgid "25.1.0" msgstr "" #: ../../:72 msgid "25.1.1" msgstr "" #: ../../:49 msgid "25.2.0" msgstr "" #: ../../:32 msgid "25.2.1" msgstr "" #: ../../:5 msgid "25.3.0" msgstr "" #: ../../:154 msgid "26.0.0" msgstr "" #: ../../:102 msgid "26.1.0" msgstr "" #: ../../:85 msgid "26.1.1" msgstr "" #: ../../:62 msgid "26.2.0" msgstr "" #: ../../:24 msgid "26.2.1" msgstr "" #: ../../:5 msgid "26.3.0" msgstr "" #: ../../:135 msgid "27.0.0" msgstr "" #: ../../:112 msgid "27.1.0" msgstr "" #: ../../:48 msgid "27.2.0" msgstr "" #: ../../:5 msgid "27.2.0-22" msgstr "" #: ../../:78 msgid "28.0.0" msgstr "" #: ../../:41 msgid "28.0.1" msgstr "" #: ../../:5 msgid "28.0.1-21" msgstr "" #: ../../:5 msgid "29.0.1" msgstr "" #: ../../:5 current msgid "29.0.1-26" msgstr "" #: ../../:604 msgid "400 for unknown param for query param and for request body." msgstr "" #: ../../:734 msgid "404 NotFound for missing resource provider" msgstr "" #: ../../:735 msgid "405 MethodNotAllowed if a microversion is specified that is before" msgstr "" #: ../../:738 msgid "409 Conflict if inventory in use or if some other request concurrently" msgstr "" #: ../../:358 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 "" #: ../../:135 stable/stein>:212 stable/train>:1435 msgid "" "A ``--dry-run`` option has been added to the ``nova-manage placement " "heal_allocations`` CLI which allows running the command to get output " "without committing any changes to placement." msgstr "" #: ../../:684 msgid "" "A ``--force`` flag is provided to skip the above checks but caution should " "be taken as this could easily lead to the underlying ABI of the instance " "changing when moving between machine types." msgstr "" #: ../../:364 msgid "" "A ``--sleep`` option has been added to the ``nova-manage db " "archive_deleted_rows`` CLI. When this command is run with the ``--until-" "complete`` option, the process will archive rows in batches in a tight loop, " "which can cause problems in busy environments where the aggressive archiving " "interferes with other requests trying to write to the database. The ``--" "sleep`` option can be used to specify a time to sleep between batches of " "rows while archiving with ``--until-complete``, allowing the process to be " "throttled." msgstr "" #: ../../:375 msgid "" "A ``--task-log`` option has been added to the ``nova-manage db " "archive_deleted_rows`` CLI. When ``--task-log`` is specified, ``task_log`` " "table records will be archived while archiving the database. The ``--task-" "log`` option works in conjunction with ``--before`` if operators desire " "archiving only records that are older than ````. The ``updated_at`` " "field is used by ``--task-log --before `` to determine the age of a " "``task_log`` record for archival." msgstr "" #: ../../:486 msgid "" "A ``[compute]image_type_exclusion_list`` configuration option was added to " "remove supported image types from being advertised by a compute node as " "supported. This is to be used in conjunction with " "``[scheduler]query_placement_for_image_type_support`` to prevent instances " "from booting on a compute node with a given image type, even if the " "underlying hypervisor supports it." msgstr "" #: ../../:1063 msgid "" "A ``default_floating_pool`` configuration option has been added in the " "``[neutron]`` group. The existing ``default_floating_pool`` option in the " "``[DEFAULT]`` group is retained and should be used by nova-network users. " "Neutron users meanwhile should migrate to the new option." msgstr "" #: ../../:526 msgid "" "A ``nova-manage db purge`` command to `purge archived shadow table data`_ is " "now available. A new ``--purge`` option is also available for the ``nova-" "manage db archive_deleted_rows`` command." msgstr "" #: ../../:541 msgid "" "A ``nova-manage placement heal_allocations`` command is now available to " "allow users of the CachingScheduler to get the placement service populated " "for their eventual migration to the FilterScheduler. The CachingScheduler is " "deprecated and could be removed as early as Stein." msgstr "" #: ../../:1038 msgid "" "A ``nova-manage placement sync_aggregates`` command has been added which can " "be used to mirror nova host aggregates to resource provider aggregates in " "the placement service. This is a useful tool if you are using aggregates in " "placement to optimize scheduling:" msgstr "" #: ../../:252 stable/rocky>:488 #: stable/stein>:1366 msgid "" "A change has been introduced in the libvirt driver to correctly handle IPv6 " "addresses for live migration." msgstr "" #: ../../:1165 msgid "" "A check for the use of the ``nova-consoleauth`` service, added to the ``nova-" "status upgrade check`` CLI in Rocky, is now removed." msgstr "" #: ../../:684 msgid "" "A config option ``[workarounds]unified_limits_count_pcpu_as_vcpu`` is " "available for operators who require the legacy quota usage behavior where " "VCPU = VCPU + PCPU. Note that if ``PCPU`` is specified in the flavor " "explicitly, it will be expected to have its own unified limit registered and " "PCPU usage will *not* be merged into VCPU usage." msgstr "" #: ../../:136 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 "" #: ../../:85 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 "" #: ../../:661 msgid "A few examples of versioned notifications that use InstancePayload:" msgstr "" #: ../../:487 msgid "" "A few of the APIs return code was not consistent for the operations/ " "features not implemented or supported. It was returned as 403, 400, or 409 " "(for Operation Not Supported For SEV , Operation Not Supported For VTPM " "cases). Now we have made it consistent and return 400 always when any " "operations/features are not implemented or supported." msgstr "" #: ../../:373 stable/ussuri>:1246 msgid "" "A fix for serious `bug 1862205`_ is provided which addresses both the " "performance aspect of schema migration 399, as well as the potential fallout " "for cases where this migration silently fails and leaves large numbers of " "instances hidden from view from the API." msgstr "" #: ../../:1670 msgid "" "A fix is made for `bug 1482040`_ where a request to rebuild a volume-backed " "server with a new image which is different than what is in the root volume " "will now fail with a `400 Bad Request` response. The compute API would " "previously return a `202 Accepted` response but the backend compute service " "does not replace the image in the root disk so the API behavior was always " "wrong and is now explicit about the failure." msgstr "" #: ../../:909 msgid "" "A list of valid vif models is extended for Virtuozzo hypervisor (virt_type=" "parallels) with VIRTIO, RTL8139 and E1000 models." msgstr "" #: ../../:831 msgid "" "A mandatory scheduling pre-filter has been added which will exclude disabled " "compute nodes where the related ``nova-compute`` service status is mirrored " "with a ``COMPUTE_STATUS_DISABLED`` trait on the compute node resource " "provider(s) for that service in Placement. See the `admin scheduler " "configuration docs`__ for details." msgstr "" #: ../../:851 msgid "" "A new 1.10 API microversion is added to the Placement REST API. This " "microversion adds support for the GET /allocation_candidates resource " "endpoint. This endpoint returns information about possible allocation " "requests that callers can make which meet a set of resource constraints " "supplied as query string parameters. Also returned is some inventory and " "capacity information for the resource providers involved in the allocation " "candidates." msgstr "" #: ../../:926 msgid "" "A new 1.11 API microversion is added to the Placement REST API. This adds " "the ``resource_providers/{rp_uuid}/allocations`` link to the ``links`` " "section of the response from ``GET /resource_providers``." msgstr "" #: ../../:969 msgid "" "A new 1.24 placement API microversion adds the ability to specify multiple " "`member_of` query parameters for the `GET /resource_providers` and `GET " "allocation_candidates` endpoints. When multiple `member_of` query parameters " "are received, the placement service will return resource providers that " "match all of the requested aggregate memberships. The `member_of=in:` format is still supported and continues to indicate an IN() " "operation for aggregate membership. Some examples for using the new " "functionality: Get all providers that are associated with BOTH agg1 and agg2:" " ?member_of=agg1&member_of=agg2 Get all providers that are associated with " "agg1 OR agg2: ?member_of=in:agg1,agg2 Get all providers that are associated " "with agg1 and ANY OF (agg2, agg3): ?member_of=agg1&member_of=in:agg2,agg3 " "Get all providers that are associated with ANY OF (agg1, agg2) AND are also " "associated with ANY OF (agg3, agg4): ?member_of=in:agg1,agg2&member_of=in:" "agg3,agg4" msgstr "" #: ../../:861 msgid "" "A new 2.41 microversion was added to the Compute API. Users specifying this " "microversion will now see the 'uuid' attribute of aggregates when calling " "the `os-aggregates` REST API endpoint." msgstr "" #: ../../:748 msgid "" "A new 2.47 microversion was added to the Compute API. Users specifying this " "microversion or later will see the \"flavor\" information displayed as a " "dict when displaying server details via the `servers` REST API endpoint. If " "the user is prevented by policy from indexing extra-specs, then the " "\"extra_specs\" field will not be included in the flavor information." msgstr "" #: ../../:528 msgid "" "A new PCI NUMA affinity policy is available. The ``hw:" "pci_numa_affinity_policy`` flavor extra spec and " "``hw_pci_numa_affinity_policy`` image metadata property now accept a " "``socket`` policy value. This value indicates that the PCI device must be " "affined to the same host socket as at least one of the guest NUMA nodes. For " "more information, see the `PCI Passthrough`__ guide." msgstr "" #: ../../:814 msgid "" "A new Placement API microversion 1.3 is added with support for filtering the " "list of resource providers to include only those resource providers which " "are members of any of the aggregates listed by uuid in the `member_of` query " "parameter. The parameter is used when making a `GET /resource_providers` " "request. The value of the parameter uses the `in:` syntax to provide a list " "of aggregate uuids as follows::" msgstr "" #: ../../:828 msgid "" "A new Placement API microversion 1.4 is added. Users may now query the " "Placement REST API for resource providers that have the ability to meet a " "set of requested resource amounts. The `GET /resource_providers` API call " "can have a \"resources\" query string parameter supplied that indicates the " "requested amounts of various resources that a provider must have the " "capacity to serve. The \"resources\" query string parameter takes the form:" msgstr "" #: ../../:357 msgid "" "A new ``[cinder]/debug`` configurable has been introduced to enable DEBUG " "logging for both the ``python-cinderclient`` and ``os-brick`` libraries " "independently to the rest of Nova." msgstr "" #: ../../:1404 msgid "" "A new ``[libvirt]/rbd_connect_timeout`` configuration option has been " "introduced to limit the time spent waiting when connecting to a RBD cluster " "via the RADOS API. This timeout currently defaults to 5 seconds." msgstr "" #: ../../:404 msgid "" "A new ``[workarounds]/report_ironic_standard_resource_class_inventory`` " "configuration option has been added." msgstr "" #: ../../:106 stable/train>:283 stable/ussuri>:305 #: unmaintained/victoria>:750 msgid "" "A new ``[workarounds]/reserve_disk_resource_for_image_cache`` config option " "was added to fix the `bug 1878024`_ where the images in the compute image " "cache overallocate the local disk. If this new config is set then the " "libvirt driver will reserve DISK_GB resources in placement based on the " "actual disk usage of the image cache." msgstr "" #: ../../:497 stable/queens>:1210 msgid "" "A new ``keystone`` config section is added so that you can set session link " "attributes for communicating with keystone. This allows the use of custom " "certificates to secure the link between Nova and Keystone." msgstr "" #: ../../:2084 msgid "" "A new ``nova-manage placement heal_allocations`` CLI has been added to help " "migrate users from the deprecated CachingScheduler. Starting in 16.0.0 " "(Pike), the nova-compute service no longer reports instance allocations to " "the Placement service because the FilterScheduler does that as part of " "scheduling. However, the CachingScheduler does not create the allocations in " "the Placement service, so any instances created using the CachingScheduler " "after Ocata will not have allocations in Placement. The new CLI allows " "operators using the CachingScheduler to find all instances in all cells " "which do not have allocations in Placement and create those allocations. The " "CLI will skip any instances that are undergoing a task state transition, so " "ideally this would be run when the API is down but it can be run, if " "necessary, while the API is up. For more details on CLI usage, see the man " "page entry:" msgstr "" #: ../../:1356 msgid "" "A new ``nova-manage`` command, ``placement audit``, has been added. This can " "be used to identify and optionally remove compute allocations in placement " "that are no longer referenced by existing instances or migrations. These " "orphaned allocations typically occur due to race conditions during instance " "migration or removal and will result in capacity issues if not addressed. " "For more details on CLI usage, see the man page entry: https://docs." "openstack.org/nova/latest/cli/nova-manage.html#placement" msgstr "" #: ../../:771 msgid "" "A new ``nova-status upgrade check`` CLI is provided for checking the " "readiness of a deployment when preparing to upgrade to the latest release. " "The tool is written to handle both fresh installs and upgrades from an " "earlier release, for example upgrading from the 14.0.3 Newton release. There " "can be multiple checks performed with varying degrees of success. More " "details on the command and how to interpret results are in the `nova-status " "man page`_." msgstr "" #: ../../:694 msgid "" "A new ``nova-status`` check has been introduced to help operators identify " "if any instances within their environment have ``hw_machine_type`` unset " "before they attempt to change the ``[libvirt]hw_machine_type`` configurable." msgstr "" #: ../../:623 msgid "" "A new ``traceback`` field has been added to each versioned instance " "notification. In an error notification this field contains the full " "traceback string of the exception which caused the error notification. See " "the `notification dev ref`_ for the sample file of ``instance.create.error`` " "as an example." msgstr "" #: ../../:153 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 "" #: ../../:149 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 "" #: ../../:847 msgid "" "A new administrator-only resource endpoint was added to the OpenStack " "Placement REST API for managing custom resource classes. Custom resource " "classes are specific to a deployment and represent types of quantitative " "resources that are not interoperable between OpenStack clouds. See the " "`Placement REST API Version History`_ documentation for usage details." msgstr "" #: ../../:424 stable/rocky>:1516 msgid "" "A new check is added to ``nova-status upgrade check`` which will scan all " "cells looking for ``nova-osapi_compute`` service versions which are from " "before Ocata and which may cause issues with how the compute API finds " "instances. This will result in a warning if:" msgstr "" #: ../../:1593 msgid "" "A new check is added to the ``nova-status upgrade check`` CLI to make sure " "request spec online migrations have been run per-cell. Missing request spec " "compatibility code is planned to be removed in the Stein release." msgstr "" #: ../../:437 stable/rocky>:1587 msgid "" "A new check is added to the ``nova-status upgrade check`` CLI which can " "assist with determining if ironic instances have had their embedded flavor " "migrated to use the corresponding ironic node custom resource class." msgstr "" #: ../../:211 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 "" #: ../../:45 stable/rocky>:66 stable/stein>:143 #: stable/train>:332 stable/ussuri>:1254 msgid "" "A new config option ``[neutron]http_retries`` is added which defaults to 3. " "It controls how many times to retry a Neutron API call in response to a HTTP " "connection failure. An example scenario where it will help is when a " "deployment is using HAProxy and connections get closed after idle time. If " "an incoming request tries to re-use a connection that is simultaneously " "being torn down, a HTTP connection failure will occur and previously Nova " "would fail the entire request. With retries, Nova can be more resilient in " "this scenario and continue the request if a retry succeeds. Refer to https://" "launchpad.net/bugs/1866937 for more details." msgstr "" #: ../../:633 msgid "" "A new configuration option ``[libvirt]/live_migration_timeout_action`` is " "added. This new option will have choices ``abort`` (default) or " "``force_complete``. This option will determine what actions will be taken " "against a VM after ``live_migration_completion_timeout`` expires. Currently " "nova just aborts the live migrate operation after completion timeout expires." " By default, we keep the same behavior of aborting after completion timeout. " "``force_complete`` will either pause the VM or trigger post-copy depending " "on if post copy is enabled and available." msgstr "" #: ../../:885 msgid "" "A new configuration option ``[quota]/recheck_quota`` has been added to " "recheck quota after resource creation to prevent allowing quota to be " "exceeded as a result of racing requests. It defaults to True, which makes it " "impossible for a user to exceed their quota. However, it will be possible " "for a REST API user to be rejected with an over quota 403 error response in " "the event of a collision close to reaching their quota limit, even if the " "user has enough quota available when they made the request. Operators may " "want to set the option to False to avoid additional load on the system if " "allowing quota to be exceeded because of racing requests is considered " "acceptable." msgstr "" #: ../../:898 msgid "" "A new configuration option ``reserved_host_cpus`` has been added for compute " "services. It helps operators to provide how many physical CPUs they would " "like to reserve for the hypervisor separately from what the instances use." msgstr "" #: ../../:686 msgid "" "A new configuration option is introduced, ``[placement]/policy_file``, which " "is used to configure the location of the placement policy file. By default, " "the ``placement-policy.yaml`` file may live alongside the nova policy file, " "e.g.:" msgstr "" #: ../../:401 msgid "" "A new configuration option is now available for supporting PCI devices that " "use the `VFIO-mdev`_ kernel framework and are stateless. Instead of using " "the ``VGPU`` resource class for both the inventory and the related " "allocations, the operator could ask to use another custom resource class for " "a specific mdev type by using the dynamic ``mdev_class``." msgstr "" #: ../../:386 msgid "" "A new configuration option, ``[DEFAULT]/max_concurrent_snapshots``, has been " "added. This allow operator to configure maximum concurrent snapshots on a " "compute host and prevent resource overuse related to snapshot." msgstr "" #: ../../:753 msgid "" "A new configuration option, ``[compute] cpu_dedicated_set``, has been added. " "This can be used to configure the host CPUs that should be used for ``PCPU`` " "inventory." msgstr "" #: ../../:382 stable/rocky>:2064 msgid "" "A new configuration option, ``[compute]/live_migration_wait_for_vif_plug``, " "has been added which can be used to configure compute services to wait for " "network interface plugging to complete on the destination host before " "starting the guest transfer on the source host during live migration." msgstr "" #: ../../:543 msgid "" "A new configuration option, ``[compute]/max_disk_devices_to_attach``, which " "defaults to ``-1`` (unlimited), has been added and can be used to configure " "the maximum number of disk devices allowed to attach to a single server, per " "compute host. Note that the number of disks supported by a server depends on " "the bus used. For example, the ``ide`` disk bus is limited to 4 attached " "devices." msgstr "" #: ../../:759 msgid "" "A new configuration option, ``[workarounds] disable_fallback_pcpu_query``, " "has been added. When creating or moving pinned instances, the scheduler will " "attempt to provide a ``PCPU``-based allocation, but can also fallback to a " "legacy ``VCPU``-based allocation. This fallback behavior is enabled by " "default to ensure it is possible to upgrade without having to modify compute " "node configuration but it results in an additional request for allocation " "candidates from placement. This can have a slight performance impact and is " "unnecessary on new or upgraded deployments where the compute nodes have been " "correctly configured to report ``PCPU`` inventory. The ``[workarounds] " "disable_fallback_pcpu_query`` config option can be used to disable this " "fallback allocation candidate request, meaning only ``PCPU``-based " "allocation candidates will be retrieved." msgstr "" #: ../../:488 msgid "" "A new framework supporting hardware-based encryption of guest memory to " "protect users against attackers or rogue administrators snooping on their " "workloads when using the libvirt compute driver. Currently only has basic " "support for `AMD SEV (Secure Encrypted Virtualization) `_." msgstr "" #: ../../:247 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 "" #: ../../:190 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 "" #: ../../:536 msgid "" "A new image metadata prefilter has been added to allow translation of " "hypervisor-specific device model requests to standard traits. When this " "feature is enabled, nova is able to utilize placement to select hosts that " "are capable of emulating the requested devices, avoiding hosts that could " "not support the request. This feature is currently supported by the libvirt " "driver and can be enabled by configuring the ``[scheduler]/" "image_metadata_prefilter`` to ``True`` in the controller ``nova.conf``." msgstr "" #: ../../:437 msgid "" "A new image metadata property, ``hw_input_bus``, has been added. This allows " "you to specify the bus used for input devices - a pointer and keyboard - " "which are attached to the instance when graphics are enabled on compute " "nodes using the libvirt virt driver. Two values are currently accepted: " "``usb`` and ``virtio``. This image metadata property effectively replaced " "the ``hw_pointer_model`` image metadata property, which is nontheless " "retained for backwards compatibility purposes." msgstr "" #: ../../:14 current 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 "" #: ../../:147 stable/queens>:288 stable/rocky>:1558 msgid "" "A new online data migration has been added to populate missing instance." "availability_zone values for instances older than Pike whose " "availability_zone was not specified during boot time. This can be run during " "the normal ``nova-manage db online_data_migrations`` routine. This fixes " "`Bug 1768876`_" msgstr "" #: ../../:593 msgid "" "A new option ``disabled`` has been added to nova-manage cell_v2 create_cell " "command by which users can create pre-disabled cells. Hence unless such " "cells are enabled, no VMs will be spawned on the hosts in these cells." msgstr "" #: ../../:1339 msgid "" "A new pair of ``ssl_ciphers`` and ``ssl_minimum_version`` configuration " "options have been introduced for use by the ``nova-novncproxy``, ``nova-" "serialproxy``, and ``nova-spicehtml5proxy`` services. These new options " "allow one to configure the allowed TLS ciphers and minimum protocol version " "to enforce for incoming client connections to the proxy services." msgstr "" #: ../../:781 msgid "" "A new param ``key_name`` was added to the instance rebuild API (v2.54), then " "it is able to reset instance key pair. It is worth noting that users within " "the same project are able to rebuild other user's instances in that project " "with a new keypair. If set ``key_name`` to None in API body, nova will unset " "the keypair of instance during rebuild." msgstr "" #: ../../:865 msgid "" "A new policy rule ``os_compute_api:os-flavor-manage:update`` is added to " "control access to the ``PUT /flavors/{flavor_id}`` API." msgstr "" #: ../../:498 msgid "" "A new policy rule ``os_compute_api:servers:allow_all_filters`` has been " "added to control whether a user can use all filters when listing servers." msgstr "" #: ../../:519 msgid "" "A new policy rule ``os_compute_api:servers:show:host_status:unknown-only`` " "has been added to control whether a user can view a server host status of " "``UNKNOWN`` in the following APIs:" msgstr "" #: ../../:98 stable/pike>:163 #: stable/queens>:304 stable/rocky>:1928 msgid "" "A new policy rule, ``os_compute_api:servers:create:zero_disk_flavor``, has " "been introduced which defaults to ``rule:admin_or_owner`` for backward " "compatibility, but can be configured to make the compute API enforce that " "server create requests using a flavor with zero root disk must be volume-" "backed or fail with a ``403 HTTPForbidden`` error." msgstr "" #: ../../:1398 msgid "" "A new request_log middleware is created to log REST HTTP requests even if " "Nova API is not running under eventlet.wsgi. Because this is an api-paste." "ini change, you will need to manually update your api-paste.ini with the one " "from the release to get this functionality. The new request logs will only " "emit when it is detected that nova-api is not running under eventlet, and " "will include the microversion of the request in addition to all the " "previously logged information." msgstr "" #: ../../:549 msgid "A new zVM virt driver is now available." msgstr "" #: ../../:1577 msgid "" "A number of `nova-manage` commands have been deprecated. The commands, along " "with the reasons for their deprecation, are listed below:" msgstr "" #: ../../:348 msgid "" "A number of commands have been managed to ``nova-manage`` to help update " "stale volume attachment connection info for a given volume and instance." msgstr "" #: ../../:524 msgid "" "A number of scheduler-related config options were renamed during the 15.0.0 " "(Ocata) release. The deprecated aliases have now been removed. These are:" msgstr "" #: ../../:414 msgid "" "A serial number is extracted from PCI VPD of network devices (if present) " "and is sent to Neutron in port updates." msgstr "" #: ../../:1144 msgid "" "A server is created without an availability zone specified but with pre-" "existing volume block device mappings" msgstr "" #: ../../:273 stable/rocky>:1447 msgid "" "A simple warning will reference the above if this issue is encountered by " "Nova however operators of the environment will still need to update Libvirt " "to a version where this issue has been fixed to resolve the issue." msgstr "" #: ../../:1360 msgid "" "A sys-admin privsep daemon has been added and needs to be included in your " "rootwrap configuration." msgstr "" #: ../../:14 stable/ussuri>:60 #: unmaintained/victoria>:122 unmaintained/wallaby>:314 unmaintained/xena>:616 msgid "" "A vulnerability in the console proxies (novnc, serial, spice) that allowed " "open redirection has been `patched`_. The novnc, serial, and spice console " "proxies are implemented as websockify servers and the request handler " "inherits from the python standard SimpleHTTPRequestHandler. There is a " "`known issue`_ in the SimpleHTTPRequestHandler which allows open redirects " "by way of URLs in the following format::" msgstr "" #: ../../:436 unmaintained/xena>:136 #: unmaintained/yoga>:194 unmaintained/zed>:141 msgid "" "A workaround has been added to the libvirt driver to catch and pass " "migrations that were previously failing with the error:" msgstr "" #: ../../:568 msgid "" "AArch64 architecture is supported by Nova with libvirt min version 3.6.0. " "See the Nova `support matrix`_ for more details." msgstr "" #: ../../:301 stable/queens>:1200 msgid "" "AArch64 currently lacks ``host-model`` support because neither libvirt nor " "QEMU are able to tell what the host CPU model exactly is and there is no CPU " "description code for ARM(64) at this point." msgstr "" #: ../../:1831 msgid "" "API calls to ``/os-quota-sets`` and flavor access will now attempt to " "validate the project_id being operated on with Keystone. If the user token " "has enough permissions to perform ``GET /v3/projects/{project_id}``, and the " "Keystone project does not exist, a 400 BadRequest will be returned to " "prevent invalid project data from being put in the Nova database. This fixes " "an effective silent error where the project_id would be stored even if it " "was not a valid project_id in the system." msgstr "" #: ../../:989 msgid "" "API configuration options have been moved to the 'api' group. They should no " "longer be included in the 'DEFAULT' group. Options affected by this change:" msgstr "" #: ../../:722 msgid "API limitations:" msgstr "" #: ../../:717 msgid "" "API microversion 2.72 adds support for creating servers with neutron ports " "that has resource request, e.g. neutron ports with `QoS minimum bandwidth " "rule`_. Deleting servers with such ports have already been handled properly " "as well as detaching these type of ports." msgstr "" #: ../../:538 msgid "" "API microversion 2.74 adds support for specifying optional ``host`` and/or " "``hypervisor_hostname`` parameters in the request body of ``POST /servers``. " "These request a specific destination host/node to boot the requested server. " "These parameters are mutually exclusive with the special " "``availability_zone`` format of ``zone:host:node``. Unlike ``zone:host:" "node``, the ``host`` and/or ``hypervisor_hostname`` parameters still allow " "scheduler filters to be run. If the requested host/node is unavailable or " "otherwise unsuitable, earlier failure will be raised. There will be also a " "new policy named ``compute:servers:create:requested_destination``. By " "default, it can be specified by administrators only." msgstr "" #: ../../:1023 msgid "API restrictions:" msgstr "" #: ../../:1551 msgid "Accept this change along with the performance penalty" msgstr "" #: ../../:460 msgid "Add Cyborg shelve/unshelve support." msgstr "" #: ../../:406 msgid "" "Add VPD capability parsing support when a PCI VPD capability is exposed via " "node device XML in Libvirt. The XML data from Libvirt is parsed and " "formatted into PCI device JSON dict that is sent to Nova API and is stored " "in the extra_info column of a PciDevice." msgstr "" #: ../../:562 msgid "" "Add ``--cell`` option to the ``nova-manage placement heal_allocations`` " "command. This option allows healing instance allocations within a specific " "cell." msgstr "" #: ../../:369 msgid "" "Add ``--force`` option to the ``nova-manage placement heal_allocations`` " "command to forcefully heal allocations for a specific instance." msgstr "" #: ../../:587 msgid "" "Add ``CPUWeigher`` weigher. This can be used to spread (default) or pack " "workloads on hosts based on their vCPU usage. This can be configured using " "the ``[filter_scheduler] cpu_weight_multiplier`` configuration option." msgstr "" #: ../../:670 msgid "" "Add ``PCIWeigher`` weigher. This can be used to ensure non-PCI instances " "don't occupy resources on hosts with PCI devices. This can be configured " "using the ``[filter_scheduler] pci_weight_multiplier`` configuration option." msgstr "" #: ../../:756 msgid "" "Add ``policy`` and ``rules`` fields in the request of POST ``/os-server-" "groups``. The ``policy`` represents the name of policy. The ``rules`` field, " "which is a dict, can be applied to the policy, which currently only supports " "``max_server_per_host`` for ``anti-affinity`` policy." msgstr "" #: ../../:719 msgid "" "Add ``required`` query parameter to the ``GET /allocation_candidates`` API " "in new placement microversion 1.17. The parameter accepts a list of traits " "separated by ``,``, which is used to further limit the list of allocation " "requests to resource providers that have the capacity to fulfill the " "requested resources AND *collectively* have all of the required traits " "associated with them. In the same microversion, the provider summary " "includes the traits associated with each provider." msgstr "" #: ../../:829 msgid "" "Add a ``nova-manage cell_v2 list_hosts`` command for listing hosts in one or " "all v2 cells." msgstr "" #: ../../:1393 msgid "" "Add a new option of ``image_handler`` in the ``xenapi`` section for " "configuring the image handler plugin which will be used by XenServer to " "download or upload images. The value for this option should be a short name " "representing a supported handler." msgstr "" #: ../../:759 msgid "" "Add granularity to the ``os_compute_api:os-flavor-manage`` policy with the " "addition of distinct actions for create and delete:" msgstr "" #: ../../:276 msgid "" "Add new ``hw:locked_memory`` extra spec and ``hw_locked_memory`` image " "property to lock memory on libvirt guest. Locking memory marks the guest " "memory allocations as unmovable and unswappable. ``hw:locked_memory`` extra " "spec and ``hw_locked_memory`` image property accept boolean values in string " "format like 'Yes' or 'false' value. Exception `LockMemoryForbidden` will " "raise, if you set lock memory value but not set either flavor extra spec " "``hw:mem_page_size`` or image property ``hw_mem_page_size``, so we can " "ensure that the scheduler can actually account for this correctly and " "prevent out of memory events." msgstr "" #: ../../:729 msgid "" "Add pagination support and ``changes-since`` filter for os-instance-actions " "API. Users can now use ``limit`` and ``marker`` to perform paginated query " "when listing instance actions. Users can also use ``changes-since`` filter " "to filter the results based on the last time the instance action was updated." "" msgstr "" #: ../../:739 msgid "" "Add pagination support and ``changes-since`` filter for os-migrations API. " "Users can now use ``limit`` and ``marker`` to perform paginate query when " "listing migrations." msgstr "" #: ../../:653 msgid "" "Add support for LAN9118 as a valid nic for hw_vif_model property in qemu." msgstr "" #: ../../:720 msgid "" "Add support for configuring the ``rx_queue_size`` and ``tx_queue_size`` " "options in the QEMU virtio-net driver by way of nova.conf. Only supported " "for vhost/vhostuser interfaces" msgstr "" #: ../../:808 msgid "" "Add support for graceful shutdown of VMware instances. The timeout parameter " "of the power_off method is now considered by the VMware driver. If you " "specify a timeout greater than 0, the driver calls the appropriate soft " "shutdown method of the VMware API and only forces a hard shutdown if the " "soft shutdown did not succeed before the timeout is reached." msgstr "" #: ../../:158 stable/stein>:361 stable/train>:1358 msgid "" "Add support for noVNC >= v1.1.0 for VNC consoles. Prior to this fix, VNC " "console token validation always failed regardless of actual token validity " "with noVNC >= v1.1.0. See https://bugs.launchpad.net/nova/+bug/1822676 for " "more details." msgstr "" #: ../../:737 msgid "" "Add support for reporting CPU traits to Placement in libvirt driver. For " "more detail, see https://specs.openstack.org/openstack/nova-specs/specs/" "rocky/approved/report-cpu-features-as-traits.html and https://docs.openstack." "org/nova/latest/user/support-matrix.html." msgstr "" #: ../../:444 msgid "" "Add support for smartnic via Cyborg device profiles in Neutron ports with " "vnic type ``accelerator-direct``. When such port is used Cyborg will manage " "the smartnic and Nova will pass through the smartnic VF to the server. Note " "that while vnic type ``accelerator-direct-physical`` also exists in Neutron " "it is not yet supported by Nova and the server create request will fail with " "such port." msgstr "" #: ../../:437 msgid "" "Add support for the ``bochs`` libvirt video model. This is a legacy-free " "video model that is best suited for UEFI guests. In limited cases (e.g. if " "the guest does not depend on direct VGA hardware access), it can be useable " "for BIOS guests as well." msgstr "" #: ../../:135 stable/ussuri>:195 #: unmaintained/victoria>:726 msgid "" "Add support for the ``hw:hide_hypervisor_id`` extra spec. This is an alias " "for the ``hide_hypervisor_id`` extra spec, which was not compatible with the " "``AggregateInstanceExtraSpecsFilter`` scheduler filter. See `bug 1841932 " "`_ for more details." msgstr "" #: ../../:651 msgid "" "Add support, in a new placement microversion 1.21, for the ``member_of`` " "query parameter, representing one or more aggregate UUIDs. When supplied, it " "will filter the returned allocation candidates to only those " "resource_providers that are associated with (\"members of\") the specified " "aggregate(s). This parameter can have a value of either a single aggregate " "UUID, or a comma-separated list of aggregate UUIDs. When specifying more " "than one aggregate, a resource provider needs to be associated with at least " "one of the aggregates in order to be included; it does not have to be " "associated with all of them. Because of this, the list of UUIDs must be " "prefixed with ``in:`` to represent the logical ``OR`` of the selection." msgstr "" #: ../../:708 msgid "" "Add support, in new placement microversion 1.16, for a ``limit`` query " "parameter when making a ``GET /allocation_candidates`` request. The " "parameter accepts an integer value, `N`, which limits the number of " "candidates returned. A new configuration item ``[placement]/" "randomize_allocation_candidates``, defaulting to `False`, controls how the " "limited results are chosen. If `True`, a random sampling of the entire " "result set is taken, otherwise the first N results are returned." msgstr "" #: ../../:425 msgid "" "Add the ``mixed`` instance CPU allocation policy for instance mixing with " "both ``PCPU`` and ``VCPU`` resources. This is useful for applications that " "wish to schedule the CPU intensive workload on the ``PCPU`` and the other " "workloads on ``VCPU``. The mixed policy avoids the necessity of making all " "instance CPUs to be pinned CPUs, as a result, reduces the consuption of " "pinned CPUs and increases the instance density." msgstr "" #: ../../:405 msgid "" "Add the ability to use ``vmxnet3`` NIC on a host using the QEMU/KVM driver. " "This allows the migration of an ESXi VM to QEMU/KVM, without any driver " "changes. ``vmxnet3`` comes with better performance and lower latency " "comparing to an emulated driver like ``e1000``." msgstr "" #: ../../:439 msgid "" "Add the extra spec ``hw:cpu_dedicated_mask`` to set the pinned CPUs for the " "mixed instance. This is a core mask and can be used to include or exclude " "CPUs. Any core not included or explicitly excluded is treated as a shared " "CPU." msgstr "" #: ../../:472 msgid "" "Added IP addresses to the metadata in libvirt XML. If an instance has more " "than one IP address, enumerate those IP addresses. The port attach or detach " "is performed dynamically after the creation of the instance. Every time " "there is a change, it is reflected in the contents of the XML." msgstr "" #: ../../:627 msgid "" "Added a new ``locked_reason`` option in microversion 2.73 to the ``POST /" "servers/{server_id}/action`` request where the action is lock. It enables " "the user to specify a reason when locking a server. This information will be " "exposed through the response of the following APIs:" msgstr "" #: ../../:1082 msgid "" "Added a new ``unique`` choice to the ``[libvirt]/sysinfo_serial`` " "configuration which if set will result in the guest serial number being set " "to ``instance.uuid``. This is now the default value of the ``[libvirt]/" "sysinfo_serial`` config option and is the recommended choice since it " "ensures the guest serial is the same even if the instance is migrated " "between hosts." msgstr "" #: ../../:1046 msgid "" "Added a new boolean configuration option " "``[filter_scheduler]shuffle_best_same_weighed_hosts`` (default is False)." msgstr "" #: ../../:166 unmaintained/xena>:210 #: unmaintained/yoga>:305 msgid "" "Added a new configuration option ``[workarounds]/" "enable_qemu_monitor_announce_self`` that when enabled causes the Libvirt " "driver to send a announce_self QEMU monitor command post live-migration. " "Please see `bug 1815989 `_ for " "more details. Please note that this causes the domain to be considered " "tainted by libvirt." msgstr "" #: ../../:891 msgid "" "Added a new flavor extra_spec, ``hide_hypervisor_id``, which hides the " "hypervisor signature for the guest when true ('kvm' won't appear in " "``lscpu``). This acts exactly like and in parallel to the image property " "``img_hide_hypervisor_id`` and is useful for running the nvidia drivers in " "the guest. Currently, this is only supported in the libvirt driver." msgstr "" #: ../../:1110 msgid "" "Added a number of new configuration options to the ``[vnc]`` group, which " "together allow for the configuration of authentication used between the " "*nova-novncproxy* server and the compute node VNC server." msgstr "" #: ../../:1261 msgid "" "Added ability to extend an attached ScaleIO volume when using the libvirt " "compute driver." msgstr "" #: ../../:702 msgid "" "Added boot order support in the Hyper-V driver. The HyperVDriver can now set " "the requested boot order for instances that are Generation 2 VMs (the given " "image has the property \"hw_machine_type=hyperv-gen2\"). For Generation 1 " "VMs, the spawned VM's boot order is changed only if the given image is an " "ISO, booting from ISO first." msgstr "" #: ../../:697 msgid "" "Added configuration option ``[api]/local_metadata_per_cell`` to allow users " "to run Nova metadata API service per cell. Doing this could provide " "performance improvement and data isolation in a multi-cell deployment. But " "it has some caveats, see the `Metadata api service in cells v2 layout`_ for " "more details." msgstr "" #: ../../:793 msgid "" "Added microversion v2.40 which introduces pagination support for usage with " "the help of new optional parameters 'limit' and 'marker'. If 'limit' isn't " "provided, it will default to the configurable max limit which is currently " "1000." msgstr "" #: ../../:701 msgid "" "Added microversion v2.48 which standardize VM diagnostics response. It has a " "set of fields which each hypervisor will try to fill. If a hypervisor driver " "is unable to provide a specific field then this field will be reported as " "'None'." msgstr "" #: ../../:101 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 "" #: ../../:737 msgid "Added pagination support for migrations, there are four changes:" msgstr "" #: ../../:412 msgid "" "Added params ``[libvirt]/rbd_destroy_volume_retries``, defaulting to 12, and " "``[libvirt]/rbd_destroy_volume_retry_interval``, defaulting to 5, that Nova " "will use when trying to remove a volume from Ceph in a retry loop that " "combines these parameters together. Thus, maximum elapsing time is by " "default 60 seconds." msgstr "" #: ../../:714 msgid "" "Added support for Hyper-V VMs with UEFI Secure Boot enabled. In order to " "create such VMs, there are a couple of things to consider:" msgstr "" #: ../../:923 msgid "" "Added support for Keystone middleware feature for interaction of Nova with " "the Glance API. With this support, if service token is sent along with the " "user token, then the expiration of user token will be ignored. In order to " "use this functionality a service user needs to be created first. Add the " "service user configurations in ``nova.conf`` under ``service_user`` group " "and set ``send_service_user_token`` flag to ``True``." msgstr "" #: ../../:882 msgid "" "Added support for Keystone middleware feature where if service token is sent " "along with the user token, then it will ignore the expiration of user token. " "This helps deal with issues of user tokens expiring during long running " "operations, such as live-migration where nova tries to access Cinder and " "Neutron at the end of the operation using the user token that has expired. " "In order to use this functionality a service user needs to be created. Add " "service user configurations in ``nova.conf`` under ``service_user`` group " "and set ``send_service_user_token`` flag to ``True``. The minimum Keytone " "API version 3.8 and Keystone middleware version 4.12.0 is required to use " "this functionality. This only currently works with Nova - Cinder and Nova - " "Neutron API interactions." msgstr "" #: ../../:997 msgid "" "Added support for PCI device NUMA affinity policies. These allow you to " "configure how strict your NUMA affinity should be on a per-device basis or, " "more specifically, per device alias. These are configured as part of the " "``[pci]alias`` configuration option(s)." msgstr "" #: ../../:300 msgid "" "Added support for VMware VStorageObject based volumes in VMware vCenter " "driver. vSphere version 6.5 is required." msgstr "" #: ../../:733 msgid "Added support for ``nvmeof`` type volumes to the libvirt driver." msgstr "" #: ../../:356 msgid "" "Added support for `evacuate, live migrate and unshelve servers with minimum " "bandwidth guarantees`__." msgstr "" #: ../../:844 msgid "" "Added support for forbidden traits to the scheduler. A flavor extra spec is " "extended to support specifying the forbidden traits. The syntax of extra " "spec is ``trait:=forbidden``, for example:" msgstr "" #: ../../:865 msgid "" "Added support for granular resource and traits requests to the scheduler. A " "flavor extra spec is extended to support specifying numbered groupings of " "resources and required/forbidden traits. A ``resources`` key with a " "positive integer suffix (e.g. ``resources42:VCPU``) will be logically " "associated with ``trait`` keys with the same suffix (e.g. ``trait42:" "HW_CPU_X86_AVX``). The resources and required/forbidden traits in that group " "will be satisfied by the same resource provider on the host selected by the " "scheduler. When more than one numbered grouping is supplied, the " "``group_policy`` extra spec is required to indicate how the groups should " "interact. With ``group_policy=none``, separate groupings - numbered or " "unnumbered - may or may not be satisfied by the same provider. With " "``group_policy=isolate``, numbered groups are guaranteed to be satisfied by " "*different* providers - though there may still be overlap with the " "unnumbered group." msgstr "" #: ../../:574 msgid "" "Added support for instance-level PCI NUMA policies using the ``hw:" "pci_numa_affinity_policy`` flavor extra spec and " "``hw_pci_numa_affinity_policy`` image metadata property. These apply to both " "PCI passthrough and SR-IOV devices, unlike host-level PCI NUMA policies " "configured via the ``alias`` key of the ``[pci] alias`` config option. See " "the `VM Scoped SR-IOV NUMA Affinity`_ spec for more info." msgstr "" #: ../../:459 msgid "" "Added support for off-path networking backends where devices exposed to the " "hypervisor host are managed remotely (which is the case, for example, with " "various SmartNIC DPU devices). ``VNIC_TYPE_REMOTE_MANAGED`` ports can now be " "added to Nova instances as soon as all compute nodes are upgraded to the new " "compute service version. In order to use this feature, VF PCI/PCIe devices " "need to be tagged as ``remote_managed: \"true\"` in the Nova config in the " "``passthrough_whitelist`` option." msgstr "" #: ../../:425 msgid "" "Added support for ports with minimum guaranteed packet rate QoS policy rules." " Support is provided for all server operations including cold migration, " "resize, interface attach/detach, etc. This feature required adding support " "for the ``port-resource-request-groups`` neutron API extension, as ports " "with such a QoS policy will have multiple rules, each requesting resources. " "For more details see the `admin guide`_." msgstr "" #: ../../:216 msgid "" "Added support for rebuilding a volume-backed instance with a different image." " This is achieved by reimaging the boot volume i.e. writing new image on the " "boot volume at cinder side. Previously rebuilding volume-backed instances " "with same image was possible but this feature allows rebuilding volume-" "backed instances with a different image than the existing one in the boot " "volume. This is supported starting from API microversion 2.93." msgstr "" #: ../../:790 msgid "" "Added support for service create and destroy versioned notifications. The " "``service.create`` notification will be emitted after the service is created " "(so the uuid is available) and also send the ``service.delete`` notification " "after the service is deleted." msgstr "" #: ../../:535 msgid "" "Added support for the High Precision Event Timer (HPET) for x86 guests in " "the libvirt driver when image property ``hypervisor_type=qemu`` is set. The " "timer can be set by setting a ``hw_time_hpet=True`` image property key/value " "pair. By default HPET remains turned off. When it is turned on the HPET is " "activated in libvirt." msgstr "" #: ../../:633 msgid "Added the StorPool libvirt volume attachment driver." msgstr "" #: ../../:670 msgid "" "Added the ability to allow users to use ``Aggregate``'s ``metadata`` to " "override the global config options for weights to achieve more fine-grained " "control over resource weights." msgstr "" #: ../../:976 msgid "" "Added traits support to the scheduler. A new flavor extra spec is added to " "support specifying the required traits. The syntax of extra spec is ``trait:" "=required``, for example:" msgstr "" #: ../../:579 msgid "" "Added validation for image machine type property. Different APIs which uses " "machine type for server creation, resize or rebuild will raise " "InvalidMachineType exception with message \"provided machine type is not " "supported by host\" and suggest possible/valid machine types in compute logs." " For more details see: `bug 1933097`_" msgstr "" #: ../../:575 msgid "" "Adding aarch64 to the list of supported architectures for NUMA and hugepage " "features. This requires libvirt>=1.2.7 for NUMA, libvirt>=1.2.8 for hugepage " "and qemu v2.1.0 for both." msgstr "" #: ../../:1937 msgid "" "Additional availability zone check is added to the volume attach flow, which " "results in an availability zone check when an instance gets unshelved. In " "case the deployment is not sensitive to availability zones and not using the " "AvailabilityZoneFilter scheduler filter the current default settings " "(cross_az_attach=True) are allowing to perform unshelve the same way as " "before this change without additional configuration." msgstr "" #: ../../:960 msgid "" "Additionally, where virtual machines already exist that were created using " "earlier versions of Libvirt interactions with these virtual machines via " "Nova or other utilities (e.g. `virsh`) may result in similar errors." msgstr "" #: ../../:79 stable/train>:239 stable/ussuri>:258 #: unmaintained/victoria>:796 msgid "" "Addressed an issue that prevented instances using multiqueue feature from " "being created successfully when their vif_type is TAP." msgstr "" #: ../../:85 unmaintained/victoria>:147 #: unmaintained/wallaby>:285 unmaintained/xena>:701 msgid "" "Addressed an issue that prevented instances with 1 vcpu using multiqueue " "feature from being created successfully when their vif_type is TAP." msgstr "" #: ../../:1854 msgid "" "Adds ``sata`` as a valid disk bus for qemu and kvm hypervisors. Setting the " "``hw_disk_bus`` custom property on glance images allows for selecting the " "type of disk bus e.g. VIRTIO/IDE/SCSI. Some Linux (custom) images require " "use of SATA bus rather than any other that seem to be allowed." msgstr "" #: ../../:278 stable/stein>:919 msgid "" "Adds a ``use_cache`` parameter to the virt driver ``get_info`` method. Out " "of tree drivers should add support for this parameter." msgstr "" #: ../../:779 msgid "" "Adds a new ``generation`` column to the consumers table. This value is " "incremented every time allocations are made for a consumer. The new " "placement microversion 1.28 requires that all ``POST /allocations`` and " "``PUT /allocations/{consumer_uuid}`` requests now include the " "``consumer_generation`` parameter to ensure that if two processes are " "allocating resources for the same consumer, the second one to complete " "doesn't overwrite the first. If there is a mismatch between the " "``consumer_generation`` in the request and the current value in the " "database, the allocation will fail, and a 409 Conflict response will be " "returned. The calling process must then get the allocations for that " "consumer by calling ``GET /allocations/{consumer}``. That response will now " "contain, in addition to the allocations, the current generation value for " "that consumer. Depending on the use case, the calling process may error; or " "it may wish to combine or replace the existing allocations with the ones it " "is trying to post, and re-submit with the current consumer_generation." msgstr "" #: ../../:643 msgid "" "Adds interface attach/detach support to baremetal nodes using ironic virt " "driver. Note that the instance info cache update relies on getting a " "``network-changed`` event from neutron, or on the periodic task healing the " "instance info cache, both of which are asynchronous. This means that nova's " "cached network information (which is what is sent e.g. in the ``GET /" "servers`` responses) may not be up to date immediately after the attachment " "or detachment." msgstr "" #: ../../:741 msgid "" "Adds serial console support to Ironic driver. Nova now supports serial " "console to Ironic bare metals for Ironic ``socat`` console driver. In order " "to use this feature, serial console must be configured in Nova and the " "Ironic ``socat`` console driver must be used and configured in Ironic. " "Ironic serial console configuration is documented in http://docs.openstack." "org/developer/ironic/deploy/console.html." msgstr "" #: ../../:643 msgid "" "Adds soft power off support to Ironic virt driver. This feature requires the " "Ironic service to support API version 1.27 or later. It also requires python-" "ironicclient >= 1.10.0." msgstr "" #: ../../:639 msgid "" "Adds soft reboot support to Ironic virt driver. If hardware driver in Ironic " "doesn't support soft reboot, hard reboot is tried. This feature requires the " "Ironic service to support API version 1.27 or later. It also requires python-" "ironicclient >= 1.10.0." msgstr "" #: ../../:919 msgid "" "Adds support for applying tags when creating a server. The tag schema is the " "same as in the 2.26 microversion." msgstr "" #: ../../:509 msgid "" "Adds support for extending RBD attached volumes using the libvirt network " "volume driver." msgstr "" #: ../../:906 msgid "" "Adds support to OVS vif type with direct port (SR-IOV). In order to use this " "OVS acceleration mode, ``openvswitch`` 2.8.0 and 'Linux Kernel' 4.8 are " "required. This feature allows control of an SR-IOV virtual function (VF) via " "OpenFlow control plane and gain improved performance of 'Open vSwitch'. " "Please note that in Pike release we can't differentiate between SR-IOV " "hardware and OVS offloaded on the same host. This limitation should be " "resolved when the enable-sriov-nic-features will be completed. Until then " "operators can use host aggregates to ensure that they can schedule instances " "on specific hosts based on hardware." msgstr "" #: ../../:635 msgid "" "Adds trigger crash dump support to ironic virt driver. This feature requires " "the Ironic service to support API version 1.29 or later. It also requires " "python-ironicclient >= 1.11.0." msgstr "" #: ../../:727 msgid "" "Adjustable RX queue sizes requires QEMU 2.7.0, and libvirt 2.3.0 (or newer) " "Adjustable TX queue sizes requires QEMU 2.10.0, and libvirt 3.7.0 (or newer)" msgstr "" #: ../../:180 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 databse." msgstr "" #: ../../:464 msgid "" "After shelve offload the ARQs of the instance will be feered in Cyborg." msgstr "" #: ../../:462 msgid "After shelve the ARQs are still kept bound to the instance." msgstr "" #: ../../:694 msgid "" "After the compute nodes have been configured, the nova-api, nova-scheduler, " "and the nova-compute services will have to be configured next [2]." msgstr "" #: ../../:617 msgid "Aggregatefilter, AggregateRAMFilter, AggregateDiskFilter" msgstr "" #: ../../:1419 msgid "" "Aliases are provided but these are marked as deprecated and will be removed " "in the next release of nova." msgstr "" #: ../../:1831 msgid "All *nova-compute* services are upgraded" msgstr "" #: ../../:478 msgid "" "All APIs except deprecated APIs were modified to implement ``scope_type`` " "and use new defaults in 21.0.0 (Ussuri). The remaining APIs have now been " "updated." msgstr "" #: ../../:124 stable/2023.2>:267 #: unmaintained/wallaby>:17 unmaintained/xena>:17 unmaintained/yoga>:61 #: unmaintained/zed>:74 msgid "" "All Nova configuration files must configure the ``[service_user]`` section " "as described in the `documentation`__." msgstr "" #: ../../:985 msgid "All compute and conductor services are upgraded to Train code." msgstr "" #: ../../:783 msgid "" "All deployments will function as a single-cell environment. Multiple v2 " "cells are technically possible, but should only be used for testing as many " "other things will not work across cell boundaries yet. For details on cells " "v2 and the setup required for Nova with cells v2, see the cells " "documentation. [1]_" msgstr "" #: ../../:1038 msgid "" "All general scheduler configuration options have been added to the " "``scheduler`` group." msgstr "" #: ../../:187 msgid "" "All lifecycle actions are now fully supported for `instances with vDPA " "ports`__, including vDPA hot-plug live migration, suspend and attach/detach." msgstr "" #: ../../:1801 msgid "" "All of the existing consoles have expired. For example, if a deployment has " "configured a token TTL of one hour, the operator may disable the " "``[workarounds]/enable_consoleauth`` option, one hour after deploying the " "new code." msgstr "" #: ../../:672 msgid "" "All other resources classes requested via flavors are also now supported as " "unified limits. Note that nova configuration is ignored, as the default " "limits come from the limits registered for the Nova endpoint in Keystone." msgstr "" #: ../../:1029 msgid "" "All pci configuration options have been added to the 'pci' group. They " "should no longer be included in the 'DEFAULT' group. These options are as " "below:" msgstr "" #: ../../:700 msgid "" "All placement policy rules are defined in code so by default no extra " "configuration is required and the default rules will be used on start of the " "placement service." msgstr "" #: ../../:1305 msgid "" "All policy rules with the following naming scheme have been removed: " "``os_compute_api:{extension_alias}:discoverable`` These policy rules were " "used to hide an enabled extension from the list active API extensions API. " "Given it is no longer possible to disable any API extensions, it makes no " "sense to have the option to hide the fact an API extension is active. As " "such, all these policy rules have been removed." msgstr "" #: ../../:676 msgid "" "All previous quotas other than ``cores``, ``instances`` and ``ram`` are " "still enforced, but the limit can only be changed globally in Keystone as " "registered limits. There are no per project or per user overrides possible." msgstr "" #: ../../:670 msgid "" "All the policies except the deprecated APIs policy have been changed to " "implement the ``scope_type`` and new defaults. Deprecated APIs policy will " "be moved to ``scope_type`` and new defaults in the next release." msgstr "" #: ../../:231 msgid "" "Allow 2 new special characters: '@' and '.' (dot), in addition to the " "existing constraints of ``[a-z][A-Z][0-9][_- ]``" msgstr "" #: ../../:429 msgid "" "Allow the following filter parameters for ``GET /servers/detail`` and ``GET /" "servers`` for non-admin in microversion 2.83:" msgstr "" #: ../../:104 stable/pike>:169 #: stable/queens>:310 stable/rocky>:1934 msgid "" "Allowing image-backed servers with a zero root disk flavor can be " "potentially hazardous if users are allowed to upload their own images, since " "an instance created with a zero root disk flavor gets its size from the " "image, which can be unexpectedly large and exhaust local disk on the compute " "host. See https://bugs.launchpad.net/nova/+bug/1739646 for more details." msgstr "" #: ../../:399 stable/ussuri>:1195 msgid "" "Also a virtio-serial controller is created when ``hw_qemu_guest_agent=yes`` " "option is used, together with iommu driver for it." msgstr "" #: ../../:616 msgid "" "Also, the following Cinder front-end QoS specs are now supported for SMB " "Cinder backends:" msgstr "" #: ../../:293 msgid "" "Also, the project reader role is ready to use. Users with reader role can " "only perform the read-only operations within their project. This role can be " "used for the audit purposes." msgstr "" #: ../../:429 msgid "" "Alternatives to this workaround would be unsetting ``memory_mb`` and/or " "``vcpus`` properties from ironic nodes, or using host aggregates to " "segregate VM from BM compute hosts and restrict flavors to those aggregates, " "but those alternatives might not be feasible at large scale." msgstr "" #: ../../:61 unmaintained/xena>:168 #: unmaintained/yoga>:575 msgid "" "Amended the guest resume operation to support mediated devices, as libvirt's " "minimum required version (v6.0.0) supports the hot-plug/unplug of mediated " "devices, which was addressed in v4.3.0." msgstr "" #: ../../:1132 stable/pike>:1162 msgid "" "An IPTables-compatible interface is used, e.g. an OVS VIF in hybrid mode, " "where the VIF is a tap device connected to OVS with a bridge" msgstr "" #: ../../:141 stable/stein>:218 stable/train>:1441 msgid "" "An ``--instance`` option has been added to the ``nova-manage placement " "heal_allocations`` CLI which allows running the command on a specific " "instance given its UUID." msgstr "" #: ../../:314 msgid "" "An `emulated Virtual Trusted Platform Module`__ can be exposed to instances " "running on a ``libvirt`` hypervisor with ``qemu`` or ``kvm`` backends." msgstr "" #: ../../:78 stable/stein>:176 stable/train>:416 #: stable/ussuri>:1266 msgid "" "An instance can be rebuilt in-place with the original image or a new image. " "Instance resource usage cannot be altered during a rebuild. Previously Nova " "would have ignored the NUMA topology of the new image continuing to use the " "NUMA topology of the existing instance until a move operation was performed. " "As Nova did not explicitly guard against inadvertent changes to resource " "requests contained in a new image, it was possible to rebuild with an image " "that would violate this requirement; see `bug #1763766`_ for details. This " "resulted in an inconsistent state as the instance that was running did not " "match the instance that was requested. Nova now explicitly checks if a " "rebuild would alter the requested NUMA topology of an instance and rejects " "the rebuild if so." msgstr "" #: ../../:1024 stable/queens>:1173 msgid "" "An instance is deployed with a flavor smaller than a node (only possible " "when exact filters are not used)" msgstr "" #: ../../:230 stable/ussuri>:241 #: unmaintained/victoria>:779 msgid "" "An issue that could result in instances with the ``isolate`` thread policy " "(``hw:cpu_thread_policy=isolate``) being scheduled to hosts with SMT " "(HyperThreading) and consuming ``VCPU`` instead of ``PCPU`` has been " "resolved. See `bug #1889633`__ for more information." msgstr "" #: ../../:1433 msgid "" "An online data migration has been added to populate the ``services.uuid`` " "column in the nova database for non-deleted services records. Listing or " "showing services out of the ``os-services`` API will have the same effect." msgstr "" #: ../../:815 msgid "" "An option ``--before`` has been added to `nova-manage db " "archive_deleted_rows` command. This options limits archiving of records to " "those deleted before the specified date." msgstr "" #: ../../:1081 msgid "" "An optional configuration group ``placement_database`` can be used in nova." "conf to configure a separate database for use with the placement API." msgstr "" #: ../../:1125 msgid "" "And as noted above, as more of the code base evolves to rely on resource " "allocations being tracked in the placement service (created during " "scheduling), out-of-tree scheduler driver support may be severely impacted." msgstr "" #: ../../:567 msgid "" "And following fine control policy use to keep host only information to " "admin:" msgstr "" #: ../../:1760 msgid "" "And the following fields are removed from the same APIs in the same " "microversion:" msgstr "" #: ../../:795 msgid "" "Any remaining users of these workarounds should plan to disable these " "workarounds as soon as possible. Note that this requires that any instances " "on compute hosts using the workaround be shutdown ahead of the value of the " "workaround changing, before being restarted." msgstr "" #: ../../:598 msgid "" "Any traits provided by the driver will be automatically added during startup " "or a periodic update of a compute node. Similarly any traits later " "retracted by the driver will be automatically removed." msgstr "" #: ../../:1787 msgid "" "Are performing a live, rolling upgrade and all compute hosts are not " "currently running Rocky code" msgstr "" #: ../../:62 unmaintained/yoga>:141 #: unmaintained/zed>:481 msgid "" "As a fix for `bug 1942329 `_ nova now updates the MAC address of the ``direct-physical`` ports " "during mova operations to reflect the MAC address of the physical device on " "the destination host. Those servers that were created before this fix need " "to be moved or the port needs to be detached and the re-attached to " "synchronize the MAC address." msgstr "" #: ../../:1261 msgid "" "As a reminder, there is also the ``[scheduler]/" "discover_hosts_in_cells_interval`` configuration option which can be used to " "automatically discover hosts from the nova-scheduler service." msgstr "" #: ../../:1581 msgid "" "As a result, the following option is also deprecated for removal since it is " "only used when specified with ``[DEFAULT]/monkey_patch_modules``:" msgstr "" #: ../../:65 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 "" #: ../../:865 msgid "" "As new hosts are added to Nova, the `nova-manage cell_v2 discover_hosts` " "command must be run in order to map them into their cell. For deployments " "with proper automation, this is a trivial extra step in that process. " "However, for smaller or non-automated deployments, there is a new " "configuration variable for the scheduler process which will perform this " "discovery periodically. By setting `scheduler." "discover_hosts_in_cells_interval` to a positive value, the scheduler will " "handle this for you. Note that this process involves listing all hosts in " "all cells, and is likely to be too heavyweight for large deployments to run " "all the time." msgstr "" #: ../../:953 msgid "" "As of Libvirt 1.3.3 (`commit`_) and later Libvirt no longer accepts an empty " "path attribute to the script element of the interface. Notably this includes " "Libvirt 2.0.0 as provided with RHEL 7.3 and CentOS 7.3-1611. The creation of " "virtual machines with offending interface definitions on a host with Libvirt " "1.3.3 or later will result in an error \"libvirtError: Cannot find '' in " "path: No such file or directory\"." msgstr "" #: ../../:1208 msgid "" "As of Ocata, the minimum version of VMware vCenter that nova compute will " "interoperate with will be 5.1.0. Deployments using older versions of vCenter " "should upgrade. Running with vCenter version less than 5.5.0 is also now " "deprecated and 5.5.0 will become the minimum version in the 16.0.0 Pike " "release of Nova." msgstr "" #: ../../:1406 msgid "" "As of Ocata, the minimum version of Virtuozzo that nova compute will " "interoperate with will be 7.0.0. Deployments using older versions of " "Virtuozzo should upgrade." msgstr "" #: ../../:1560 msgid "" "As of the 16.0.0 Pike release, the ``ExactRamFilter``, ``ExactCoreFilter``, " "and ``ExactDiskFilter`` scheduler filters are all deprecated along with the " "``[scheduler]/use_baremetal_filters`` and ``[scheduler]/" "baremental_enabled_filters`` options. Deployments should migrate to using " "resource classes with baremetal flavors as described in the ironic install " "guide:" msgstr "" #: ../../:1345 msgid "" "As of the ``2018-08-27`` metadata API version, a boolean ``vf_trusted`` key " "appears for all network interface ``devices`` in ``meta_data.json``, " "indicating whether the device is a trusted virtual function or not." msgstr "" #: ../../:51 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 "" #: ../../:255 unmaintained/xena>:478 msgid "" "As part of the fix for bug 1910466, code that attempted to optimize VM CPU " "thread assignment based on the host CPU topology as it was determined to be " "buggy, undocumented and rejected valid virtual CPU topologies while also " "producing different behavior when CPU pinning was enabled vs disabled. The " "optimization may be reintroduced in the future with a more generic " "implementation that works for both pinned and unpinned VMs." msgstr "" #: ../../:863 msgid "" "At this time, FreeBSD does not have a libguestfs package, therefore file " "injection cannot be supported with the libvirt driver on a FreeBSD compute " "host." msgstr "" #: ../../:727 msgid "" "Attaching Neutron ports and networks having QoS minimum bandwidth rule is " "not supported." msgstr "" #: ../../:402 msgid "" "Attaching `neutron ports with QoS minimum bandwidth rules`__ to existing " "instances is now possible." msgstr "" #: ../../:1032 msgid "" "Attaching a multiattach volume to a shelved offloaded instance is not " "supported and will result in a 400 HTTPBadRequest response." msgstr "" #: ../../:1034 msgid "" "Attaching a multiattach volume to an existing server instance will check " "that the compute hosting that instance is new enough to support it and has " "the capability to support it. If the compute cannot support the multiattach " "volume, a 409 HTTPConflict response is returned." msgstr "" #: ../../:627 msgid "Attaching volumes over fibre channel on a passthrough basis." msgstr "" #: ../../:1739 msgid "" "Baremetal scheduling will use the custom resource class defined for each " "baremetal node to make its selection. Refer to the ironic documentation for " "more details:" msgstr "" #: ../../:627 msgid "" "Be sure to read the **Security** release notes about upgrade impacts for " "resolving bug 1552042." msgstr "" #: ../../:1147 msgid "" "Before the bug was fixed, users would have to specify an availability zone " "that matches the zone that the volume(s) were in. With the fix, the compute " "API will implicitly create the server in the zone that the volume(s) are in " "as long as the volume zone is not the same as the ``[DEFAULT]/" "default_availability_zone`` value (defaults to ``nova``)." msgstr "" #: ../../:1025 msgid "" "Behavior will be different for resizes. During a resize, resource " "allocations are held on both the source and destination (even on the same " "host, see https://bugs.launchpad.net/nova/+bug/1790204) until the resize is " "confirmed or reverted. Quota usage will be inflated for servers in the " "``VERIFY_RESIZE`` state and operators should weigh the advantages and " "disadvantages before enabling ``[quota]count_usage_from_placement``." msgstr "" #: ../../:1048 msgid "" "Behavior will be different for servers in ``SHELVED_OFFLOADED`` state. A " "server in ``SHELVED_OFFLOADED`` state will not have placement allocations, " "so it will not consume quota usage for cores and ram. Note that because of " "this, it will be possible for a request to unshelve a server to be rejected " "if the user does not have enough quota available to support the cores and " "ram needed by the server to be unshelved." msgstr "" #: ../../:1043 msgid "" "Behavior will be different for unscheduled servers in ``ERROR`` state. A " "server in ``ERROR`` state that has never been scheduled to a compute host " "will not have placement allocations, so it will not consume quota usage for " "cores and ram." msgstr "" #: ../../:1116 msgid "Below bugs are fixed for policies default values" msgstr "" #: ../../:170 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 "" #: ../../:692 msgid "" "Blueprint `placement-req-filter-forbidden-aggregates`_ adds the ability for " "operators to set traits on aggregates which if not requested in flavor extra " "specs or image properties will result in disallowing all hosts belonging to " "those aggregates from booting the requested instances. This feature is " "enabled via a new config option ``[scheduler]/" "enable_isolated_aggregate_filtering``. See `Filtering hosts by isolated " "aggregates`_ for more details." msgstr "" #: ../../:1326 msgid "" "Blueprints `hide-hypervisor-id-flavor-extra-spec`_ and `add-kvm-hidden-" "feature`_ enabled NVIDIA drivers in Linux guests using KVM and QEMU, but " "support was not included for Windows guests. This is now fixed. See `bug " "1779845`_ for details." msgstr "" #: ../../:1986 msgid "" "Booting volume-backed instances no longer includes an incorrect allocation " "against the compute node for the root disk. Historically, this has been " "quite broken behavior in Nova, where volume-backed instances would count " "against available space on the compute node, even though their storage was " "provided by the volume service. Now, newly-booted volume-backed instances " "will not create allocations of ``DISK_GB`` against the compute node for the " "``root_gb`` quantity in the flavor. Note that if you are still using a " "scheduler configured with the (now deprecated) DiskFilter (including " "deployments using CachingScheduler), the above change will not apply to you." msgstr "" #: ../../:781 msgid "" "Both these problems are addressed by the QEMU-native support in Nova -- this " "is the recommended approach for securing all live migration streams (guest " "RAM, device state, and disks). Assuming TLS environment is setup, this can " "be enabled by setting the config attribute " "``[libvirt]live_migration_with_native_tls``." msgstr "" #: ../../:38 stable/2023.2>:31 stable/2024.1>:295 #: unmaintained/zed>:14 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 "" #: ../../:39 #: origin/stable/ocata>:198 origin/stable/ocata>:278 origin/stable/ocata>:354 #: origin/stable/ocata>:373 origin/stable/ocata>:482 origin/stable/ocata>:1565 #: stable/2023.1>:10 stable/2023.1>:65 stable/2023.1>:351 stable/2023.2>:10 #: stable/2023.2>:46 stable/2023.2>:320 stable/2024.1>:260 stable/pike>:39 #: stable/pike>:66 stable/pike>:102 stable/pike>:196 stable/pike>:239 #: stable/pike>:271 stable/pike>:346 stable/pike>:406 stable/pike>:468 #: stable/pike>:539 stable/pike>:1749 stable/queens>:10 stable/queens>:64 #: stable/queens>:109 stable/queens>:161 stable/queens>:182 stable/queens>:229 #: stable/queens>:248 stable/queens>:357 stable/queens>:462 stable/queens>:486 #: stable/queens>:506 stable/queens>:553 stable/queens>:1666 stable/rocky>:27 #: stable/rocky>:115 stable/rocky>:154 stable/rocky>:201 stable/rocky>:248 #: stable/rocky>:311 stable/rocky>:393 stable/rocky>:484 stable/rocky>:1973 #: stable/stein>:27 stable/stein>:61 stable/stein>:91 stable/stein>:130 #: stable/stein>:162 stable/stein>:347 stable/stein>:375 stable/stein>:1276 #: stable/train>:35 stable/train>:131 stable/train>:168 stable/train>:212 #: stable/train>:261 stable/train>:279 stable/train>:300 stable/train>:369 #: stable/train>:388 stable/train>:1299 stable/ussuri>:10 stable/ussuri>:81 #: stable/ussuri>:97 stable/ussuri>:134 stable/ussuri>:191 stable/ussuri>:223 #: stable/ussuri>:301 stable/ussuri>:1112 unmaintained/victoria>:10 #: unmaintained/victoria>:143 unmaintained/victoria>:159 #: unmaintained/victoria>:181 unmaintained/victoria>:250 #: unmaintained/victoria>:708 unmaintained/wallaby>:49 #: unmaintained/wallaby>:108 unmaintained/wallaby>:176 #: unmaintained/wallaby>:231 unmaintained/wallaby>:266 #: unmaintained/wallaby>:335 unmaintained/wallaby>:880 unmaintained/xena>:28 #: unmaintained/xena>:58 unmaintained/xena>:154 unmaintained/xena>:244 #: unmaintained/xena>:652 unmaintained/yoga>:37 unmaintained/yoga>:77 #: unmaintained/yoga>:137 unmaintained/yoga>:212 unmaintained/yoga>:556 #: unmaintained/zed>:10 unmaintained/zed>:29 unmaintained/zed>:90 #: unmaintained/zed>:107 unmaintained/zed>:477 msgid "Bug Fixes" msgstr "" #: ../../:744 msgid "" "Bug `1875418 `_ is fixed by " "changing the default value of ``[oslo_policy] policy_file`` config option to " "YAML format." msgstr "" #: ../../:683 msgid "" "By default, all operations continue to use the ``role:admin`` check string " "so there is no upgrade impact." msgstr "" #: ../../:1303 msgid "" "By incorporating oslo fixes for `bug 1715374`_ and `bug 1794708`_, the nova-" "compute service now handles ``SIGHUP`` properly." msgstr "" #: ../../:187 msgid "" "By opting into 2.95 API microversion, evacuated instances will remain " "stopped on the destination host until manually started." msgstr "" #: ../../:336 #: stable/pike>:455 stable/queens>:1631 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 "" #: ../../:1929 msgid "" "By removing the ``check_attach`` internal call from Nova, small behavioral " "changes were introduced." msgstr "" #: ../../:389 stable/queens>:1645 msgid "" "By repeatedly rebuilding an instance with new images, an authenticated user " "may consume untracked resources on a hypervisor host leading to a denial of " "service. This regression was introduced with the fix for `OSSA-2017-005`_ " "(CVE-2017-16239), however, only Nova stable/pike or later deployments with " "that fix applied and relying on the default FilterScheduler are affected." msgstr "" #: ../../:1370 msgid "" "By using ``writeback`` QEMU cache mode, make Nova's disk image conversion (e." "g. from raw to QCOW2 or vice versa) dramatically faster, without " "compromising data integrity. `Bug 1818847`_." msgstr "" #: ../../:1463 msgid "" "CI testing of Cells v1 has been moved to the ``experimental`` queue meaning " "changes proposed to nova will not be tested against a Cells v1 setup unless " "explicitly run through the ``experimental`` queue by leaving a review " "comment on the patch of \"check experimental\". Cells v1 has been deprecated " "since the 16.0.0 Pike release and this is a further step in its eventual " "removal." msgstr "" #: ../../:1365 msgid "" "Calls to mount in the virt disk api no longer ignore the value of stderr." msgstr "" #: ../../:600 msgid "" "Cells v1 and nova-network continue to be deprecated, and plan to be removed " "in the 18.0.0 Rocky release." msgstr "" #: ../../:611 msgid "Cells v1 is now deprecated in favor of Cells v2." msgstr "" #: ../../:1806 msgid "" "Cells v1 was not converted to use the database backend for console token " "authorizations. Cells v1 console token authorizations will continue to be " "supported by the ``nova-consoleauth`` service and use of the ``[workarounds]/" "enable_consoleauth`` option does not apply to Cells v1 users." msgstr "" #: ../../:1882 msgid "" "Cells v1 was not converted to use the database backend for console token " "authorizations. Cells v1 console token authorizations will continue to be " "supported by the ``nova-consoleauth`` service." msgstr "" #: ../../:1510 msgid "" "Cells v1, which includes the ``[cells]`` configuration options and ``nova-" "cells`` service, is deprecated in favor of Cells v2. For information on " "Cells v2, see: https://docs.openstack.org/nova/latest/user/cells.html" msgstr "" #: ../../:611 msgid "" "Change the default return value of swap field from the empty string to 0 " "(integer) in flavor APIs." msgstr "" #: ../../:867 msgid "" "Cold migration and resize are now supported for servers with neutron ports " "having resource requests. E.g. ports that have QoS minimum bandwidth rules " "attached. Note that the migration is only supported if both the source and " "the destination compute services are upgraded to Train and the " "``[upgrade_levels]/compute`` configuration does not prevent the computes " "from using the latest RPC version." msgstr "" #: ../../:1025 msgid "" "Compatibility code for compute drivers that do not implement the " "`update_provider_tree`__ interface has been removed. All compute drivers " "must now implement ``update_provider_tree``." msgstr "" #: ../../:1254 msgid "" "Compatibility code for compute drivers that do not implement the " "`update_provider_tree`__ interface is deprecated and will be removed in a " "future release." msgstr "" #: ../../:1025 msgid "" "Compute API microversion 2.60 must be used to create a server from a " "multiattach volume or to attach a multiattach volume to an existing server " "instance." msgstr "" #: ../../:446 msgid "" "Compute capabilities are now exposed as traits in the placement API. See the " "`compute capabilities as traits`_ documentation for more details." msgstr "" #: ../../:584 msgid "" "Compute drivers now expose capabilities via traits in the Placement API. " "Capabilities must map to standard traits defined in `the os-traits project " "`_; for now these are:" msgstr "" #: ../../:733 msgid "" "Compute nodes using the libvirt driver can now report ``PCPU`` inventory. " "This is consumed by instances with dedicated (pinned) CPUs. This can be " "configured using the ``[compute] cpu_dedicated_set`` config option. The " "scheduler will automatically translate the legacy ``hw:cpu_policy`` flavor " "extra spec or ``hw_cpu_policy`` image metadata property to ``PCPU`` " "requests, falling back to ``VCPU`` requests only if no ``PCPU`` candidates " "are found. Refer to the help text of the ``[compute] cpu_dedicated_set``, " "``[compute] cpu_shared_set`` and ``vcpu_pin_set`` config options for more " "information." msgstr "" #: ../../:745 msgid "" "Compute nodes using the libvirt driver will now report the " "``HW_CPU_HYPERTHREADING`` trait if the host has hyperthreading. The " "scheduler will automatically translate the legacy ``hw:cpu_thread_policy`` " "flavor extra spec or ``hw_cpu_thread_policy`` image metadata property to " "either require or forbid this trait." msgstr "" #: ../../:615 msgid "" "Compute-specific documentation is being migrated from http://docs.openstack." "org to https://docs.openstack.org/nova/ and the layout for the Nova " "developer documentation is being re-organized. If you think anything is " "missing or you now have broken bookmarks, please `report a bug`_." msgstr "" #: ../../:1149 msgid "" "Config option ``[ironic]api_endpoint`` was deprecated in the 17.0.0 Queens " "release and is now removed. To achieve the same effect, set the " "``[ironic]endpoint_override`` option. (However, it is preferred to omit this " "setting and let the endpoint be discovered via the service catalog.)" msgstr "" #: ../../:1022 msgid "" "Config option ``[libvirt]/live_migration_progress_timeout`` was deprecated " "in Ocata, and has now been removed." msgstr "" #: ../../:121 stable/2023.2>:264 #: unmaintained/wallaby>:14 unmaintained/xena>:14 unmaintained/yoga>:58 #: unmaintained/zed>:71 msgid "" "Configuration of service user tokens is now **required** for all Nova " "services to ensure security of block-storage volume data." msgstr "" #: ../../:1610 msgid "" "Configuration option ``[ironic]api_endpoint`` is deprecated in favor of " "``[ironic]endpoint_override``." msgstr "" #: ../../:1293 msgid "" "Configuration option ``console_driver`` in the ``DEFAULT`` group has been " "deprecated since the Ocata release and is now removed." msgstr "" #: ../../:1656 msgid "" "Configuration option ``wsgi_log_format`` is deprecated. This only applies " "when running nova-api under eventlet, which is no longer the preferred " "deployment mode." msgstr "" #: ../../:912 msgid "" "Configuration options for `oslo.reports`, found in the ``oslo_reports`` " "group, are now exposed in nova. These include:" msgstr "" #: ../../:1615 msgid "" "Configuration options in the ``[placement]`` section are deprecated as " "follows:" msgstr "" #: ../../:1355 msgid "" "Configuration options related to RPC topics were deprecated in the past " "releases and are now completly removed from nova. There was no need to let " "users choose the RPC topics for all services. There was little benefit from " "this and it made it really easy to break Nova by changing the value of topic " "options." msgstr "" #: ../../:1381 msgid "" "Configuration options related to image file have been removed. They were " "marked as deprecated because the feature to download images from glance via " "filesystem is not used. Below are the removed options:" msgstr "" #: ../../:1308 msgid "" "Configuration options related to the Barbican were deprecated and now " "completly removed from ``barbican`` group. These options are available in " "the Castellan library. Following are the affected options:" msgstr "" #: ../../:1800 msgid "Console proxies have been deployed per cell" msgstr "" #: ../../:355 unmaintained/xena>:672 msgid "" "Constraints in the fix's implementation mean that it only applies to " "instances booted **after** it has been applied. Existing instances will " "still experience bug 1851545 after being shelved and unshelved, even with " "the fix applied." msgstr "" #: ../../:1033 msgid "" "Consult https://docs.openstack.org/nova/latest/reference/notifications.html " "for more information including payload samples." msgstr "" #: ../../:1385 msgid "" "Context: What makes ``writethrough`` so safe against host crashes is that it " "never keeps data in a \"write cache\", but it calls fsync() after *every* " "write. This is also what makes it horribly slow. But cache mode ``none`` " "doesn't do this and therefore doesn't provide this kind of safety. The " "guest OS must explicitly flush the cache in the right places to make sure " "data is safe on the disk; and all modern OSes flush data as needed. So if " "cache mode ``none`` is safe enough for you, then ``writeback`` should be " "safe enough too." msgstr "" #: ../../:1554 msgid "" "Contribute your custom filter/weigher upstream (this is the best option)" msgstr "" #: ../../:358 stable/pike>:1816 msgid "" "Correctly allow the use of a custom scheduler driver by using the name of " "the custom driver entry point in the ``[scheduler]/driver`` config option. " "You must also update the entry point in ``setup.cfg``." msgstr "" #: ../../:1018 msgid "" "Counted usage will not be accurate in an environment where multiple Nova " "deployments are sharing a placement deployment because currently placement " "has no way of partitioning resource providers between different Nova " "deployments. Operators who are running multiple Nova deployments that share " "a placement deployment should not set the " "``[quota]count_usage_from_placement`` configuration option to ``True``." msgstr "" #: ../../:1508 msgid "Create, Update, Show & List detail flavor" msgstr "" #: ../../:1149 msgid "Create, Update, Show & List flavor details" msgstr "" #: ../../:724 msgid "" "Creating servers with Neutron networks having QoS minimum bandwidth rule is " "not supported." msgstr "" #: ../../:455 msgid "Critical Issues" msgstr "" #: ../../:491 msgid "" "Cross-cell resize is now supported but is disabled by default for all users. " "Refer to the `administrator documentation`__ for details." msgstr "" #: ../../:1025 msgid "" "Current logic in libvirt driver to auto trigger post-copy based on progress " "information is removed as it has `proved impossible`__ to detect when live-" "migration appears to be making little progress." msgstr "" #: ../../:786 msgid "" "Currently only the libvirt compute driver can hide hypervisor signature for " "the guest host." msgstr "" #: ../../:828 msgid "" "Currently only the libvirt compute driver with iSCSI and FC volumes supports " "the online volume size change." msgstr "" #: ../../:1232 msgid "" "Currently the ``nova-manage cell_v2 map_instances`` command uses a marker " "setup by which repeated runs of the command will start from where the last " "run finished, by default. A ``--reset`` option has been added to this " "command by which the marker can be reset and users can start the process " "from the beginning if needed, instead of the default behavior." msgstr "" #: ../../:297 msgid "Currently, nova supports the following roles:" msgstr "" #: ../../:724 msgid "" "Currently, valid values for the ring buffer sizes are 256, 512, and 1024." msgstr "" #: ../../:305 msgid "" "Custom Placement resource inventories and traits can now be described using " "a single `providers configuration file`__." msgstr "" #: ../../:1545 msgid "" "Custom scheduler filters and weighers should continue to function since the " "Instance objects will lazy-load any accessed fields, but this means a round-" "trip to the database to re-load the object per instance, per host." msgstr "" #: ../../:729 msgid "DELETE /resource-providers/{uuid}/inventories" msgstr "" #: ../../:880 msgid "" "DELETE /resource_providers/{uuid}/traits: Remove any existing trait " "associations for a specific resource provider" msgstr "" #: ../../:875 msgid "DELETE /traits/{name}: To delete the specified trait." msgstr "" #: ../../:692 msgid "" "Default image properties for device buses and models are now persisted in " "the instance system metadata for the following image properties:" msgstr "" #: ../../:1537 msgid "" "Deployments with custom scheduler filters (or weighers) that rely on the " "``HostState.instances`` dict to contain full Instance objects will now hit a " "performance penalty because the Instance values in that dict are no longer " "fully populated objects. The in-tree filters that do rely on ``HostState." "instances`` only care about the (1) uuids of the instances per host, which " "is the keys in the dict and (2) the number of instances per host, which can " "be determined via ``len(host_state.instances)``." msgstr "" #: ../../:1505 msgid "" "Deprecate the VMware driver's ``wsdl_location`` config option. This option " "pointed to the location of the WSDL files required when using vCenter " "versions earlier than 5.1. Since the minimum supported version of vCenter is " "5.1, there is no longer a need for this option and its value is ignored." msgstr "" #: ../../:1095 msgid "Deprecated Option" msgstr "" #: ../../:1298 msgid "" "Deprecated config options to enable/disable extensions " "``extensions_blacklist`` and ``extensions_whitelist`` have been removed. " "This means all API extensions are always enabled. If you modifed policy, " "please double check you have the correct policy settings for all APIs." msgstr "" #: ../../:611 msgid "" "Deprecated in Train (20.0.0). The RetryFilter has not been requied since " "Queens following the completion of the return-alternate-hosts blueprint" msgstr "" #: ../../:616 msgid "" "Deprecated in Train (20.0.0). These filters have not worked correctly since " "the introduction of placement in ocata." msgstr "" #: ../../:1416 stable/2023.1>:53 stable/2023.2>:278 #: stable/pike>:1473 stable/queens>:1484 stable/rocky>:1816 stable/stein>:1224 #: stable/train>:1202 stable/ussuri>:1035 unmaintained/victoria>:687 #: unmaintained/wallaby>:769 unmaintained/xena>:575 unmaintained/yoga>:544 #: unmaintained/zed>:458 msgid "Deprecation Notes" msgstr "" #: ../../:262 msgid "" "Disable eventlet monkey-patching using the environment variable " "``OS_NOVA_DISABLE_EVENTLET_PATCHING=yes``." msgstr "" #: ../../:995 msgid "" "Due to `bug 1707256`_, shared storage modeling in Placement is not supported " "by the scheduler. This means that in the Pike release series, an operator " "will be unable to model a shared storage pool between two or more compute " "hosts using the Placement service for scheduling and resource tracking." msgstr "" #: ../../:1159 msgid "Due to a bug in python-glanceclient:" msgstr "" #: ../../:1021 stable/queens>:1170 msgid "" "Due to the changes in scheduling of bare metal nodes, additional resources " "may be reported as free to Placement. This happens in two cases:" msgstr "" #: ../../:1039 msgid "" "During Policy new defaults, below policies are deprecated and will be " "removed in 23.0.0 release. These are replaced by the new granular policies " "listed in feature section." msgstr "" #: ../../:32 unmaintained/wallaby>:130 #: unmaintained/xena>:94 unmaintained/yoga>:629 msgid "" "During the havana cycle it was discovered that eventlet monkey patching of " "greendns broke ipv6. https://bugs.launchpad.net/nova/+bug/1164822 Since then " "nova has been disabling eventlet monkey patching of greendns. Eventlet " "adressed the ipv6 limitation in v0.17 with the introduction of python 3 " "support in 2015. Nova however continued to disable it, which can result i " "slow dns queries blocking the entire nova api or other binary because socket." "getaddrinfo becomes a blocking call into glibc see: https://bugs.launchpad." "net/nova/+bug/1964149 for more details." msgstr "" #: ../../:406 msgid "" "During the triage of https://bugs.launchpad.net/nova/+bug/1978372 we " "compared the performance of nova's numa allocations strategies as it applied " "to the large numbers of host and guest numa nodes. Prior to ``Xena`` nova " "only supported a linear packing strategy. In ``Xena`` ``[compute]/" "packing_host_numa_cells_allocation_strategy`` was introduced maintaining the " "previous packing behavior by default. The numa allocation strategy has now " "been defaulted to spread. The old behavior can be restored by defining: " "``[compute]/packing_host_numa_cells_allocation_strategy=true``" msgstr "" #: ../../:467 msgid "" "During unshelve the ARQs will be reallocated and bound to the instance if " "needed." msgstr "" #: ../../:594 msgid "" "Dynamic configuration groups called ``[vgpu_*]`` are now deprecated in " "favour of ``[mdev_*]``" msgstr "" #: ../../:679 msgid "" "Each policy is protected with appropriate ``scope_type``. Nova support two " "types of ``sope_type`` with their combination. ``['system']``, " "``['project']`` and ``['system', 'project']``." msgstr "" #: ../../:1846 msgid "Enable a foundation on which to build support for multi-attach volumes" msgstr "" #: ../../:377 msgid "" "Enabled `rescue for boot-from-volume instances`__. Rescue now also allows to " "attach stable disk devices to the rescued instance." msgstr "" #: ../../:685 msgid "" "Enables to launch an instance from an iscsi volume with ironic virt driver. " "This feature requires an ironic service supporting API version 1.32 or " "later, which is present in ironic releases > 8.0. It also requires python-" "ironicclient >= 1.14.0." msgstr "" #: ../../:1049 msgid "" "Enabling it will spread instances between hosts that have the same weight " "according to request spec. It is mostly useful when the " "``[filter_scheduler]host_subset_size`` option has default value of 1, but " "available hosts have the same weight (e.g. ironic nodes using resource " "classes). In this case enabling it will decrease the number of rescheduling " "events." msgstr "" #: ../../:734 msgid "" "Encryption provider constants have been introduced detailing the supported " "encryption formats such as LUKs along with their associated in-tree provider " "implementations. These constants should now be used to identify an " "encryption provider implementation for a given encryption format." msgstr "" #: ../../:810 msgid "" "Enhance pci.passthrough_whitelist to support regular expression syntax. The " "'address' field can be regular expression syntax. The old pci." "passthrough_whitelist, glob sytnax, is still valid config." msgstr "" #: ../../:1368 msgid "" "Ensure that the version of ``ip-link`` on the compute host supports setting " "the trust mode on the device." msgstr "" #: ../../:1247 msgid "" "Even in a cell fully upgraded to Train, RPC pinning via ``[upgrade_levels]/" "compute`` can cause live migration of instances with a NUMA topology to " "revert to the legacy naive behavior. For more details refer to the Upgrade " "section." msgstr "" #: ../../:765 msgid "" "Every versioned notification has a sample file stored under doc/" "notification_samples directory. Consult http://docs.openstack.org/developer/" "nova/notifications.html for more information." msgstr "" #: ../../:905 msgid "" "Every versioned notification has a sample file stored under doc/" "notification_samples directory. Consult https://docs.openstack.org/nova/" "latest/reference/notifications.html for more information." msgstr "" #: ../../:1736 msgid "" "ExactCoreFilter, ExactDiskFilter and ExactRamFilter were deprecated for " "removal in the 16.0.0 Pike release and have now been removed." msgstr "" #: ../../:908 msgid "" "Existing ``compute_nodes`` table records with ``0.0`` or ``None`` values for " "``cpu_allocation_ratio``, ``ram_allocation_ratio`` or " "``disk_allocation_ratio`` will be migrated online when accessed or when the " "``nova-manage db online_data_migrations`` command is run." msgstr "" #: ../../:334 msgid "" "Existing compute nodes will, upon upgrade, perist 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 "" #: ../../:284 msgid "" "Experimental support for `emulated architecture is now implemented`__. " "AArch64, PPC64LE, MIPs, and s390x guest architectures are available " "independent of the host architecture. This is strictly not intended for " "production use for various reasons, including no security guarantees." msgstr "" #: ../../:504 msgid "" "Experimental support for thread pooling of DB API calls has been removed. " "This feature was first introduced in the 2014.2 (Juno) release but has not " "graduated to fully-supported status since nor was it being used for any API " "DB calls. The ``[oslo_db] use_tpool`` config option used to enable this " "feature will now be ignored by nova." msgstr "" #: ../../:256 msgid "" "Experimental support is added for Keystone's `unified limits`__. This will " "allow operators to test this feature in non-production systems so we can " "collect early feedback about performance." msgstr "" #: ../../:446 msgid "" "Export instance pinned CPU list through the ``dedicated_cpus`` section in " "the metadata service API." msgstr "" #: ../../:605 msgid "" "Exposes flavor extra_specs in the flavor representation since microversion 2." "61. Flavor extra_specs will be included in Response body of the following " "APIs:" msgstr "" #: ../../:432 msgid "" "Extend the real-time instance with the ``mixed`` CPU allocation policy. In " "comparing with ``dedicated`` policy real-time instance, the non-real-time " "CPUs are not longer required to be pinned on dedicated host CPUs, but float " "on a range of host CPUs sharing with other instances." msgstr "" #: ../../:500 msgid "" "Extending attached encrypted volumes that failed before because they were " "not being decrypted using libvirt (any other than LUKS) now work as expected " "and the new size will be visible within the instance. See `Bug 1967157`_ for " "more details." msgstr "" #: ../../:363 msgid "" "Extra sortings were added to numa_fit_instance_to_host function to balance " "usage of hypervisor's NUMA cells. Hypervisor's NUMA cells with more free " "resources (CPU, RAM, PCI if requested) will be used first (spread strategy) " "when configuration option ``packing_host_numa_cells_allocation_strategy`` " "was set to False. Default value of " "``packing_host_numa_cells_allocation_strategy`` option is set to True which " "leads to packing strategy usage." msgstr "" #: ../../:762 msgid "" "Failing to meet these minimum versions when using the libvirt compute driver " "will result in the `nova-compute` service not starting." msgstr "" #: ../../:1119 msgid "" "Finally, it is still technically possible to load an out-of-tree scheduler " "driver using the ``nova.scheduler.driver`` entry-point. However, out-of-tree " "driver interfaces are not guaranteed to be stable:" msgstr "" #: ../../:827 msgid "" "Finally, the ``GET /os-hypervisors/{hypervisor}/uptime`` API, which provided " "a similar response to the ``GET /os-hypervisors/{hypervisor}`` API but with " "an additional ``uptime`` field, has been removed in favour of including this " "field in the primary ``GET /os-hypervisors/{hypervisor}`` API." msgstr "" #: ../../:358 msgid "" "Finally, the ``nova-manage volume_attachment refresh`` command can be used " "to update the volume attachment with this updated connection information." msgstr "" #: ../../:846 msgid "" "Finally, the following policies are removed. These were related to the " "removed APIs listed above and no longer had any effect:" msgstr "" #: ../../:407 unmaintained/xena>:45 #: unmaintained/yoga>:94 unmaintained/zed>:94 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 "" #: ../../:67 unmaintained/xena>:174 #: unmaintained/yoga>:597 msgid "" "Fixed bug `1960230 `_ that " "prevented resize of instances that had previously failed and not been " "cleaned up." msgstr "" #: ../../:383 unmaintained/zed>:111 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 "" #: ../../:1842 msgid "" "Fixes `bug 1581230`_ by removing the internal ``check_attach`` call from the " "Nova code as it can cause race conditions and the checks are handled by " "``reserve_volume`` in Cinder. ``reserve_volume`` is called in every volume " "attach scenario to provide the necessary checks and volume state validation " "on the Cinder side." msgstr "" #: ../../:1573 stable/pike>:1778 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 "" #: ../../:486 stable/pike>:1788 msgid "" "Fixes `bug 1670522`_ which was a regression in the 15.0.0 Ocata release. For " "compute nodes running the libvirt driver with ``virt_type`` not set to " "\"kvm\" or \"qemu\", i.e. \"xen\", creating servers will fail by default if " "libvirt >= 1.3.3 and QEMU >= 2.7.0 without this fix." msgstr "" #: ../../:386 #: stable/pike>:1806 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 "" #: ../../:302 stable/pike>:472 #: stable/queens>:1701 msgid "" "Fixes `bug 1695861`_ in which the aggregate API accepted requests that have " "availability zone names including ':'. With this fix, a creation of an " "availabilty zone whose name includes ':' results in a ``400 BadRequest`` " "error response." msgstr "" #: ../../:1313 msgid "" "Fixes `bug 1773342`_ where the Hyper-v driver always deleted unused images " "ignoring ``remove_unused_images`` config option. This change will now allow " "deployers to disable the auto-removal of old images." msgstr "" #: ../../:24 stable/rocky>:45 stable/stein>:42 #: stable/train>:172 stable/ussuri>:204 unmaintained/victoria>:254 #: unmaintained/wallaby>:908 msgid "" "Fixes `bug 1892361`_ in which the pci stat pools are not updated when an " "existing device is enabled with SRIOV capability. Restart of nova-compute " "service updates the pci device type from type-PCI to type-PF but the pools " "still maintain the device type as type-PCI. And so the PF is considered for " "allocation to instance that requests vnic_type=direct. With this fix, the " "pci device type updates are detected and the pci stat pools are updated " "properly." msgstr "" #: ../../:355 msgid "" "Fixes `bug 1996995`_ in which VMs live migrated on certain VXLAN Arista " "network fabrics were inaccessible until the switch arp cache expired." msgstr "" #: ../../:1311 msgid "" "Fixes a bug causing mount failures on systemd based systems that are using " "the systemd-run based mount with the Nova Quobyte driver." msgstr "" #: ../../:481 stable/queens>:1785 msgid "" "Fixes a bug preventing ironic nodes without VCPUs, memory or disk in their " "properties from being picked by nova." msgstr "" #: ../../:68 stable/rocky>:262 stable/stein>:389 #: stable/train>:1353 msgid "" "Fixes a bug that caused Nova to fail on mounting Quobyte volumes whose " "volume URL contained multiple registries." msgstr "" #: ../../:322 stable/stein>:1343 msgid "" "Fixes a race condition that could allow a newly created Ironic instance to " "be powered off after deployment, without letting the user power it back on." msgstr "" #: ../../:89 msgid "" "Fixes an issue with cold migrating (resizing) an instance from ocata to pike " "compute by correcting parameters order in resize_instance rpcapi call to " "destination compute." msgstr "" #: ../../:180 unmaintained/xena>:679 msgid "" "Fixes an issue with multiple ``nova-compute`` services used with Ironic, " "where a rebalance operation could result in a compute node being deleted " "from the database and not recreated. See `bug 1853009 `__ for details." msgstr "" #: ../../:1808 msgid "" "Fixes how memory stats are reported for VMware. The total memory for the " "vCenter cluster managed by Nova should be the aggregated sum of total memory " "of each ESX host in the cluster. This is more accurate than using the " "available memory of the resource pool associated to the cluster." msgstr "" #: ../../:50 stable/ussuri>:14 #: unmaintained/victoria>:21 unmaintained/wallaby>:119 unmaintained/xena>:188 #: unmaintained/yoga>:618 msgid "" "Fixes slow compute restart when using the ``nova.virt.ironic`` compute " "driver where the driver was previously attempting to attach VIFS on start-up " "via the ``plug_vifs`` driver method. This method has grown otherwise unused " "since the introduction of the ``attach_interface`` method of attaching VIFs. " "As Ironic manages the attachment of VIFs to baremetal nodes in order to " "align with the security requirements of a physical baremetal node's " "lifecycle. The ironic driver now ignores calls to the ``plug_vifs`` method." msgstr "" #: ../../:919 msgid "" "Flavor.projects (access) will not be present in the instance versioned " "notifications since notifications currently do not lazy-load fields. This " "limitation is being tracked with `bug 1653221`_." msgstr "" #: ../../:1217 msgid "" "Following Notifications related configuration options have been moved from " "the ``DEFAULT`` group to the ``notifications`` group:" msgstr "" #: ../../:1231 msgid "" "For AArch64 Nova now sets ``max`` as the default CPU model. It does the " "right thing in context of both QEMU TCG (plain emulation) and for KVM " "(hardware acceleration)." msgstr "" #: ../../:988 msgid "" "For all three actions we will now check both the flavor and image to " "validate the CPU policy, CPU thread policy, CPU topology, memory topology, " "hugepages, serial ports, realtime CPU mask, NUMA topology details, CPU " "pinning, and a few other things." msgstr "" #: ../../:1357 msgid "For example, modify ``/etc/nova/nova.conf`` and set:" msgstr "" #: ../../:1423 msgid "" "For image download, the proxy downloads an image stream from glance; " "extracts the data stream from the image stream; and then remotely imports " "the data stream to XenServer's VDI via the remote API supplied by XAPI." msgstr "" #: ../../:1419 msgid "" "For image upload, the proxy will export a data stream for a VDI from " "XenServer via the remote API supplied by XAPI; convert the stream to the " "image format supported by glance; and upload the image to glance." msgstr "" #: ../../:672 msgid "" "For information on how to set up support for AMD SEV, please see the `KVM " "section of the Configuration Guide `_." msgstr "" #: ../../:837 msgid "" "For instance, if the user wishes to see resource providers that can service " "a request for 2 vCPUs, 1024 MB of RAM and 50 GB of disk space, the user can " "issue a request of::" msgstr "" #: ../../:644 msgid "" "For knowing which types the physical GPU driver supports for libvirt, the " "operator can look at the sysfs by doing::" msgstr "" #: ../../:371 msgid "" "For libvirt driver. Now when creating tap devices the MTU will be configured." " Requires libvirt 3.3.0 at least." msgstr "" #: ../../:789 unmaintained/victoria>:511 msgid "" "For more background about the possible problem, check `this bug `_. A upgrade check has been added to " "the ``nova-status upgrade check`` command for this." msgstr "" #: ../../:870 msgid "" "For more background on this change, see https://bugs.launchpad.net/nova/+bug/" "1552042." msgstr "" #: ../../:400 msgid "For more detail on command usage, see the machine type documentation:" msgstr "" #: ../../:913 msgid "For more details, refer to the `spec`__." msgstr "" #: ../../:942 msgid "For more details, see the admin guide documentation:" msgstr "" #: ../../:1052 msgid "For more details, see the command documentation:" msgstr "" #: ../../:704 msgid "" "For more information about placement policy including a sample file, see the " "configuration reference documentation:" msgstr "" #: ../../:152 stable/rocky>:302 stable/stein>:962 msgid "For more information, refer to `bug #1289064`_." msgstr "" #: ../../:1119 stable/queens>:1147 msgid "For more information, refer to `the documentation`__." msgstr "" #: ../../:1064 msgid "For more information, refer to the `spec`__ and `documentation`__." msgstr "" #: ../../:832 msgid "For more information, see the Cinder admin guide:" msgstr "" #: ../../:431 unmaintained/zed>:55 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 "" #: ../../:1166 msgid "" "For non-admin users, the sort key ``host`` and ``node`` will be excluded." msgstr "" #: ../../:1129 msgid "" "For non-admin users, there is a whitelist for filters already. That " "whitelist is unchanged." msgstr "" #: ../../:148 stable/rocky>:298 stable/stein>:958 msgid "" "For operators that are aware of the issues and are able to manually work " "around them, the ``[workarounds] enable_numa_live_migration`` option can be " "used to allow the broken behavior." msgstr "" #: ../../:599 msgid "" "For the VMWare driver, only the VNC option applied. However, the ``[vmware] " "vnc_keymap`` option was introduce in 18.0.0 (Rocky) and can be used to " "replace ``[vnc] keymap``." msgstr "" #: ../../:1855 msgid "" "For the VMWare driver, only the VNC option applies. However, this option is " "deprecated and will not affect any other driver in the future. A new option " "has been added to the ``[vmware]`` group to replace this:" msgstr "" #: ../../:600 msgid "" "For the VMware ESXi, VM memory should be multiple of 4. Otherwise creating " "instance on ESXi fails with error \"VimFaultException: Memory (RAM) size is " "invalid.\". Instances will now fail to spawn if flavor memory is not a " "multiple of 4." msgstr "" #: ../../:785 msgid "" "For the VMware vCenter driver, added support for the configured video ram " "``hw_video_ram`` from the image, which will be checked against the maximum " "allowed video ram ``hw_video:ram_max_mb`` from the flavor. If the selected " "video ram from the image is less than or equal to the maximum allowed ram, " "the ``videoRamSizeInKB`` will be set. If the selected ram is more than the " "maximum allowed one, then server creation will fail for the given image and " "flavor. If the maximum allowed video ram is not set in the flavor we do not " "set ``videoRamSizeInKB`` in the VM." msgstr "" #: ../../:1815 msgid "" "For the XenAPI driver, in order to delete cached images based on when they " "were created, a new ``--keep-days DAYS`` option is added to the " "``destroy_cached_images`` script to delete cached images which were created " "at least ``DAYS`` days ago. By default, all unused cached images will be " "deleted when the script is run if they have ``cached_time``." msgstr "" #: ../../:339 msgid "" "For the details on what changed from the existing policy, please refer the " "`RBAC new guidelines`_. We have implemented only phase-1 `RBAC new " "guidelines`_. Currently, scope checks and new defaults are disabled by " "default. You can enable them by switching the below config option in ``nova." "conf`` file::" msgstr "" #: ../../:303 msgid "" "For the details on what changed from the existing policy, please refer to " "the `RBAC new guidelines`_. We have implemented only phase-1 of the `RBAC " "new guidelines`_. Currently, scope checks and new defaults are disabled by " "default. You can enable them by switching the below config option in ``nova." "conf`` file::" msgstr "" #: ../../:976 msgid "" "For the libvirt driver, the NUMA-aware live migration feature requires the " "conductor, source compute, and destination compute to be upgraded to Train. " "It also requires the conductor and source compute to be able to send RPC 5.3 " "- that is, their ``[upgrade_levels]/compute`` configuration option must not " "be set to less than 5.3 or a release older than \"train\"." msgstr "" #: ../../:656 msgid "" "For the moment, only a single type can be supported across one compute node, " "which means that libvirt will create the vGPU by using that specific type " "only. It's also possible to have two compute nodes having different types " "but there is no possibility yet to specify in the flavor which specific type " "we want to use for that instance." msgstr "" #: ../../:1186 msgid "" "From microversion 1.27, the ``provider_summaries`` field in the response of " "the ``GET /allocation_candidates`` API includes all the resource class " "inventories, while it had only requested resource class inventories with " "older microversions. Now callers can use this additional inventory " "information in making further sorting or filtering decisions." msgstr "" #: ../../:1008 msgid "" "From microversion 1.29, we support allocation candidates with nested " "resource providers. Namely, the following features are added. 1) ``GET /" "allocation_candidates`` is aware of nested providers. Namely, when provider " "trees are present, ``allocation_requests`` in the response of ``GET /" "allocation_candidates`` can include allocations on combinations of multiple " "resource providers in the same tree. 2) ``root_provider_uuid`` and " "``parent_provider_uuid`` are added to ``provider_summaries`` in the response " "of ``GET /allocation_candidates``." msgstr "" #: ../../:514 msgid "" "From microversion 2.69 the responses of ``GET /servers``, ``GET /servers/" "detail``, ``GET /servers/{server_id}`` and ``GET /os-services`` will contain " "missing keys during down cell situations because of adding support for " "returning minimal constructs based on the available information from the API " "database for those records in the down cells. See `Handling Down Cells`_ for " "more information on the missing keys." msgstr "" #: ../../:450 msgid "" "From this release, Nova instances will get ``virtio`` as the default display " "device (instead of ``cirrus``, which has many limitations). If your guest " "has a native kernel (called \"virtio-gpu\" in Linux; available since Linux " "4.4 and above) driver, then it'll be used; otherwise, the 'virtio' model " "will gracefully fallback to VGA compatibiliy mode, which is still better " "than ``cirrus``." msgstr "" #: ../../:184 msgid "" "Fully-Qualified Domain Names are now considered valid for an instance " "hostname if you use the 2.94 API microversion." msgstr "" #: ../../:856 msgid "" "Furthermore, the `2.57 compute REST API microversion`_ deprecated the use of " "personality files for file injection. For more history on deprecating file " "injection, see the `spec`__." msgstr "" #: ../../:876 msgid "" "GET /resource_providers/{uuid}/traits: a list of traits associated with a " "specific resource provider" msgstr "" #: ../../:664 msgid "GET /servers/{server_id}/os-interface (list)" msgstr "" #: ../../:665 msgid "GET /servers/{server_id}/os-interface/{port_id} (show)" msgstr "" #: ../../:658 msgid "GET /servers/{server_id}/os-volume_attachments (list)" msgstr "" #: ../../:659 msgid "GET /servers/{server_id}/os-volume_attachments/{volume_id} (show)" msgstr "" #: ../../:874 msgid "GET /traits/{name}: To check if a trait name exists." msgstr "" #: ../../:872 msgid "GET /traits: Returns all resource classes." msgstr "" #: ../../:212 msgid "GET RDP console connection information:" msgstr "" #: ../../:204 msgid "GET RDP console:" msgstr "" #: ../../:1174 msgid "" "Given that there are other better documented and better tested ways to " "approach this, such as through use of neutron's native port filtering or " "security groups, this functionality has been removed. Users should instead " "rely on one of these alternatives." msgstr "" #: ../../:310 msgid "" "Glance multistore configuration with multiple RBD backends is now supported " "within Nova for libvirt RBD-backed images using ``[libvirt]/" "images_rbd_glance_store_name`` configuration option." msgstr "" #: ../../:282 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 "" #: ../../:976 msgid "" "HVM guests may not have the paravirtualization (PV) drivers installed, in " "which case the disk will be accessible on the ``ide`` bus. When the PV " "drivers are installed the disk will be accessible on the ``xen`` bus." msgstr "" #: ../../:407 msgid "" "Handling accelerator requests for an instance is now supported (where " "supported by the underlying virt driver) as of microversion 2.82. The Cyborg " "service generates an event for the binding completion for each accelerator " "request (ARQ) for an instance. Adds a new event " "``accelerator_request_bound`` for this to the API ``POST /os-server-external-" "events``" msgstr "" #: ../../:172 msgid "" "Handling packed virtqueue requests for an instance is now supported on the " "nodes with Qemu v4.2 and Libvirt v6.3." msgstr "" #: ../../:1790 msgid "Have configured a much longer token TTL" msgstr "" #: ../../:1789 msgid "Have not yet deployed console proxies per cell" msgstr "" #: ../../:392 msgid "" "Historically, there has been no way to delete ``task_log`` table records " "other than manual database modification. Because of this, ``task_log`` " "records could pile up over time and operators are forced to perform manual " "steps to periodically truncate the ``task_log`` table." msgstr "" #: ../../:603 msgid "" "However any traits which are removed by the admin from the compute node " "resource provider via the Placement API will not be reinstated until the " "compute service's provider cache is reset. This can be triggered via a " "``SIGHUP``." msgstr "" #: ../../:413 msgid "" "However, existing ironic instances require a data migration which can be " "achieved either by restarting ``nova-compute`` services managing ironic " "nodes or running ``nova-manage db ironic_flavor_migration``. The completion " "of the data migration can be checked by running the ``nova-status upgrade " "check`` command and checking the \"Ironic Flavor Migration\" result." msgstr "" #: ../../:694 msgid "" "However, if desired, ``[placement]/policy_file`` makes it possible to " "package and deploy the placement policy file separately to make the future " "split of placement and nova packages easier, e.g.:" msgstr "" #: ../../:1163 msgid "" "If ``[glance]/api_servers`` is not set in nova.conf, and there is a " "versioned endpoint URL in the service catalog, nova makes a best attempt at " "parsing and stripping the version from the URL in order to make API requests " "to the image service." msgstr "" #: ../../:1085 msgid "" "If ``placement_database.connection`` has a value then the " "``placement_database`` configuration group will be used to configure a " "separate placement database, including using ``connection`` to identify the " "target database. That database will have a schema that is a replica of all " "the tables used in the API database. The new database schema will be created " "and synchronized when the ``nova-manage api_db sync`` command is run." msgstr "" #: ../../:989 msgid "" "If any of these requirements are not met, live migration of instances with a " "NUMA topology with the libvirt driver will revert to the legacy naive " "behavior, in which the instance was simply moved over without updating its " "NUMA guest to host mappings or its resource usage." msgstr "" #: ../../:1366 msgid "" "If by Newton (14.0.0), you don't use any of the CoreFilter, RamFilter or " "DiskFilter, then please modify all your compute node's configuration by " "amending either ``cpu_allocation_ratio`` (if you don't use CoreFilter) or " "``ram_allocation_ratio`` (if you don't use RamFilter) or " "``disk_allocation_ratio`` (if you don't use DiskFilter) by putting a 9999.0 " "value for the ratio before upgrading the nova-scheduler to Ocata." msgstr "" #: ../../:61 stable/ussuri>:25 #: unmaintained/victoria>:46 unmaintained/wallaby>:144 unmaintained/xena>:108 #: unmaintained/yoga>:166 unmaintained/zed>:568 msgid "" "If compute service is down in source node and user try to stop instance, " "instance gets stuck at powering-off, hence evacuation fails with msg: Cannot " "'evacuate' instance while it is in task_state powering-off. It " "is now possible for evacuation to ignore the vm task state. For more details " "see: `bug 1978983`_" msgstr "" #: ../../:823 msgid "" "If other filtering query parameters are present, the results are a boolean " "AND of all the filters." msgstr "" #: ../../:862 msgid "If running on s390x, you will need libguestfs >= 1.37.14." msgstr "" #: ../../:257 msgid "" "If running with ``threads=1`` is not an option in a particular environment, " "there are two other workarounds:" msgstr "" #: ../../:210 stable/pike>:358 #: stable/queens>:1753 msgid "" "If scheduling fails during rebuild the server instance will go to ERROR " "state and a fault will be recorded. `Bug 1744325`_" msgstr "" #: ../../:712 msgid "" "If the ``[cinder]/cross_az_attach`` configuration option is False then the " "specified availability zone has to be the same as the availability zone of " "any volumes attached to the shelved offloaded server, otherwise a 409 " "HTTPConflict error response is returned." msgstr "" #: ../../:961 msgid "" "If the ``[placement]`` section is missing from the nova-api's nova.conf " "file, nothing will break however there will be some warnings generated in " "the nova-api's log file when administrators associate a compute host with a " "host aggregate. However, this will become a failure starting in the 19.0.0 " "Stein release." msgstr "" #: ../../:690 msgid "" "If the host supports this feature and it has at least an assignable PCI " "device, the host must be configured to allow those PCI devices to be " "assigned to VMs. For information on how to do this, follow this guide [1]." msgstr "" #: ../../:466 msgid "" "If the project should not have any outstanding resource usage, then one " "possible workaround is to delete the existing quota usage for the project::" msgstr "" #: ../../:1766 msgid "" "If the scheduler service is started before the cell mappings are created or " "setup, nova-scheduler needs to be restarted or SIGHUP-ed for the newly added " "cells to get registered in the scheduler cache." msgstr "" #: ../../:1549 msgid "If this is an issue for you, you have three options:" msgstr "" #: ../../:1298 msgid "" "If using the ``api_servers`` option in the ``[glance]`` configuration " "section, the values therein must be URLs. Raw IP addresses will result in " "hard failure of API requests." msgstr "" #: ../../:774 unmaintained/victoria>:496 msgid "" "If you are overwriting the policy rules (all or some of them) in the policy " "file with new default values or any new value that requires scoped tokens, " "then non-scoped tokens will not work. Also if you generate the policy file " "with 'oslopolicy-sample-generator' json format or any other tool, you will " "get rules defaulted in the new format, which examines the token scope. " "Unless you turn on ``oslo_policy.enforce_scope``, scope-checking rules will " "fail. Thus, be sure to enable ``oslo_policy.enforce_scope`` and `educate " "`_ end users on how to request scoped tokens from Keystone, or use a " "pre-existing sample config file from the Train release until you are ready " "to migrate to scoped policies. Another way is to generate the policy file in " "yaml format as described `here `_ and update the policy." "yaml location in ``oslo_policy.policy_file``." msgstr "" #: ../../:166 stable/pike>:316 #: stable/queens>:1222 msgid "" "If you have been relying on per-aggregate overcommit, during your upgrade, " "you must change to using per-compute-node overcommit ratios in order for " "your scheduling behavior to stay consistent. Otherwise, you may notice " "increased NoValidHost scheduling failures as the aggregate-based overcommit " "is no longer being considered." msgstr "" #: ../../:1129 msgid "" "If you rely on the ``caching_scheduler`` driver or your own out-of-tree " "driver which sets ``USES_ALLOCATION_CANDIDATES = False`` to bypass the " "placement service, please communicate with the nova development team in the " "openstack-dev mailing list and/or #openstack-nova freenode IRC channel to " "determine what prevents you from using the ``filter_scheduler`` driver." msgstr "" #: ../../:387 msgid "" "If you set this option the same on all of your compute hosts, which you " "should do if you use the same networking backend universally, you do not " "have to worry about this." msgstr "" #: ../../:1000 msgid "" "If you upgraded your OpenStack deployment to Stein without switching to use " "the now independent placement service, you must do so before upgrading to " "Train. `Instructions `_ for one way to do this are available." msgstr "" #: ../../:695 msgid "" "If you use NVIDIA GRID cards, please know that there is a limitation with " "the NVIDIA driver that prevents one guest to have more than one virtual GPU " "from the same physical card. One guest can have two or more virtual GPUs but " "then it requires each vGPU to be hosted by a separate physical card. Until " "that limitation is removed, please avoid creating flavors asking for more " "than one vGPU." msgstr "" #: ../../:312 msgid "" "If you want to disable them then modify the below config options value in " "``nova.conf`` file::" msgstr "" #: ../../:1253 msgid "" "If you were using ``nova hypervisor-list`` after starting new nova-compute " "services to tell when to run ``nova-manage cell_v2 discover_hosts``, you " "should change your tooling to instead use one of the following commands::" msgstr "" #: ../../:547 msgid "" "Image pre-caching on hosts by aggregate is now supported (where supported by " "the underlying virt driver) as of microversion 2.81. A group of hosts within " "an aggregate can be compelled to fetch and cache a list of images to reduce " "time-to-boot latency. Adds the new API:" msgstr "" #: ../../:717 msgid "" "Images should be prepared for Generation 2 VMs. The image property " "\"hw_machine_type=hyperv-gen2\" is mandatory." msgstr "" #: ../../:1420 msgid "" "Implemented microversion v2.39 that deprecates `image-metadata` proxy API, " "removes image metadata quota checks for 'createImage' and 'createBackup' " "actions. After this version Glance configuration option " "`image_property_quota` should be used to control the quota of image " "metadatas. Also, removes the `maxImageMeta` field from `os-limits` API " "response." msgstr "" #: ../../:494 msgid "" "Improved `operational tooling `_ for things like archiving the database and healing " "instance resource allocations in Placement." msgstr "" #: ../../:180 msgid "" "Improved behavior for Windows guest by adding by default following `Hyper-V " "enlightments`__ on all libvirt guests : `vpindex`, `runtime`, `synic`, " "`reset`, `frequencies`, `reenlightenment`, `tlbflush`, `ipi` and `evmc`." msgstr "" #: ../../:498 msgid "" "Improved coordination with the baremetal service during external node `power " "cycles `_." msgstr "" #: ../../:31 stable/train>:39 stable/ussuri>:101 #: unmaintained/victoria>:163 unmaintained/wallaby>:339 unmaintained/xena>:656 msgid "" "Improved detection of anti-affinity policy violation when performing live " "and cold migrations. Most of the violations caused by race conditions due to " "performing concurrent live or cold migrations should now be addressed by " "extra checks in the compute service. Upon detection, cold migration " "operations are automatically rescheduled, while live migrations have two " "checks and will be rescheduled if detected by the first one, otherwise the " "live migration will fail cleanly and revert the instance state back to its " "previous value." msgstr "" #: ../../:629 msgid "" "Improved iSCSI MPIO support, by connecting to multiple iSCSI targets/portals " "when available and allowing using a predefined list of initiator HBAs." msgstr "" #: ../../:484 msgid "" "Improved multi-cell resilience with the ability to `count quota usage `_ using the Placement service and API database." msgstr "" #: ../../:481 msgid "" "Improvements to the scheduler for more intelligently filtering `results from " "the Placement service `_." msgstr "" #: ../../:376 stable/queens>:1187 msgid "" "In 16.0.0 Pike release, quota limits are checked in a new fashion after " "change 5c90b25e49d47deb7dc6695333d9d5e46efe8665 and a new config option " "``[quota]/recheck_quota`` has been added in change " "eab1d4b5cc6dd424c5c7dfd9989383a8e716cae5 to recheck quota after resource " "creation to prevent allowing quota to be exceeded as a result of racing " "requests. These changes could lead to requests blocked by over quota " "resulting in instances in the ``ERROR`` state, rather than no instance " "records as before. Refer to https://bugs.launchpad.net/nova/+bug/1716706 for " "detailed bug report." msgstr "" #: ../../:1222 msgid "" "In Ocata, the nova-scheduler would fall back to not calling the placement " "service during instance boot if old computes were running. That " "compatibility mode is no longer present in Pike, and as such, the scheduler " "fully depends on the placement service. This effectively means that in Pike " "Nova requires Placement API version 1.4 (Ocata)." msgstr "" #: ../../:1346 msgid "" "In Queens, specifying ``url`` will trigger the legacy behavior. The ``url`` " "option will be removed in Rocky." msgstr "" #: ../../:277 msgid "" "In Stein the Placement service is available either as part of Nova, or " "independently packaged from its own project. This is to allow easier " "migration from one to another. See the `upgrade notes`_ for more information." "" msgstr "" #: ../../:637 msgid "" "In addition, ``locked`` will be supported as a valid filter/sort parameter " "for ``GET /servers/detail`` and ``GET /servers`` so that users can filter " "servers based on their locked value. Also the instance action versioned " "notifications for the lock/unlock actions now contain the ``locked_reason`` " "field." msgstr "" #: ../../:1046 msgid "" "In addition, all filter scheduler configuration options have been added to " "the ``filter_scheduler`` group." msgstr "" #: ../../:431 msgid "" "In addition, starting with the 2.90 microversion, the ``OS-EXT-SRV-ATTR:" "hostname`` field is now returned for all users. Previously this was " "restricted to admin users." msgstr "" #: ../../:823 msgid "" "In addition, the ``GET /os-hypervisors/statistics`` API, which provided a " "summary view with just the fields listed above, has been removed entirely " "and will now raise a HTTP 404 with microversion 2.88 or greater." msgstr "" #: ../../:1118 msgid "" "In addition, the following *cells v1* related RPC configuration options, " "previously found in ``upgrade_levels``, have been removed." msgstr "" #: ../../:838 msgid "" "In addition, the following APIs have been removed. Calling these APIs will " "now result in a ``410 HTTPGone`` error response:" msgstr "" #: ../../:1489 msgid "In addition, the following configuration options have been removed." msgstr "" #: ../../:664 msgid "" "In all cases, SEV instances can only be booted from images which have the " "``hw_firmware_type`` property set to ``uefi``, and only when the machine " "type is set to ``q35``. The latter can be set per image by setting the " "image property ``hw_machine_type=q35``, or per compute node by the operator " "via the ``hw_machine_type`` configuration option in the ``[libvirt]`` " "section of :file:`nova.conf`." msgstr "" #: ../../:1008 msgid "" "In all cases, strict NUMA affinity is provided if possible. The key " "difference between the policies is how much NUMA affinity one is willing to " "forsake before failing to schedule." msgstr "" #: ../../:467 msgid "" "In both cases this means when looking at resource providers, depending on " "the scenario, you can see more than one provider where there was initially " "just a root compute node provider per compute service." msgstr "" #: ../../:1428 msgid "" "In case of infrastructure failures like non-responsive cells, prior to " "`change e3534d`_ we raised an API 500 error. However currently when listing " "instances or migrations, we skip that cell and display results from the up " "cells with the aim of increasing availability at the expense of accuracy. If " "the old behaviour is desired, a new flag called ``CONF.api." "list_records_by_skipping_down_cells`` has been added which can be set to " "False to mimic the old behavior. Both of these potential behaviors will be " "unified in an upcoming microversion done through the `blueprint handling-" "down-cell`_ where minimal constructs would be returned for the down cell " "instances instead of raising 500s or skipping down cells." msgstr "" #: ../../:621 msgid "" "In deployments with Ironic, adds the ability for compute services to manage " "a subset of Ironic nodes. If the ``[ironic]/partition_key`` configuration " "option is set, the compute service will only consider nodes with a matching " "``conductor_group`` attribute for management. Setting the ``[ironic]/" "peer_list`` configuration option allows this subset of nodes to be " "distributed among the compute services specified to further reduce failure " "domain. This feature is useful to co-locate nova-compute services with " "ironic-conductor services managing the same nodes, or to better control " "failure domain of a given compute service." msgstr "" #: ../../:1038 msgid "" "In deployments with multiple (v2) cells, upcalls from the computes to the " "scheduler (or other control services) cannot occur. This prevents certain " "things from happening, such as the track_instance_changes updates, as well " "as the late affinity checks for server groups. See the related documentation " "on the `scheduler.track_instance_changes` and `workarounds." "disable_group_policy_check_upcall` configuration options for more details. " "Single-cell deployments without any MQ isolation will continue to operate as " "they have for the time being." msgstr "" #: ../../:1105 msgid "" "In microversion 1.23 of the placement service, JSON formatted error " "responses gain a new attribute, ``code``, with a value that identifies the " "type of this error. This can be used to distinguish errors that are " "different but use the same HTTP status code. Any error response which does " "not specifically define a code will have the code ``placement." "undefined_code``." msgstr "" #: ../../:1358 msgid "" "In mitaka, an online migration was added to migrate older SRIOV parent " "device information from extra_info to a new column. Since two releases have " "gone out with that migration, it is removed in Ocata and operators are " "expetected to have run it as part of either of the previous two releases, if " "applicable." msgstr "" #: ../../:1182 msgid "" "In order to maintain backward compatibility, filter and sort parameters " "which are not mapped to the REST API `servers` resource representation are " "ignored." msgstr "" #: ../../:324 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 "" #: ../../:982 msgid "" "In other words, NUMA-aware live migration with the libvirt driver is not " "supported until:" msgstr "" #: ../../:1123 msgid "" "In placement API microversion 1.20, a successful `POST /resource_providers` " "returns 200 with a payload representing the newly-created resource provider. " " The format is the same format as the result of the corresponding ``GET /" "resource_providers/{uuid}`` call. This is to allow the caller to glean " "automatically-set fields, such as UUID and generation, without a subsequent " "GET." msgstr "" #: ../../:626 msgid "" "In prior releases, an attempt to boot an instance directly from an image " "that was created by the Block Storage Service from an encrypted volume " "resulted in the instance going ACTIVE but being unusable. If a user then " "performed the image-create action on such an instance, the new image would " "inherit the ``cinder_encryption_key_id`` and, beginning with the 20.0.0 " "(Train) release, the ``cinder_encryption_key_deletion_policy`` image " "properties, assuming these were not included in the " "``non_inheritable_image_properties`` configuration option. (The default " "setting for that option does *not* include these.) Beginning with 20.0.0 " "(Train), when the new image was deleted, the encryption key for the " "*original* image would be deleted, thereby rendering it unusable for the " "normal workflow of creating a volume from the image and booting an instance " "from the volume. Beginning with this release:" msgstr "" #: ../../:1753 msgid "" "In the 2.50 microversion, the following fields are added to the ``GET /os-" "quota-class-sets`` and ``PUT /os-quota-class-sets/{id}`` API response:" msgstr "" #: ../../:85 stable/ussuri>:138 #: unmaintained/victoria>:835 msgid "" "In the Rocky (18.0.0) release support was added to nova to use neutron's " "multiple port binding feature when the binding-extended API extension is " "available. In the Train (20.0.0) release the SR-IOV live migration feature " "broke the semantics of the vifs field in the ``migration_data`` object that " "signals if the new multiple port binding workflow should be used by always " "populating it even when the ``binding-extended`` API extension is not " "present. This broke live migration for any deployment that did not support " "the optional ``binding-extended`` API extension. The Rocky behavior has now " "been restored enabling live migration using the single port binding workflow " "when multiple port bindings are not available." msgstr "" #: ../../:1597 msgid "" "In the context of virtual device role tagging at server create time, the 2." "42 microversion restores the tag attribute to networks and " "block_device_mapping_v2. A bug has caused the tag attribute to no longer be " "accepted starting with version 2.33 for block_device_mapping_v2 and starting " "with version 2.37 for networks. In other words, block devices could only be " "tagged in version 2.32 and network interfaces between versions 2.32 and 2.36 " "inclusively. Starting with 2.42, both network interfaces and block devices " "can be tagged again." msgstr "" #: ../../:297 msgid "" "In the environment of the web server running the placement service, set " "``OS_NOVA_DISABLE_EVENTLET_PATCHING=yes`` so that eventlet does not conflict " "with thread handling in the web server." msgstr "" #: ../../:14 unmaintained/zed>:428 msgid "" "In the libvirt driver, the default value of the ```` " "element has been removed, and is now left to libvirt to decide. This is " "because allowed values are platform dependant, and the previous code was not " "guaranteed to be supported on all platforms. If any of your flavors are " "using the quota:cpu_shares extra spec, you may need to resize to a supported " "value before upgrading." msgstr "" #: ../../:457 msgid "" "In this microversion, expose the ``user_id`` and ``project_id`` fields in " "the following APIs:" msgstr "" #: ../../:32 unmaintained/xena>:635 msgid "" "In this release OVS port creation has been delegated to os-vif when the " "``noop`` or ``openvswitch`` security group firewall drivers are enabled in " "Neutron. Those options, and others that disable the ``hybrid_plug`` " "mechanism, will now use os-vif instead of libvirt to plug VIFs into the " "bridge. By delegating port plugging to os-vif we can use the " "``isolate_vif`` config option to ensure VIFs are plugged securely preventing " "guests from accessing other tenants' networks before the neutron ovs agent " "can wire up the port. See `bug #1734320`_ for details. Note that OVN, ODL " "and other SDN solutions also use ``hybrid_plug=false`` but they are not " "known to be affected by the security issue caused by the previous behavior. " "As such the ``isolate_vif`` os-vif config option is only used when deploying " "with ml2/ovs." msgstr "" #: ../../:848 msgid "" "In this release SR-IOV live migration support is added to the libvirt virt " "driver for Neutron interfaces. Neutron SR-IOV interfaces can be grouped into " "two categories, direct mode interfaces and indirect. Direct mode SR-IOV " "interfaces are directly attached to the guest and exposed to the guest OS. " "Indirect mode SR-IOV interfaces have a software interface such as a macvtap " "between the guest and the SR-IOV device. This feature enables transparent " "live migration for instances with indirect mode SR-IOV devices. As there is " "no generic way to copy hardware state during a live migration, direct mode " "migration is not transparent to the guest. For direct mode interfaces, we " "mimic the workflow already in place for suspend and resume. For instance " "with SR-IOV devices, we detach the direct mode interfaces before migration " "and re-attach them after the migration. As a result, instances with direct " "mode SR-IOV port will lose network connectivity during a migration unless a " "bond with a live migratable interface is created within the guest." msgstr "" #: ../../:774 msgid "" "In this release support was added for two additional libvirt video models: " "``gop``, the UEFI graphic output protocol device model; and the ``none`` " "device model. Existing support for ``virtio`` has been extended to all " "architectures and may now be requested via the ``hw_video_model`` image " "metadata property. Prior to this release the ``virtio`` video model was " "unconditionally enabled for ``AARCH64``. This is unchanged but it can now be " "explicitly enabled on all supported architectures. The ``none`` video model " "can be used to disable emulated video devices when using pGPU or vGPU " "passthrough." msgstr "" #: ../../:342 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 "" #: ../../:87 unmaintained/xena>:718 msgid "" "In this release we delegate port plugging to os-vif for all OVS interface " "types. This allows os-vif to create the OVS port before libvirt creates a " "tap device during a live migration therefore preventing the loss of the MAC " "learning frames generated by QEMU. This resolves a long-standing race " "condition between Libvirt creating the OVS port, Neutron wiring up the OVS " "port and QEMU generating RARP packets to populate the vswitch MAC learning " "table. As a result this reduces the interval during a live migration where " "packets can be lost. See `bug #1815989`_ for details." msgstr "" #: ../../:1132 msgid "" "In version 1.25 of the Placement API, ``GET /allocation_candidates`` is " "enhanced to accept numbered groupings of resource, required/forbidden trait, " "and aggregate association requests. A ``resources`` query parameter key with " "a positive integer suffix (e.g. ``resources42``) will be logically " "associated with ``required`` and/or ``member_of`` query parameter keys with " "the same suffix (e.g. ``required42``, ``member_of42``). The resources, " "required/forbidden traits, and aggregate associations in that group will be " "satisfied by the same resource provider in the response. When more than one " "numbered grouping is supplied, the ``group_policy`` query parameter is " "required to indicate how the groups should interact. With ``group_policy=" "none``, separate groupings - numbered or unnumbered - may or may not be " "satisfied by the same provider. With ``group_policy=isolate``, numbered " "groups are guaranteed to be satisfied by *different* providers - though " "there may still be overlap with the unnumbered group. In all cases, each " "``allocation_request`` will be satisfied by providers in a single non-" "sharing provider tree and/or sharing providers associated via aggregate with " "any of the providers in that tree." msgstr "" #: ../../:377 #: stable/pike>:1797 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 "" #: ../../:1203 msgid "" "Injected network templates will now ignore the ``use_ipv6`` config option." msgstr "" #: ../../:579 msgid "" "Instance action versioned notifications now contain " "``action_initiator_user`` and ``action_initiator_project`` fields to " "distinguish between the owner of the instance and who initiated the action " "upon the instance, for example an administrator or another user within the " "same project." msgstr "" #: ../../:702 msgid "" "Instance device buses and models will now remain stable across reboots and " "will not be changed by new defaults in libosinfo or the OpenStack Nova " "libvirt driver." msgstr "" #: ../../:318 msgid "" "Instance hostnames published by the metadata API service or config drives " "can be explicitly defined at instance creation time thanks to the new `2.90 " "API microversion`__. See the ``hostname`` field documentation on the `API " "docs`__ for further details." msgstr "" #: ../../:610 msgid "" "Instance list operations across cells are now made more efficient by " "batching queries as a fraction of the total limit for a request. Before " "this, an instance list with a limit of 1000 records (the default) would " "generate queries to each cell with that limit, and potentially process/sort/" "merge $num_cells*$limit records, despite only returning $limit to the user. " "The strategy can now be controlled via ``[api]/" "instance_list_cells_batch_strategy`` and related options to either use fixed " "batch sizes, or a fractional value that scales with the number of configured " "cells." msgstr "" #: ../../:958 msgid "Instance with network related PCI device and either:" msgstr "" #: ../../:956 msgid "Instance with non-network related PCI device." msgstr "" #: ../../:962 msgid "" "Instances that have attached encrypted volumes from before Queens will " "continue to use os-brick encryptors after a live migration or direct upgrade " "to Queens. A full reboot or another live migration between Queens compute " "hosts is required before the instance will attempt to use QEMU native LUKS " "decryption." msgstr "" #: ../../:43 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 "" #: ../../:107 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 "" #: ../../:60 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 "" #: ../../:158 unmaintained/yoga>:216 #: unmaintained/zed>:490 msgid "" "Instances with hardware offloaded ovs ports no longer lose connectivity " "after failed live migrations. The driver.rollback_live_migration_at_source " "function is no longer called during during pre_live_migration rollback which " "previously resulted in connectivity loss following a failed live migration. " "See `Bug 1944619`_ for more details." msgstr "" #: ../../:1405 msgid "" "Instead of ``api_class`` option ``nova.keymgr.barbican.BarbicanKeyManager``, " "use ``castellan.key_manager.barbican_key_manager.BarbicanKeyManager``" msgstr "" #: ../../:1407 msgid "" "Instead of ``api_class`` option ``nova.tests.unit.keymgr.mock_key_mgr." "MockKeyManager``, use ``castellan.tests.unit.key_manager.mock_key_manager." "MockKeyManager``" msgstr "" #: ../../:582 msgid "" "Intel CMT perf events - ``cmt``, ``mbmt``, and ``mbml`` - are no longer " "supported by the ``[libvirt] enabled_perf_events`` config option. These " "event types were broken by design and are not supported in recent Linux " "kernels (4.14+)." msgstr "" #: ../../:1054 msgid "" "Interface attachment/detachment for ironic virt driver was implemented in in-" "tree network interfaces in ironic version 8.0, and this release is required " "for nova's interface attachment feature to work. Prior to that release, " "calling VIF attach on an active ironic node using in-tree network interfaces " "would be basically a noop. It should not be an issue during the upgrade " "though, as it is required to upgrade ironic before nova." msgstr "" #: ../../:526 msgid "" "Introduced a new config option ``[compute]/max_concurrent_disk_ops`` to " "reduce disk contention by specifying the maximum number of concurrent disk-" "IO-intensive operations per compute service. This would include operations " "such as image download, image format conversion, snapshot extraction, etc. " "The default value is 0, which means that there is no limit." msgstr "" #: ../../:805 msgid "" "Introduces ``[compute]/cpu_shared_set`` option for compute nodes. Some " "workloads run best when the hypervisor overhead processes (emulator threads " "in libvirt/QEMU) can be placed on different physical host CPUs than other " "guest CPU resources. This allows those workloads to prevent latency spikes " "for guest vCPU threads." msgstr "" #: ../../:664 msgid "" "Introduces new placement API version ``1.26``. Starting with this version it " "is allowed to define resource provider inventories with reserved value equal " "to total." msgstr "" #: ../../:1226 msgid "" "Introduces the ``powervm`` configuration group which contains the " "``proc_units_factor`` configuration option. This allows the operator to " "specify the physical processing power to assign per vCPU." msgstr "" #: ../../:1333 msgid "" "Ironic configuration options that were used for a deprecated Identity v2 API " "have been removed from ``ironic`` group. Below is the detailed list of " "removed options:" msgstr "" #: ../../:1000 msgid "" "Ironic nodes are now only scheduled using the ``resource_class`` field set " "on the node. CPUs, RAM, and disks are not reported to the resource tracker. " "Ironic nodes must have the ``resource_class`` field set before upgrading. " "Flavors must also be configured to use resource classes instead of node " "properties. See the `ironic flavor configuration guide `_ for more " "information on doing this." msgstr "" #: ../../:927 msgid "" "Ironic nodes that were deleted from ironic's database during Newton may " "result in orphaned resource providers causing incorrect scheduling " "decisions, leading to a reschedule. If this happens, the orphaned resource " "providers will need to be identified and removed." msgstr "" #: ../../:143 msgid "" "Ironic nova-compute services can now target a specific shard of ironic nodes " "by setting the config ``[ironic]shard``. This is particularly useful when " "using active-passive methods to choose on which physical host your ironic " "nova-compute process is running, while ensuring ``[DEFAULT]host`` stays the " "same for each shard. You can use this alongside ``[ironic]conductor_group`` " "to further limit which ironic nodes are managed by each nova-compute service." " Note that when you use ``[ironic]shard`` the ``[ironic]peer_list`` is hard " "coded to a single nova-compute service." msgstr "" #: ../../:291 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 "" #: ../../:1180 msgid "" "It is no longer possible to force server live migrations or evacuations to a " "specific destination host starting with API microversion 2.68. This is " "because it is not possible to support these requests for servers with " "complex resource allocations. It is still possible to request a destination " "host but it will be validated by the scheduler." msgstr "" #: ../../:562 msgid "" "It is no longer possible to specify an sqlalchemy-migrate-based version. " "When the ``nova-manage db sync`` and ``nova-manage api_db sync`` commands " "are run, all remaining sqlalchemy-migrate-based migrations will be " "automatically applied. Attempting to specify an sqlalchemy-migrate-based " "version will result in an error." msgstr "" #: ../../:530 msgid "" "It is now possible to `disable a cell`_ to stop scheduling to a cell by " "using the ``nova-manage cell_v2 update_cell`` command." msgstr "" #: ../../:338 msgid "" "It is now possible to allocate all cores in an instance to realtime and omit " "the ``hw:cpu_realtime_mask`` extra spec. This requires specifying the ``hw:" "emulator_threads_policy`` extra spec." msgstr "" #: ../../:1058 msgid "" "It is now possible to configure NUMA affinity for most neutron networks. " "This is available for networks that use a ``provider:network_type`` of " "``flat`` or ``vlan`` and a ``provider:physical_network`` (L2 networks) or " "networks that use a ``provider:network_type`` of ``vxlan``, ``gre`` or " "``geneve`` (L3 networks)." msgstr "" #: ../../:537 msgid "" "It is now possible to configure a separate database for the placement " "service, which could help in easing the eventual placement service " "extraction from Nova and data migration associated with it." msgstr "" #: ../../:680 msgid "" "It is now possible to configure granular policy rules for placement REST API " "operations." msgstr "" #: ../../:989 msgid "" "It is now possible to configure multiple *nova-scheduler* workers via the " "``[scheduler]workers`` configuration option. By default, the option runs " "``ncpu`` workers if using the ``filter_scheduler`` scheduler driver, " "otherwise the default is 1." msgstr "" #: ../../:70 stable/queens>:1760 msgid "" "It is now possible to configure the ``[cinder]`` section of nova.conf to " "allow setting admin-role credentials for scenarios where a user token is not " "available to perform actions on a volume. For example, when " "``reclaim_instance_interval`` is a positive integer, instances are soft " "deleted until the nova-compute service periodic task removes them. If a soft " "deleted instance has volumes attached, the compute service needs to be able " "to detach and possibly delete the associated volumes, otherwise they will be " "orphaned in the block storage service. Similarly, if " "``running_deleted_instance_poll_interval`` is set and " "``running_deleted_instance_action = reap``, then the compute service will " "need to be able to detach and possibly delete volumes attached to instances " "that are reaped. See `bug 1733736`_ and `bug 1734025`_ for more details." msgstr "" #: ../../:1007 msgid "" "It is now possible to count quota usage for cores and ram from the placement " "service and instances from instance mappings in the API database instead of " "counting resources from cell databases. This makes quota usage counting " "resilient in the presence of down or poor-performing cells." msgstr "" #: ../../:133 msgid "" "It is now possible to define different authorization policies for migration " "with and without a target host." msgstr "" #: ../../:508 msgid "" "It is now possible to place CPU pinned and unpinned servers on the same " "compute host when using the libvirt compute driver. See the `admin guide " "`_ for details." msgstr "" #: ../../:416 msgid "" "It is now possible to run Nova with version 1.0.0 of the recently extracted " "placement service, hosted from its own repository. Note that install/upgrade " "of an extracted placement service is not yet fully implemented in all " "deployment tools. Operators should check with their particular deployment " "tool for support before proceeding. See the placement `install`_ and " "`upgrade`_ documentation for more details. In Stein, operators may choose to " "continue to run with the integrated placement service from the Nova " "repository, but should begin planning a migration to the extracted placement " "service by Train, as the removal of the integrated placement code from Nova " "is planned for the Train release." msgstr "" #: ../../:822 msgid "" "It is now possible to signal and perform an online volume size change as of " "the 2.51 microversion using the ``volume-extended`` external event. Nova " "will perform the volume extension so the host can detect its new size. It " "will also resize the device in QEMU so instance can detect the new disk size " "without rebooting." msgstr "" #: ../../:678 msgid "" "It is now possible to signal and perform an update of an instance's power " "state as of the 2.76 microversion using the ``power-update`` external event. " "Currently it is only supported in the ironic driver and through this event " "Ironic will send all \"power-on to power-off\" and \"power-off to power-on\" " "type power state changes on a physical instance to nova which will update " "its database accordingly. This way nova will not be able to enforce an " "incorrect power state on the physical instance during the periodic " "``_sync_power_states`` task. The changes to the power state of an instance " "caused by this event can be viewed through ``GET /servers/{server_id}/os-" "instance-actions`` and ``GET /servers/{server_id}/os-instance-actions/" "{request_id}``." msgstr "" #: ../../:344 msgid "" "It is now possible to specify a mask in ``hw:cpu_realtime_mask`` without a " "leading ``^``. When this is ommitted, the value will specify the cores that " "should be included in the set of realtime cores, as opposed to those that " "should be excluded." msgstr "" #: ../../:795 msgid "" "It is now possible to specify an ordered list of CPU models in the " "``[libvirt] cpu_models`` config option. If ``[libvirt] cpu_mode`` is set to " "``custom``, the libvirt driver will select the first CPU model in this list " "that can provide the required feature traits." msgstr "" #: ../../:567 stable/queens>:1798 msgid "" "It is now possible to unset the ``[vnc]keymap`` and ``[spice]keymap`` " "configuration options. These were known to cause issues for some users with " "non-US keyboards and may be deprecated in the future." msgstr "" #: ../../:366 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 "" #: ../../:262 msgid "" "Keystone's policy concepts of system vs. project scope and roles has been " "implemented in Nova and `defaults roles and scopes have been defined`__, " "while legacy policies continue to be enabled by default. Operators are " "encouraged to familiarize with the new policies and `enable them in " "advance`__ before Nova switches from the legacy roles in a later release." msgstr "" #: ../../:245 origin/stable/ocata>:440 origin/stable/ocata>:915 #: stable/pike>:372 stable/pike>:991 stable/queens>:263 stable/queens>:1155 #: stable/rocky>:1437 stable/stein>:231 stable/stein>:818 stable/train>:878 #: stable/ussuri>:159 stable/ussuri>:622 unmaintained/victoria>:89 #: unmaintained/victoria>:215 unmaintained/victoria>:453 #: unmaintained/wallaby>:194 unmaintained/wallaby>:564 unmaintained/xena>:220 #: unmaintained/xena>:455 unmaintained/yoga>:107 unmaintained/yoga>:488 #: unmaintained/zed>:372 msgid "Known Issues" msgstr "" #: ../../:487 msgid "LXC instances now support cloud-init." msgstr "" #: ../../:1341 msgid "" "Legacy option ``url`` is deprecated and replaced by ``endpoint_override``. " "This should not need to be specified if an appropriate service catalog entry " "exists for the network service." msgstr "" #: ../../:462 msgid "" "Libvirt compute nodes reporting VGPU inventory will have that VGPU inventory " "and corresponding allocations moved to a child resource provider on restart " "of the nova-compute service after upgrading to Stein." msgstr "" #: ../../:417 msgid "" "Libvirt supports parsing the VPD capability from PCI/PCIe devices and " "exposing it via nodedev XML as of 7.9.0." msgstr "" #: ../../:326 msgid "" "Libvirt virt driver now supports any PCI device, not just virtual GPUs, that " "are using the ``VFIO-mdev`` virtualization framework, like network adapters " "or compute accelerators. `See more in the spec`__." msgstr "" #: ../../:599 msgid "" "Like SR-IOV, vDPA leverages DMA transfer between the guest and hardware. " "This requires the DMA buffers to be locked in memory. As the DMA buffers are " "allocated by the guest and can be allocated anywhere in the guest RAM, QEMU " "locks **all** guest RAM. By default the ``RLIMIT_MEMLOCK`` for a normal QEMU " "intance is set to 0 and qemu is not allowed to lock guest memory. In the " "case of SR-IOV, libvirt automatically set the limit to guest RAM + 1G which " "enables QEMU to lock the memory. This does not happen today with vDPA ports. " "As a result if you use VDPA ports without enabling locking of the guest " "memory you will get DMA errors. To workaround this issues until libvirt is " "updated, you must set ``hw:cpu_realtime=yes`` and define a valid ``CPU-" "REALTIME-MASK`` e.g ``hw:cpu_realtime_mask=^0`` or define ``hw:" "emulator_threads_policy=share|isolate``. Note that since we are just using " "``hw:cpu_realtime`` for its side-effect of locking the guest memory, this " "usage does not require the guest or host to use realtime kernels. However, " "all other requirements of ``hw:cpu_realtime`` such as requiring hw:" "cpu_policy=dedicated still apply. It is also stongly recommended that " "hugpages be enabled for all instnace with locked memory. This can be done by " "setting ``hw:mem_page_size``. This will enable nova to correctly account for " "the fact that the memory is unswapable." msgstr "" #: ../../:755 msgid "" "Like the ``changes-since`` filter, the ``changes-before`` filter will also " "return deleted servers." msgstr "" #: ../../:216 unmaintained/xena>:459 msgid "" "Linux guest images that have known kernel bugs related to virtualized apic " "initialization previously would sporadically hang. For images where the " "kernel cannot be upgraded, a ``[workarounds]`` config option has been " "introduced:" msgstr "" #: ../../:979 msgid "" "Listing instances across multiple cells with a sort order will result in " "barber-pole sorting, striped across the cell boundaries." msgstr "" #: ../../:361 stable/rocky>:1999 msgid "" "Listing server and migration records used to give a 500 to users when a cell " "database was unreachable. Now only records from available cells are included " "to avoid the 500 error. The down cells are basically skipped when forming " "the results and this solution is planned to be further enhanced through the " "`blueprint handling-down-cell`_." msgstr "" #: ../../:745 msgid "" "Live migration is supported for both Virtuozzo containers and virtual " "machines when using virt_type=parallels." msgstr "" #: ../../:953 msgid "" "Live migration of an instance with PCI devices is now blocked in the " "following scenarios:" msgstr "" #: ../../:134 stable/rocky>:284 stable/stein>:944 msgid "" "Live migration of instances with NUMA topologies is now disabled by default " "when using the libvirt driver. This includes live migration of instances " "with CPU pinning or hugepages. CPU pinning and huge page information for " "such instances is not currently re-calculated, as noted in `bug #1289064`_. " "This means that if instances were already present on the destination host, " "the migrated instance could be placed on the same dedicated cores as these " "instances or use hugepages allocated for another instance. Alternately, if " "the host platforms were not homogeneous, the instance could be assigned to " "non-existent cores or be inadvertently split across host NUMA nodes." msgstr "" #: ../../:473 msgid "" "Live migration support for servers with `SR-IOV ports `_ attached when using the " "libvirt compute driver." msgstr "" #: ../../:468 msgid "" "Live migration support for servers with a `NUMA topology, pinned CPUs `_ and/or `huge " "pages `_, when " "using the libvirt compute driver." msgstr "" #: ../../:964 msgid "Live migration will fail with a user friendly error." msgstr "" #: ../../:934 msgid "" "Live migrations from nodes not compatible with file backed memory to nodes " "with file backed memory is not allowed, and will result in an error. It's " "recommended to upgrade all nodes before enabling file backed memory." msgstr "" #: ../../:1139 msgid "" "Long standing `bug 1694844`_ is now fixed where the following conditions " "would lead to a 400 error response during server create:" msgstr "" #: ../../:228 msgid "" "Make public_key a mandatory parameter for keypair creation. This means that " "by this microversion, Nova will stop to support automatic keypair " "generations. Only imports will be possible." msgstr "" #: ../../:606 msgid "" "Making server representation always consistent among GET, PUT and Rebuild " "serevr APIs response. ``PUT /servers/{server_id}`` and ``POST /servers/" "{server_id}/action {rebuild}`` API response is modified to add all the " "missing fields which are return by ``GET /servers/{server_id}``." msgstr "" #: ../../:688 msgid "" "Mediated devices that are created by the libvirt driver are not persisted " "upon reboot. Consequently, a guest startup would fail since the virtual " "device wouldn't exist. In order to prevent that issue, when restarting the " "compute service, the libvirt driver now looks at all the guest XMLs to check " "if they have mediated devices, and if the mediated device no longer exists, " "then Nova recreates it by using the same UUID." msgstr "" #: ../../:651 msgid "" "Memory encryption can be required either via a flavor which has the ``hw:" "mem_encryption`` extra spec set to ``True``, or via an image which has the " "``hw_mem_encryption`` property set to ``True``. These do not inherently " "cause a preference for SEV-capable hardware, but for now SEV is the only way " "of fulfilling the requirement. However in the future, support for other " "hardware-level guest memory encryption technology such as Intel MKTME may be " "added. If a guest specifically needs to be booted using SEV rather than any " "other memory encryption technology, it is possible to ensure this by adding " "``trait:HW_CPU_X86_AMD_SEV=required`` to the flavor extra specs or image " "properties." msgstr "" #: ../../:946 msgid "" "Microversion 1.13 of the Placement API gives the ability to set or clear " "allocations for more than one consumer uuid with a request to ``POST /" "allocations``." msgstr "" #: ../../:685 msgid "" "Microversion 1.30 of the placement API adds support for a ``POST /reshaper`` " "resource that provides for atomically migrating resource provider " "inventories and associated allocations when some of the inventory moves from " "one resource provider to another, such as when a class of inventory moves " "from a parent provider to a new child provider." msgstr "" #: ../../:939 msgid "" "Microversion 2.49 brings device role tagging to the attach operation of " "volumes and network interfaces. Both network interfaces and volumes can now " "be attached with an optional ``tag`` parameter. The tag is then exposed to " "the guest operating system through the metadata API. Unlike the original " "device role tagging feature, tagged attach does not support the config drive." " Because the config drive was never designed to be dynamic, it only contains " "device tags that were set at boot time with API 2.32. Any changes made to " "tagged devices with API 2.49 while the server is running will only be " "reflected in the metadata obtained from the metadata API. Because of " "metadata caching, changes may take up to ``metadata_cache_expiration`` to " "appear in the metadata API. The default value for " "``metadata_cache_expiration`` is 15 seconds." msgstr "" #: ../../:705 msgid "" "Microversion 2.53 changes service and hypervisor IDs to UUIDs to ensure " "uniqueness across cells. Prior to this, ID collisions were possible in multi-" "cell deployments. See the `REST API Version History`_ and `Compute API " "reference`_ for details." msgstr "" #: ../../:853 msgid "" "Microversion 2.55 adds a ``description`` field to the flavor resource in the " "following APIs:" msgstr "" #: ../../:752 msgid "" "Microversion 2.64 is added and enables users to define rules on server group " "policy to meet more advanced policy requirements. This microversion brings " "the following changes in server group APIs:" msgstr "" #: ../../:751 msgid "" "Microversion 2.66 adds the optional filter parameter ``changes-before`` " "which can be used to get resources changed before or equal to the specified " "date and time." msgstr "" #: ../../:503 msgid "" "Microversion 2.67 adds the optional parameter ``volume_type`` to " "block_device_mapping_v2, which can be used to specify ``volume_type`` when " "creating a server. This would only apply to BDMs with ``source_type`` of " "`blank`, `image` and `snapshot` and ``destination_type`` of `volume`. The " "compute API will reject server create requests with a specified " "``volume_type`` until all nova-compute services are upgraded to Stein." msgstr "" #: ../../:705 msgid "" "Microversion 2.77 adds the optional parameter ``availability_zone`` to the " "``unshelve`` server action API." msgstr "" #: ../../:553 msgid "" "Microversion 2.78 adds a new ``topology`` sub-resource to the servers API:" msgstr "" #: ../../:719 msgid "" "Microversion 2.79 adds support for specifying the ``delete_on_termination`` " "field in the request body when attaching a volume to a server, to support " "configuring whether to delete the data volume when the server is destroyed. " "Also, ``delete_on_termination`` is added to the GET responses when showing " "attached volumes." msgstr "" #: ../../:454 msgid "" "Microversion 2.80 changes the list migrations APIs and the os-migrations API." "" msgstr "" #: ../../:340 msgid "" "Microversion 2.89 has been introduced and will include the ``attachment_id`` " "of a volume attachment, ``bdm_uuid`` of the block device mapping record and " "removes the duplicate ``id`` from the responses for ``GET /servers/" "{server_id}/os-volume_attachments`` and ``GET /servers/{server_id}/os-" "volume_attachments/{volume_id}``." msgstr "" #: ../../:245 msgid "" "Microversion 2.91 adds the optional parameter ``host`` to the ``unshelve`` " "server action API. Specifying a destination host is only allowed to admin " "users and server status must be ``SHELVED_OFFLOADED`` otherwise a HTTP 400 " "(bad request) response is returned. It also allows to set " "``availability_zone`` to None to unpin a server from an availability_zone." msgstr "" #: ../../:675 msgid "" "Migrating an instance to another host will have the same problem as resize. " "In case you want to migrate an instance, make sure to rebuild it." msgstr "" #: ../../:72 stable/ussuri>:36 #: unmaintained/victoria>:57 unmaintained/wallaby>:290 unmaintained/xena>:743 msgid "" "Minimizes a race condition window when using the ``ironic`` virt driver " "where the data generated for the Resource Tracker may attempt to compare " "potentially stale instance information with the latest known baremetal node " "information. While this doesn't completely prevent nor resolve the " "underlying race condition identified in `bug 1841481 `_, this change allows Nova to have the latest state " "information, as opposed to state information which may be out of date due to " "the time which it may take to retrieve the status from Ironic. This issue " "was most observable on baremetal clusters with several thousand physical " "nodes." msgstr "" #: ../../:1576 stable/rocky>:1705 msgid "" "Monkey patching nova is not tested, not supported, and is a barrier to " "interoperability. If you have code which relies on monkey patching " "decorators, for example, for notifications, please propose those changes " "upstream." msgstr "" #: ../../:1848 msgid "More details can be found in the spec:" msgstr "" #: ../../:1254 msgid "" "Most quota options have been moved into their own configuration group. The " "exception is quota_networks as it is an API flag not a quota flag. These " "options are as below:" msgstr "" #: ../../:730 msgid "" "Moving (resizing, migrating, live-migrating, evacuating, unshelving after " "shelve offload) servers with ports having resource request is not yet " "supported." msgstr "" #: ../../:602 msgid "Multiple API cleanups is done in API microversion 2.75:" msgstr "" #: ../../:960 msgid "Neutron does not support extended port binding API." msgstr "" #: ../../:515 msgid "Neutron is now the default configuration for new deployments." msgstr "" #: ../../:1131 stable/pike>:1161 msgid "Neutron port filtering is disabled/unsupported" msgstr "" #: ../../:10 current origin/stable/ocata>:564 stable/2023.1>:198 #: stable/2023.2>:145 stable/2024.1>:97 stable/pike>:635 stable/queens>:629 #: stable/rocky>:564 stable/stein>:485 stable/train>:534 stable/ussuri>:403 #: unmaintained/victoria>:334 unmaintained/wallaby>:162 #: unmaintained/wallaby>:433 unmaintained/xena>:206 unmaintained/xena>:336 #: unmaintained/yoga>:296 unmaintained/zed>:212 msgid "New Features" msgstr "" #: ../../:1096 msgid "New Option" msgstr "" #: ../../:360 msgid "" "New ``[glance]/enable_rbd_download`` config option was introduced. The " "option allows for the configuration of direct downloads of Ceph hosted " "glance images into the libvirt image cache via rbd when ``[glance]/" "enable_rbd_download= True`` and ``[glance]/rbd_user``, ``[glance]/" "rbd_pool``, ``[glance]/rbd_connect_timeout``, ``[glance]/rbd_ceph_conf`` are " "correctly configured." msgstr "" #: ../../:389 msgid "" "New ``nova-manage image_property`` commands have been added to help update " "instance image properties that have become invalidated by a change of " "instance machine type." msgstr "" #: ../../:361 msgid "" "New ``nova-manage placement audit`` CLI command to `find and clean up " "orphaned resource allocations`__." msgstr "" #: ../../:1018 msgid "" "New paste pipelines and middleware have been created to allow API version " "discovery to be performed without authentication or redirects. Because this " "involves an ``api-paste.ini`` change, you will need to manually update your " "``api-paste.ini`` with the one from the release to get this functionality." msgstr "" #: ../../:942 msgid "" "New placement REST API microversion 1.14 is added to support nested resource " "providers. Users of the placement REST API can now pass a ``in_tree=`` " "parameter to the ``GET /resource_providers`` REST API call. This will " "trigger the placement service to return all resource provider records within " "the \"provider tree\" of the resource provider with the supplied UUID value. " "The resource provider representation now includes a ``parent_provider_uuid`` " "value that indicates the UUID of the immediate parent resource provider, or " "``null`` if the provider has no parent. For convenience, the resource " "provider resource also contains a ``root_provider_uuid`` field that is " "populated with the UUID of the top-most resource provider in the provider " "tree." msgstr "" #: ../../:429 stable/rocky>:1521 msgid "No cell mappings are found" msgstr "" #: ../../:592 msgid "" "No changes have been made to the request or reponse parameters of the rescue " "API itself." msgstr "" #: ../../:1026 stable/queens>:1175 msgid "Node properties were modified in ironic for a deployed nodes" msgstr "" #: ../../:646 msgid "" "Note if you configure Nova to have no timeout, post copy will never be " "automatically triggered. None of this affects triggering post copy via the " "force live-migration API, that continues to work in the same way." msgstr "" #: ../../:230 stable/pike>:256 #: stable/queens>:523 stable/rocky>:915 msgid "" "Note that besides ``custom``, Nova's libvirt driver has two other CPU modes: " "``host-model`` (which is the default), and ``host-passthrough``. Refer to " "the ``[libvirt]/cpu_model_extra_flags`` documentation for what to do when " "you are using either of those CPU modes in context of 'PCID'." msgstr "" #: ../../:265 msgid "" "Note that disabling eventlet monkey-patching will cause queries across " "multiple cells to be serialized instead of running in parallel and this may " "be undesirable in a large deployment with multiple cells, for performance " "reasons." msgstr "" #: ../../:938 msgid "" "Note that file backed memory is not compatible with hugepages, and is not " "compatible with memory overcommit. If file backed memory is enabled, " "``ram_allocation_ratio`` must be configured to ``1.0``" msgstr "" #: ../../:973 msgid "" "Note that multiple paths will exist for a tagged disk for the following " "reasons:" msgstr "" #: ../../:928 msgid "" "Note that non-raw cache image files will be removed if you set " "force_raw_images = True and images_type = rbd now." msgstr "" #: ../../:211 stable/stein>:1293 msgid "" "Note that only the image owner may delete the image, so in the case of a " "shelved offloaded server, if the user unshelves or deletes the server, that " "operation will work but there will be a warning in the logs because the " "shelved snapshot image could not be deleted since the user does not own the " "image. Similarly, if an admin creates a snapshot of a server in another " "project, the admin owns the snapshot image and the non-admin project, while " "having shared image member access to see the image, cannot delete the " "snapshot." msgstr "" #: ../../:473 msgid "" "Note that the PCI devices (VFs or, alternatively, their PF) must have a " "valid PCI Vital Product Data (VPD) with a serial number present in it for " "this feature to work properly. Also note that only VFs can be tagged as " "``remote_managed: \"true\"`` and they cannot be used for legacy SR-IOV use-" "cases." msgstr "" #: ../../:2031 stable/stein>:1355 msgid "" "Note that the original fix for `bug 1414559`_ committed early in rocky was " "automatic and always enabled. Because of `bug 1786346`_ that fix has since " "been reverted and superseded by an opt-in mechanism which must be enabled. " "Setting ``[compute]/live_migration_wait_for_vif_plug=True`` will restore the " "behavior of `waiting for neutron events`_ during the live migration process." msgstr "" #: ../../:425 msgid "" "Note that this option does not apply starting in the 19.0.0 Stein release " "since the ironic compute driver no longer reports standard resource class " "inventory regardless of configuration." msgstr "" #: ../../:2069 msgid "" "Note that this option is read on the destination host of a live migration. " "If you set this option the same on all of your compute hosts, which you " "should do if you use the same networking backend universally, you do not " "have to worry about this." msgstr "" #: ../../:220 msgid "" "Note that those options are only taken into account if SPICE support is " "enabled (and the VNC support is disabled)." msgstr "" #: ../../:268 msgid "" "Note that, enable vIOMMU might introduce significant performance overhead. " "You can see performance comparision table from `AMD vIOMMU session on KVM " "Forum 2021`_. For above reason, vIOMMU should only be enable for workflow " "that require it. .. _`AMD vIOMMU session on KVM Forum 2021`: https://static." "sched.com/hosted_files/kvmforum2021/da/vIOMMU%20KVM%20Forum%202021%20-%20v4." "pdf" msgstr "" #: ../../:1428 msgid "" "Note: Under this implementation, the image data may reside in one or more " "pieces of storage of various formats on the host, but the import and export " "operations interact with a single, proxied VDI object independent of the " "underlying structure." msgstr "" #: ../../:1493 msgid "" "Nova API extension concept is removed in Pike. These extensions have their " "own policies enforcement which are not needed any more. All the below " "policies which were added mainly for extensions are deprecated for removal:" msgstr "" #: ../../:190 msgid "" "Nova APIs now `by default support new RBAC policies ` and scopes. See our `Policy " "Concepts documention ` for further details." msgstr "" #: ../../:586 msgid "" "Nova currenly does not support the following livecycle operations when " "combined with a instance using vDPA ports: shelve, resize, cold migration, " "live migration, evacuate, suspend or interface attach/detach. Attempting to " "use one of the above operations will result in a HTTP 409 (Conflict) error. " "While some operations like \"resize to same host\", shelve or attach " "interface technically work, they have been blocked since unshelve and detach " "interface currently do not. Resize to a different host has been blocked " "since its untested, evacuate has also been blocked for the same reason. " "These limitation may be removed in the future as testing is improved. Live " "migration is currently not supported with vDPA interfaces by QEMU and " "therefore cannot be enabled in openstack at this time." msgstr "" #: ../../:249 msgid "" "Nova does not support running the nova-api service under mod_wsgi or uwsgi " "in Ocata. There are some experimental scripts that have been available for " "years which allow you do to this, but doing so in Ocata results in possible " "failures to list and show instance details in a cells v2 setup. See `bug " "1661360`_ for details." msgstr "" #: ../../:1439 msgid "" "Nova is now configured to use the v3 version of the Cinder API. You need to " "ensure that the v3 version of the Cinder API is available and listed in the " "service catalog in order to use Nova with the default configuration option." msgstr "" #: ../../:515 msgid "" "Nova is now using the new Neutron port binding API to minimize network " "downtime during live migrations. See the `related spec`_ for more details." msgstr "" #: ../../:858 msgid "" "Nova leaks bandwidth resources if a bound port that has QoS minimum " "bandwidth rules is deleted in Neutron before the port is logically detached " "from the server. To avoid any leaks, users should detach the port from the " "server using the Nova API first before deleting the port in Neutron. If the " "server is in a state such that the port cannot be detached using the Nova " "API, bandwidth resources will be freed when the server is deleted. Another " "alternative to clean up the leak is to remove the " "``NET_BW_EGR_KILOBIT_PER_SEC`` and/or ``NET_BW_IGR_KILOBIT_PER_SEC`` " "allocations related to the deleted port for the server `using the CLI`_. See " "related bug https://bugs.launchpad.net/nova/+bug/1820588 for more details." msgstr "" #: ../../:846 msgid "" "Nova leaks resource allocations in placement during ``POST /servers/" "{server_id}/action (revertResize Action)`` and ``POST /servers/{server_id}/" "action (confirmResize Action)`` and ``POST /servers/{server_id}/action (os-" "migrateLive Action)`` and if the allocation held by the migration_uuid is " "modified in parallel with the lifecycle operation. Nova will log an ERROR " "and will put the server into ERROR state but will not delete the migration " "allocation. We assume that this can only happen if somebody outside of nova " "is actively changing the migration allocation in placement. Therefore it is " "not considered as a bug." msgstr "" #: ../../:1549 msgid "" "Nova network was deprecated in Newton and is no longer supported for regular " "deployments in Ocata. The network service binary will now refuse to start, " "except in the special case of CellsV1 where it is still required to function." "" msgstr "" #: ../../:513 msgid "" "Nova no longer includes Placement code. You must use the extracted Placement " "service. See the `Placement extraction upgrade instructions`_ for details." msgstr "" #: ../../:1290 msgid "" "Nova no longer supports the Block Storage (Cinder) v2 API. Ensure the " "following configuration options are set properly for Cinder v3:" msgstr "" #: ../../:1239 msgid "Nova no longer supports the deprecated Cinder v1 API." msgstr "" #: ../../:313 msgid "" "Nova now allows to create an instance with a non-deferred port that has no " "fixed IP address if the network backend has level-2 connectivity." msgstr "" #: ../../:1178 msgid "" "Nova now correctly check for guest os support via the ``hw_firmware_type`` " "image metadata property when spawning new instance and only enables ``UEFI`` " "if the guest and host support it. Guest deletion has also been updated to " "correctly clean up based on the ``UEFI`` or ``BIOS`` configuration of the vm." "" msgstr "" #: ../../:1322 msgid "" "Nova now defaults to using the live snapshot feature of libvirt when taking " "snapshots. This was previously disabled by default due to crashes on load " "seen with older libvirt versions. It has been used in production by many " "clouds, and appears stable in real world environments. If you see crashes of " "guests during snapshots, you can disable this with the " "``disable_libvirt_livesnapshot`` config value in ``[workarounds]``." msgstr "" #: ../../:105 stable/ussuri>:1320 msgid "" "Nova now has a config option called ``[workarounds]/" "never_download_image_if_on_rbd`` which helps to avoid pathological storage " "behavior with multiple ceph clusters. Currently, Nova does *not* support " "multiple ceph clusters properly, but Glance can be configured with them. If " "an instance is booted from an image residing in a ceph cluster other than " "the one Nova knows about, it will silently download it from Glance and re-" "upload the image to the local ceph privately for that instance. Unlike the " "behavior you expect when configuring Nova and Glance for ceph, Nova will " "continue to do this over and over for the same image when subsequent " "instances are booted, consuming a large amount of storage unexpectedly. The " "new workaround option will cause Nova to refuse to do this download/upload " "behavior and instead fail the instance boot. It is simply a stop-gap effort " "to allow unsupported deployments with multiple ceph clusters from silently " "consuming large amounts of disk space." msgstr "" #: ../../:1476 msgid "" "Nova now has a hard requirement that the Port Binding extension is enabled " "in the Neutron service. This simplifies the logic between Nova and Neutron." msgstr "" #: ../../:1263 msgid "" "Nova now requires Ceph/librados >= 11.1.0 if running under Python 3 with the " "RBD image backend for the libvirt driver. Requirements for Python 2 users or " "users using a different backend remain unchanged." msgstr "" #: ../../:541 msgid "" "Nova now requires that the Placement API supports at least microversion 1." "36, added in Train. The related nova-upgrade check has been modified to warn " "if this prerequisite is not fulfilled." msgstr "" #: ../../:381 msgid "" "Nova now support integration with the Lightbits Labs (http://www." "lightbitslabs.com) LightOS storage solution. LightOS is a software-defined, " "cloud native, high-performance, clustered scale-out and redundant NVMe/TCP " "storage that performs like local NVMe flash." msgstr "" #: ../../:607 msgid "" "Nova now supports a Cells v2 multi-cell deployment. The default deployment " "is a single cell. There are known `limitations with multiple cells`_. Refer " "to the `Cells v2 Layout`_ page for more information about deploying multiple " "cells." msgstr "" #: ../../:351 msgid "" "Nova now supports adding an emulated virtual `Trusted Platform Module`__ to " "libvirt guests with a ``virt_type`` of ``kvm`` or ``qemu``. Not all server " "operations are fully supported yet. See the documentation__ for details." msgstr "" #: ../../:420 msgid "" "Nova now supports attaching and detaching PCI device backed Neutron ports to " "running servers." msgstr "" #: ../../:393 msgid "" "Nova now supports defining of additional resource provider traits and " "inventories by way of YAML configuration files. The location of these files " "is defined by the new config option ``[compute]provider_config_location``. " "Nova will look in this directory for ``*.yaml`` files. See the " "`specification`__ and `admin guide`__ for more details." msgstr "" #: ../../:458 msgid "Nova now supports nested resource providers in two cases:" msgstr "" #: ../../:1315 msgid "" "Nova now uses keystoneauth1 configuration to set up communication with the " "baremetal service. Use keystoneauth1 loading parameters for auth, Session, " "and Adapter setup in the ``[ironic]`` conf section. This includes using " "``endpoint_override`` in favor of ``api_endpoint``." msgstr "" #: ../../:1304 msgid "" "Nova now uses keystoneauth1 configuration to set up communication with the " "image service. Use keystoneauth1 loading parameters for Session and Adapter " "setup in the ``[glance]`` conf section. This includes using " "``endpoint_override`` in favor of ``api_servers``. The " "``[glance]api_servers`` conf option is still supported, but should only be " "used if you need multiple endpoints and are unable to use a load balancer " "for some reason. However, note that no configuration is necessary with an " "appropriate service catalog entry for the image service." msgstr "" #: ../../:1336 msgid "" "Nova now uses keystoneauth1 configuration to set up communication with the " "network service. Use keystoneauth1 loading parameters for Adapter setup in " "the ``[neutron]`` conf section (auth and Session options continue to work as " "before). Of note:" msgstr "" #: ../../:1351 msgid "" "Nova now uses keystoneauth1 configuration to set up communication with the " "placement service. Use keystoneauth1 loading parameters for auth, Session, " "and Adapter setup in the ``[placement]`` conf section. Note that, by " "default, the 'internal' interface will be tried first, followed by the " "'public' interface. Use the conf option ``[placement].valid_interfaces`` to " "override this behavior." msgstr "" #: ../../:841 msgid "" "Nova now uses oslo.middleware for request_id processing. This means that " "there is now a new ``X-OpenStack-Request-ID`` header returned on every " "request which mirrors the content of the existing ``X-Compute-Request-ID``. " "The expected existence of this header is signaled by Microversion 2.46. If " "server version >= 2.46, you can expect to see this header in your results " "(regardless of microversion requested)." msgstr "" #: ../../:479 msgid "" "Nova operations on instances with ``VNIC_TYPE_REMOTE_MANAGED`` ports follow " "the same logic as the operations on direct SR-IOV ports." msgstr "" #: ../../:765 unmaintained/victoria>:487 msgid "" "Nova policies implemented the ``scope_type`` and new defaults provided by " "keystone. Old defaults are deprecated and still work if rules are not " "overridden in the policy file. If you don't override any policies at all, " "then you don't need to do anything different until the W release when old " "deprecated rules are removed and tokens need to be scoped to work with new " "defaults and scope of policies. For migration to new policies you can refer " "to `this document `_." msgstr "" #: ../../:887 msgid "" "Nova publishes hostnames for instances via the metadata service and config " "drives. This hostname is based on a sanitized version of the instance name " "combined with the domain value specified in ``[api] dhcp_domain``. The " "previous sanitization of the hostname included the replacement of whitespace " "and underscores with dashes and the stripping of unicode characters along " "with leading and trailing periods and dashes. It did not, however, include " "the removal of periods in the name. Periods are not valid in the hostname " "or, more specifically, in the host-specific or leaf label (the ``host`` in " "``host.example.com``) and their presence can cause conflicts when ``[api] " "dhcp_domain`` is configured, leading to instances being mistakenly " "configured with hostnames like ``host.example.com.example.com``. More " "pressingly, their use can result in a failure to boot instances if DNS " "integration is enabled in neutron, likely via designate, as the hostname is " "identified as a FQDN (fully-qualified domain name) by neutron and reasonable " "instance names like ``test-ubuntu20.04`` will be rejected as invalid FQDNs, " "in this case because the name would yield a TLD (top-level domain) of ``04`` " "and TLDs cannot be entire numerical. To avoid these issues, periods are now " "replaced with dashes." msgstr "" #: ../../:123 unmaintained/victoria>:234 msgid "" "Nova services only support old computes if the compute is not older than the " "previous major nova release. From now on nova services will emit a warning " "at startup if the deployment contains too old compute services. From the 23." "0.0 (Wallaby) release nova services will refuse to start if the deployment " "contains too old compute services to prevent compatibility issues." msgstr "" #: ../../:701 msgid "" "Nova services only support old computes if the compute is not older than the " "previous major nova release. To prevent compatibility issues at run time " "nova services will refuse to start if the deployment contains too old " "compute services." msgstr "" #: ../../:236 msgid "" "Nova started tracking PCI devices in Placement. This is an optional feature " "disabled by default while we are implementing inventory tracking and " "scheduling support for both PCI passthrough devices and SR-IOV devices " "consumed via Neutron ports. Please read our `documentation `_ for more details on what is supported how this feature can be " "enabled." msgstr "" #: ../../:1627 msgid "" "Nova support for using the Block Storage (Cinder) v2 API is now deprecated " "and will be removed in the 17.0.0 Queens release. The v3 API is now the " "default and is backward compatible with the v2 API." msgstr "" #: ../../:1205 msgid "" "Nova supports file injection of network templates. Putting these in a config " "drive is the only way to configure networking without DHCP." msgstr "" #: ../../:823 msgid "" "Nova tries to remove a volume from Ceph in a retry loop of 10 attempts at 1 " "second intervals, totaling 10 seconds overall - which, due to 30 second ceph " "watcher timeout, might result in intermittent object removal failures on " "Ceph side (`bug 1856845`_). Setting default values for ``[libvirt]/" "rbd_destroy_volume_retries`` to 12 and ``[libvirt]/" "rbd_destroy_volume_retry_interval`` to 5, now gives Ceph reasonable amount " "of time to complete the operation successfully." msgstr "" #: ../../:590 msgid "" "Nova will invoke this utility to identify available PMEM namespaces. Then " "users can specify vPMEM resources in a flavor by adding flavor's extra specs:" ":" msgstr "" #: ../../:1829 msgid "" "Nova will now internally use a new flow for new volume attachments when:" msgstr "" #: ../../:884 msgid "" "Nova will now replace periods (``.``) with dashes (``-``) when santizing an " "instance's display name for use as a hostname." msgstr "" #: ../../:173 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 "" #: ../../:413 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 "" #: ../../:111 unmaintained/zed>:376 msgid "" "Nova's use of libvirt's compareCPU() API served its purpose over the years, " "but its design limitations break live migration in subtle ways. For example, " "the compareCPU() API compares against the host physical CPUID. Some of the " "features from this CPUID aren not exposed by KVM, and then there are some " "features that KVM emulates that are not in the host CPUID. The latter can " "cause bogus live migration failures." msgstr "" #: ../../:544 msgid "" "Now nova-api and nova-api-metadata WSGI services support command line " "arguments similarly to other nova services. For example these services now " "support specifying mutliple config files via --config-file parameter. Please " "note that passing command line arguments to WSGI apps depends on the given " "WSGI runner. For example uwsgi supports this via the --pyargv parameter of " "the uwsgi binary." msgstr "" #: ../../:160 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 "" #: ../../:614 msgid "" "Now users can see the flavor extra-specs in flavor APIs response and do not " "need to call ``GET /flavors/{flavor_id}/os-extra_specs`` API. The visibility " "of the flavor extra_specs within the flavor resource will be controlled by " "the same policy rules as are used for showing the flavor extra_specs. If the " "user has no access to query extra_specs, the ``flavor.extra_specs`` will not " "be included." msgstr "" #: ../../:970 msgid "" "Now when you rebuild a baremetal instance, a new config drive will be " "generated for the node based on the passed in personality files, metadata, " "admin password, etc. This fix requires Ironic API 1.35." msgstr "" #: ../../:1559 msgid "" "OSProfiler support requires passing of trace information between various " "OpenStack services. This information is securely signed by one of HMAC keys, " "defined in nova.conf configuration file. To allow cross-project tracing user " "should use the key, that is common among all OpenStack services he or she " "wants to trace." msgstr "" #: ../../:579 msgid "" "OSProfiler support was added. This cross-project profiling library allows to " "trace various OpenStack requests through all OpenStack services that support " "it. To initiate OpenStack request tracing `--profile ` option " "needs to be added to the CLI command. This key needs to present one of the " "secret keys defined in nova.conf configuration file with `hmac_keys` option " "under the `[profiler]` configuration section. To enable or disable Nova " "profiling the appropriate `enabled` option under the same section needs to " "be set either to `True` or `False`. By default Nova will trace all API and " "RPC requests, but there is an opportunity to trace DB requests as well. For " "this purpose `trace_sqlalchemy` option needs to be set to `True`. As a " "prerequisite OSProfiler library and its storage backend needs to be " "installed to the environment. If so (and if profiling is enabled in nova." "conf) the trace can be generated via following command, for instance - `$ " "nova --profile SECRET_KEY boot --image --flavor `. At " "the end of output there will be message with , and to plot nice " "HTML graphs the following command should be used - `$ osprofiler trace show " " --html --out result.html`" msgstr "" #: ../../:540 msgid "" "Ocata contains a lot of new CellsV2 functions, but not all of it is fully " "ready for production. All deployments must set up their existing nodes as a " "cell, with database connection and MQ transport_url config items matching " "that cell. In a subsequent release, additional cells will be fully " "supported, as will a migration path for CellsV1 users. By default, an Ocata " "deployment now needs to configure at least one new \"Cell V2\" (not to be " "confused with the first version of cells). In Newton, it was possible to " "deploy a single cell V2 and schedule on it but this was optional. Now in " "Ocata, single CellsV2 deployments are mandatory. More details to be found " "when reading the release notes below." msgstr "" #: ../../:1243 msgid "" "Ocata requires that your deployment have created the cell and host mappings " "in Newton. If you have not done this, Ocata's `db sync` command will fail. " "Small deployments will want to run `nova-manage cell_v2 simple_cell_setup` " "on Newton before upgrading. Operators must create a new database for cell0 " "before running `cell_v2 simple_cell_setup`. The simple cell setup command " "expects the name of the cell0 database to be `
_cell0` as " "it will create a cell mapping for cell0 based on the main database " "connection, sync the cell0 database, and associate existing hosts and " "instances with the single cell." msgstr "" #: ../../:803 msgid "" "Older microversions will not accept these new paging query parameters, but " "they will start to silently limit by the max limit to encourage the adoption " "of this new microversion, and circumvent the existing possibility DoS-like " "usage requests on systems with thousands of instances." msgstr "" #: ../../:298 stable/queens>:1197 msgid "" "On AArch64 architecture ``cpu_mode`` for libvirt is set to ``host-" "passthrough`` by default." msgstr "" #: ../../:362 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 "" #: ../../:706 msgid "" "On some hardware platforms, an SR-IOV virtual function for a NIC port may " "exist without being associated with a parent physical function that has an " "assocatied netdev. In such a case the the PF interface name lookup will fail." " As the ``PciDeviceNotFoundById`` exception was not handled this would " "prevent the nova compute agent from starting on affected hardware. See: " "https://bugs.launchpad.net/nova/+bug/1915255 for more details. This edgecase " "has now been addressed, however, features that depend on the PF name such as " "minimum bandwidth based QoS cannot be supported on these platforms." msgstr "" #: ../../:1056 msgid "" "On the other hand, enabling it will make packing of VMs on hypervizors less " "dence even when host weighing is disabled." msgstr "" #: ../../:619 msgid "" "On upgrade operators should ensure they have not configured any of the new " "removed filters and instead should use placement to control cpu, ram and " "disk allocation ratios." msgstr "" #: ../../:1144 msgid "" "Once all compute nodes have VeNCrypt enabled, the ``auth_schemes`` parameter " "can be set to just ``['vencrypt']``." msgstr "" #: ../../:420 msgid "" "Once all data migrations are complete, you can set this option to False to " "stop reporting VCPU, MEMORY_MB and DISK_GB resource class inventory to the " "Placement service so that scheduling will only rely on the custom resource " "class for each ironic node, as described in the document above." msgstr "" #: ../../:975 msgid "" "Once fully upgraded, if you create multiple real cells with hosts, the " "scheduler will utilize them, but those instances will likely be unusable " "because not all API functions are cells-aware yet." msgstr "" #: ../../:223 stable/pike>:249 #: stable/queens>:516 stable/rocky>:908 msgid "" "One of the motivations for this is to alleviate the performance degradation " "(caused as a result of applying the \"Meltdown\" CVE fixes) for guests " "running with certain Intel-based virtual CPU models. This guest performance " "impact is reduced by exposing the CPU feature flag 'PCID' (\"Process-Context " "ID\") to the *guest* CPU, assuming that it is available in the physical " "hardware itself." msgstr "" #: ../../:584 msgid "" "Only PMEM namespaces listed in the configuration file can be used by " "instances. To identify the available PMEM namespaces on the host or create " "new namespaces, the ``ndctl`` utility can be used::" msgstr "" #: ../../:168 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 "" #: ../../:441 msgid "" "Operators can now set overcommit allocation ratios using Nova configuration " "files or the placement API, by making use of the initial allocation ratio " "configuration options. See the `initial allocation ratios`_ documentation " "for more details." msgstr "" #: ../../:649 msgid "" "Operators can specify a VGPU resource in a flavor by adding in the flavor's " "extra specs::" msgstr "" #: ../../:822 msgid "" "Operators changing the ``[compute]/max_disk_devices_to_attach`` on a compute " "service that is hosting servers should be aware that it could cause rebuilds " "to fail, if the maximum is decreased lower than the number of devices " "already attached to servers. For example, if server A has 26 devices " "attached and an operators changes ``[compute]/max_disk_devices_to_attach`` " "to 20, a request to rebuild server A will fail and go into ERROR state " "because 26 devices are already attached and exceed the new configured " "maximum of 20." msgstr "" #: ../../:1797 msgid "Operators may unset the configuration option when:" msgstr "" #: ../../:1434 msgid "" "Operators must ensure no instances are running on the compute host before " "enabling this workaround. Any instances with attached RBD volumes left " "running on the hosts will fail to migrate or stop after this workaround has " "been enabled." msgstr "" #: ../../:1411 msgid "" "Operators must ensure no instances are running on the compute host before " "enabling this workaround. Any instances with encrypted LUKSv1 disks left " "running on the hosts will fail to migrate or stop after this workaround has " "been enabled." msgstr "" #: ../../:831 msgid "" "Operators setting ``[compute]/max_disk_devices_to_attach`` should also be " "aware that during a cold migration, the configured maximum is only enforced " "in-place and the destination is not checked before the move. This means if " "an operator has set a maximum of 26 on compute host A and a maximum of 20 on " "compute host B, a cold migration of a server with 26 attached devices from " "compute host A to compute host B will succeed. Then, once the server is on " "compute host B, a subsequent request to rebuild the server will fail and go " "into ERROR state because 26 devices are already attached and exceed the " "configured maximum of 20 on compute host B." msgstr "" #: ../../:235 msgid "" "Operators should be aware that nova-api has a dependency on eventlet for " "executing parallel queries across multiple cells and is monkey-patched " "accordingly. When nova-api is running under uWSGI or mod_wsgi, the wsgi app " "will pause after idle time. While the wsgi app is paused, rabbitmq " "heartbeats will not be sent and log messages related to this can be seen in " "the nova-api logs when the wsgi app resumes when new requests arrive to the " "nova-api. These messages are not harmful. When the wsgi app resumes, oslo." "messaging will reconnect to rabbitmq and requests will be served " "successfully." msgstr "" #: ../../:205 stable/rocky>:350 #: stable/stein>:1400 msgid "" "Operators should be aware that this workaround only applies when using the " "libvirt compute driver and rbd images_type as enabled by the following " "configuration options:" msgstr "" #: ../../:1401 msgid "" "Operators should be aware that this workaround only applies when using the " "libvirt compute driver with attached encrypted Cinder volumes using the " "``luks`` encryption provider. The ``luks2`` encryption provider will " "continue to use the ``dm-crypt`` based os-brick encryptors regardless of " "what this configurable is set to." msgstr "" #: ../../:294 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 "" #: ../../:212 stable/rocky>:357 #: stable/stein>:1407 msgid "" "Operators will need to ensure that the instance directory itself, specified " "by ``[DEFAULT]/instances_path``, is not shared between computes before " "enabling this workaround, otherwise files associated with running instances " "may be removed." msgstr "" #: ../../:72 origin/stable/ocata>:1628 #: stable/2023.1>:427 stable/pike>:506 stable/pike>:1856 stable/queens>:194 #: stable/queens>:378 stable/queens>:1825 stable/rocky>:131 stable/rocky>:339 #: stable/rocky>:2044 stable/stein>:208 stable/stein>:1389 stable/train>:101 #: stable/train>:186 stable/train>:1400 stable/ussuri>:1316 #: unmaintained/wallaby>:985 unmaintained/xena>:132 unmaintained/yoga>:190 #: unmaintained/yoga>:645 unmaintained/zed>:51 unmaintained/zed>:137 msgid "Other Notes" msgstr "" #: ../../:1791 msgid "Otherwise wish to avoid immediately resetting all existing consoles" msgstr "" #: ../../:666 msgid "POST /servers/{server_id}/os-interface (attach)" msgstr "" #: ../../:660 msgid "POST /servers/{server_id}/os-volume_attachments (attach)" msgstr "" #: ../../:878 msgid "" "PUT /resource_providers/{uuid}/traits: Set all the traits for a specific " "resource provider" msgstr "" #: ../../:873 msgid "PUT /traits/{name}: To insert a single custom trait." msgstr "" #: ../../:179 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 "" #: ../../:1244 msgid "" "Parts of the compute REST API are now relying on getting information from " "cells via their mappings in the ``nova_api`` database. This is to support " "multiple cells. For example, when listing compute hosts or services, all " "cells will be iterated in the API and the results will be returned." msgstr "" #: ../../:1850 msgid "" "Physical network name will be retrieved from a multi-segement network. The " "current implementation will retrieve the physical network name for the first " "segment that provides it. This is mostly intended to support a combinatin of " "vxlan and vlan segments. Additional work will be required to support a case " "of multiple vlan segments associated with different physical networks." msgstr "" #: ../../:362 msgid "" "Physical network name will be retrieved from a multi-segment network. The " "current implementation will retrieve the physical network name for the first " "segment that provides it. This is mostly intended to support a combination " "of vxlan and vlan segments. Additional work will be required to support a " "case of multiple vlan segments associated with different physical networks." msgstr "" #: ../../:1174 msgid "" "Placement API microversion 1.18 adds support for the `required` query " "parameter to the `GET /resource_providers` API. It accepts a comma-separated " "list of string trait names. When specified, the API results will be filtered " "to include only resource providers marked with all the specified traits. " "This is in addition to (logical AND) any filtering based on other query " "parameters." msgstr "" #: ../../:1071 msgid "" "Placement API microversion 1.19 enhances the payloads for the `GET /" "resource_providers/{uuid}/aggregates` response and the `PUT /" "resource_providers/{uuid}/aggregates` request and response to be identical, " "and to include the ``resource_provider_generation``. As with other " "generation-aware APIs, if the ``resource_provider_generation`` specified in " "the `PUT` request does not match the generation known by the server, a 409 " "Conflict error is returned." msgstr "" #: ../../:1114 msgid "" "Placement microversion '1.22' adds support for expressing traits which are " "forbidden when filtering ``GET /resource_providers`` or ``GET /" "allocation_candidates``. A forbidden trait is a properly formatted trait in " "the existing ``required`` parameter, prefixed by a ``!``. For example " "``required=!STORAGE_DISK_SSD`` asks that the results not include any " "resource providers that provide solid state disk." msgstr "" #: ../../:1652 msgid "Please note you should remove these from your policy file(s)." msgstr "" #: ../../:674 unmaintained/yoga>:349 #: unmaintained/zed>:317 msgid "" "Please refer `Policy New Defaults`_ for detail about policy new defaults and " "migration plan." msgstr "" #: ../../:270 msgid "Please see the following related bugs for more details:" msgstr "" #: ../../:178 stable/pike>:328 #: stable/queens>:1234 msgid "" "Please see the mailing list thread for more information: http://lists." "openstack.org/pipermail/openstack-operators/2018-January/014748.html" msgstr "" #: ../../:690 msgid "" "Policies are default to Admin, Member and Reader roles. Old roles are also " "supproted. You can switch to new defaults via config option " "``[oslo_policy]enforce_new_defaults`` in ``nova.conf`` file." msgstr "" #: ../../:1371 msgid "" "Policy rule with name os_compute_api:os-admin-actions has been removed as it " "was never used by any API." msgstr "" #: ../../:1371 msgid "" "Ports from the physical network will have to be created with a binding " "profile to match the trusted tag. Only ports with ``binding:vif_type=" "hw_veb`` and ``binding:vnic_type=direct`` are supported." msgstr "" #: ../../:147 origin/stable/ocata>:403 #: origin/stable/ocata>:430 origin/stable/ocata>:511 stable/2023.1>:140 #: stable/2023.2>:83 stable/2024.1>:10 stable/pike>:216 stable/pike>:580 #: stable/queens>:581 stable/rocky>:499 stable/stein>:401 stable/train>:453 #: stable/ussuri>:329 unmaintained/victoria>:283 unmaintained/wallaby>:380 #: unmaintained/xena>:286 unmaintained/yoga>:240 unmaintained/zed>:159 msgid "Prelude" msgstr "" #: ../../:94 stable/2023.2>:60 stable/2024.1>:303 #: unmaintained/zed>:33 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 "" #: ../../:1611 msgid "" "Previously the PowerVM driver would default to 0.5 physical processors per " "vCPU, which is the default from the pypowervm library. The default will now " "be 0.1 physical processors per vCPU, from the ``proc_units_factor`` " "configuration option in the ``powervm`` configuration group." msgstr "" #: ../../:116 stable/train>:265 stable/ussuri>:315 #: unmaintained/victoria>:760 msgid "" "Previously, attempting to configure an instance with the ``e1000e`` or " "legacy ``VirtualE1000e`` VIF types on a host using the QEMU/KVM driver would " "result in an incorrect ``UnsupportedHardware`` exception. These interfaces " "are now correctly marked as supported." msgstr "" #: ../../:334 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 "" #: ../../:945 msgid "" "Previously, if ``vcpu_pin_set`` was not defined, the libvirt driver would " "count all available host CPUs when calculating ``VCPU`` inventory, " "regardless of whether those CPUs were online or not. The driver will now " "only report the total number of online CPUs. This should result in fewer " "build failures on hosts with offlined CPUs." msgstr "" #: ../../:845 msgid "" "Previously, if the libguestfs package was not installed, the nova-compute " "service would fallback to mounting to the local compute host file system " "which is a security exposure. This has been discussed for years in several " "forums:" msgstr "" #: ../../:767 msgid "" "Previously, it was possible to specify values for the ``hw:" "cpu_realtime_mask`` extra spec that were not within the range of valid " "instances cores. This value is now correctly validated." msgstr "" #: ../../:1208 msgid "" "Previously, setting the ``use_ipv6`` config option to ``False`` prevented " "the generation of IPv6 network info, even if there were IPv6 networks " "available. This was fine when using nova-network, where the same config " "option is used to control generation of these subnets. However, a mismatch " "between this nova option and equivalent IPv6 options in neutron would have " "resulted in IPv6 packets being dropped." msgstr "" #: ../../:1138 msgid "" "Previously, setting the ``use_ipv6`` config option to ``False`` prevented " "the generation of IPv6 rules even when there were IPv6 subnets available. " "This was fine when using nova-network, where the same config option was used " "to control generation of these subnets. However, a mismatch between this " "nova option and equivalent IPv6 options in neutron would have resulted in " "IPv6 packets being dropped." msgstr "" #: ../../:1168 msgid "" "Previously, setting the `allow_same_net_traffic` config option to `True` " "allowed for same network traffic when using these port filters. This was the " "default case and was the only case tested. Setting this to `False` disabled " "same network traffic *when using the libvirt driver port filtering " "functionality only*, however, this was neither tested nor documented." msgstr "" #: ../../:558 msgid "" "Previously, the number of concurrent snapshots was unlimited, now it is " "limited via ``[DEFAULT]/max_concurrent_snapshots``, which currently defaults " "to 5." msgstr "" #: ../../:966 msgid "" "Previously, the operation would have failed with an obscure error resulting " "in the instance still running on the source node or ending up in an " "inoperable state." msgstr "" #: ../../:964 msgid "" "Previously, when using the libvirt driver on x86 hosts, a USB controller was " "added by default to all instances even if no guest device actually required " "this controller. This has been resolved. A USB controller will now only be " "added if an input or disk device requires a USB bus." msgstr "" #: ../../:1569 msgid "" "Prior to Newton, volumes encrypted by the CryptsetupEncryptor and " "LuksEncryptor encryption providers used a mangled passphrase stripped of " "leading zeros per hexadecimal. When opening encrypted volumes, LuksEncryptor " "now attempts to replace these mangled passphrases if detected while " "CryptsetupEncryptor simply uses the mangled passphrase." msgstr "" #: ../../:1163 msgid "" "Prior to microversion 1.8 of the placement API, one could create allocations " "and not supply a project or user ID for the consumer of the allocated " "resources. While this is no longer allowed after placement API 1.8, older " "allocations exist and we now ensure that a consumer record is created for " "these older allocations. Use the two new CONF options ``CONF.placement." "incomplete_consumer_project_id`` and ``CONF.placement." "incomplete_consumer_user_id`` to control the project and user identifiers " "that are written for these incomplete consumer records." msgstr "" #: ../../:1175 msgid "" "Prior to this release Nova determined if ``UEFI`` support should be enable " "solely by checking host support as reported in `bug 1845628`_." msgstr "" #: ../../:1660 msgid "" "Privsep transitions. Nova is transitioning from using the older style " "rootwrap privilege escalation path to the new style Oslo privsep path. This " "should improve performance and security of Nova in the long term. - | " "privsep daemons are now started by nova when required. These daemons can be " "started via rootwrap if required. rootwrap configs therefore need to be " "updated to include new privsep daemon invocations." msgstr "" #: ../../:390 msgid "Python 2 is no longer supported by Nova, Python 3.6 and 3.7 are." msgstr "" #: ../../:796 msgid "" "Python 2.7 support has been dropped. The minimum version of Python now " "supported by nova is Python 3.6." msgstr "" #: ../../:423 msgid "" "Python 3.6 & 3.7 support has been dropped. The minimum version of Python now " "supported by nova is Python 3.8." msgstr "" #: ../../:952 msgid "" "QEMU 2.6.0 and Libvirt 2.2.0 allow LUKS encrypted RAW files, block devices " "and network devices (such as rbd) to be decrypted natively by QEMU. If qemu " ">= 2.6.0 and libvirt >= 2.2.0 are installed and the volume encryption " "provider is 'luks', the libvirt driver will use native QEMU decryption for " "encrypted volumes. The libvirt driver will generate a secret to hold the " "LUKS passphrase for unlocking the volume and the volume driver will use the " "secret to generate the required encryption XML for the disk. QEMU will then " "be able to read from and write to the encrypted disk natively, without the " "need of os-brick encryptors." msgstr "" #: ../../:351 msgid "" "QEMU and the Linux kernel do not currently support transparent live " "migration of vDPA devices at this time. Hot-plug live migration unplugs the " "VDPA device on the source host before the VM is live migrated and " "automatically hot-plugs the device on the destination after the migration. " "While this can lead to packet loss it enable live migration to be used when " "needed until transparent live migration can be added in a future release." msgstr "" #: ../../:119 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 "" #: ../../:199 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 "" #: ../../:460 msgid "" "QoS-enabled ports will have inventories and allocations created on nested " "resource providers from the start." msgstr "" #: ../../:1268 msgid "" "Quota limits and classes are being moved to the API database for Cells v2. " "In this release, the online data migrations will move any quota limits and " "classes you have in your main database to the API database, retaining all " "attributes." msgstr "" #: ../../:1273 msgid "" "Quota limits and classes can no longer be soft-deleted as the API database " "does not replicate the legacy soft-delete functionality from the main " "database. As such, deleted quota limits and classes are not migrated and the " "behavior users will experience will be the same as if a purge of deleted " "records was performed." msgstr "" #: ../../:1012 msgid "" "Quota usage counting from placement is opt-in via the " "``[quota]count_usage_from_placement`` configuration option." msgstr "" #: ../../:209 msgid "" "RDP protocol support from remote console API: POST /servers/{server_id}/" "remote-consoles" msgstr "" #: ../../:482 msgid "" "Refer to the `Nova Policy Concepts `_ for details and migration plan." msgstr "" #: ../../:455 msgid "" "Refer to the ``[libvirt]cpu_model_extra_flags`` documentation for more " "information." msgstr "" #: ../../:623 msgid "Refer to the `config reference documentation`__ for more information." msgstr "" #: ../../:223 stable/stein>:1305 msgid "Refer to the image API reference for details on image sharing:" msgstr "" #: ../../:69 stable/2023.2>:50 stable/2024.1>:272 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 "" #: ../../:1633 msgid "" "Remember to run ``nova-status upgrade check`` before upgrading to 18.0.0 " "Rocky to ensure baremetal instances have had their embedded flavor migrated " "to use the corresponding ironic node custom resource class." msgstr "" #: ../../:1845 msgid "Removal of technical debt from the compute service long-term" msgstr "" #: ../../:395 msgid "" "Removal of the ``nova-dhcpbridge``, ``nova-console`` and ``nova-" "xvpvncproxy`` services. See the :ref:`Upgrade Notes <21.0.0.0-upgrade-notes-" "xvncproxy>` section for more details." msgstr "" #: ../../:392 msgid "" "Removal of the ``os-consoles`` and ``os-networks`` REST APIs. See the :ref:" "`Upgrade Notes <21.0.0.0-upgrade-notes-os-consoles>` section for more " "details." msgstr "" #: ../../:989 msgid "" "Remove the old config option ``bindir`` since it was used for *nova-network* " "which had been removed." msgstr "" #: ../../:740 msgid "Requires OpenStack-API-Version placement 1.5" msgstr "" #: ../../:679 msgid "" "Rescuing an instance having vGPUs will mean that the rescue image won't use " "the existing vGPUs. When unrescuing, it will use again the existing vGPUs " "that were allocated to the instance. That said, given Nova looks at all the " "allocated vGPUs when trying to find unallocated ones, there could be a race " "condition if an instance is rescued at the moment a new instance asking for " "vGPUs is created, because both instances could use the same vGPUs. If you " "want to rescue an instance, make sure to disable the host until we fix that " "in Nova." msgstr "" #: ../../:670 msgid "" "Resizing an instance with a new flavor that has vGPU resources doesn't " "allocate those vGPUs to the instance (the instance is created without vGPU " "resources). We propose to work around this problem by rebuilding the " "instance once it has been resized so then it will have allocated vGPUs." msgstr "" #: ../../:250 unmaintained/victoria>:788 msgid "" "Resolve a race condition that may occur during concurrent ``interface detach/" "attach``, resulting in an interface accidentally unbind after attached. See " "`bug 1892870`_ for more details." msgstr "" #: ../../:244 stable/ussuri>:263 #: unmaintained/victoria>:801 msgid "" "Resolved an issue whereby providing an empty list for the ``policies`` field " "in the request body of the ``POST /os-server-groups`` API would result in a " "server error. This only affects the 2.1 to 2.63 microversions, as the 2.64 " "microversion replaces the ``policies`` list field with a ``policy`` string " "field. See `bug #1894966`__ for more information." msgstr "" #: ../../:613 msgid "RetryFilter" msgstr "" #: ../../:614 msgid "" "Return ``servers`` field always in the response of GET hypervisors API even " "there are no servers on hypervisor." msgstr "" #: ../../:731 msgid "Return codes" msgstr "" #: ../../:1552 msgid "" "Revert change I766bb5645e3b598468d092fb9e4f18e720617c52 and carry the fork " "in the scheduler code" msgstr "" #: ../../:1837 msgid "" "Running API services (nova-osapi_compute or nova-metadata) with eventlet is " "now deprecated. Deploy with a WSGI server such as uwsgi or mod_wsgi." msgstr "" #: ../../:1695 stable/queens>:1595 msgid "" "Scheduling bare metal (ironic) instances using standard resource classes " "(VCPU, memory, disk) is deprecated and will no longer be supported in Queens." " Custom resource classes should be used instead. Please refer to the " "`ironic documentation `_ for a " "detailed explanation." msgstr "" #: ../../:10 origin/stable/ocata>:58 #: origin/stable/ocata>:94 origin/stable/ocata>:125 origin/stable/ocata>:185 #: origin/stable/ocata>:330 origin/stable/ocata>:413 origin/stable/ocata>:1555 #: stable/pike>:10 stable/pike>:159 stable/pike>:226 stable/pike>:382 #: stable/pike>:449 stable/pike>:1737 stable/queens>:80 stable/queens>:300 #: stable/queens>:445 stable/queens>:1625 stable/rocky>:172 stable/rocky>:1924 #: stable/stein>:318 stable/train>:10 stable/train>:1264 stable/ussuri>:56 #: unmaintained/victoria>:118 unmaintained/wallaby>:28 #: unmaintained/wallaby>:310 unmaintained/wallaby>:837 unmaintained/xena>:612 msgid "Security Issues" msgstr "" #: ../../:1130 stable/pike>:1160 msgid "Security groups are disabled" msgstr "" #: ../../:441 unmaintained/xena>:141 #: unmaintained/yoga>:199 unmaintained/zed>:146 msgid "See `bug 1982284`_ for more details." msgstr "" #: ../../:184 msgid "See `spec`__ for more details." msgstr "" #: ../../:932 msgid "See also https://bugs.launchpad.net/nova/+bug/1661258" msgstr "" #: ../../:433 stable/rocky>:1525 msgid "See https://bugs.launchpad.net/nova/+bug/1759316 for more details." msgstr "" #: ../../:127 stable/2023.2>:270 #: unmaintained/wallaby>:20 unmaintained/xena>:20 unmaintained/yoga>:64 #: unmaintained/zed>:77 msgid "See https://bugs.launchpad.net/nova/+bug/2004555 for more details." msgstr "" #: ../../:1294 msgid "" "See https://docs.openstack.org/nova/latest/reference/notifications." "html#existing-versioned-notifications for notification samples." msgstr "" #: ../../:434 msgid "" "See related bug https://bugs.launchpad.net/nova/+bug/1796920 for more " "details." msgstr "" #: ../../:1039 msgid "" "See the `Cinder enable multiattach`_ spec for details on configuring Cinder " "for multiattach support." msgstr "" #: ../../:557 msgid "" "See the `[image_cache]/precache_concurrency` config option for more " "information about throttling this operation." msgstr "" #: ../../:764 unmaintained/yoga>:321 msgid "See the `spec`_ for more details and reasoning." msgstr "" #: ../../:985 msgid "" "See the following XenAPI documentation for details: http://xenbits.xen.org/" "docs/4.2-testing/misc/vbd-interface.txt" msgstr "" #: ../../:1145 msgid "" "Seeing as there was no apparent reason for not allowing IPv6 traffic when " "the network is IPv6-capable, we now ignore this option. Instead, we use the " "availability of IPv6-capable subnets as an indicator that IPv6 rules should " "be added." msgstr "" #: ../../:1215 msgid "" "Seeing as there was no apparent reason for not including IPv6 network info " "when IPv6 capable networks are present, we now ignore this option. Instead, " "we include info for all available networks in the template, be they IPv4 or " "IPv6." msgstr "" #: ../../:206 msgid "" "Server Action Get RDP Console: POST /servers/{server_id}/action (os-" "getRDPConsole Action)" msgstr "" #: ../../:1096 msgid "" "Setting ``placement_database.connection`` and calling ``nova-manage api_db " "sync`` will only create tables. No data will be migrated. In an existing " "OpenStack deployment, if there is existing placement data in the " "``nova_api`` database this will not be copied. It is up to the deployment to " "manually replicate that data in a fashion that works best for the " "environment." msgstr "" #: ../../:1414 msgid "" "Setting of 'nicira-iface-id' in XenServer VIF's other-config field by XenAPI " "driver has been removed to avoid VM booting timeout problem when using " "neutron polling mode. It was previously deprecated in Pike." msgstr "" #: ../../:522 msgid "" "Several REST APIs specific to nova-network were removed and the core " "functionality of nova-network is planned to be removed in the 19.0.0 Stein " "release." msgstr "" #: ../../:1513 msgid "Show & List detail image" msgstr "" #: ../../:1498 msgid "Show & List detail server" msgstr "" #: ../../:1154 msgid "Show & List image details" msgstr "" #: ../../:1139 msgid "Show & List server details" msgstr "" #: ../../:214 msgid "" "Show Console Connection Information: GET /os-console-auth-tokens/" "{console_token}" msgstr "" #: ../../:1624 msgid "" "Similarly, the ``ironic_host_manager`` choice for the ``[scheduler]/" "host_manager`` configuration option was deprecated in the 17.0.0 Queens " "release because ``ironic_host_manager`` is only useful when using " "``use_baremetal_filters=True`` and ``baremetal_enabled_filters``. Now that " "those options are gone, the deprecated ``ironic_host_manager`` host manager " "choice has also been removed. As a result, the ``[scheduler]/host_manager`` " "configuration option has also been removed since there is only one host " "manager now and no need for an option." msgstr "" #: ../../:250 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 "" #: ../../:31 stable/stein>:65 stable/train>:216 #: stable/ussuri>:227 unmaintained/victoria>:712 msgid "" "Since Libvirt v.1.12.0 and the introduction of the `libvirt issue`_ , there " "is a fact that if we set cache mode whose write semantic is not O_DIRECT (i." "e. \"unsafe\", \"writeback\" or \"writethrough\"), there will be a problem " "with the volume drivers (i.e. LibvirtISCSIVolumeDriver, " "LibvirtNFSVolumeDriver and so on), which designate native io explicitly." msgstr "" #: ../../:994 msgid "" "Since `blueprint placement-claims`_ in Pike, the FilterScheduler uses the " "Placement service to create resource allocations (claims) against a resource " "provider (i.e. compute node) chosen by the scheduler. That reduces the risk " "of scheduling collisions when running multiple schedulers." msgstr "" #: ../../:1000 msgid "" "Since other scheduler drivers, like the CachingScheduler, do not use " "Placement, it is recommended to set workers=1 (default) for those other " "scheduler drivers." msgstr "" #: ../../:811 msgid "" "Since the 16.0.0 (Pike) release, nova has collected NIC feature flags via " "libvirt. To look up the NIC feature flags for a whitelisted PCI device the " "nova libvirt driver computed the libvirt nodedev name by rendering a format " "string using the netdev name associated with the interface and its current " "MAC address. In some environments the libvirt nodedev list can become out of " "sync with the current MAC address assigned to a netdev and as a result the " "nodedev look up can fail. Nova now uses PCI addresses, rather than MAC " "addresses, to look up these PCI network devices." msgstr "" #: ../../:1362 msgid "" "Since the Placement service is now mandatory in Ocata, you need to deploy it " "and amend your compute node configuration with correct placement " "instructions before restarting nova-compute or the compute node will refuse " "to start." msgstr "" #: ../../:1453 msgid "" "Since we now use Placement to verify basic CPU/RAM/disk resources when using " "the FilterScheduler, the ``RamFilter`` and ``DiskFilter`` entries are being " "removed from the default value for the ``enabled_filters`` config option in " "the ``[filter_scheduler]`` group. If you are overriding this option, you " "probably should remove them from your version. If you are using " "CachingScheduler you may wish to enable these filters as we will not use " "Placement in that case." msgstr "" #: ../../:21 stable/2023.2>:14 stable/2024.1>:264 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 "" #: ../../:772 msgid "" "Some hypervisors add a signature to their guests, e.g. KVM is adding " "``KVMKVMKVM\\0\\0\\0``, Xen: ``XenVMMXenVMM``. The existence of a hypervisor " "signature enables some paravirtualization features on the guest as well as " "disallowing certain drivers which test for the hypervisor to load e.g. " "Nvidia driver [1]: \"The latest Nvidia driver (337.88) specifically checks " "for KVM as the hypervisor and reports Code 43 for the driver in a Windows " "guest when found. Removing or changing the KVM signature is sufficient for " "the driver to load and work.\"" msgstr "" #: ../../:599 msgid "Some of the `multi-cell cells v2 caveats`_ have been resolved." msgstr "" #: ../../:1647 msgid "Some unused policies have been deprecated. These are:" msgstr "" #: ../../:961 msgid "" "Source or destination compute node does not support libvirt-sriov-live-" "migration." msgstr "" #: ../../:708 msgid "" "Specifying an availability zone is only allowed when the server status is " "``SHELVED_OFFLOADED`` otherwise a 409 HTTPConflict response is returned." msgstr "" #: ../../:587 msgid "" "Stable device rescue for boot from volume instances is now supported through " "the use of the 2.87 microversion when the compute hosting the instance also " "reports the ``COMPUTE_RESCUE_BFV`` trait such as the libvirt driver." msgstr "" #: ../../:161 stable/pike>:311 #: stable/queens>:1217 msgid "" "Starting in Ocata, there is a behavior change where aggregate-based " "overcommit ratios will no longer be honored during scheduling for the " "FilterScheduler. Instead, overcommit values must be set on a per-compute-" "node basis in the Nova configuration files." msgstr "" #: ../../:407 msgid "" "Starting in the 16.0.0 Pike release, ironic nodes can be scheduled using " "custom resource classes rather than the standard resource classes VCPU, " "MEMORY_MB and DISK_GB:" msgstr "" #: ../../:813 msgid "" "Starting in the Ussuri release, compute node resource providers are " "automatically marked with the ``COMPUTE_NODE`` trait. This allows them to be " "distinguished easily from other providers, including sharing and nested " "providers, as well as other non-compute-related providers in a deployment. " "To make effective use of this trait (e.g. for scheduling purposes), all " "compute nodes must be upgrade to Ussuri. Alternatively, you can manually add " "the trait to pre-Ussuri compute node providers via `openstack resource " "provider trait set `_" msgstr "" #: ../../:707 msgid "" "Starting with the 2.71 microversion the ``server_groups`` parameter will be " "in the response body of the following APIs to list the server groups to " "which the server belongs:" msgstr "" #: ../../:225 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 "" #: ../../:675 msgid "" "Such as, for the CPUWeigher, it weighs hosts based on available vCPUs on the " "compute node, and multiplies it by the cpu weight multiplier. If per-" "aggregate value (which the key is \"cpu_weight_multiplier\") is found, this " "value would be chosen as the cpu weight multiplier. Otherwise, it will fall " "back to the ``[filter_scheduler]/cpu_weight_multiplier``. If more than one " "value is found for a host in aggregate metadata, the minimum value will be " "used." msgstr "" #: ../../:1198 msgid "" "Support for **hw_watchdog_action** as a flavor extra spec has been removed. " "The valid flavor extra spec is **hw:watchdog_action** and the image " "property, which takes precedence, is **hw_watchdog_action**." msgstr "" #: ../../:1604 msgid "" "Support for Windows / Hyper-V Server 2012 has been deprecated in Queens in " "nova and will be removed in Rocky. The supported versions are Windows / " "Hyper-V Server 2012 R2 or newer." msgstr "" #: ../../:501 msgid "" "Support for `VPMEM (Virtual Persistent Memory) `_ when using the libvirt " "compute driver. This provides data persistence across power cycles at a " "lower cost and with much larger capacities than DRAM, especially benefitting " "HPC and memory databases such as redis, rocksdb, oracle, SAP HANA, and " "Aerospike." msgstr "" #: ../../:352 msgid "" "Support for `cold migrating and resizing servers between Nova cells`__." msgstr "" #: ../../:373 msgid "Support for `creating servers with accelerator devices via Cyborg`__." msgstr "" #: ../../:386 msgid "Support for `heterogenous virtual GPU types per compute node`__." msgstr "" #: ../../:300 msgid "" "Support for a new ``mixed`` `flavor CPU allocation policy`__ that allows " "both pinned and floating CPUs within the same instance." msgstr "" #: ../../:592 msgid "" "Support for archiving all deleted rows from the database has been added to " "the ``nova-manage db archive_deleted_rows`` command. The ``--until-" "complete`` option will continuously run the process until no more rows are " "available for archiving." msgstr "" #: ../../:619 msgid "" "Support for archiving deleted rows from the database across all cells has " "been added to the ``nova-manage db archive_deleted_rows`` command. Specify " "the ``--all-cells`` option to run the process across all existing cells. It " "is only possible to archive all DBs from a node where the ``[api_database]/" "connection`` option is configured." msgstr "" #: ../../:495 msgid "" "Support for automatically retrying all database interactions by configuring " "the ``[database] use_db_reconnect`` config option has been removed. This " "behavior was only ever supported for interactions with the main database and " "was generally not necessary as a number of lookups were already explicitly " "wrapped in retries. The ``[database] use_db_reconnect`` option is provided " "by oslo.db and will now be ignored by nova." msgstr "" #: ../../:477 msgid "" "Support for cold migrating and resizing servers with bandwidth-aware " "`Quality of Service ports `_ attached." msgstr "" #: ../../:70 unmaintained/wallaby>:971 msgid "" "Support for cold migration and resize between hosts with different network " "backends was previously incomplete. If the os-vif plugin for all network " "backends available in the cloud are not installed on all nodes unplugging " "will fail during confirming the resize. The issue is caused by the VIF " "unplug that happened during the resize confirm action on the source host " "when the original backend information of the VIF was not available. The fix " "moved the unplug to happen during the resize action when such information is " "still available. See `bug #1895220`_ for more details." msgstr "" #: ../../:708 msgid "" "Support for custom scheduler drivers, deprecated since the 21.0.0 (Ussuri) " "release, has been removed. The default ``filter_scheduler`` is now " "considered performant enough to suit all use cases. Users with specific " "requirements that they feel are not met by the filter scheduler should " "contact the nova developers to discuss their issue." msgstr "" #: ../../:1265 msgid "" "Support for filtering out disabled cells during scheduling for server create " "requests has been added. Firstly the concept of disabled cells has been " "introduced which means such disabled cells will not be candidates for the " "scheduler. Secondly changes have been made to the filter scheduler to ensure " "that it chooses only the enabled cells for scheduling and filters out the " "disabled ones. Note that operations on existing instances already inside a " "disabled cell like move operations will not be blocked." msgstr "" #: ../../:564 msgid "" "Support for hooks has been removed. In previous versions of nova, these " "provided a mechanism to extend nova with custom code through a plugin " "mechanism. However, they were deprecated in 13.0.0 (Mitaka) as " "unmaintainable long-term. `Versioned notifications`__ and `vendordata`__ " "should be used instead. For more information, refer to `this thread`__." msgstr "" #: ../../:366 msgid "" "Support for scope types and additional roles in the default nova policies, " "allowing for richer access management including the ability to configure " "*read-only* access to resources. This feature is disabled by default. See " "the `Policy Concepts`__ documentation for more details." msgstr "" #: ../../:535 msgid "" "Support for the ``qos-queue`` extension provided by the vmware-nsx neutron " "plugin for the VMWare NSX Manager has been removed. This extension was " "removed from the vmware-nsx project when support for NSX-MH was removed in " "15.0.0." msgstr "" #: ../../:320 msgid "" "Support for the ``xen``, ``uml``, ``lxc`` and ``parallels`` libvirt backends " "has been deprecated." msgstr "" #: ../../:691 msgid "" "Support for the ``xen``, ``uml``, ``lxc`` and ``parallels`` libvirt " "backends, configured via the ``[libvirt] virt_type`` config option, has been " "deprecated. None of these drivers have upstream testing and the ``xen`` and " "``uml`` backends specifically have never been considered production ready. " "With this change, only the ``kvm`` and ``qemu`` backends are considered " "supported when using the libvirt virt driver." msgstr "" #: ../../:597 msgid "" "Support for the deprecated options will be removed in a future release." msgstr "" #: ../../:632 msgid "" "Support for the libvirt+UML hypervisor model has been removed. This has not " "been validated in some time and was never intended for production use." msgstr "" #: ../../:637 msgid "" "Support for the libvirt+xen hypervisor model has been removed. This has not " "been validated in some time and was not supported." msgstr "" #: ../../:273 msgid "" "Support is added for network backends that leverage SmartNICs to `offload " "the control plane from the host server`__. Accordingly, Neutron needs to be " "`configured`__ in order to enable it correctly. Increased security is " "enabled by removing the control plane from the host server and overhead is " "reduced by leveraging the cpu and ram resources on modern SmartNIC DPUs." msgstr "" #: ../../:1820 msgid "" "Support to monitor performance events for Intel CMT (Cache Monitoring " "Technology, or \"CQM\" in Linux kernel parlance) -- namely ``cmt``, " "``mbm_local`` and ``mbm_total`` -- via the config attribute ``[libvirt]/" "enabled_perf_events`` is now *deprecated* from Nova, and will be *removed* " "in the \"Stein\" release. Otherwise, if you have enabled those events, and " "upgraded to Linux kernel 4.14 (or suitable downstream version), it will " "result in instances failing to boot." msgstr "" #: ../../:603 msgid "" "Support versioned notifications for flavor operations like create, delete, " "update access and update extra_specs." msgstr "" #: ../../:495 msgid "" "Support was added to specify a port NUMA affinity policy for SR-IOV ports. " "This feature allows users to set a NUMA affinity policy between a neutron " "port and a NUMA guest's CPUs and memory. This feature supports the same " "policies as the existing VM Scoped PCI NUMA Affinity policy and take " "precedence over the flavor and image policy. This allows operators to set a " "default affinity policy in the flavor or image while end users can express a " "more granular affinity policy. To use this feature operators must enable the " "``port-numa-affinity-policy`` neutron extension and configure the service " "plugin in neutron. By default the extension is listed as available but is " "not enabled." msgstr "" #: ../../:726 msgid "" "Supports a new method for deleting all inventory for a resource provider" msgstr "" #: ../../:711 msgid "" "Supports instance rescue and unrescue with ironic virt driver. This feature " "requires an ironic service supporting API version 1.38 or later, which is " "present in ironic releases >= 10.1. It also requires python-ironicclient >= " "2.3.0." msgstr "" #: ../../:662 msgid "" "Suspending a guest having vGPUs doesn't work yet given a libvirt concern (it " "can't hot-unplug mediated devices from a guest). Workarounds using other " "instance actions (like snapshotting the instance or shelving it) are " "recommended until libvirt supports that. If a user asks to suspend the " "instance, Nova will get an exception that will set the instance state back " "to ``ACTIVE``, and you can see the suspend action in ``os-instance-action`` " "API will be Error." msgstr "" #: ../../:304 msgid "" "Switch to using the extracted placement. It does not suffer from eventlet." msgstr "" #: ../../:952 msgid "" "Tagged volume attachment is not supported for shelved-offloaded instances. " "Tagged device attachment (both volumes and network interfaces) is not " "supported for Cells V1 deployments." msgstr "" #: ../../:1828 msgid "" "That is because the Linux kernel has deleted the `perf` framework " "integration with Intel CMT, as the feature was broken by design -- an " "incompatibility between Linux's `perf` infrastructure and Intel CMT. It was " "removed in upstream Linux version v4.14; but bear in mind that downstream " "Linux distributions with lower kernel versions than 4.14 have backported the " "said change." msgstr "" #: ../../:654 msgid "That said, Nova currently has some caveats for using vGPUs." msgstr "" #: ../../:525 stable/pike>:594 #: stable/queens>:590 stable/rocky>:508 msgid "" "That said, a few major changes are worth mentioning. This is not an " "exhaustive list:" msgstr "" #: ../../:471 msgid "" "That will cleanup the ``project_user_quotas``, ``quota_usages`` and " "``reservations`` tables for the given project in the ``nova`` database and " "reset the quota limits for the project back to the defaults defined in nova." "conf." msgstr "" #: ../../:479 msgid "" "The \"API unexpected exception\" message can now be configured by the cloud " "provider to point to a custom support page. By default it continues to show " "\"http://bugs.launchpad.net/nova/\". It can be configured using the release " "file." msgstr "" #: ../../:776 msgid "" "The \"tunnelled live migration\" has two inherent limitations: (a) it cannot " "handle live migration of disks in a non-shared storage setup, and (b) it has " "a huge performance overhead and latency, because it burns more CPU and " "memory during live migration." msgstr "" #: ../../:1370 msgid "" "The ''use_local'' option, which made it possible to perform nova-conductor " "operations locally, has been removed. This legacy mode was introduced to " "bridge a gap during the transition to the conductor service. It no longer " "represents a reasonable alternative for deployers." msgstr "" #: ../../:62 stable/queens>:347 msgid "" "The 'AMD-SSBD' and 'AMD-NO-SSB' flags have been added to the list of " "available choices for the ``[libvirt]/cpu_model_extra_flags`` config option. " "These are important for proper mitigation of security issues in AMD CPUs. " "For more information see https://www.redhat.com/archives/libvir-list/2018-" "June/msg01111.html" msgstr "" #: ../../:129 stable/pike>:183 #: stable/queens>:449 msgid "" "The 'SSBD' and 'VIRT-SSBD' cpu flags have been added to the list of " "available choices for the ``[libvirt]/cpu_model_extra_flags`` config option. " "These are important for proper mitigation of the Spectre 3a and 4 CVEs. Note " "that the use of either of these flags require updated packages below nova, " "including libvirt, qemu (specifically >=2.9.0 for virt-ssbd), linux, and " "system firmware. For more information see https://www.us-cert.gov/ncas/" "alerts/TA18-141A" msgstr "" #: ../../:1457 msgid "" "The *TrustedFilter* along with its related ``[trusted_computing]`` " "configuration options were deprecated in the 16.0.0 Pike release and have " "been removed in the 17.0.0 Queens release. The *TrustedFilter* was always " "experimental, had no continuous integration testing to prove it still " "worked, and no reported users." msgstr "" #: ../../:1832 msgid "The *block-storage* 3.44 API microversion is available" msgstr "" #: ../../:1065 msgid "" "The *cells v1* feature has been deprecated since the 16.0.0 Pike release and " "has now been removed. The ``nova-cells`` service and ``nova-manage cells`` " "commands have been removed, while the ``nova-manage cell_v2 " "simple_cell_setup`` command will no longer check if cells v1 is enabled and " "therefore can no longer exit with ``2``." msgstr "" #: ../../:1071 msgid "" "The *cells v1* specific REST APIs have been removed along with their related " "policy rules. Calling these APIs will now result in a ``410 (Gone)`` error " "response." msgstr "" #: ../../:1091 msgid "" "The *cells v1* specific configuration options, previously found in " "``cells``, have been removed." msgstr "" #: ../../:1086 msgid "The *cells v1* specific policies have been removed." msgstr "" #: ../../:856 msgid "" "The *nova-network* feature has been deprecated since the 14.0.0 (Newton) " "release and has now been removed. The remaining *nova-network* specific REST " "APIs have been removed along with their related policy rules. Calling these " "APIs will now result in a ``410 (Gone)`` error response." msgstr "" #: ../../:1466 msgid "" "The *nova-network* service has been deprecated since the 14.0.0 Newton " "release and now the following *nova-network* specific REST APIs have been " "removed along with their related policy rules. Calling these APIs will now " "result in a ``410 HTTPGone`` error response." msgstr "" #: ../../:1125 msgid "" "The *nova-novncproxy* server can now be configured to do a security " "negotiation with the compute node VNC server. If the VeNCrypt auth scheme is " "enabled, this establishes a TLS session to provide encryption of all data. " "The proxy will validate the x509 certs issued by the remote server to ensure " "it is connecting to a valid compute node. The proxy can also send its own " "x509 cert to allow the compute node to validate that the connection comes " "from the official proxy server." msgstr "" #: ../../:797 msgid "" "The 1.12 version of the placement API changes handling of the `PUT /" "allocations/{consumer_uuid}` request to use a dict-based structure for the " "JSON request body to make it more aligned with the response body of `GET /" "allocations/{consumer_uuid}`. Because `PUT` requires `user_id` and " "`project_id` in the request body, these fields are added to the `GET` " "response. In addition, the response body for ``GET /allocation_candidates`` " "is updated so the allocations in the ``allocation_requests`` object work " "with the new `PUT` format." msgstr "" #: ../../:804 msgid "" "The 1.7 version of the placement API changes handling of `PUT /" "resource_classes/{name}` to be a create or verification of the resource " "class with `{name}`. If the resource class is a custom resource class and " "does not already exist it will be created and a ``201`` response code " "returned. If the class already exists the response code will be ``204``. " "This makes it possible to check or create a resource class in one request." msgstr "" #: ../../:520 msgid "" "The 15.0.0 release includes many new features and bug fixes. It is difficult " "to cover all the changes that have been introduced. Please at least read the " "upgrade section which describes the required actions to upgrade your cloud " "from 14.0.0 (Newton) to 15.0.0 (Ocata)." msgstr "" #: ../../:434 msgid "" "The 15.0.1 Ocata release contains fixes for several high severity, high " "impact bugs. If you have not yet upgraded to 15.0.0, it is recommended to " "upgrade directly to 15.0.1." msgstr "" #: ../../:589 msgid "" "The 16.0.0 release includes many new features and bug fixes. It is difficult " "to cover all the changes that have been introduced. Please at least read the " "upgrade section which describes the required actions to upgrade your cloud " "from 15.0.0 (Ocata) to 16.0.0 (Pike)." msgstr "" #: ../../:585 msgid "" "The 17.0.0 release includes many new features and bug fixes. It is difficult " "to cover all the changes that have been introduced. Please at least read the " "upgrade section which describes the required actions to upgrade your cloud " "from 16.0.0 (Pike) to 17.0.0 (Queens)." msgstr "" #: ../../:503 msgid "" "The 18.0.0 release includes many new features and bug fixes. It is difficult " "to cover all the changes that have been introduced. Please at least read the " "upgrade section which describes the required actions to upgrade your cloud " "from 17.0.0 (Queens) to 18.0.0 (Rocky)." msgstr "" #: ../../:405 msgid "" "The 19.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 18.0.0 (Rocky) to 19.0.0 (Stein)." msgstr "" #: ../../:1895 msgid "" "The 2.45 microversion is introduced which changes the response for the " "``createImage`` and ``createBackup`` server action APIs to no longer return " "a ``Location`` response header. With microversion 2.45 those APIs now return " "a json dict in the response body with a single ``image_id`` key whose value " "is the snapshot image ID (a uuid). The old ``Location`` header in the " "response before microversion 2.45 is most likely broken and inaccessible by " "end users since it relies on the internal Glance API server configuration " "and does not take into account Glance API versions." msgstr "" #: ../../:833 msgid "" "The 2.51 microversion exposes the ``events`` field in the response body for " "the ``GET /servers/{server_id}/os-instance-actions/{request_id}`` API. This " "is useful for API users to monitor when a volume extend operation completes " "for the given server instance. By default only users with the administrator " "role will be able to see event ``traceback`` details." msgstr "" #: ../../:753 msgid "The 2.57 microversion makes the following changes:" msgstr "" #: ../../:1299 msgid "" "The 2.63 compute REST API microversion adds support for the " "``trusted_image_certificates`` parameter, which is used to define a list of " "trusted certificate IDs that can be used during image signature verification " "and certificate validation. The list is restricted to a maximum of 50 IDs. " "Note that there is not support with volume-backed servers." msgstr "" #: ../../:431 msgid "" "The 2.69 compute API microversion adds handling of server details in the " "presence of down or poor-performing cells in a multi-cell environment for " "the ``GET /servers``, ``GET /servers/detail``, ``GET /servers/{server_id}``, " "``GET /os-services`` REST APIs. See the `handling down cells`_ documentation " "for more details." msgstr "" #: ../../:652 msgid "" "The 2.70 compute API microversion exposes virtual device tags for volume " "attachments and virtual interfaces (ports). A ``tag`` parameter is added to " "the response body for the following APIs:" msgstr "" #: ../../:498 msgid "" "The 2.86 microversion adds support for flavor extra spec validation when " "creating or updating flavor extra specs. Use of an unrecognized or invalid " "flavor extra spec in the following namespaces will result in a HTTP 400 " "response." msgstr "" #: ../../:802 msgid "" "The 2.88 API microversion has been added. This microversion removes a number " "of fields have been removed from the ``GET /os-hypervisors/detail`` " "(detailed list) and ``GET /os-hypervisors/{hypervisor_id}`` (show) APIs::" msgstr "" #: ../../:421 msgid "" "The 2.90 microversion has been added. This microversion allows users to " "specify a requested hostname to be configured for the instance metadata when " "creating an instance (``POST /servers``), updating an instance (``PUT /" "servers/{id}``), or rebuilding an instance (``POST /servers/{server_id}/" "action (rebuild)``). When specified, this hostname replaces the hostname " "that nova auto-generates from the instance display name. As with the auto-" "generated hostnames, a service such as ``cloud-init`` can automatically " "configure the hostname in the guest OS using this information retrieved from " "the metadata service." msgstr "" #: ../../:226 msgid "The 2.92 microversion makes the following changes:" msgstr "" #: ../../:258 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 "" #: ../../:166 msgid "" "The 2.96 microversion has been added. This microversion adds " "pinned_availability_zone in `server show` and `server list --long` responses." "" msgstr "" #: ../../:457 msgid "" "The 20.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 19.0.0 (Stein) to 20.0.0 (Train)." msgstr "" #: ../../:333 msgid "" "The 21.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 20.0.0 (Train) to 21.0.0 (Ussuri)." msgstr "" #: ../../:287 msgid "" "The 22.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 21.0.0 (Ussuri) to 22.0.0 (Victoria)." msgstr "" #: ../../:384 msgid "" "The 23.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 22.0.0 (Victoria) to 23.0.0 (Wallaby)." msgstr "" #: ../../:290 msgid "" "The 24.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 23.0.0 (Wallaby) to 24.0.0 (Xena)." msgstr "" #: ../../:244 msgid "" "The 25.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 24.0.0 (Xena) to 25.0.0 (Yoga)." msgstr "" #: ../../:163 msgid "" "The 26.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 25.0.0 (Yoga) to 26.0.0 (Zed)." msgstr "" #: ../../:1726 msgid "" "The CachingScheduler and ChanceScheduler drivers are deprecated in Pike. " "These are not integrated with the placement service, and their primary " "purpose (speed over correctness) should be addressed by the default " "FilterScheduler going forward. If ChanceScheduler behavior is desired (i.e. " "speed trumps correctness) then configuring the FilterScheduler with no " "enabled filters should approximate that behavior." msgstr "" #: ../../:640 msgid "" "The Compute API will return a 400 (Bad Request) response to a request to " "directly boot an image created from an encrypted volume." msgstr "" #: ../../:36 stable/rocky>:57 stable/stein>:134 #: stable/train>:323 stable/ussuri>:1237 msgid "" "The Compute service has never supported direct booting of an instance from " "an image that was created by the Block Storage service from an encrypted " "volume. Previously, this operation would result in an ACTIVE instance that " "was unusable. Beginning with this release, an attempt to boot from such an " "image will result in the Compute API returning a 400 (Bad Request) response." msgstr "" #: ../../:600 msgid "" "The FilterScheduler driver now provides allocations to the Placement API, " "which helps concurrent schedulers to verify resource consumptions directly " "without waiting for compute services to ask for a reschedule in case of a " "race condition. That is an important performance improvement that includes " "allowing one to use more than one scheduler worker if there are capacity " "concerns. For more details, see the `Pike Upgrade Notes for Placement`_." msgstr "" #: ../../:992 stable/rocky>:860 msgid "" "The FilterScheduler is currently the only scheduler driver that supports " "this feature." msgstr "" #: ../../:1790 msgid "" "The FilterScheduler now limits the number of results in the query it makes " "to placement to avoid situations where every compute node in a large " "deployment is returned. This is configurable with the new ``[scheduler]/" "max_placement_results`` configuration option, which defaults to 1000, a sane " "starting value for any size deployment." msgstr "" #: ../../:510 msgid "" "The Hyper-V driver can now attach Cinder RBD volumes. The minimum " "requirements are Ceph 16 (Pacific) and Windows Server 2016." msgstr "" #: ../../:1583 msgid "" "The Hyper-V driver no longer accepts cold migrating instances to the same " "host. Note that this does not apply to resizes, in which case this is still " "allowed." msgstr "" #: ../../:607 msgid "" "The Hyper-V driver now supports the following quota flavor extra specs, " "allowing to specify IO limits applied for each of the instance local disks, " "individually." msgstr "" #: ../../:624 msgid "" "The Hyper-V driver now uses os-brick for volume related operations, " "introducing the following new features:" msgstr "" #: ../../:413 msgid "The Hyper-V virt driver can now attach Cinder RBD volumes." msgstr "" #: ../../:80 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 "" #: ../../:105 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 "" #: ../../:31 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 "" #: ../../:1204 msgid "" "The Ironic driver now requires python-ironicclient>=1.9.0, and requires " "Ironic service to support API version 1.28 or higher. As usual, Ironic " "should be upgraded before Nova for a smooth upgrade process." msgstr "" #: ../../:1176 msgid "" "The Libvirt SR-IOV migration feature intoduced in this release requires both " "the source and destination node to support the feature. As a result it will " "be automatically disabled until the conductor and compute nodes have been " "upgraded." msgstr "" #: ../../:255 msgid "" "The Libvirt driver can now add a virtual IOMMU device to all created guests, " "when running on an x86 host and using the Q35 machine type or on AArch64." msgstr "" #: ../../:531 msgid "" "The Nova FilterScheduler driver is now able to make scheduling decisions " "based on the new Placement RESTful API endpoint that becomes mandatory in " "Ocata. Accordingly, the compute nodes will refuse to start if you do not " "amend the configuration to add the ``[placement]`` section so they can " "provide their resource usage. For the moment, only CPU, RAM and disk " "resource usage are verified by the Placement API, but we plan to add more " "resource classes in the next release. You will find further details in the " "features and upgrade sections below, and the `Placement API`_ page." msgstr "" #: ../../:289 msgid "" "The Nova policies have been modified to drop the system scope. Every API " "policy is scoped to project. This means that system scoped users will get " "403 permission denied error." msgstr "" #: ../../:327 msgid "" "The Nova policies have been modified to isolate the system and project level " "APIs policy. This means system users will be allowed to perform the " "operation on system level resources and will not to allowed any operation on " "project level resources. Project Level APIs operation will be performed by " "the project scoped users. Currently, nova supports:" msgstr "" #: ../../:482 msgid "" "The Nova policies implemented the scope concept and new default roles " "(``admin``, ``member``, and ``reader``) provided by keystone." msgstr "" #: ../../:301 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 "" #: ../../:144 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 "" #: ../../:87 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 "" #: ../../:14 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 "" #: ../../:1632 stable/pike>:1906 msgid "" "The Placement API can be set to connect to a specific keystone endpoint " "interface using the ``os_interface`` option in the ``[placement]`` section " "inside ``nova.conf``. This value is not required but can be used if a non-" "default endpoint interface is desired for connecting to the Placement " "service. By default, keystoneauth will connect to the \"public\" endpoint." msgstr "" #: ../../:1195 msgid "" "The PowerVM driver now supports hot plugging/unplugging of network " "interfaces." msgstr "" #: ../../:1200 msgid "" "The PowerVM virt driver now supports booting from local ephemeral disk. Two " "new configuration options have been introduced to the ``powervm`` " "configuration group, ``disk_driver`` and ``volume_group_name``. The former " "allows the selection of either ssp or localdisk for the PowerVM disk driver. " "The latter specifies the name of the volume group when using the localdisk " "disk driver." msgstr "" #: ../../:1209 msgid "The PowerVM virt driver now supports instance snapshot." msgstr "" #: ../../:1213 msgid "" "The PowerVM virt driver now supports vSCSI Fibre Channel cinder volumes. " "PowerVM now supports attaching, detaching, and extending the size of vSCSI " "FC cinder volumes." msgstr "" #: ../../:1599 msgid "" "The PowerVM virt driver previously used the PowerVM Shared Storage Pool disk " "driver by default. The default disk driver for PowerVM is now localdisk. See " "configuration option ``[powervm]/disk_driver`` for usage details." msgstr "" #: ../../:841 msgid "" "The Quobyte Nova volume driver now supports identifying Quobyte mounts via " "the mounts fstype field, which is used by Quobyte 2.x clients. The previous " "behaviour is deprecated and may be removed from the Quobyte clients in the " "future." msgstr "" #: ../../:201 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 "" #: ../../:557 stable/rocky>:2009 msgid "" "The SchedulerReportClient (``nova.scheduler.client.report." "SchedulerReportClient``) sends requests with the global request ID in the " "``X-Openstack-Request-Id`` header to the placement service. `Bug 1734625`_" msgstr "" #: ../../:722 msgid "" "The UEFI Secure Boot feature can be requested through the image property " "\"os_secure_boot\" (acceptable values: \"disabled\", \"optional\", " "\"required\") or flavor extra spec \"os:secure_boot\" (acceptable values: " "\"disabled\", \"required\"). The flavor extra spec will take precedence. If " "the image property and the flavor extra spec values are conflicting, then an " "exception is raised." msgstr "" #: ../../:741 msgid "" "The URLs in cell mapping records may now include variables that are filled " "from the corresponding default URL specified in the host's configuration " "file. This allows per-host credentials, as well as other values to be set in " "the config file which will affect the URL of a cell, as calculated when " "loading the record. For ``database_connection``, the ``[database]/" "connection`` URL is used as the base. For ``transport_url``, the ``[DEFAULT]/" "transport_url`` is used. For more information, see the cells configuration " "docs: https://docs.openstack.org/nova/latest/user/cells.html" msgstr "" #: ../../:796 msgid "" "The VMware compute driver now supports live migration. Each compute node " "must be managing a cluster in the same vCenter and ESX hosts must have " "vMotion enabled." msgstr "" #: ../../:1096 msgid "" "The VMware vCenter compute driver now supports booting from images which " "specify they require UEFI or BIOS firmware, using the ``hw_firmware_type`` " "image metadata." msgstr "" #: ../../:454 msgid "" "The VMwareVCDriver now supports live migration. See the `live migration " "configuration`_ documentation for information on how to enable it." msgstr "" #: ../../:1847 msgid "" "The VNC option affects the libvirt and VMWare virt drivers, while the SPICE " "option only affects libvirt. For the libvirt driver, configuring these " "options resulted in lossy keymap conversions for the given graphics method. " "It is recommended that users should unset these options and configure their " "guests as necessary instead. In the case of noVNC, noVNC 1.0.0 should be " "used as this provides support for QEMU's Extended Key Event messages. Refer " "to `bug #1682020`__ and the `QEMU RFB pull request`__ for more information." msgstr "" #: ../../:517 msgid "" "The XenAPI virt driver is now deprecated and may be removed in a future " "release as its quality can not be ensured due to lack of maintainers." msgstr "" #: ../../:651 msgid "" "The XenServer compute driver now supports hot-plugging virtual network " "interfaces." msgstr "" #: ../../:1525 msgid "" "The XenServer driver provides support for downloading images via torrents. " "This feature has not been tested, and it's not clear whether there's a clear " "use case for such a feature. As a result, this feature is now deprecated as " "are the following config options." msgstr "" #: ../../:462 msgid "" "The [pci]passthrough_whitelist config option is renamed to [pci]device_spec. " "The old name is deprecated and aliased to the new one. The old name will be " "removed in a future release." msgstr "" #: ../../:14 stable/2023.2>:324 msgid "" "The `CPU power management`_ feature has been fixed to use privsep to avoid a " "FileNotFound error when offlining CPUs." msgstr "" #: ../../:1557 msgid "" "The `IronicHostManager` is now deprecated along with the ``[scheduler]/" "host_manager`` option of ``ironic_host_manager``." msgstr "" #: ../../:2048 msgid "" "The `[api]/instance_list_per_project_cells` configuration option was added, " "which controls whether or not an instance list for non-admin users checks " "all cell databases for results. If disabled (the default), then a list will " "always contact each cell database looking for instances. This is appropriate " "if you have a small number of cells, and/or if you spread instances from " "tenants evenly across cells. If you confine tenants to a subset of cells, " "then enabling this will result in fewer cell database calls, as nova will " "only query the cells for which the tenant has instances mapped. Doing this " "requires one more (fast) call to the API database to get the relevant subset " "of cells, so if that is likely to always be the same, disabling this feature " "will provide better performance." msgstr "" #: ../../:1057 msgid "" "The ``--version`` argument has been removed in the following commands. Use " "the ``VERSION`` positional argument instead." msgstr "" #: ../../:1720 msgid "" "The ``--version`` parameters of the ``nova-manage api_db sync`` and ``nova-" "manage db sync`` commands has been deprecated in favor of positional " "arguments." msgstr "" #: ../../:1213 msgid "" "The ``AggregateCoreFilter``, ``AggregateRamFilter`` and " "``AggregateDiskFilter`` are now deprecated. They will be removed in a future " "release and should no longer be used. Their functionality has been replaced " "with a placement native approach by combining host aggregate mirroring added " "in Rocky and initial allocation ratios added in Stein. See the `scheduler " "documentation`_ for details." msgstr "" #: ../../:579 msgid "" "The ``AvailabilityZoneFilter`` scheduler filters is now deprecated for " "removal in a future release. The functionality of the " "``AvailabilityZoneFilter`` has been replaced by the " "``map_az_to_placement_aggregate`` pre-filter which was introduced in 18.0.0 " "(Rocky). This pre-filter is now enabled by default and will be mandatory in " "a future release." msgstr "" #: ../../:225 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 "" #: ../../:1236 msgid "" "The ``CoreFilter``, ``DiskFilter`` and ``RamFilter`` are now deprecated. " "VCPU, DISK_GB and MEMORY_MB filtering is performed natively using the " "Placement service when using the ``filter_scheduler`` driver. Users of the " "``caching_scheduler`` driver may still rely on these filters but the " "``caching_scheduler`` driver is itself deprecated. Furthermore, enabling " "these filters may incorrectly filter out baremetal nodes which must be " "`scheduled using custom resource classes `_." msgstr "" #: ../../:1126 msgid "" "The ``CoreFilter``, ``DiskFilter`` and ``RamFilter``, which were deprecated " "in Stein (19.0.0), are now removed. ``VCPU``, ``DISK_GB`` and ``MEMORY_MB`` " "filtering is performed natively using the Placement service. These filters " "have been warning operators at startup that they conflict with proper " "operation of placement and should have been disabled since approximately " "Pike. If you did still have these filters enabled and were relying on them " "to account for virt driver overhead (at the expense of scheduler races and " "retries), see the `scheduler`_ documentation about the topic." msgstr "" #: ../../:14 stable/rocky>:119 stable/stein>:166 #: stable/train>:406 stable/ussuri>:1213 msgid "" "The ``DELETE /os-services/{service_id}`` compute API will now return a ``409 " "HTTPConflict`` response when trying to delete a ``nova-compute`` service " "which is involved in in-progress migrations. This is because doing so would " "not only orphan the compute node resource provider in the placement service " "on which those instances have resource allocations but can also break the " "ability to confirm/revert a pending resize properly. See https://bugs." "launchpad.net/nova/+bug/1852610 for more details." msgstr "" #: ../../:200 stable/queens>:466 stable/rocky>:2018 msgid "" "The ``DELETE /os-services/{service_id}`` compute API will now return a ``409 " "HTTPConflict`` response when trying to delete a ``nova-compute`` service " "which is still hosting instances. This is because doing so would orphan the " "compute node resource provider in the placement service on which those " "instances have resource allocations, which affects scheduling. See https://" "bugs.launchpad.net/nova/+bug/1763183 for more details." msgstr "" #: ../../:464 msgid "" "The ``GET /os-migrations`` API will also have optional ``user_id`` and " "``project_id`` query parameters for filtering migrations by user and/or " "project, for example:" msgstr "" #: ../../:196 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 "" #: ../../:743 msgid "" "The ``Ironic Flavor Migration`` upgrade check has been removed. It is no " "longer necessary." msgstr "" #: ../../:539 msgid "" "The ``POST /servers/{server_id}/os-interface`` API now supports attaching " "neutron ports with QoS minimum bandwidth rules attached." msgstr "" #: ../../:1454 msgid "" "The ``POST /servers/{server_id}/os-interface`` request and the ``POST /" "servers`` request will be rejected with HTTP 400 if the Neutron network " "referenced in the request body has `QoS minimum bandwidth rule`_ attached as " "Nova currently cannot support such operations." msgstr "" #: ../../:1444 msgid "" "The ``POST /servers/{server_id}/os-interface`` request will be rejected with " "HTTP 400 if the Neutron port referenced in the request body has resource " "request as Nova currently cannot support such operation. For example a " "Neutron port has resource request if a `QoS minimum bandwidth rule`_ is " "attached to that port in Neutron." msgstr "" #: ../../:248 unmaintained/yoga>:560 msgid "" "The ``POST /servers`` (create server) API will now reject attempts to create " "a server with the same port specified multiple times. This was previously " "accepted by the API but the instance would fail to spawn and would instead " "transition to the error state." msgstr "" #: ../../:1771 msgid "" "The ``POST`` and ``DELETE`` operations on the ``os-assisted-volume-" "snapshots`` API will now fail with a 400 error if the related instance is " "undergoing a task state transition or does not have a host, i.e. is shelved " "offloaded." msgstr "" #: ../../:1871 msgid "" "The ``PUT /os-services/disable``, ``PUT /os-services/enable`` and ``PUT /os-" "services/force-down`` APIs to enable, disable, or force-down a service will " "now only work with *nova-compute* services. If you are using those APIs to " "try and disable a non-compute service, like nova-scheduler or nova-" "conductor, those APIs will result in a 404 response." msgstr "" #: ../../:1224 msgid "" "The ``RetryFilter`` is deprecated and will be removed in an upcoming release." " Since the 17.0.0 (Queens) release, the scheduler has provided alternate " "hosts for rescheduling so the scheduler does not need to be called during a " "reschedule which makes the ``RetryFilter`` useless. See the `Return " "Alternate Hosts`_ spec for details." msgstr "" #: ../../:1641 msgid "" "The ``TrustedFilter`` scheduler filter has been experimental since its " "existence on May 18, 2012. Due to the lack of tests and activity with it, " "it's now deprecated and set for removal in the 17.0.0 Queens release." msgstr "" #: ../../:1279 msgid "" "The ``TypeAffinityFilter``, which was deprecated in the 16.0.0 Pike release, " "has been removed. The filter was flawed in that it relied on the flavor " "``id`` primary key which cannot be relied upon since you cannot \"edit\" a " "flavor to change its disk, vcpu, etc values. Therefore to change a given " "flavor, it must be deleted and re-created, which means a new ``id`` value, " "thus potentially breaking the usefulness of the filter. Also, the flavor " "migration from the ``nova`` database to the ``nova_api`` database would also " "have resulted in different ``id`` values." msgstr "" #: ../../:969 msgid "" "The ``XenAPI`` compute driver now supports creating servers with virtual " "interface and block device tags which was introduced in the ``2.32`` " "microversion." msgstr "" #: ../../:629 msgid "" "The ``XenAPI`` driver, which was deprecated in the 20.0.0 (Train), has now " "been removed." msgstr "" #: ../../:1443 msgid "" "The ``[DEFAULT] vendordata_driver`` option was deprecated in Mitaka and has " "now been removed. Configuration of vendordata drivers should now be done by " "using the ``[api] vendordata_providers`` option. For more information, refer " "to the `vendordata documentation`__." msgstr "" #: ../../:909 msgid "" "The ``[DEFAULT]/block_device_allocate_retries`` configuration option now has " "a minimum required value of 0. Any previous configuration with a value less " "than zero will now result in an error." msgstr "" #: ../../:1141 msgid "" "The ``[DEFAULT]/default_flavor`` option deprecated in 14.0.0 (Newton) has " "been removed." msgstr "" #: ../../:1886 msgid "" "The ``[DEFAULT]/enable_new_services`` configuration option will now only be " "used to auto-disable new nova-compute services. Other services like nova-" "conductor, nova-scheduler and nova-osapi_compute will not be auto-disabled " "since disabling them does nothing functionally, and starting in Pike the " "``PUT /os-services/enable`` REST API will not be able to find non-compute " "services to enable them." msgstr "" #: ../../:1734 msgid "" "The ``[DEFAULT]/log_options`` configuration option can be used to log " "configuration options at DEBUG level when the `placement-api` and/or `nova-" "api` services are started under WSGI. The default behavior is to log options " "on startup." msgstr "" #: ../../:1712 msgid "" "The ``[DEFAULT]/scheduler_driver_task_period`` configuration option, which " "was deprecated in the 15.0.0 Ocata release, has now been removed. Use the " "``[scheduler]/periodic_task_interval`` option instead." msgstr "" #: ../../:1328 msgid "" "The ``[DEFAULT]/shutdown_timeout`` configuration option minimum value has " "been fixed to be 0 rather than 1 to align with the corresponding " "``os_shutdown_timeout`` image property. See bug https://launchpad.net/bugs/" "1799707 for details." msgstr "" #: ../../:468 msgid "" "The ``[api] use_forwarded_for`` parameter has been deprecated. Instead of " "using this parameter, add the ``HTTPProxyToWSGI`` middleware to api " "pipelines, and ``[oslo_middleware] enable_proxy_headers_parsing = True`` to " "nova.conf." msgstr "" #: ../../:1452 msgid "" "The ``[api] vendordata_providers`` option now defaults to ``[StaticJSON]``. " "This ensures existing behavior of the vendordata v1 driver is preserved." msgstr "" #: ../../:1487 msgid "" "The ``[api]/allow_instance_snapshots`` configuration option is now " "deprecated for removal. To disable snapshots in the ``createImage`` server " "action API, change the ``os_compute_api:servers:create_image`` and " "``os_compute_api:servers:create_image:allow_volume_backed`` policies." msgstr "" #: ../../:1215 msgid "" "The ``[api]/hide_server_address_states`` configuration option and " "``os_compute_api:os-hide-server-addresses`` policy rule were deprecated in " "the 17.0.0 Queens release. They have now been removed. If you never changed " "these values, the API behavior remains unchanged." msgstr "" #: ../../:1056 msgid "" "The ``[api]auth_strategy`` conf option and the corresponding test-only " "``noauth2`` pipeline in ``api-paste.ini`` are deprecated and will be removed " "in a future release. The only supported ``auth_strategy`` is ``keystone``, " "the default." msgstr "" #: ../../:1417 msgid "" "The ``[cinder]/catalog_info`` default value is changed such that the " "``service_name`` portion of the value is no longer set and is also no longer " "required. Since looking up the cinder endpoint in the service catalog should " "only need the endpoint type (``volumev3`` by default) and interface " "(``publicURL`` by default), the service name is dropped and only provided " "during endpoint lookup if configured. See `bug 1803627 `_ for details." msgstr "" #: ../../:1718 msgid "" "The ``[conductor] topic`` configuration option was previously deprecated and " "is now removed from nova. There was no need to let users choose the RPC " "topics for all services. There was little benefit from this and it made it " "really easy to break nova by changing the value of topic options." msgstr "" #: ../../:1207 msgid "" "The ``[filter_scheduler]/soft_affinity_weight_multiplier`` and " "``[filter_scheduler]/soft_anti_affinity_weight_multiplier`` configuration " "options now have a hard minimum value of 0.0. Also, the deprecated alias to " "the ``[DEFAULT]`` group has been removed so the options must appear in the " "``[filter_scheduler]`` group." msgstr "" #: ../../:1618 msgid "" "The ``[filter_scheduler]/use_baremetal_filters`` and ``[filter_scheduler]/" "baremetal_enabled_filters`` configuration options were deprecated in the 16." "0.0 Pike release since deployments serving baremetal instances should be " "`scheduling based on resource classes`_. Those options have now been removed." "" msgstr "" #: ../../:732 msgid "" "The ``[glance]/allowed_direct_url_schemes`` config option, which was first " "deprecated in the 17.0.0 (Queens) release has now been removed." msgstr "" #: ../../:1545 msgid "" "The ``[glance]/allowed_direct_url_schemes`` configuration option and ``nova." "image.download.modules`` extension point have been deprecated for removal. " "These were originally added for the *nova.image.download.file* FileTransfer " "extension which was removed in the 16.0.0 Pike release. The ``nova.image." "download.modules`` extension point is not maintained and there is no " "indication of its use in production clouds. If you are using this extension " "point, please make the nova development team aware by contacting us in the " "#openstack-nova freenode IRC channel or on the openstack-dev mailing list." msgstr "" #: ../../:1063 msgid "" "The ``[glance]api_servers`` configuration option is deprecated and will be " "removed in a future release. Deployments should use standard keystoneauth1 " "options to configure communication with a single image service endpoint. Any " "load balancing or high availability requirements should be satisfied outside " "of nova." msgstr "" #: ../../:726 msgid "" "The ``[libvirt] use_usb_tablet`` config option, which was first deprecated " "in the 14.0.0 (Newton) release, has now been removed. It has been replaced " "by the ``[DEFAULT] pointer_model`` config option." msgstr "" #: ../../:642 msgid "" "The ``[libvirt] xen_hvmloader_path`` config option has been removed. This " "was only used with the libvirt+xen hypervisor, which is no longer supported." msgstr "" #: ../../:642 msgid "" "The ``[libvirt]/live_migration_completion_timeout`` is restricted by minimum " "0 and will now raise a ValueError if the configuration option value is less " "than minimum value." msgstr "" #: ../../:1894 msgid "" "The ``[libvirt]/sparse_logical_volumes`` configuration option is now " "deprecated. Sparse logical volumes were never verified by tests in Nova and " "some bugs were found without having fixes so we prefer to deprecate that " "feature. By default, the LVM image backend allocates all the disk size to a " "logical volume. If you want to have the volume group having thin-provisioned " "logical volumes, use Cinder with volume-backed instances." msgstr "" #: ../../:773 msgid "" "The ``[libvirt]live_migration_tunnelled`` option is deprecated as of Wallaby " "(23.0.0) release." msgstr "" #: ../../:1170 msgid "" "The ``[neutron]/url`` configuration option, which was deprecated in the 17.0." "0 Queens release, has now been removed. The same functionality is available " "via the ``[neutron]/endpoint_override`` option." msgstr "" #: ../../:1258 msgid "" "The ``[notifications]/default_publisher_id`` configuration option now " "defaults to ``[DEFAULT]/host`` rather than ``[DEFAULT]/my_ip``." msgstr "" #: ../../:825 msgid "" "The ``[osapi_v21]/project_id_regex`` configuration option which has been " "deprecated since the Mitaka 13.0.0 release has now been removed." msgstr "" #: ../../:1755 msgid "" "The ``[quota]/driver`` configuration option is no longer deprecated but now " "only allows one of two possible values:" msgstr "" #: ../../:1071 msgid "" "The ``[scheduler] driver`` config option has been deprecated. This was " "previously used to switch between different scheduler drivers including " "custom, out-of-tree ones. However, only the ``FilterScheduler`` has been " "supported in-tree since 19.0.0 (Stein) and nova increasingly relies on " "placement for basic functionality, meaning developing and maintaining out-of-" "tree drivers is increasingly difficult. Users who still rely on a custom " "scheduler driver should migrate to the filter scheduler, using custom " "filters and weighters where necessary." msgstr "" #: ../../:721 msgid "" "The ``[scheduler] periodic_task_interval`` config option has been removed. " "It was no longer used by any supported scheduler drivers." msgstr "" #: ../../:716 msgid "" "The ``[scheduler] scheduler_driver`` config option has been removed, along " "with the ``nova.scheduler.driver`` setuptools entrypoint." msgstr "" #: ../../:986 msgid "" "The ``[upgrade_levels]/compute`` RPC API pin is removed (or set to \"auto\") " "and services are restarted." msgstr "" #: ../../:1376 msgid "" "The ``[vmware] wsdl_location`` configuration option has been removed after " "being deprecated in 15.0.0. It was unused and should have no impact." msgstr "" #: ../../:589 msgid "" "The ``[vnc] keymap`` and ``[spice] keymap`` configuration options, first " "deprecated in 18.0.0 (Rocky), have now been removed. The VNC option " "affected the libvirt and VMWare virt drivers, while the SPICE option only " "affected libvirt. For the libvirt driver, configuring these options resulted " "in lossy keymap conversions for the given graphics method. Users can " "replace this host-level configuration with guest-level configuration. This " "requires noVNC 1.0.0 or greater, which provides support for QEMU's Extended " "Key Event messages. Refer to `bug #1682020`__ and the `QEMU RFB pull " "request`__ for more information." msgstr "" #: ../../:1861 msgid "" "The ``[vnc] keymap`` and ``[spice] keymap`` options will be removed in a " "future release." msgstr "" #: ../../:1246 msgid "" "The ``[workarounds] disable_libvirt_livesnapshot`` config option has been " "deprecated. This was necessary to work around an issue with libvirt v1.2.2, " "which we no longer support. For more information refer to `bug #1334398`__." msgstr "" #: ../../:1394 msgid "" "The ``[workarounds]/disable_native_luksv1`` configuration option has been " "introduced. This can be used by operators to workaround recently discovered " "performance issues found within the `libgcrypt library`__ used by QEMU when " "natively decrypting LUKSv1 encrypted disks. Enabling this option will result " "in the use of the legacy ``dm-crypt`` based os-brick provided encryptors." msgstr "" #: ../../:198 stable/rocky>:343 #: stable/stein>:1393 msgid "" "The ``[workarounds]/ensure_libvirt_rbd_instance_dir_cleanup`` configuration " "option has been introduced. This can be used by operators to ensure that " "instance directories are always removed during cleanup within the Libvirt " "driver while using ``[libvirt]/images_type = rbd``. This works around known " "issues such as `bug 1414895`_ when cleaning up after an evacuation and `bug " "1761062`_ when reverting from an instance resize." msgstr "" #: ../../:1420 msgid "" "The ``[workarounds]/rbd_volume_local_attach`` configuration option has been " "introduced. This can be used by operators to ensure RBD volumes are " "connected to compute hosts as block devices. This can be used with the " "``[worarounds]/disable_native_luksv1`` configuration option to workaround " "recently discovered performance issues found within the `libgcrypt " "library`__ used by QEMU when natively decrypting LUKSv1 encrypted disks." msgstr "" #: ../../:512 msgid "" "The ``[workarounds]disable_native_luksv1`` workaround configurable has been " "removed after previously being deprecated during the Wallaby (23.0.0) " "release." msgstr "" #: ../../:789 msgid "" "The ``[workarounds]rbd_volume_local_attach`` and " "``[workarounds]disable_native_luksv1`` options have been deprecated as of " "the 23.0.0 release ahead of removal in the future as the underlying " "``libgcrypt`` performance regressions that prompted their introduction have " "been resolved." msgstr "" #: ../../:518 msgid "" "The ``[workarounds]rbd_volume_local_attach`` workaround configurable has " "been removed after previously being deprecated in the Wallaby (23.0.0) " "release." msgstr "" #: ../../:1509 stable/pike>:1633 msgid "" "The ``[xenserver]/vif_driver`` configuration option is deprecated for " "removal. The ``XenAPIOpenVswitchDriver`` vif driver is used for Neutron and " "the ``XenAPIBridgeDriver`` vif driver is used for nova-network, which itself " "is deprecated. In the future, the ``use_neutron`` configuration option will " "be used to determine which vif driver to load." msgstr "" #: ../../:1725 msgid "" "The ``[xenserver]/vif_driver`` configuration option was deprecated in the 15." "0.0 Ocata release and has now been removed. The only supported vif driver is " "now ``XenAPIOpenVswitchDriver`` used with Neutron as the backend networking " "service configured to run the ``neutron-openvswitch-agent`` service. See the " "`XenServer configuration guide`_ for more details on networking setup." msgstr "" #: ../../:516 msgid "" "The ``bandwidth`` field has been removed from the ``instance.exists`` and " "``instance.update`` versioned notifications and the version for both " "notifications has been bumped to 2.0. The ``bandwidth`` field was only " "relevant when the XenAPI virt driver was in use, but this driver was removed " "in the Victoria (22.0.0) release and the field has been a no-op since." msgstr "" #: ../../:1091 msgid "" "The ``caching_scheduler`` scheduler driver, which was deprecated in the 16.0." "0 Pike release, has now been removed. Unlike the default " "``filter_scheduler`` scheduler driver which creates resource allocations in " "the placement service during scheduling, the ``caching_scheduler`` driver " "did not interface with the placement service. As more and more functionality " "within nova relies on managing (sometimes complex) resource allocations in " "the placement service, compatibility with the ``caching_scheduler`` driver " "is difficult to maintain, and seldom tested. The original reasons behind the " "need for the CachingScheduler should now be resolved with the " "FilterScheduler and the placement service, notably:" msgstr "" #: ../../:1197 msgid "" "The ``chance_scheduler`` scheduler driver was deprecated in Pike and has now " "been removed. You should enable the ``filter_scheduler`` driver instead. If " "``chance_scheduler`` behavior is desired (i.e. speed is valued over " "correctness) then configuring the ``filter_scheduler`` with only the " "``AllHostsFilter`` enabled and adjusting ``[filter_scheduler]/" "host_subset_size`` will provide similar performance." msgstr "" #: ../../:765 msgid "" "The ``changes-before`` request parameter can be passed to the servers, os-" "instance-action and os-migrations APIs:" msgstr "" #: ../../:1284 msgid "" "The ``compute_stats_class`` configuration option was deprecated since the 13." "0.0 Mitaka release and has been removed. Compute statistics are now always " "generated from the ``nova.compute.stats.Stats`` class within Nova." msgstr "" #: ../../:1228 msgid "" "The ``config_drive_format`` config option has been deprecated. This was " "necessary to workaround an issue with libvirt that was later resolved in " "libvirt v1.2.17. For more information refer to `bug #1246201`__." msgstr "" #: ../../:1432 msgid "" "The ``console_driver`` config opt in the ``DEFAULT`` group has been " "deprecated and will be removed in a future release. This option no longer " "does anything. Previously this option had only two valid, in-tree values: " "``nova.console.xvp.XVPConsoleProxy`` and ``nova.console.fake." "FakeConsoleProxy``. The latter of these was only used in tests and has since " "been replaced." msgstr "" #: ../../:1015 msgid "" "The ``console_token_ttl`` configuration option has been moved to the " "``consoleauth`` group and renamed ``token_ttl``. It should no longer be " "included in the ``DEFAULT`` group." msgstr "" #: ../../:1657 msgid "" "The ``db_driver`` configuration option was deprecated in a previous release " "and has now been removed. This option allowed you to replace the SQLAlchemy " "database layer with one of your own. The approach was deprecated and " "unsupported, and it is now time to remove it completely." msgstr "" #: ../../:202 stable/pike>:350 #: stable/queens>:815 msgid "" "The ``delete_host`` command has been added in ``nova-manage cell_v2`` to " "delete a host from a cell (host mappings). The ``force`` option has been " "added in ``nova-manage cell_v2 delete_cell``. If the ``force`` option is " "specified, a cell can be deleted even if the cell has hosts." msgstr "" #: ../../:1472 msgid "" "The ``dhcp_domain`` option has been undeprecated and moved to the ``[api]`` " "group. It is used by the metadata service to configure fully-qualified " "domain names for instances, in addition to its role configuring DHCP " "services for *nova-network*. This use case was missed when deprecating the " "option initially." msgstr "" #: ../../:1888 msgid "" "The ``fping_path`` configuration option has been deprecated. /os-fping is " "used by nova-network and nova-network itself is deprecated and will be " "removed in the future." msgstr "" #: ../../:1535 msgid "" "The ``hide_server_address_states`` configuration option is now deprecated " "for removal. In future, there will be hard coded server state ``building`` " "for which server address will be hidden. The policy 'os_compute_api:os-hide-" "server-addresses' also is deprecated for removal. More details `here`_" msgstr "" #: ../../:373 msgid "" "The ``hw:vif_multiqueue_enabled`` flavor extra spec has been added. This is " "a boolean option that, when set, can be used to enable or disable multiqueue " "for virtio-net VIFs. It complements the equivalent image metadata property, " "``hw_vif_multiqueue_enabled``. If both values are set, they must be " "identical or an error will be raised." msgstr "" #: ../../:1488 msgid "" "The ``idle_timeout`` option in the ``api_database`` group has been renamed " "to ``connection_recycle_time``." msgstr "" #: ../../:1145 msgid "" "The ``image_info_filename_pattern``, ``checksum_base_images``, and " "``checksum_interval_seconds`` options have been removed in the ``[libvirt]`` " "config section." msgstr "" #: ../../:542 stable/rocky>:1507 msgid "" "The ``image_ref_url`` entry in legacy instance notification payloads will be " "just the instance image id if ``[glance]/api_servers`` is not set and the " "notification is being sent from a periodic task. In this case the periodic " "task does not have a token to get the image service endpoint URL from the " "identity service so only the image id is in the payload. This does not " "affect versioned notifications." msgstr "" #: ../../:1916 msgid "" "The ``image_upload_handler`` option in the ``xenserver`` conf section has " "been deprecated. Please use the new option of ``image_handler`` to configure " "the image handler which is used to download or upload images." msgstr "" #: ../../:895 msgid "" "The ``initial_cpu_allocation_ratio``, ``initial_ram_allocation_ratio`` and " "``initial_disk_allocation_ratio`` configuration options have been added to " "the ``DEFAULT`` group:" msgstr "" #: ../../:760 msgid "" "The ``injected_files``, ``injected_file_content_bytes`` and " "``injected_file_path_bytes`` quotas are removed from the ``os-quota-sets`` " "and ``os-quota-class-sets`` APIs." msgstr "" #: ../../:1517 msgid "" "The ``live_migration_uri`` option in the [libvirt] configuration section is " "deprecated, and will be removed in a future release. The " "``live_migration_scheme`` should be used to change scheme used for live " "migration, and ``live_migration_inbound_addr`` should be used to change " "target URI." msgstr "" #: ../../:397 stable/stein>:1321 msgid "" "The ``long_rpc_timeout`` configuration option is now used for the RPC call " "to the scheduler to select a host. This is in order to avoid a timeout when " "scheduling multiple servers in a single request and/or when the scheduler " "needs to process a large number of hosts." msgstr "" #: ../../:758 msgid "" "The ``maxPersonality`` and ``maxPersonalitySize`` limits are excluded from " "the ``GET /limits`` API response." msgstr "" #: ../../:972 msgid "" "The ``max_concurrent_live_migrations`` configuration option has been " "restricted by the minimum value and now raises a ValueError if the value is " "less than 0." msgstr "" #: ../../:1040 msgid "" "The ``maximum_instance_delete_attempts`` configuration option has been " "restricted by the minimum value and now raises a ValueError if the value is " "less than 1." msgstr "" #: ../../:883 msgid "" "The ``networks`` quota, which was only enabled if the " "``enabled_network_quota`` config option was enabled and only useful with " "*nova-network*, is removed. It will not longer be present in the responses " "for the APIs while attempts to update the quota will be rejected." msgstr "" #: ../../:654 msgid "" "The ``non_inheritable_image_properties`` configuration option inhibits the " "transfer of image properties from the image an instance was created from to " "images created from that instance. There are, however, image properties " "(for example, the properties used for image signature validation) that " "should *never* be transferred to an instance snapshot. Prior to this " "release, such properties were included in the default setting for this " "configuration option, but this allowed the possibility that they might be " "removed by mistake, thereby resulting in a poor user experience. To prevent " "that from happening, nova now maintains an internal list of image properties " "that are absolutely non-inheritable regardless of the setting of the " "configuration option. See the help text for " "``non_inheritable_image_properties`` in the sample nova configuration file " "for details." msgstr "" #: ../../:1239 msgid "" "The ``notify_on_api_faults`` config option and the ``api.fault`` " "notification it enabled have been removed. As noted in `bug 1699115`_, the " "``api.fault`` notification has not worked since the v2.1 API was introduced. " "As the v2.0 API is supported with the v2.1 codebase since Newton, this " "notification has not been emitted since Newton. Given that no one has " "reported an issue with this in that time, it is simply removed." msgstr "" #: ../../:125 stable/queens>:412 stable/rocky>:1495 msgid "" "The ``nova-api`` service now requires the ``[placement]`` section to be " "configured in nova.conf if you are using a separate config file just for " "that service. This is because the ``nova-api`` service now needs to talk to " "the placement service in order to delete resource provider allocations when " "deleting an instance and the ``nova-compute`` service on which that instance " "is running is down. This change is idempotent if ``[placement]`` is not " "configured in ``nova-api`` but it will result in new warnings in the logs " "until configured. See bug https://bugs.launchpad.net/nova/+bug/1679750 for " "more details." msgstr "" #: ../../:1382 msgid "" "The ``nova-compute`` service requires Placement API version 1.14 at a " "minimum to support `nested resource providers`_." msgstr "" #: ../../:530 stable/queens>:1251 msgid "" "The ``nova-conductor`` service now needs access to the Placement service in " "the case of forcing a destination host during a live migration. Ensure the " "``[placement]`` section of nova.conf for the ``nova-conductor`` service is " "filled in." msgstr "" #: ../../:832 msgid "" "The ``nova-console`` service has been deprecated since the 19.0.0 Stein " "release and has now been removed. The following configuration options are " "therefore removed." msgstr "" #: ../../:1255 msgid "" "The ``nova-console`` service is deprecated as it is XenAPI specific, does " "not function properly in a multi-cell environment, and has effectively been " "replaced by noVNC and the ``nova-novncproxy`` service. noVNC should " "therefore be configured instead." msgstr "" #: ../../:1778 msgid "" "The ``nova-consoleauth`` service has been deprecated and new consoles will " "have their token authorizations stored in cell databases. With this, console " "proxies are required to be deployed per cell. All existing consoles will be " "reset. For most operators, this should be a minimal disruption as the " "default TTL of a console token is 10 minutes." msgstr "" #: ../../:1156 msgid "" "The ``nova-consoleauth`` service has been deprecated since the 18.0.0 Rocky " "release and has now been removed. The following configuration options have " "been removed:" msgstr "" #: ../../:1876 msgid "" "The ``nova-consoleauth`` service has been deprecated. Console token " "authorization storage is moving from the ``nova-consoleauth`` service " "backend to the database backend, with storage happening in both, in Rocky. " "In Stein, only the database backend will be used for console token " "authorization storage." msgstr "" #: ../../:520 msgid "" "The ``nova-consoleauth`` service has been removed as it was deprecated since " "the 18.0.0 (Rocky) release." msgstr "" #: ../../:464 stable/stein>:1069 msgid "" "The ``nova-consoleauth`` service is deprecated and should no longer be " "deployed, however, if there is a requirement to maintain support for " "existing console sessions through a live/rolling upgrade, operators should " "set ``[workarounds]enable_consoleauth = True`` in their configuration and " "continue running ``nova-consoleauth`` for the duration of the live/rolling " "upgrade. A new check has been added to the ``nova-status upgrade check`` CLI " "to help with this and it will emit a warning and provide additional " "instructions to set ``[workarounds]enable_consoleauth = True`` while " "performing a live/rolling upgrade." msgstr "" #: ../../:913 msgid "" "The ``nova-dhcpbridge`` service has been removed. This was only used with " "the now-removed *nova-network* service." msgstr "" #: ../../:1409 msgid "" "The ``nova-manage api_db sync`` and ``nova-manage db sync`` commands " "previously took an optional ``--version`` parameter to determine which " "version to sync to. For example::" msgstr "" #: ../../:823 msgid "" "The ``nova-manage cell_v2 delete_cell`` command returns an exit code 4 when " "there are instance mappings to a cell to delete but all instances have been " "deleted in the cell." msgstr "" #: ../../:1587 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 "" #: ../../:737 msgid "" "The ``nova-manage db ironic_flavor_migration`` command has been removed. " "This command could be used to assist users skipping the 16.0.0 (Pike) " "release, which is now in the distant past." msgstr "" #: ../../:748 msgid "" "The ``nova-manage db null_instance_uuid_scan`` command has been removed. A " "blocking migration has been in place since the 12.0.0 (Liberty) release " "making this check unnecessary." msgstr "" #: ../../:378 stable/stein>:1056 msgid "" "The ``nova-manage db online_data_migrations`` command now returns exit " "status 2 in the case where some migrations failed (raised exceptions) and no " "others were completed successfully from the last batch attempted. This " "should be considered a fatal condition that requires intervention. Exit " "status 1 will be returned in the case where the ``--max-count`` option was " "used and some migrations failed but others succeeded (updated at least one " "row), because more work may remain for the non-failing migrations, and their " "completion may be a dependency for the failing ones. The command should be " "reiterated while it returns exit status 1, and considered completed " "successfully only when it returns exit status 0." msgstr "" #: ../../:979 msgid "" "The ``nova-manage db online_data_migrations`` command will now fill missing " "``virtual_interfaces`` records for instances created before the Newton " "release. This is related to a fix for https://launchpad.net/bugs/1751923 " "which makes the _heal_instance_info_cache periodic task in the ``nova-" "compute`` service regenerate an instance network info cache from the current " "neutron port list, and the VIFs from the database are needed to maintain the " "port order for the instance." msgstr "" #: ../../:396 msgid "" "The ``nova-manage image_property set`` command can be used to update the " "stored image properties stored in the database for a given instance and " "image properties." msgstr "" #: ../../:393 msgid "" "The ``nova-manage image_property show`` command can be used to show the " "current stored image property value for a given instance and property." msgstr "" #: ../../:1447 msgid "" "The ``nova-manage placement heal_allocations`` `CLI`_ has been extended to " "heal missing port allocations which are possible due to `bug 1819923`_ ." msgstr "" #: ../../:435 msgid "" "The ``nova-manage placement heal_allocations`` `CLI`_ now allows " "regenerating the placement allocation of servers with ports using minimum " "guaranteed packet rate QoS policy rules." msgstr "" #: ../../:1109 msgid "" "The ``nova-manage project quota_usage_refresh`` and its alias ``nova-manage " "account quota_usage_refresh`` commands have been renamed ``nova-manage quota " "refresh``. Aliases are provided but these are marked as deprecated and will " "be removed in the next release of nova." msgstr "" #: ../../:1714 msgid "" "The ``nova-manage quota refresh`` command has been deprecated and is now a " "no-op since quota usage is counted from resources instead of being tracked " "separately. The command will be removed during the Queens cycle." msgstr "" #: ../../:355 msgid "" "The ``nova-manage volume_attachment get_connector`` command can be used to " "get updated host connector for the localhost." msgstr "" #: ../../:351 msgid "" "The ``nova-manage volume_attachment show`` command can be used to show the " "current volume attachment information for a given volume and instance." msgstr "" #: ../../:935 msgid "" "The ``nova-manage`` set of commands would previously exit with return code 1 " "due to any unexpected error. However, some commands, such as ``nova-manage " "db archive_deleted_rows``, ``nova-manage cell_v2 map_instances`` and ``nova-" "manage placement heal_allocations`` use return code 1 for flow control with " "automation. As a result, the unexpected error return code has been changed " "from 1 to 255 for all ``nova-manage`` commands." msgstr "" #: ../../:1003 msgid "" "The ``nova-xvpvncproxy`` service has been deprecated since the 19.0.0 Stein " "release and has now been removed. The following configuration options have " "also been removed:" msgstr "" #: ../../:1139 msgid "" "The ``nova.conf`` file should have the ``auth_schemes`` parameter in the " "``vnc`` group set. If there are a mix of compute nodes, some with VeNCrypt " "enabled and others with it disabled, then the ``auth_schemes`` configuration " "option should be set to ``['vencrypt', 'none']``." msgstr "" #: ../../:577 msgid "" "The ``nova.image.download`` entry point hook has been removed, per the " "deprecation announcement in the 17.0.0 (Queens) release." msgstr "" #: ../../:300 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 "" #: ../../:1128 stable/pike>:1158 msgid "" "The ``nova.virt.libvirt.firewall.IptablesFirewallDriver`` firewall driver is " "enabled" msgstr "" #: ../../:1315 msgid "" "The ``nova.virt.libvirt.volume.glusterfs.LibvirtGlusterfsVolumeDriver`` " "volume driver has been removed. The GlusterFS volume driver in Cinder was " "deprecated during the Newton release and was removed from Cinder in the " "Ocata release so it is effectively not maintained and therefore no longer " "supported." msgstr "" #: ../../:1337 msgid "" "The ``nova.virt.libvirt.volume.scality.LibvirtScalityVolumeDriver`` volume " "driver has been removed. The Scality volume driver in Cinder was deprecated " "during the Newton release and was removed from Cinder in the Ocata release " "so it is effectively not maintained and therefore no longer supported." msgstr "" #: ../../:1045 msgid "" "The ``os-aggregates`` compute API ``add_host`` and ``remove_host`` actions " "will automatically add/remove compute node resource providers from resource " "provider aggregates in the placement service if the ``nova-api`` service is " "configured to communicate with the placement service, so this command is " "mostly useful for existing deployments with host aggregates which are not " "yet mirrored in the placement service." msgstr "" #: ../../:1704 msgid "" "The ``os-hosts`` API is deprecated as of the 2.43 microversion. Requests " "made with microversion >= 2.43 will result in a 404 error. To list and show " "host details, use the ``os-hypervisors`` API. To enable or disable a " "service, use the ``os-services`` API. There is no replacement for the " "`shutdown`, `startup`, `reboot`, or `maintenance_mode` actions as those are " "system-level operations which should be outside of the control of the " "compute service." msgstr "" #: ../../:53 stable/queens>:186 stable/rocky>:447 #: stable/stein>:1349 msgid "" "The ``os-simple-tenant-usage`` pagination has been fixed. In some cases, " "nova usage-list would have returned incorrect results because of this. See " "bug https://launchpad.net/bugs/1796689 for details." msgstr "" #: ../../:1163 msgid "" "The ``os_compute_api:flavors`` policy deprecated in 16.0.0 has been removed." msgstr "" #: ../../:601 msgid "" "The ``os_compute_api:os-extended-server-attributes`` policy controls which " "users a number of server extended attributes are shown to. Configuring " "visiblity of the ``OS-EXT-SRV-ATTR:hostname`` attribute via this policy has " "now been deprecated and will be removed in a future release. Upon removal, " "this attribute will be shown for all users regardless of policy " "configuration." msgstr "" #: ../../:1167 msgid "" "The ``os_compute_api:os-flavor-manage`` policy has been removed because it " "has been deprecated since 16.0.0. Use the following policies instead:" msgstr "" #: ../../:1176 msgid "" "The ``os_compute_api:os-server-groups`` policy deprecated in 16.0.0 has been " "removed." msgstr "" #: ../../:756 msgid "" "The ``personality`` parameter is removed from the server create and rebuild " "APIs. Use the ``user_data`` parameter instead." msgstr "" #: ../../:764 msgid "" "The ``policies`` and ``metadata`` fields have been removed from the response " "body of POST, GET ``/os-server-groups`` API and GET ``/os-server-groups/" "{server_group_id}`` API." msgstr "" #: ../../:761 msgid "" "The ``policy`` and ``rules`` fields will be returned in response body of " "POST, GET ``/os-server-groups`` API and GET ``/os-server-groups/" "{server_group_id}`` API." msgstr "" #: ../../:1032 msgid "" "The ``populate_queued_for_delete`` and ``populate_user_id`` online data " "migrations must be completed before usage can be counted from placement. " "Until the data migration is complete, the system will fall back to legacy " "quota usage counting from cell databases depending on the result of an " "``EXISTS`` database query during each quota check, if " "``[quota]count_usage_from_placement`` is set to ``True``. Operators who " "want to avoid the performance hit from the ``EXISTS`` queries should wait to " "set the ``[quota]count_usage_from_placement`` configuration option to " "``True`` until after they have completed their online data migrations via " "``nova-manage db online_data_migrations``." msgstr "" #: ../../:1586 msgid "" "The ``quota_usage_refresh`` sub-command has been renamed to ``nova-manage " "quota refresh``. This new command should be used instead." msgstr "" #: ../../:1487 msgid "" "The ``remap_vbd_dev`` option is deprecated and will be removed in a future " "release." msgstr "" #: ../../:643 msgid "" "The ``request_id`` field has been added to all instance action and instance " "update versioned notification payloads. Note that notifications triggered by " "periodic tasks will have the ``request_id`` field set to be ``None``." msgstr "" #: ../../:1150 msgid "" "The ``required`` and ``member_of`` query parameters for a given group are " "optional. That is, you may specify ``resources42=XXX`` without a " "corresponding ``required42=YYY`` or ``member_of42=ZZZ``. However, the " "reverse (specifying ``required42=YYY`` or ``member_of42=ZZZ`` without " "``resources42=XXX``) will result in an error." msgstr "" #: ../../:1367 msgid "" "The ``resize`` and ``migrate`` server action APIs used to synchronously " "block until a destination host is selected by the scheduler. Those APIs now " "asynchronously return a response to the user before scheduling. The response " "code remains 202 and users can monitor the operation via the ``status`` and " "``OS-EXT-STS:task_state`` fields on the server resource and also by using " "the ``os-instance-actions`` API. The most notable change is ``NoValidHost`` " "will not be returned in a 400 error response from the API if scheduling " "fails but that information is available via the instance actions API " "interface." msgstr "" #: ../../:1303 msgid "" "The ``scheduler_json_config_location`` configuration option has not been " "used since the 13.0.0 Mitaka release and has been removed." msgstr "" #: ../../:1192 msgid "" "The ``ssl`` options were only used by Nova code that interacts with Glance " "client. These options are now defined and read by Keystoneauth. " "``api_insecure`` option from glance group is renamed to ``insecure``. The " "following ''ssl'' options are moved to ``glance`` group" msgstr "" #: ../../:383 msgid "" "The ``task_log`` database table contains instance usage audit records if " "``nova-compute`` has been configured with ``[DEFAULT]instance_usage_audit = " "True``. This will be the case if OpenStack Telemetry is being used in the " "deployment, as the option causes Nova to generate audit notifications that " "Telemetry consumes from the message bus." msgstr "" #: ../../:1492 msgid "" "The ``topic`` config options are now deprecated and will be removed in the " "next release. The deprecated options are as below:" msgstr "" #: ../../:1319 msgid "" "The ``trusted_image_certificates`` parameter will be in the response body of " "the following APIs (not restricted by policy):" msgstr "" #: ../../:1306 msgid "" "The ``trusted_image_certificates`` request parameter can be passed to the " "server create and rebuild APIs (if allowed by policy):" msgstr "" #: ../../:755 msgid "The ``user_data`` parameter is added to the server rebuild API." msgstr "" #: ../../:1206 msgid "" "The ``vcpu_pin_set`` configuration option has been deprecated. You should " "migrate host CPU configuration to the ``[compute] cpu_dedicated_set`` or " "``[compute] cpu_shared_set`` config options, or both. Refer to the help text " "of these config options for more information." msgstr "" #: ../../:818 msgid "" "The ``virtio-forwarder`` VNIC type has been added to the list of VNICs. This " "VNIC type is intended to request a low-latency virtio port inside the " "instance, likely backed by hardware acceleration. Currently the Agilio OVS " "external Neutron and OS-VIF plugins provide support for this VNIC mode." msgstr "" #: ../../:235 unmaintained/xena>:263 #: unmaintained/yoga>:581 msgid "" "The `bug 1952941`_ is fixed where a pre-Victoria server with pinned CPUs " "cannot be migrated or evacuated after the cloud is upgraded to Victoria or " "newer as the scheduling fails with ``NotImplementedError: Cannot load " "'pcpuset'`` error." msgstr "" #: ../../:180 unmaintained/yoga>:603 msgid "" "The `bug 1960401`_ is fixed which can cause invalid `BlockDeviceMappings` " "to accumulate in the database. This prevented the respective volumes from " "being attached again to the instance." msgstr "" #: ../../:744 msgid "" "The `discover_hosts_in_cells_interval` periodic task in the scheduler is now " "more efficient in that it can specifically query unmapped compute nodes from " "the cell databases instead of having to query them all and compare against " "existing host mappings." msgstr "" #: ../../:144 stable/rocky>:294 stable/stein>:954 msgid "" "The `long term solution`_ to these issues is to recalculate the XML on the " "destination node. When this work is completed, the restriction on live " "migration with NUMA topologies will be lifted." msgstr "" #: ../../:715 msgid "" "The `nova-compute` worker can automatically disable itself in the service " "database if consecutive build failures exceed a set threshold. The " "``[compute]/consecutive_build_service_disable_threshold`` configuration " "option allows setting the threshold for this behavior, or disabling it " "entirely if desired. The intent is that an admin will examine the issue " "before manually re-enabling the service, which will avoid that compute node " "becoming a black hole build magnet." msgstr "" #: ../../:1588 msgid "" "The `nova-manage cell` command has been deprecated. This command configures " "various aspects of the Cells v1 functionality. Cells v1 has been deprecated, " "thus, this command is also deprecated. It will be removed in its entirety " "when Cells v1 is removed." msgstr "" #: ../../:185 unmaintained/wallaby>:931 msgid "" "The `os-resetState`_ API will now log an instance action when called. The " "resulting instance action being visable via the `os-instance-actions`_ API " "to users and admins, resolving `bug 1911924`_." msgstr "" #: ../../:165 stable/rocky>:252 stable/stein>:379 #: stable/train>:1316 msgid "" "The `os-volume_attachments`_ update API, commonly referred to as the swap " "volume API will now return a ``400`` (BadRequest) error when attempting to " "swap from a multi attached volume with more than one active read/write " "attachment resolving `bug #1775418`_." msgstr "" #: ../../:197 msgid "" "The `unshelve` instance API action now provides a new `host` parameter with " "2.91 microversion (for only admins)." msgstr "" #: ../../:725 msgid "The affected APIs are as follows:" msgstr "" #: ../../:516 msgid "" "The algorithm that is used to see if a multi NUMA guest fits to a multi NUMA " "host has been optimized to speed up the decision on hosts with high number " "of NUMA nodes ( > 8). For details see `bug 1978372`_" msgstr "" #: ../../:770 msgid "" "The amount of PCI Express ports (slots in virtual motherboard) can now be " "configured using ``num_pcie_ports`` option in ``libvirt`` section of ``nova." "conf`` file. This affects x86-64 with ``hw_machine_type`` set to 'pc-q35' " "value and AArch64 instances of 'virt' ``hw_machine_type`` (which is default " "for that architecture). Due to QEMU's memory map limits on aarch64/virt " "maximum value is limited to 28." msgstr "" #: ../../:1443 msgid "" "The base ``3.0`` version is identical to v2 and it was introduced in the " "Newton release of OpenStack. In case you need Nova to continue using the v2 " "version you can point it towards that by setting the ``catalog_info`` option " "in the ``nova.conf`` file under the ``cinder`` section, like::" msgstr "" #: ../../:341 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 "" #: ../../:475 stable/rocky>:2027 msgid "" "The behaviour of ImagePropertiesFilter when using multiple architectures in " "a cloud can be unpredictable for a user if they forget to set the " "architecture property in their image. Nova now allows the deployer to " "specify a fallback in " "``[filter_scheduler]image_properties_default_architecture`` to use a default " "architecture if none is specified. Without this, it is possible that a VM " "would get scheduled on a compute node that does not support the image." msgstr "" #: ../../:1183 msgid "" "The block-storage (cinder) version 3.44 API is now required when working " "with volume attachments. A check has been added to the ``nova-status upgrade " "check`` command for this requirement." msgstr "" #: ../../:220 stable/stein>:1302 msgid "" "The bug fix applies to both the ``nova-osapi_compute`` and ``nova-compute`` " "service so older compute services will need to be patched." msgstr "" #: ../../:576 msgid "" "The cache can be cleared manually at any time by sending SIGHUP to the " "compute process. This will cause the cache to be repopulated the next time " "the data is accessed." msgstr "" #: ../../:1332 msgid "" "The cells topic configuration option has been removed. Please make sure your " "cells related message queue topic is 'cells'." msgstr "" #: ../../:1456 msgid "" "The code for the `placement service `_ " "was moved to its own `repository `_ in Stein. The placement code in nova has been deleted." msgstr "" #: ../../:411 msgid "" "The code gracefully handles the lack of the capability since it is optional " "or Libvirt may not support it in a particular release." msgstr "" #: ../../:270 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 predicatble " "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 "" #: ../../:1344 msgid "" "The concept that ``service manager`` were replaceable components was " "deprecated in Mitaka, so following config options are removed." msgstr "" #: ../../:1425 msgid "" "The config options ``multi_instance_display_name_template`` and " "``null_kernel`` in the ``DEFAULT`` group are now deprecated and may be " "removed as early as the 16.0.0 release. These options are deprecated to keep " "API behaviour consistent across deployments." msgstr "" #: ../../:570 msgid "" "The configuration option ``[compute]resource_provider_association_refresh`` " "can now be set to zero to disable refresh entirely. This follows on from " "`bug 1767309`_ allowing more aggressive reduction in the amount of traffic " "to the placement service." msgstr "" #: ../../:449 msgid "" "The configuration option ``[compute]resource_provider_association_refresh`` " "can now be set to zero to disable refresh entirely. This should be useful " "for large-scale deployments." msgstr "" #: ../../:1494 stable/queens>:1519 msgid "" "The configuration options ``baremetal_enabled_filters`` and " "``use_baremetal_filters`` are deprecated in Pike and should only be used if " "your deployment still contains nodes that have not had their resource_class " "attribute set. See `Ironic release notes `_ for upgrade concerns." msgstr "" #: ../../:560 msgid "" "The configured maximum is enforced during server create, rebuild, evacuate, " "unshelve, live migrate, and attach volume. When the maximum is exceeded " "during server create, rebuild, evacuate, unshelve, or live migrate, the " "server will go into ``ERROR`` state and the server fault message will " "indicate the failure reason. When the maximum is exceeded during a server " "attach volume API operation, the request will fail with a ``403 " "HTTPForbidden`` error." msgstr "" #: ../../:841 msgid "" "The configured maximum is not enforced on shelved offloaded servers, as they " "have no compute host." msgstr "" #: ../../:548 msgid "" "The database migration engine has changed from `sqlalchemy-migrate`__ to " "`alembic`__. For most deployments, this should have minimal to no impact and " "the switch should be mostly transparent. The main user-facing impact is the " "change in schema versioning. While sqlalchemy-migrate used a linear, integer-" "based versioning scheme, which required placeholder migrations to allow for " "potential migration backports, alembic uses a distributed version control-" "like schema where a migration's ancestor is encoded in the file and branches " "are possible. The alembic migration files therefore use a arbitrary UUID-" "like naming scheme and the ``nova-manage db sync`` and ``nova-manage api_db " "sync`` commands now expect such an version when manually specifying the " "version that should be applied. For example::" msgstr "" #: ../../:933 msgid "" "The defalut value for policy rule ``os_compute_api:servers:create:" "zero_disk_flavor`` has changed from ``rule:admin_or_owner`` to ``rule:" "admin_api`` which means that by default, users without the admin role will " "not be allowed to create servers using a flavor with ``disk=0`` *unless* " "they are creating a volume-backed server. If you have these kinds of " "flavors, you may need to take action or temporarily override the policy rule." " Refer to `bug 1739646 `_ for more " "details." msgstr "" #: ../../:880 msgid "" "The default QEMU machine type for ARMv7 architecture is now changed to " "``virt`` (from the older ``vexpress-a15``, which is a particular ARM " "development board). The ``virt`` board is the recommended default for " "ARMv7, which is explicitly designed to be used with virtual machines. It is " "more flexible, supports PCI and 'virtio' devices, has decent RAM limits, and " "so forth. For pre-existing Nova guests on ARMv7 to acquire the ``virt`` " "machine type: (a) upgrade Nova with this fix; (b) explicitly start and stop " "the guests, then they will pick up the 'virt' machine type." msgstr "" #: ../../:418 msgid "" "The default ``api-paste.ini`` file has been updated and now the Metadata API " "pipeline includes the ``HTTPProxyToWSGI`` middleware." msgstr "" #: ../../:14 stable/stein>:14 stable/train>:155 #: stable/ussuri>:178 unmaintained/victoria>:547 msgid "" "The default for ``[glance] num_retries`` has changed from ``0`` to ``3``. " "The option controls how many times to retry a Glance API call in response to " "a HTTP connection failure. When deploying Glance behind HAproxy it is " "possible for a response to arrive just after the HAproxy idle time. As a " "result, an exception will be raised when the connection is closed resulting " "in a failed request. By increasing the default value, Nova can be more " "resilient to this scenario were HAproxy is misconfigured by retrying the " "request." msgstr "" #: ../../:447 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 "" #: ../../:137 stable/queens>:1269 msgid "" "The default list of non-inherited image properties to pop when creating a " "snapshot has been extended to include image signature properties. The " "properties ``img_signature_hash_method``, ``img_signature``, " "``img_signature_key_type`` and ``img_signature_certificate_uuid`` are no " "longer inherited by the snapshot image as they would otherwise result in a " "Glance attempting to verify the snapshot image with the signature of the " "original." msgstr "" #: ../../:1281 msgid "" "The default policy for os_compute_api:os-quota-sets:detail has been changed " "to permit listing of quotas with details to project users, not only to " "admins." msgstr "" #: ../../:1226 msgid "" "The default policy on os-server-tags has been changed from ``RULE_ANY`` " "(allow all) to ``RULE_ADMIN_OR_OWNER``. This is because server tags should " "only be manipulated on servers owned by the user or admin. This doesn't have " "any affect on how the API works." msgstr "" #: ../../:203 msgid "" "The default system scope is removed from all APIs hence finishing to " "implement `phase #1 of new RBAC guidelines`__ that are opt-in." msgstr "" #: ../../:892 msgid "" "The default value for the \"cpu_allocation_ratio\", \"ram_allocation_ratio\" " "and \"disk_allocation_ratio\" configurations have been changed to ``None``." msgstr "" #: ../../:1033 msgid "" "The default value for the ``[compute]/live_migration_wait_for_vif_plug`` " "configuration option has been changed to True. As noted in the help text for " "the option, some networking backends will not work with this set to True, " "although OVS and linuxbridge will." msgstr "" #: ../../:1192 stable/pike>:1116 msgid "" "The default value for the ``[xenserver]/vif_driver`` configuration option " "has been changed to ``nova.virt.xenapi.vif.XenAPIOpenVswitchDriver`` to " "match the default configuration of ``[DEFAULT]/use_neutron=True``." msgstr "" #: ../../:518 msgid "" "The default value of ``[oslo_policy] policy_file`` config option has been " "changed from ``policy.json`` to ``policy.yaml``. Nova policy new defaults " "since 21.0.0 and current default value of ``[oslo_policy] policy_file`` " "config option (``policy.json``) does not work when ``policy.json`` is " "generated by `oslopolicy-sample-generator `_ tool. Refer to `bug " "1875418 `_ for more details. " "Also check `oslopolicy-convert-json-to-yaml `_ tool to convert " "the JSON to YAML formatted policy file in backward compatible way." msgstr "" #: ../../:1230 msgid "" "The default value of the ``[DEFAULT]/firewall_driver`` configuration option " "has been changed to ``nova.virt.firewall.NoopFirewallDriver`` to coincide " "with the default value of ``[DEFAULT]/use_neutron=True``." msgstr "" #: ../../:1772 msgid "" "The default value of the configuration attribute ``[libvirt]/rng_dev_path`` " "is now set to ``/dev/urandom``. Refer to the documentation of " "``rng_dev_path`` for details." msgstr "" #: ../../:1289 msgid "" "The deprecated /os-cloudpipe API endpoint has been removed. Whenever calls " "are made to that endpoint it now returns a 410 response." msgstr "" #: ../../:1295 msgid "The deprecated S3 image backend has been removed." msgstr "" #: ../../:523 msgid "" "The deprecated ``Cells V1`` feature (not to be confused with `Cells V2`_) " "has been removed." msgstr "" #: ../../:254 msgid "The deprecated ``[api] use_forwarded_for`` option has been removed." msgstr "" #: ../../:250 msgid "The deprecated ``[upgrade_levels] cert`` option has been removed." msgstr "" #: ../../:1324 msgid "The deprecated ``cert_topic`` configuration option has been removed." msgstr "" #: ../../:1379 msgid "" "The deprecated compute config option ``snapshot_name_template`` has been " "removed. It is not used anywhere and has no effect on any code, so there is " "no impact." msgstr "" #: ../../:1385 msgid "" "The deprecated config option ``compute_available_monitors`` has been removed " "from the ``DEFAULT`` config section. Use setuptools entry points to list " "available monitor plugins." msgstr "" #: ../../:1285 msgid "" "The deprecated nova cert daemon is now removed. The /os-certificates API " "endpoint that depended on this service now returns 410 whenever it is called." "" msgstr "" #: ../../:1541 msgid "" "The direct use of the encryption provider classes such as nova.volume." "encryptors.luks.LuksEncryptor is now deprecated and will be blocked in the " "Pike release of Nova. The use of out of tree encryption provider classes is " "also deprecated and will be blocked in the Pike release of Nova." msgstr "" #: ../../:1948 msgid "" "The disabled ``os-pci`` API has been removed. This API was originally added " "to the v3 API which over time finally became the v2.1 API and the initial " "microversion is backward compatible with the v2.0 API, where the ``os-pci`` " "extension did not exist. The ``os-pci`` API was never enabled as a " "microversion in the v2.1 API and at this time no longer aligns with Nova " "strategically and is therefore just technical debt, so it has been removed. " "Since it was never enabled or exposed out of the compute REST API endpoint " "there was no deprecation period for this." msgstr "" #: ../../:577 msgid "" "The dnspython 2.0.0 package is incompatible with even the latest eventlet " "package version. This makes nova-novncproxy service to fail if the version " "of the dnspython package is equal or greater than 2.0.0. See `eventlet issue " "619`_ for more details" msgstr "" #: ../../:862 msgid "" "The embedded flavor description will not be included in server " "representations." msgstr "" #: ../../:135 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 "" #: ../../:588 msgid "" "The existing config options in the ``[devices]`` group for managing virtual " "GPUs are now renamed in order to be more generic since the mediated devices " "framework from the linux kernel can support other devices:" msgstr "" #: ../../:25 stable/pike>:25 #: stable/queens>:95 stable/rocky>:187 stable/stein>:333 stable/train>:1279 msgid "" "The fault ``details``, which are only exposed to users with the admin role, " "will continue to include the traceback and also include the exception value " "which for non-nova exceptions is what used to be exposed in the fault " "``message`` field. Meaning, the information that admins could see for server " "faults is still available, but the exception value may be in ``details`` " "rather than ``message`` now." msgstr "" #: ../../:489 msgid "" "The field ``instance_name`` has been added to the ``InstanceCreatePayload`` " "in the following versioned notifications:" msgstr "" #: ../../:657 msgid "" "The fields ``locked`` and ``display_description`` have been added to " "InstancePayload. Versioned notifications for instance actions will include " "these fields." msgstr "" #: ../../:819 msgid "" "The fields have been removed as the information they provided was frequently " "misleading or outright wrong, and more accurate information can now be " "queried from placement." msgstr "" #: ../../:1073 msgid "" "The filter and sort query parameters for server list API are now limited " "according to whitelists. The whitelists are different for admin and non-" "admin users." msgstr "" #: ../../:1910 msgid "" "The filter scheduler will now attempt to claim a number of resources in the " "placement API after determining a list of potential hosts. We attempt to " "claim these resources for each instance in the build request, and if a claim " "does not succeed, we try this claim against the next potential host the " "scheduler selected. This claim retry process can potentially attempt claims " "against a large number of hosts, and we do not limit the number of hosts to " "attempt claims against. Claims for resources may fail due to another " "scheduler process concurrently claiming resources against the same compute " "node. This concurrent resource claim is normal and the retry of a claim " "request should be unusual but harmless." msgstr "" #: ../../:282 #: stable/pike>:410 stable/queens>:1681 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 "" #: ../../:397 stable/queens>:1653 msgid "" "The fix for errata in `OSSA-2017-005`_ (CVE-2017-16239) will need to be " "applied in addition to this fix." msgstr "" #: ../../:341 stable/pike>:460 #: stable/queens>:1636 msgid "The fix is in the `nova-api` and `nova-conductor` services." msgstr "" #: ../../:395 stable/queens>:1651 msgid "The fix is in the `nova-api` and `nova-scheduler` services." msgstr "" #: ../../:293 #: stable/pike>:421 stable/queens>:1692 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 "" #: ../../:1662 msgid "" "The following APIs which are considered as proxies of Neutron networking " "API, are deprecated and will result in a 404 error response in microversion " "`2.44`::" msgstr "" #: ../../:202 msgid "" "The following SPICE-related options are added to the ``spice`` configuration " "group of a Nova configuration:" msgstr "" #: ../../:1421 stable/ussuri>:903 msgid "The following ``nova-manage`` commands have been removed." msgstr "" #: ../../:1398 msgid "" "The following are the short names and description of the plugins which they " "represent:" msgstr "" #: ../../:1374 msgid "" "The following commands are no longer required to be listed in your rootwrap " "configuration: blkid; blockdev; cat; chown; cryptsetup; dd; ebrctl; ifc_ctl; " "kpartx; losetup; lvcreate; lvremove; lvs; mkdir; mm-ctl; mount; nova-" "idmapshift; parted; ploop; prl_disk_tool; qemu-nbd; readlink; shred; tee; " "touch; umount; vgs; vrouter-port-control; and xend." msgstr "" #: ../../:1606 msgid "" "The following commands are no longer required to be listed in your rootwrap " "configuration: e2fsck; mkfs; tune2fs; xenstore_read." msgstr "" #: ../../:1088 msgid "" "The following conf options have been moved to the ``[image_cache]`` group " "and renamed accordingly. The old option paths are deprecated and will be " "removed in a future release." msgstr "" #: ../../:918 msgid "" "The following config options only applied when using the *nova-network* " "network driver which has now been removed. The config options have therefore " "been removed also." msgstr "" #: ../../:634 msgid "" "The following config options only apply when using the ``XenAPI`` virt " "driver which has now been removed. The config options have therefore been " "removed also." msgstr "" #: ../../:217 msgid "" "The following config options which only apply for the ``HyperV`` virt driver " "or RDP console APIs also have been removed:" msgstr "" #: ../../:1571 msgid "The following configuration options are deprecated for removal:" msgstr "" #: ../../:1465 msgid "The following configuration options have been renamed:" msgstr "" #: ../../:1904 msgid "" "The following configuration options in the ``[upgrade_levels]`` group have " "been deprecated:" msgstr "" #: ../../:1188 msgid "" "The following configuration options in the ``quota`` group have been removed " "because they have not been used since 17.0.0." msgstr "" #: ../../:1698 msgid "" "The following configuration options were deprecated for removal in the 17.0." "0 Queens release and have now been removed:" msgstr "" #: ../../:1321 stable/pike>:1344 msgid "" "The following configuration options, previously found in the ``libvirt`` " "group, have been removed:" msgstr "" #: ../../:1137 msgid "The following deprecated Policy Rules have been removed:" msgstr "" #: ../../:1664 msgid "" "The following deprecated configuration options have been removed from the " "``api`` section of ``nova.conf``:" msgstr "" #: ../../:1389 stable/rocky>:1677 msgid "" "The following deprecated configuration options have been removed from the " "``compute`` section of ``nova.conf``:" msgstr "" #: ../../:1435 msgid "" "The following deprecated configuration options have been removed from the " "``xenserver`` section of ``nova.conf``:" msgstr "" #: ../../:1391 origin/stable/ocata>:1400 msgid "The following deprecated nova-manage commands have been removed:" msgstr "" #: ../../:1687 msgid "" "The following deprecated options have been removed from the ``placement`` " "group of ``nova.conf``:" msgstr "" #: ../../:608 msgid "The following deprecated scheduler filters have been removed." msgstr "" #: ../../:325 msgid "" "The following enlightenments are now added by default to the libvirt XML for " "Windows guests:" msgstr "" #: ../../:241 msgid "" "The following extra specs which only apply for the ``HyperV`` virt driver " "have been removed." msgstr "" #: ../../:838 msgid "The following instance action records have been added:" msgstr "" #: ../../:750 stable/queens>:883 #: stable/rocky>:1019 msgid "" "The following legacy notifications have been transformed to a new versioned " "payload:" msgstr "" #: ../../:656 msgid "" "The following new ``nova-manage`` commands have been introduced to help " "operators manage the ``hw_machine_type`` image property:" msgstr "" #: ../../:1361 msgid "The following options are removed:" msgstr "" #: ../../:1446 stable/pike>:1521 #: stable/rocky>:1869 stable/stein>:1267 msgid "" "The following options, found in ``DEFAULT``, were only used for configuring " "nova-network and are, like nova-network itself, now deprecated." msgstr "" #: ../../:1478 msgid "The following options, found in ``quota``, are also deprecated." msgstr "" #: ../../:1641 msgid "" "The following options, previously found in the ``[crypto]`` group, have been " "removed:" msgstr "" #: ../../:875 msgid "The following policies have also been removed." msgstr "" #: ../../:1312 msgid "" "The following policy rules were added to restrict the usage of the " "``trusted_image_certificates`` request parameter in the server create and " "rebuild APIs:" msgstr "" #: ../../:896 msgid "The following related config options have been removed." msgstr "" #: ../../:1502 stable/queens>:1527 msgid "" "The following scheduler filters are deprecated in Pike: ``ExactRamFilter``, " "``ExactCoreFilter`` and ``ExactDiskFilter`` and should only be used if your " "deployment still contains nodes that have not had their resource_class " "attribute set. See `Ironic release notes `_ for upgrade concerns." msgstr "" #: ../../:583 msgid "" "The following versioned swap volume notifications have been added in the " "compute manager:" msgstr "" #: ../../:958 msgid "" "The following volume attach and volume detach versioned notifications have " "been added to the nova-compute service:" msgstr "" #: ../../:291 unmaintained/victoria>:539 msgid "" "The former combination is invalid as it would suggest reserved memory is " "greater than total memory available, while the latter is considered " "incorrect behavior as reserving of file-backed memory can and should be " "achieved by reducing the filespace allocated as memory by modifying " "``[libvirt] file_backed_memory``." msgstr "" #: ../../:719 msgid "" "The guest OS type must be specified in order to properly spawn the VMs. It " "can be specifed through the image property \"os_type\", and the acceptable " "values are \"windows\" or \"linux\"." msgstr "" #: ../../:57 stable/2023.2>:306 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 "" #: ../../:1820 msgid "" "The i/o performance for Quobyte volumes has been increased significantly by " "disabling xattrs." msgstr "" #: ../../:642 msgid "" "The image properties ``cinder_encryption_key_id`` and " "``cinder_encryption_key_deletion_policy`` are absolutely non-inheritable " "regardless of the ``non_inheritable_image_properties`` setting." msgstr "" #: ../../:562 msgid "" "The information exposed by this API is admin or owner only by default, " "controlled by rule:" msgstr "" #: ../../:1070 msgid "" "The information in the network.json metadata has been amended, for IPv6 " "networks under Neutron control, the ``type`` field has been changed from " "being always set to ``ipv6_dhcp`` to correctly reflecting the " "``ipv6_address_mode`` option in Neutron." msgstr "" #: ../../:267 stable/rocky>:1441 msgid "" "The initial implementation of native LUKS decryption within Libvirt 2.2.0 " "had a `known issue`_ with the use of passphrases that were a multiple of 16 " "bytes in size. This was `resolved`_ in the upstream 3.3.0 release of Libvirt " "and has been backported to various downstream distribution specific versions." "" msgstr "" #: ../../:669 msgid "" "The instance must have a ``vm_state`` of ``STOPPED``, ``SHELVED`` or " "``SHELVED_OFFLOADED``." msgstr "" #: ../../:510 stable/queens>:1858 msgid "" "The ironic driver will automatically migrate instance flavors for resource " "classes at runtime. If you are not able to run the compute and ironic " "services at pike because you are automating an upgrade past this release, " "you can use the ``nova-manage db ironic_flavor_migration`` to push the " "migration manually. This is only for advanced users taking on the risk of " "automating the process of upgrading through pike and is not recommended for " "normal users." msgstr "" #: ../../:1825 stable/queens>:1779 msgid "" "The ironic virt driver no longer reports an empty inventory for bare metal " "nodes that have instances on them. Instead the custom resource class, VCPU, " "memory and disk are reported as they are configured on the node." msgstr "" #: ../../:1025 msgid "" "The ivs-ctl command has been added to the rootwrap filters in compute." "filters. Deployments needing support for BigSwitch no longer need to add the " "filters manually nor include network.filters at installation." msgstr "" #: ../../:528 msgid "" "The latest API microversion supported for Ocata is v2.42. Details on REST " "API microversions added since the 14.0.0 Newton release can be found in the " "`REST API Version History`_ page." msgstr "" #: ../../:157 msgid "The latest Compute API microversion supported for 2023.1 is `v2.95`__." msgstr "" #: ../../:101 msgid "The latest Compute API microversion supported for 2023.2 is `v2.95`__." msgstr "" #: ../../:27 msgid "The latest Compute API microversion supported for 2024.1 is `v2.96`__." msgstr "" #: ../../:597 msgid "" "The latest Compute API microversion supported for Pike is v2.53. Details on " "REST API microversions added since the 15.0.0 Ocata release can be found in " "the `REST API Version History`_ page." msgstr "" #: ../../:593 msgid "" "The latest Compute API microversion supported for Queens is v2.60. Details " "on REST API microversions added since the 16.0.0 Pike release can be found " "in the `REST API Version History`_ page." msgstr "" #: ../../:511 msgid "" "The latest Compute API microversion supported for Rocky is v2.65. Details on " "REST API microversions added since the 17.0.0 Queens release can be found in " "the `REST API Version History`_ page." msgstr "" #: ../../:412 msgid "" "The latest Compute API microversion supported for Stein is v2.72. Details on " "REST API microversions added since the 18.0.0 Rocky release can be found in " "the `REST API Version History`_ page." msgstr "" #: ../../:464 msgid "" "The latest Compute API microversion supported for Train is v2.79. Details on " "REST API microversions added since the 19.0.0 Stein release can be found in " "the `REST API Version History`_ page." msgstr "" #: ../../:340 msgid "" "The latest Compute API microversion supported for Ussuri is v2.87. Details " "on REST API microversions added since the 20.0.0 Train release can be found " "in the `REST API Version History`__ page." msgstr "" #: ../../:294 msgid "" "The latest Compute API microversion supported for Victoria is v2.87. No new " "microversions were added during this cycle but you can find all of them in " "the `REST API Version History`__ page." msgstr "" #: ../../:391 msgid "" "The latest Compute API microversion supported for Wallaby is v2.88. Details " "on REST API microversions added since the 22.0.0 Victoria release can be " "found in the `REST API Version History`__ page." msgstr "" #: ../../:297 msgid "" "The latest Compute API microversion supported for Xena is v2.90. Details on " "REST API microversions added since the 23.0.0 Wallaby release can be found " "in the `REST API Version History`__ page." msgstr "" #: ../../:251 msgid "" "The latest Compute API microversion supported for Yoga is `v2.90`__ (same as " "the Xena release)." msgstr "" #: ../../:170 msgid "The latest Compute API microversion supported for Zed is `v2.93`__." msgstr "" #: ../../:259 msgid "" "The legacy ``sqlalchemy-migrate`` migrations, which have been deprecated " "since Wallaby, have been removed. There should be no end-user impact." msgstr "" #: ../../:994 msgid "" "The legacy naive behavior is dependent on the value of the ``[workarounds]/" "enable_numa_live_migration`` option. Refer to the Deprecations sections for " "more details." msgstr "" #: ../../:111 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 "" #: ../../:373 msgid "" "The libvirt RBD image backend module can now handle a Glance multistore " "environment where multiple RBD clusters are in use across a single Nova/" "Glance deployment, configured as independent Glance stores. In the case " "where an instance is booted with an image that does not exist in the RBD " "cluster that Nova is configured to use, Nova can ask Glance to copy the " "image from whatever store it is currently in to the one that represents its " "RBD cluster. To enable this feature, set ``[libvirt]/" "images_rbd_glance_store_name`` to tell Nova the Glance store name of the RBD " "cluster it uses." msgstr "" #: ../../:602 msgid "" "The libvirt and xenapi compute drivers now have (experimental) native " "support for virtual GPU devices. See the `virtual GPU`_ admin guide for more " "details." msgstr "" #: ../../:1351 msgid "" "The libvirt compute driver now allows users to create instances with SR-IOV " "virtual functions which will be configured as trusted." msgstr "" #: ../../:752 msgid "" "The libvirt compute driver now supports attaching volumes of type \"drbd\". " "See the `DRBD documentation`_ for more information." msgstr "" #: ../../:935 msgid "" "The libvirt compute driver now supports connecting to Veritas HyperScale " "volume backends." msgstr "" #: ../../:533 msgid "" "The libvirt compute driver now supports trusted image certificates when " "using the 2.63 compute API microversion. See the `image signature " "certificate validation`_ documentation for more details." msgstr "" #: ../../:605 msgid "" "The libvirt compute driver now supports volume multi-attach when using the 2." "60 compute API microversion. See the cinder admin guide for more details " "about volume multi-attach support in OpenStack." msgstr "" #: ../../:1010 msgid "" "The libvirt compute driver will \"reshape\" VGPU inventories and allocations " "on start of the ``nova-compute`` service. This will result in moving VGPU " "inventory from the root compute node resource provider to a nested (child) " "resource provider in the tree and move any associated VGPU allocations with " "it. This will be a one-time operation on startup in Stein. There is no end-" "user visible impact for this; it is for internal resource tracking purposes. " "See the `spec`__ for more details." msgstr "" #: ../../:645 msgid "" "The libvirt driver can now support requests for guest RAM to be encrypted at " "the hardware level, if there are compute hosts which support it. Currently " "only AMD SEV (Secure Encrypted Virtualization) is supported, and it has " "certain minimum version requirements regarding the kernel, QEMU, and libvirt." "" msgstr "" #: ../../:553 msgid "" "The libvirt driver has added support for hardware-offloaded OVS with vDPA " "(vhost Data Path Acceleration) type interfaces. vDPA allows virtio net " "interfaces to be presented to the guest while the datapath can be offloaded " "to a software or hardware implementation. This enables high performance " "networking with the portablity of standard virtio interfaces." msgstr "" #: ../../:803 msgid "" "The libvirt driver has been extended to support user configurable " "performance monitoring unit (vPMU) virtualization. This is particularly " "useful for real-time workloads. A pair of boolean flavor extra spec and " "image metadata properties ``hw:pmu`` and ``hw_pmu`` have been added to " "control the emulation of the vPMU. By default the behavior of vPMU emulation " "has not been changed. To take advantage of this new feature, the operator or " "tenant will need to update their flavors or images to define the new " "property." msgstr "" #: ../../:447 msgid "" "The libvirt driver now allows explicitly disabling CPU flags for guests via " "the ``[libvirt]cpu_model_extra_flags`` config attribute. This is possible " "via a ``+`` / ``-`` notation, where if you specify a CPU flag prefixed with " "a ``+`` sign (without quotes), it will be enabled for the guest, while a " "prefix of ``-`` will disable it. If neither ``+`` nor ``-`` is specified, " "the CPU flag will be enabled, which is the default behaviour." msgstr "" #: ../../:217 stable/pike>:243 #: stable/queens>:510 msgid "" "The libvirt driver now allows specifying individual CPU feature flags for " "guests, via a new configuration attribute ``[libvirt]/" "cpu_model_extra_flags`` -- only with ``custom`` as the ``[libvirt]/" "cpu_model``. Refer to its documentation in ``nova.conf`` for usage details." msgstr "" #: ../../:900 msgid "" "The libvirt driver now allows specifying individual CPU feature flags for " "guests, via a new configuration attribute ``[libvirt]/" "cpu_model_extra_flags`` -- this is valid in combination with all the three " "possible values for ``[libvirt]/cpu_mode``: ``custom``, ``host-model``, or " "``host-passthrough``. The ``cpu_model_extra_flags`` also allows specifying " "multiple CPU flags. Refer to its documentation in ``nova.conf`` for usage " "details." msgstr "" #: ../../:444 msgid "" "The libvirt driver now allows using Native NVMeoF multipathing for NVMeoF " "connector, via the configuration attribute in nova-cpu.conf ``[libvirt]/" "volume_use_multipath``, defaulting to False (disabled)." msgstr "" #: ../../:923 msgid "" "The libvirt driver now allows utilizing file backed memory for qemu/KVM " "virtual machines, via a new configuration attribute ``[libvirt]/" "file_backed_memory``, defaulting to 0 (disabled)." msgstr "" #: ../../:665 msgid "" "The libvirt driver now has a ``live_migration_scheme`` configuration option " "which should be used where the ``live_migration_uri`` would previously have " "been configured with non-default scheme." msgstr "" #: ../../:736 msgid "" "The libvirt driver now supports \"QEMU-native TLS\" transport for live " "migration. This will provide encryption for all migration streams, namely: " "guest RAM, device state and disks on a non-shared setup that are transported " "over NBD (Network Block Device), also called as \"block migration\"." msgstr "" #: ../../:820 msgid "" "The libvirt driver now supports additional Cinder front-end QoS specs, " "allowing the specification of additional IO burst limits applied for each " "attached disk, individually." msgstr "" #: ../../:637 msgid "" "The libvirt driver now supports booting instances by asking for virtual GPUs." " In order to support that, the operators should specify the enabled vGPU " "types in the nova-compute configuration file by using the configuration " "option ``[devices]/enabled_vgpu_types``. Only the enabled vGPU types can be " "used by instances." msgstr "" #: ../../:574 msgid "" "The libvirt driver now supports booting instances with virtual persistent " "memory (vPMEM), also called persistent memory (PMEM) namespaces. To enable " "vPMEM support, the user should specify the PMEM namespaces in the ``nova." "conf`` by using the configuration option ``[libvirt]/pmem_namespaces``. For " "example::" msgstr "" #: ../../:603 msgid "" "The libvirt driver now supports defining different virtual GPU types for " "each physical GPU. See the ``[devices]/enabled_vgpu_types`` configuration " "option for knowing how to do it. Please refer to https://docs.openstack.org/" "nova/latest/admin/virtual-gpu.html for further documentation." msgstr "" #: ../../:421 msgid "" "The libvirt driver now supports live migration with virtual persistent " "memory (vPMEM), which requires QEMU as hypervisor. In virtualization layer, " "QEMU will copy vpmem over the network like volatile memory, due to the " "typical large capacity of vPMEM, it may takes longer time for live migration." "" msgstr "" #: ../../:70 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 "" #: ../../:1152 msgid "" "The libvirt driver port filtering feature will now ignore the " "``allow_same_net_traffic`` config option." msgstr "" #: ../../:1122 msgid "" "The libvirt driver port filtering feature will now ignore the ``use_ipv6`` " "config option." msgstr "" #: ../../:1125 stable/pike>:1155 msgid "" "The libvirt driver provides port filtering capability. This capability is " "enabled when the following is true:" msgstr "" #: ../../:922 msgid "" "The libvirt driver's RBD imagebackend no longer supports setting " "force_raw_images to False. Setting force_raw_images = False and images_type =" " rbd in nova.conf will cause the nova compute service to refuse to start. To " "fix this, set force_raw_images = True. This change was required to fix the " "`bug 1816686`_." msgstr "" #: ../../:93 unmaintained/wallaby>:198 #: unmaintained/xena>:224 unmaintained/yoga>:492 msgid "" "The libvirt virt driver in Nova implements power on and hard reboot by " "destroying the domain first and unpluging the vifs then recreating the " "domain and replugging the vifs. However nova does not wait for the network-" "vif-plugged event before unpause the domain. This can cause the domain to " "start running and requesting IP via DHCP before the networking backend has " "finished plugging the vifs. The config option " "[workarounds]wait_for_vif_plugged_event_during_hard_reboot has been added, " "defaulting to an empty list, that can be used to ensure that the libvirt " "driver waits for the network-vif-plugged event for vifs with specific " "``vnic_type`` before it unpauses the domain during hard reboot. This should " "only be used if the deployment uses a networking backend that sends such " "event for the given ``vif_type`` at vif plug time. The ml2/ovs and the " "networking-odl Neutron backend is known to send plug time events for ports " "with ``normal`` ``vnic_type``. For more information see https://bugs." "launchpad.net/nova/+bug/1946729" msgstr "" #: ../../:415 msgid "The libvirt virt driver now supports new features :" msgstr "" #: ../../:195 unmaintained/wallaby>:951 msgid "" "The libvirt virt driver will no longer attempt to fetch volume encryption " "metadata or the associated secret key when attaching ``LUKSv1`` encrypted " "volumes if a libvirt secret already exists on the host." msgstr "" #: ../../:648 msgid "" "The libvirt virt driver will now attempt to record the machine type of an " "instance at startup and when launching an instance if the machine type is " "not already recorded in the image metadata associated with the instance." msgstr "" #: ../../:414 msgid "" "The lists of operations that are supported or unsupported for instances with " "accelerators are listed in `accelerator operation guide `_" msgstr "" #: ../../:1799 msgid "The live, rolling upgrade has all compute hosts running Rocky code" msgstr "" #: ../../:936 stable/pike>:1009 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 have changed the default to 0, which " "means do not trigger a timeout. 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 "" #: ../../:672 msgid "" "The machine type is supported. The supported list includes alias and " "versioned types of ``pc``, ``pc-i440fx``, ``pc-q35``, ``q35``, ``virt``, " "``s390-ccw-virtio``, ``hyperv-gen1`` and ``hyperv-gen2`` as supported by the " "hyperv driver." msgstr "" #: ../../:993 msgid "" "The main advantage to this is to catch invalid configurations as early as " "possible so that we can return a useful error to the user rather than fail " "later on much further down the stack where the operator would have to get " "involved." msgstr "" #: ../../:633 msgid "" "The microversion 2.62 adds ``host`` (hostname) and ``hostId`` (an obfuscated " "hashed host id string) fields to the instance action ``GET /servers/" "{server_id}/os-instance-actions/{req_id}`` API. The display of the newly " "added ``host`` field will be controlled via policy rule ``os_compute_api:os-" "instance-actions:events``, which is the same policy used for the ``events." "traceback`` field. If the user is prevented by policy, only ``hostId`` will " "be displayed." msgstr "" #: ../../:270 #: stable/pike>:338 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 "" #: ../../:430 stable/rocky>:1522 msgid "" "The minimum ``nova-osapi_compute`` service version is less than 15 in any " "given cell" msgstr "" #: ../../:758 msgid "" "The minimum required version of QEMU used by the `nova-compute` service is " "now 4.2.0. The next minimum required version to be used in a future release " "is 5.2.0." msgstr "" #: ../../:236 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 "" #: ../../:1236 msgid "" "The minimum required version of libvirt used by the `nova-compute` service " "is now 1.2.9. The minimum required version of QEMU used by the `nova-" "compute` service is now 2.1.0. Failing to meet these minimum versions when " "using the libvirt compute driver will result in the `nova-compute` service " "not starting." msgstr "" #: ../../:1747 msgid "" "The minimum required version of libvirt used by the `nova-compute` service " "is now 1.3.1. And the minimum required version of QEMU used by the `nova-" "compute` service is now 2.5.0. Failing to meet these minimum versions when " "using the libvirt compute driver will result in the `nova-compute` service " "not starting." msgstr "" #: ../../:677 msgid "" "The minimum required version of libvirt used by the `nova-compute` service " "is now 5.0.0. The minimum required version of QEMU used by the `nova-" "compute` service is now 4.0.0. Failing to meet these minimum versions when " "using the libvirt compute driver will result in the `nova-compute` service " "not starting." msgstr "" #: ../../:754 msgid "" "The minimum required version of libvirt used by the `nova-compute` service " "is now 6.0.0. The next minimum required version to be used in a future " "release is 7.0.0." msgstr "" #: ../../:1332 msgid "The minimum required version of shred has been increased to 8.22." msgstr "" #: ../../:1462 msgid "" "The minimum version of libvirt on AArch64 architecture that nova compute " "will interoperate with is now 3.6.0. Deployments using older versions of " "libvirt on AArch64 should upgrade." msgstr "" #: ../../:692 msgid "" "The model name vhostuser_vrouter_plug is set by the neutron contrail plugin " "during a VM (network port) creation. The libvirt compute driver now supports " "plugging virtual interfaces of type \"contrail_vrouter\" which are provided " "by the contrail-nova-vif-driver plugin [1]. [1] https://github.com/Juniper/" "contrail-nova-vif-driver" msgstr "" #: ../../:1841 msgid "The motivation behind these changes are:" msgstr "" #: ../../:677 msgid "" "The network.json metadata format has been amended for IPv6 networks under " "Neutron control. The type that is shown has been changed from being always " "set to ``ipv6_dhcp`` to correctly reflecting the ``ipv6_address_mode`` " "option in Neutron, so the type now will be ``ipv6_slaac``, ``ipv6_dhcpv6-" "stateless`` or ``ipv6_dhcpv6-stateful``." msgstr "" #: ../../:1579 msgid "" "The new ``[scheduler]workers`` configuration option defaults to ``ncpu`` " "workers if using the ``filter_scheduler`` scheduler driver. If you are " "running *nova-scheduler* on the same host as other services, you may want to " "change this default value, or to otherwise account for running other " "instances of the *nova-scheduler* service." msgstr "" #: ../../:783 msgid "" "The new ``img_hide_hypervisor_id`` image metadata property hides the " "hypervisor signature for the guest." msgstr "" #: ../../:120 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 "" #: ../../:1102 msgid "" "The new configuration option ``[compute]/" "consecutive_build_service_disable_threshold`` defaults to a nonzero value, " "which means multiple failed builds will result in a compute node auto-" "disabling itself." msgstr "" #: ../../:925 msgid "" "The new configuration option, ``[compute]/max_disk_devices_to_attach`` " "defaults to ``-1`` (unlimited). Users of the libvirt driver should be " "advised that the default limit for non-ide disk buses has changed from 26 to " "unlimited, upon upgrade to Stein. The ``ide`` disk bus continues to be " "limited to 4 attached devices per server." msgstr "" #: ../../:1384 msgid "" "The new style ``policy`` field has been added to ``ServerGroupPayload``. The " "``server_group.create``, ``server_group.delete`` and ``server_group." "add_member`` versioned notifications will be updated to include the new " "``policy`` and ``rules`` field. The ``policies`` field is deprecated for " "removal but still put into the notification payload for backward " "compatibility." msgstr "" #: ../../:242 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 "" #: ../../:671 msgid "" "The nova Hyper-V driver can now plug OVS VIFs. This means that neutron-ovs-" "agent can be used as an L2 agent instead of neutron-hyperv-agent. In order " "to plug OVS VIFs, the configuration option \"vswitch_name\" from the " "\"hyperv\" section must be set to the vSwitch which has the OVS extension " "enabled. Hot-plugging is only supported on Windows / Hyper-V Server 2016 + " "Generation 2 VMs. Older Hyper-V versions only support attaching vNICs while " "the VM is turned off." msgstr "" #: ../../:675 msgid "" "The nova Hyper-V driver now supports adding PCI passthrough devices to Hyper-" "V instances (discrete device assignment). This feature has been introduced " "in Windows / Hyper-V Server 2016 and offers the possibility to attach some " "of the host's PCI devices (e.g.: GPU devices) directly to Hyper-V instances. " "In order to benefit from this feature, Hyper-V compute nodes must support SR-" "IOV and must have assignable PCI devices. This can easily be checked by " "running the following powershell commands::" msgstr "" #: ../../:710 msgid "" "The nova Hyper-V driver now supports symmetric NUMA topologies. This means " "that all the NUMA nodes in the NUMA topology must have the same amount of " "vCPUs and memory. It can easily be requested by having the flavor extra_spec " "\"hw:numa_nodes\", or the image property \"hw_numa_nodes\". An instance with " "NUMA topology cannot have dynamic memory enabled. Thus, if an instance " "requires a NUMA topology, it will be spawned without dynamic memory, " "regardless of the value set in the \"dynamic_memory_ratio\" config option in " "the compute node's \"nova.conf\" file. In order to benefit from this " "feature, the host's NUMA spanning must be disabled. Hyper-V does not " "guarantee CPU pinning, thus, the nova Hyper-V driver will not spawn " "instances with the flavor extra_spec \"hw:cpu_policy\" or image property " "\"hw_cpu_policy\" set to \"dedicated\"." msgstr "" #: ../../:270 unmaintained/xena>:686 msgid "" "The nova libvirt driver supports two independent features, virtual CPU " "topologies and virtual NUMA topologies. Previously, when ``hw:" "cpu_max_sockets``, ``hw:cpu_max_cores`` and ``hw:cpu_max_threads`` were " "specified for pinned instances (``hw:cpu_policy=dedicated``) without " "explicit ``hw:cpu_sockets``, ``hw:cpu_cores``, ``hw:cpu_threads`` extra " "specs or their image equivalent, nova failed to generate a valid virtual CPU " "topology. This has now been fixed and it is now possible to use max CPU " "constraints with pinned instances. e.g. a combination of ``hw:numa_nodes=" "2``, ``hw:cpu_max_sockets=2``, ``hw:cpu_max_cores=2``, ``hw:cpu_max_threads=" "8`` and ``hw:cpu_policy=dedicated`` can now generate a valid topology using " "a flavor with 8 vCPUs." msgstr "" #: ../../:190 stable/ussuri>:1379 msgid "" "The nova libvirt virt driver supports creating instances with multi-queue " "virtio network interfaces. In previous releases nova has based the maximum " "number of virtio queue pairs that can be allocated on the reported kernel " "major version. It has been reported in `bug #1847367`_ that some distros " "have backported changes from later major versions that make major version " "number no longer suitable to determine the maximum virtio queue pair count. " "A new config option has been added to the libvirt section of the nova.conf. " "When defined nova will now use the ``[libvirt]/max_queues`` option to define " "the max queues that can be configured, if undefined it will fallback to the " "previous kernel version approach." msgstr "" #: ../../:1612 msgid "" "The nova metadata service will now pass a nove service token to the external " "vendordata server. These options can be configured using various Keystone-" "related options available in the ``vendordata_dynamic_auth`` group. A new " "service token has been created for this purpose. Previously, the requesting " "user's keystone token was passed through to the external vendordata server " "if available, otherwise no token is passed. This resolves issues with " "scenarios such as cloud-init's use of the metadata server on first boot to " "determine configuration information. Refer to the blueprints at http://" "specs.openstack.org/openstack/nova-specs/specs/ocata/approved/vendordata-" "reboot-ocata.html for more information." msgstr "" #: ../../:1280 msgid "" "The nova-all binary to launch all services has been removed after a " "deprecation period. It was only intended for testing purposes and not " "production use. Please use the individual Nova binaries to launch services." msgstr "" #: ../../:955 msgid "" "The nova-api service needs to understand how to connect to the placement " "service in order for this mirroring process to work. Administrators should " "ensure that there is a ``[placement]`` section in the nova.conf file which " "is used by the nova-api service, and that credentials for interacting with " "placement are contained in that section." msgstr "" #: ../../:490 stable/rocky>:1977 msgid "" "The nova-compute service now allows specifying the interval for updating " "nova-compute-side cache of the compute node resource provider's aggregates " "and traits info via a new config option called ``[compute]/" "resource_provider_association_refresh`` which defaults to 300. This was " "previously hard-coded to run every 300 seconds which may be too often in a " "large deployment." msgstr "" #: ../../:551 msgid "The nova-consoleauth service has been deprecated." msgstr "" #: ../../:1369 msgid "" "The nova-idmapshift binary has been removed. This has been replaced by " "internal functionality using privsep." msgstr "" #: ../../:1219 msgid "" "The nova-manage command now has a 'db purge' command that will delete data " "from the shadow tables after 'db archive_deleted_rows' has been run. There " "is also now a ``--purge`` option for 'db archive_deleted_rows' that will " "automatically do a full purge after archiving." msgstr "" #: ../../:275 stable/queens>:566 stable/rocky>:797 msgid "" "The nova-manage discover_hosts command now has a ``--by-service`` option " "which allows discovering hosts in a cell purely by the presence of a nova-" "compute binary. At this point, there is no need to use this unless you're " "using ironic, as it is less efficient. However, if you are using ironic, " "this allows discovery and mapping of hosts even when no ironic nodes are " "present." msgstr "" #: ../../:901 msgid "" "The nova-manage online_data_migrations command now prints a tabular summary " "of completed and remaining records. The goal here is to get all your numbers " "to zero. The previous execution return code behavior is retained for " "scripting." msgstr "" #: ../../:1247 msgid "" "The nova-network service was deprecated in the 14.0.0 Newton release. In the " "15.0.0 Ocata release, nova-network will only work in a Cells v1 deployment. " "The Neutron networking service is now the default configuration for new " "deployments based on the ``use_neutron`` configuration option." msgstr "" #: ../../:1685 msgid "" "The nova-network specific API to query the server's interfaces is deprecated:" ":" msgstr "" #: ../../:407 msgid "" "The nova-scheduler service now verifies which compute nodes can be used for " "instances having `requested networks or ports`__ by looking at the network " "segments related to the compute nodes." msgstr "" #: ../../:1262 msgid "" "The nova-xvpvncproxy service is deprecated as it is Xen specific and has " "effectively been replaced by noVNC and the nova-novncproxy service." msgstr "" #: ../../:25 stable/ussuri>:71 #: unmaintained/victoria>:133 unmaintained/wallaby>:325 unmaintained/xena>:627 msgid "" "The novnc, serial, and spice console proxies will now reject requests that " "pass a redirection URL beginning with \"//\" with a 400 Bad Request." msgstr "" #: ../../:1399 msgid "" "The old deprecated ``keymgr`` options have been removed. Configuration " "options using the ``[keymgr]`` group will not be applied anymore. Use the " "``[key_manager]`` group from Castellan instead. The Castellan ``api_class`` " "options should also be used instead, as most of the options that lived in " "Nova have migrated to Castellan." msgstr "" #: ../../:969 msgid "" "The online data migration ``migrate_instances_add_request_spec``, which was " "added in the 14.0.0 Newton release, has now been removed. Compatibility code " "in the controller services for old instances without a matching " "``request_specs`` entry in the ``nova_api`` database is also gone. Ensure " "that the ``Request Spec Migration`` check in the ``nova-status upgrade " "check`` command is successful before upgrading to the 19.0.0 Stein release." msgstr "" #: ../../:1354 msgid "" "The operator will have to create pools of devices with tag trusted=true." msgstr "" #: ../../:1085 msgid "" "The operators should specify a vGPU resource in the flavor's extra_specs::" msgstr "" #: ../../:1094 msgid "" "The os-volume_attachments APIs no longer check ``os_compute_api:os-volumes`` " "policy. They do still check ``os_compute_api:os-volumes-attachments`` policy " "rules. Deployers who have customized policy should confirm that their " "settings for os-volume_attachments policy checks are sufficient." msgstr "" #: ../../:1327 msgid "" "The payload of the ``instance.create.start`` and ``instance.create.end`` and " "``instance.create.error`` versioned notifications have been extended with " "the ``trusted_image_certificates`` field that contains the list of trusted " "certificate IDs used when the instance is created." msgstr "" #: ../../:1332 msgid "" "The payload of the ``instance.rebuild.start`` and ``instance.rebuild.end`` " "and ``instance.rebuild.error`` versioned notifications have been extended " "with the ``trusted_image_certificates`` field that contains the list of " "trusted certificate IDs used when the instance is rebuilt. This change also " "causes the type of the payload object to change from " "``InstanceActionPayload`` version 1.6 to ``InstanceActionRebuildPayload`` " "version 1.7. See the `notification dev reference`_ for the sample file of " "``instance.rebuild.start`` as an example." msgstr "" #: ../../:870 msgid "" "The payload of the ``instance.snapshot.start`` and ``instance.snapshot.end`` " "notifications have been extended with the ``snapshot_image_id`` field that " "contains the image id of the snapshot created. This change also causes that " "the type of the payload object has been changed from " "``InstanceActionPayload`` version 1.5 to ``InstanceActionSnapshotPayload`` " "version 1.6. See the `notification dev reference`_ for the sample file of " "``instance.snapshot.start`` as an example." msgstr "" #: ../../:843 msgid "The placement API is only available to admin users." msgstr "" #: ../../:861 msgid "" "The placement API service can now be configured to support `CORS `_. If a `cors` " "configuration group is present in the service's configuration file " "(currently `nova.conf`), with `allowed_origin` configured, the values within " "will be used to configure the middleware. If `cors.allowed_origin` is not " "set, the middleware will not be used." msgstr "" #: ../../:546 msgid "" "The placement service now supports granular RBAC policy rules configuration. " "See the `placement policy`_ documentation for details." msgstr "" #: ../../:596 msgid "" "The placement service should be upgraded before the nova controller and " "compute services. See the `Pike Upgrade Notes for Queens`_ for more details." msgstr "" #: ../../:444 msgid "" "The powervm virt driver has been removed. The driver was not tested by the " "OpenStack project nor did it have clear maintainers and thus its quality " "could not be ensured." msgstr "" #: ../../:548 msgid "" "The powervm virt driver is deprecated and may be removed in a future release." " The driver is not tested by the OpenStack project nor does it have clear " "maintainers and thus its quality can not be ensured." msgstr "" #: ../../:748 msgid "" "The query parameter schema of the ``GET /os-migrations`` API no longer " "allows additional properties." msgstr "" #: ../../:612 msgid "" "The quota system has been reworked to `count resources`_ at the point of " "creation rather than using a reserve/commit/rollback approach. No operator " "impacts are expected." msgstr "" #: ../../:294 msgid "" "The reasons this is happening are discussed in bug 1829062_. There are three " "workarounds available:" msgstr "" #: ../../:1033 stable/queens>:1182 msgid "" "The recommended work around is to assign a resource class to all ironic " "nodes, and use it for scheduling of bare metal instances." msgstr "" #: ../../:1463 msgid "" "The reporting for bytes available for RBD has been enhanced to accomodate " "`unrecommended `_ Ceph deployments where multiple OSDs " "are running on a single disk. The new reporting method takes the number of " "configured replicas into consideration when reporting bytes available." msgstr "" #: ../../:1077 msgid "" "The required ironic API version is updated to 1.32. The ironic service must " "be upgraded to an ironic release > 8.0 before nova is upgraded, otherwise " "all ironic intergration will fail." msgstr "" #: ../../:793 msgid "The result should not be (for KVM hypervisor)::" msgstr "" #: ../../:655 msgid "" "The same policy rule (os_compute_api:os-server-groups) was being used for " "all actions (show, index, delete, create) for server_groups REST APIs. It " "was thus impossible to provide different RBAC for specific actions based on " "roles. To address this changes were made to have separate policy rules for " "each action. The original rule (os_compute_api:os-server-groups) is left " "unchanged for backward compatibility." msgstr "" #: ../../:786 msgid "" "The scheduler can now use placement to more efficiently query for hosts that " "support the disk_format of the image used in a given request. The " "``[scheduler]/query_placement_for_image_type_support`` config option enables " "this behavior, but must not be turned on until all computes have been " "upgraded to this version and thus are exposing image type support traits." msgstr "" #: ../../:1276 msgid "" "The scheduler can now use placement to more efficiently query for hosts " "within a tenant-restricted aggregate. This requires that a host aggregate is " "created in nova with the ``filter_tenant_id`` key (optionally suffixed with " "any string for multiple tenants, like ``filter_tenant_id3=$tenantid``) and " "the same aggregate is created in placement with an identical UUID. The " "``[scheduler]/limit_tenants_to_placement_aggregate`` config option enables " "this behavior and ``[scheduler]/placement_aggregate_required_for_tenants`` " "makes it either optional or mandatory, allowing only some tenants to be " "restricted. For more information, see the schedulers section__ of the " "administration guide." msgstr "" #: ../../:670 msgid "" "The scheduler can now use placement to more efficiently query for hosts " "within an availability zone. This requires that a host aggregate is created " "in nova with the ``availability_zone`` key set, and the same aggregate is " "created in placement with an identical UUID. The ``[scheduler]/" "query_placement_for_availability_zone`` config option enables this behavior " "and, if enabled, eliminates the need for the ``AvailabilityZoneFilter`` to " "be enabled." msgstr "" #: ../../:515 msgid "" "The scheduler can now verify if the requested networks or the port are " "related to Neutron `routed networks`_ with some specific segments to use. In " "this case, the routed networks prefilter will require the related aggregates " "to be reported in Placement, so only hosts within the asked aggregates would " "be accepted. In order to support this behaviour, operators need to set the " "``[scheduler]/query_placement_for_routed_network_aggregates`` configuration " "option which defaults to ``False``." msgstr "" #: ../../:1424 msgid "" "The scheduler now requests allocation candidates from the Placement service " "during scheduling. The allocation candidates information was introduced in " "the Placement API 1.10 microversion, so you should upgrade the placement " "service before the Nova scheduler service so that the scheduler can take " "advantage of the allocation candidate information." msgstr "" #: ../../:983 msgid "" "The scheduler will pass required traits to the ``GET /" "allocation_candidates`` endpoint in the Placement API to include only " "resource providers that can satisfy the required traits. Currently the only " "valid value is ``required``. Any other value will be considered invalid." msgstr "" #: ../../:851 msgid "" "The scheduler will pass the forbidden traits to the ``GET /" "allocation_candidates`` endpoint in the Placement API to include only " "resource providers that do not include the forbidden traits. Currently the " "only valid values are ``required`` and ``forbidden``. Any other values will " "be considered invalid." msgstr "" #: ../../:687 msgid "" "The script above will print a list of assignable PCI devices available on " "the host, and if the host supports SR-IOV." msgstr "" #: ../../:374 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 "" #: ../../:885 msgid "" "The semantic of the (unnumbered) ``resources`` and ``trait`` keys is " "unchanged: the resources and traits specified thereby may be satisfied by " "any provider on the same host or associated via aggregate." msgstr "" #: ../../:1156 msgid "" "The semantic of the (unnumbered) ``resources``, ``required``, and " "``member_of`` query parameters is unchanged: the resources, traits, and " "aggregate associations specified thereby may be satisfied by any provider in " "the same non-sharing tree or associated via the specified aggregate(s)." msgstr "" #: ../../:597 msgid "" "The server ``evacuate``, ``os-migrateLive`` and ``unshelve`` action APIs now " "support servers with neutron ports having resource requests, e.g. ports that " "have QoS minimum bandwidth rules attached." msgstr "" #: ../../:838 msgid "" "The shutdown retry interval in powering off instances can now be set using " "the configuration setting ``shutdown_retry_interval``, in the compute " "configuration group." msgstr "" #: ../../:882 msgid "" "The support for guest RAM encryption using AMD SEV (Secure Encrypted " "Virtualization) added in Train is incompatible with a number of image " "metadata options:" msgstr "" #: ../../:575 msgid "" "The support to abort live migrations with ``queued`` and ``preparing`` " "status using ``DELETE /servers/{server_id}/migrations/{migration_id}`` API " "has been added in microversion 2.65." msgstr "" #: ../../:1188 msgid "" "The three configuration options ``cpu_allocation_ratio``, " "``ram_allocation_ratio`` and ``disk_allocation_ratio`` for the nova compute " "are now checked against negative values. If any of these three options is " "set to negative value then nova compute service will fail to start." msgstr "" #: ../../:1291 msgid "" "The transition from rootwrap (or sudo) to privsep has been completed for " "nova. The only case where rootwrap is still used is to start privsep helpers." " All other rootwrap configurations for nova may now be removed." msgstr "" #: ../../:1083 msgid "" "The type of following config options have been changed from string to URI. " "They are checked whether they follow the URI format or not and its scheme." msgstr "" #: ../../:680 msgid "" "The update will not move the instance between an alias and versioned machine " "type or vice versa. For example, ``pc`` to ``pc-1.2.3`` or ``pc-1.2.3`` to " "``pc``." msgstr "" #: ../../:677 msgid "" "The update will not move the instance between underlying machine types. For " "example, ``pc`` to ``q35``." msgstr "" #: ../../:450 msgid "" "The upgrade check tooling now returns a non-zero exit code in the presence " "of compute node services that are too old. This is to avoid situations in " "which Nova control services fail to start after an upgrade." msgstr "" #: ../../:1080 msgid "" "The values of ``model-name ( RO):`` from the output of the above commands " "are the vGPU type names which you can choose from to set the nova configure -" " ``[devices]/enabled_vgpu_types``. Please choose only one vGPU type to be " "enabled." msgstr "" #: ../../:886 msgid "" "The vendordata metadata system now caches boot time roles. Some external " "vendordata services want to provide metadata based on the role of the user " "who started the instance. It would be confusing if the metadata returned " "changed later if the role of the user changed, so we cache the boot time " "roles and then pass those to the external vendordata service." msgstr "" #: ../../:894 msgid "" "The vendordata metadata system now supports a hard failure mode. This can be " "enabled using the ``api.vendordata_dynamic_failure_fatal`` configuration " "option. When enabled, an instance will fail to start if the instance cannot " "fetch dynamic vendordata." msgstr "" #: ../../:1290 msgid "" "The versioned ``instance.lock`` and ``instance.unlock`` notifications have " "been added. These notifications are emitted as a result of the respective " "server ``lock`` and server ``unlock`` REST API calls." msgstr "" #: ../../:775 msgid "" "The versioned notification interface of nova is now complete and in feature " "parity with the legacy interface. The emitted notifications are documented " "in `notification dev ref`_ with full sample files. The deprecation of the " "legacy notification interface is under dicussion and will be handled " "separately." msgstr "" #: ../../:639 msgid "" "The versioned_notifications_topic configuration option; This enables one to " "configure the topics used for versioned notifications." msgstr "" #: ../../:1082 msgid "" "The vmwareapi driver is deprecated in this release and may be removed in a " "future one. The driver is not tested by the OpenStack Nova project and does " "not have a clear maintainer." msgstr "" #: ../../:312 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 "" #: ../../:700 msgid "" "The vmwareapi driver was deprecated in Ussuri due to missing third-party CI " "coverage and a clear maintainer. These issues have been addressed during the " "Victoria cycle and the driver is now undeprecated." msgstr "" #: ../../:1079 msgid "The whitelist for REST API filters for admin users:" msgstr "" #: ../../:1134 msgid "The whitelist for sort keys for admin users:" msgstr "" #: ../../:1234 msgid "" "The xenapi driver is deprecated and may be removed in a future release. The " "driver is not tested by the OpenStack project nor does it have clear " "maintainer(s) and thus its quality can not be ensured. If you are using the " "driver in production please let us know in freenode IRC and/or the openstack-" "discuss mailing list." msgstr "" #: ../../:1089 msgid "" "Then users can use the flavor to boot instances with a vGPU attached. At the " "moment, XenServer doesn't support multiple vGPUs for a single instance, so " "``resources:VGPU`` in the flavor's extra_specs should always be ``1``." msgstr "" #: ../../:154 stable/2023.2>:98 stable/2024.1>:24 #: stable/stein>:409 stable/train>:461 stable/ussuri>:337 #: unmaintained/victoria>:291 unmaintained/wallaby>:388 unmaintained/xena>:294 #: unmaintained/yoga>:248 unmaintained/zed>:167 msgid "" "There are a few major changes worth mentioning. This is not an exhaustive " "list:" msgstr "" #: ../../:860 msgid "There are some known caveats with this:" msgstr "" #: ../../:1015 msgid "" "There are some things to note when opting in to counting quota usage from " "placement:" msgstr "" #: ../../:1109 msgid "" "There are still known race issues with concurrently building some types of " "resources and workloads, such as anything that requires PCI/NUMA or (anti-" ")affinity groups. However, those races also existed with the " "``caching_scheduler`` driver." msgstr "" #: ../../:1002 msgid "There are three policies supported:" msgstr "" #: ../../:1365 msgid "" "There had been `bug 1777591`_ that placement filters out the specified " "target host when deploying an instance by the random limitation. In previous " "releases the bug has been worked around by unlimiting the results from the " "Placement service if the target host is specified. From this release, the " "Nova scheduler uses more optimized path retrieving only the target host " "information from placement. Note that it still uses the unlimit workaround " "if a target host is specified without a specific node and multiple nodes are " "found for the target host. This can happen in some of the virt drivers such " "as the Ironic driver." msgstr "" #: ../../:21 stable/pike>:21 #: stable/queens>:91 stable/rocky>:183 stable/stein>:329 stable/train>:1275 msgid "" "There is a behavior change where non-nova exceptions will only record the " "exception class name in the fault ``message`` field which is exposed to all " "users, regardless of the admin role." msgstr "" #: ../../:444 msgid "" "There is a known regression in Ocata reported in `bug 1671648`_ where server " "build failures on a compute node are not retried on another compute node. " "The fix for this bug is being worked and will be provided shortly in a 15.0." "2 release." msgstr "" #: ../../:1784 msgid "" "There is a new configuration option ``[workarounds]/enable_consoleauth`` for " "use by operators who:" msgstr "" #: ../../:153 msgid "" "There is a new nova-manage command ``db ironic_compute_node_move`` that can " "be used to move ironic nodes, and the associated instances, between nova-" "compute services. This is useful when migrating from the legacy hash ring " "based HA towards the new sharding approach." msgstr "" #: ../../:551 msgid "" "There is a new nova-status command that gives operators a better view of " "their cloud. In particular, a new subcommand called \"upgrade\" allows " "operators to run a pre-flight check on their deployment before upgrading. " "This helps them to proactively identify potential upgrade issues that could " "occur." msgstr "" #: ../../:466 msgid "There is no known workaround within OpenStack Nova to this issue." msgstr "" #: ../../:245 msgid "" "There is one caveat, which is that the wsgi app configuration must be left " "as the default ``threads=1`` or set explicitly to ``threads=1`` to ensure " "that reconnection will work properly. When threads > 1, it is not guaranteed " "that oslo.messaging will reconnect to rabbitmq when the wsgi app resumes " "after pausing during idle time. Threads are used internally by oslo." "messaging for heartbeats and more, and it may fail in a variety of ways if " "run under eventlet with an app that violates eventlet's threading guarantees." " When oslo.messaging does not reconnect to rabbitmq after a wsgi app pause, " "RPC requests will fail with a ``MessagingTimeout`` error. So, it is " "necessary to have the wsgi app configured with ``threads=1`` for " "reconnection to work properly." msgstr "" #: ../../:1877 msgid "" "There really never was a good reason to disable or enable non-compute " "services anyway since that would not do anything. The nova-scheduler and " "nova-api services are checking the ``status`` and ``forced_down`` fields to " "see if instance builds can be scheduled to a compute host or if instances " "can be evacuated from a downed compute host. There is nothing that relies on " "a disabled or downed nova-conductor or nova-scheduler service." msgstr "" #: ../../:290 #: stable/pike>:418 stable/queens>:1689 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 "" #: ../../:1619 msgid "" "These commands will be removed in their entirety during the Queens cycle." msgstr "" #: ../../:211 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 explictly to configure the " "associated SPICE compression setting for libvirt. If all configuration " "options are not set, then none of the SPICE compression settings will be " "configured for libvirt, which corresponds to the behavior before this change." " In this case, the built-in defaults from the libvirt backend (e.g. QEMU) " "are used." msgstr "" #: ../../:1653 msgid "These have not been used in recent releases." msgstr "" #: ../../:903 msgid "" "These options help operators specify initial virtual CPU/ram/disk to " "physical CPU/ram/disk allocation ratios. These options are only used when " "initially creating the ``computes_nodes`` table record for a given nova-" "compute service." msgstr "" #: ../../:1069 msgid "These options should no longer be included in the ``DEFAULT`` group." msgstr "" #: ../../:1693 msgid "" "These were deprecated in 17.0.0 as they have been superseded by their " "respective keystoneauth1 Adapter configuration options." msgstr "" #: ../../:1394 stable/rocky>:1682 msgid "" "These were deprecated in the 15.0.0 release as they allowed for inconsistent " "API behavior across deployments." msgstr "" #: ../../:1669 msgid "" "These were deprecated in the 16.0.0 release as they allowed inconsistent API " "behavior across deployments. To disable snapshots in the ``createImage`` " "server action API, change the ``os_compute_api:servers:create_image`` and " "``os_compute_api:servers:create_image:allow_volume_backed`` policies." msgstr "" #: ../../:1158 msgid "" "These were deprecated in the 17.0.0 release as nova removed the concept of " "API extensions." msgstr "" #: ../../:908 msgid "" "These were only useful for the now-removed *nova-network* service and have " "been deprecated since the 15.0.0 (Ocata) release." msgstr "" #: ../../:1431 msgid "These were previously deprecated in 16.0.0." msgstr "" #: ../../:1327 msgid "" "These were used by the now-removed ``LibvirtGlusterfsVolumeDriver`` volume " "driver and therefore no longer had any effect." msgstr "" #: ../../:1350 msgid "" "These were used by the now-removed ``LibvirtScalityVolumeDriver`` volume " "driver and therefore no longer had any effect." msgstr "" #: ../../:919 msgid "" "These will allow using a file trigger for the reports, which is particularly " "useful for Windows nodes where the default signals are not available. Also, " "specifying a log directory will allow the reports to be generated at a " "specific location instead of stdout." msgstr "" #: ../../:558 msgid "" "This API provides information about the NUMA topology of a server, including " "instance to host CPU pin mappings, if CPU pinning is used, and pagesize " "information." msgstr "" #: ../../:337 msgid "This adds to the list of already existing enlightenments, namely:" msgstr "" #: ../../:1408 msgid "" "This aims to address issues reported in `bug 1834048`_ where failures to " "initially connect to a RBD cluster left the nova-compute service inoperable " "due to constant RPC timeouts being hit." msgstr "" #: ../../:1345 msgid "" "This aims to address the issues reported in `bug 1842149`_, where it " "describes that the proxy services can inherit insecure TLS ciphers and " "protocol versions from the compiled-in defaults of the OpenSSL library on " "the underlying system. The proxy services provided no way to override such " "insecure defaults with current day generally accepted secure TLS settings." msgstr "" #: ../../:1591 msgid "" "This allows for the creation, deletion, update and listing of \"agent " "builds\". Operators should use the equivalent resources in the `REST API`__ " "instead." msgstr "" #: ../../:1582 msgid "" "This allows for the creation, deletion, update and listing of user and " "project quotas. Operators should use the equivalent resources in the `REST " "API`__ instead." msgstr "" #: ../../:1602 msgid "" "This allows for the filtering of errors from nova's logs and extraction of " "all logs from syslog. This command has not been actively maintained in a " "long time, is not tested, and can be achieved using `journalctl` or by " "simply grepping through ``/var/log``. It will simply be removed." msgstr "" #: ../../:1597 msgid "" "This allows for the listing of compute hosts. Operators should use the " "equivalent resources in the `REST API`__ instead." msgstr "" #: ../../:31 current msgid "" "This also simplifies deployment with other WSGI servers that expect module " "paths such as gunicorn." msgstr "" #: ../../:742 msgid "" "This can be configured via a new configuration attribute ``[libvirt]/" "live_migration_with_native_tls``. Refer to its documentation in ``nova." "conf`` for usage details. Note that this is the preferred the way to secure " "all migration streams in an OpenStack network, instead of ``[libvirt]/" "live_migration_tunnelled``." msgstr "" #: ../../:1249 msgid "" "This change can have impacts, however, to deployment tooling that relies on " "parts of the API, like listing compute hosts, `before` the compute hosts are " "mapped using the ``nova-manage cell_v2 discover_hosts`` command." msgstr "" #: ../../:166 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 "" #: ../../:420 msgid "" "This change replaces the usage of older API, compareCPU(), with the new one, " "compareHypervisorCPU()." msgstr "" #: ../../:1834 msgid "" "This change should be transparent to end users and does not affect existing " "volume attachments. Also, this does not affect how new volumes are created " "and attached during boot-from-volume when the ``block_device_mapping_v2." "source_type`` is ``blank``, ``image`` or ``snapshot`` and the " "``block_device_mapping_v2.destination_type`` is ``volume``." msgstr "" #: ../../:690 msgid "" "This command will list instance UUIDs that do not have a machine type " "recorded. An optional cell UUID can be provided to list on instances without " "a machine type from that cell." msgstr "" #: ../../:661 msgid "" "This command will print the current machine type if set in the image " "metadata of the instance." msgstr "" #: ../../:666 msgid "" "This command will set or update the machine type of the instance assuming " "the following criteria are met:" msgstr "" #: ../../:206 msgid "" "This config option can be used to configure tb_cache size for guest VMs, " "it's only applicable with ``virt_type=qemu``." msgstr "" #: ../../:138 msgid "" "This ensures the graceful closure of console sessions on the server side, " "aligning with security best practices." msgstr "" #: ../../:1471 msgid "" "This establishes a consistent naming between VNC and Spice options and " "removes some unnecessary duplication." msgstr "" #: ../../:930 msgid "" "This feature is already implemented for Nova interaction with the Cinder and " "Neutron APIs in Ocata." msgstr "" #: ../../:1020 msgid "" "This feature is currently only supported by the libvirt compute driver and " "only then if qemu<2.10 or libvirt>3.10 on the compute host." msgstr "" #: ../../:685 msgid "" "This feature is disabled by default can be enabled via config option " "``[oslo_policy]enforce_scope`` in ``nova.conf``" msgstr "" #: ../../:482 msgid "This feature is only supported with the Libvirt driver." msgstr "" #: ../../:728 msgid "" "This feature is supported on Windows / Hyper-V Server 2012 R2 for Windows " "guests, and Windows / Hyper-V Server 2016 for both Windows and Linux guests." msgstr "" #: ../../:467 msgid "" "This feature relies on Neutron being upgraded to the corresponding release " "of OpenStack and having an appropriate backend capable of binding " "``VNIC_TYPE_REMOTE_MANAGED`` ports (at the time of writing, ML2 with the OVN " "ML2 mechanism driver is the only supported backend, see the Neutron " "documentation for more details)." msgstr "" #: ../../:370 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 "" #: ../../:131 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 "" #: ../../:691 msgid "" "This is a special operation that should only be used in rare cases of " "resource provider topology changing when inventory is in use. Only use this " "if you are really sure of what you are doing." msgstr "" #: ../../:1609 msgid "" "This is an alias for `account` and has been deprecated for the same reasons." msgstr "" #: ../../:529 msgid "" "This is different than the ``os_compute_api:servers:show:host_status`` " "policy rule which controls whether a user can view all possible host status " "in the aforementioned APIs including ``UP``, ``DOWN``, ``MAINTENANCE``, and " "``UNKNOWN``." msgstr "" #: ../../:391 stable/rocky>:2074 msgid "" "This is disabled by default for backward compatibilty and because the " "compute service cannot reliably determine which types of virtual interfaces " "(``port.binding:vif_type``) will send ``network-vif-plugged`` events without " "an accompanying port ``binding:host_id`` change. Open vSwitch and " "linuxbridge should be OK, but OpenDaylight is at least one known backend " "that will not currently work in this case, see bug https://launchpad.net/" "bugs/1755890 for more details." msgstr "" #: ../../:1001 msgid "" "This is not a regression, just a note about functionality that is not yet " "available. Support for modeling shared storage providers will be worked on " "in the Queens release." msgstr "" #: ../../:1415 msgid "This is now an optional positional argument. For example::" msgstr "" #: ../../:232 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 "" #: ../../:652 msgid "" "This machine type will then be used when the instance is restarted or " "migrated as it will now appear as an image metadata property associated with " "the instance." msgstr "" #: ../../:306 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 "" #: ../../:1761 msgid "" "This means it is no longer possible to class-load custom out-of-tree quota " "drivers." msgstr "" #: ../../:223 unmaintained/xena>:466 msgid "" "This option is primarily intended for CI and development clouds as a bridge " "for operators to mitigate the issue while they work with their upstream " "image vendors." msgstr "" #: ../../:758 msgid "" "This parameter (``changes-before``) does not change any read-deleted " "behavior in the os-instance-actions or os-migrations APIs. The os-instance-" "actions API with the 2.21 microversion allows retrieving instance actions " "for a deleted server resource. The os-migrations API takes an optional " "``instance_uuid`` filter parameter but does not support returning deleted " "migration records." msgstr "" #: ../../:104 stable/2023.2>:70 #: stable/2024.1>:313 unmaintained/zed>:43 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 "" #: ../../:1403 msgid "" "This plugin directly processes the VHD files in XenServer SR(Storage " "Repository). So this plugin only works when the host's SR type is file " "system based e.g. ext, nfs. This is the default plugin." msgstr "" #: ../../:1417 msgid "This plugin implements an image proxy in nova compute service." msgstr "" #: ../../:1409 msgid "" "This plugin implements an image upload method which attaches the VDI as a " "local disk in the VM in which the OpenStack Compute service runs. It uploads " "the raw disk to glance when creating an image; When booting an instance from " "a glance image, it downloads the image and streams it into the disk which is " "attached to the compute VM." msgstr "" #: ../../:814 msgid "" "This release adds support for Netronome's Agilio OVS VIF type. In order to " "use the accelerated plugging modes, external Neutron and OS-VIF plugins are " "required. Consult https://github.com/Netronome/agilio-ovs-openstack-plugin " "for installation and operation instructions. Consult the Agilio " "documentation available at https://support.netronome.com/ for more " "information about the plugin compatibility and support matrix." msgstr "" #: ../../:802 msgid "" "This release adds support for ``direct`` and ``virtio-forwarder`` VNIC types " "to the ``vrouter`` VIF type. In order to use these VNIC types, support is " "required from the version of OpenContrail, Contrail or Tungsten Fabric that " "is installed, as well the required hardware. At this time, the reference os-" "vif plugin is hosted on OpenContrail at https://github.com/Juniper/contrail-" "nova-vif-driver but is expected to transition to Tungsten Fabric in the " "future. Version 5.1 or later of the plugin is required to use these new VNIC " "types. Consult the `Tungsten Fabric documentation `_ for release notes, when available, about hardware " "support. For commercial support, consult the release notes from a downstream " "vendor." msgstr "" #: ../../:1014 msgid "" "This release adds support to attach a volume to multiple server instances. " "The feature can only be used in Nova if the volume is created in Cinder with " "the **multiattach** flag set to True. It is the responsibility of the user " "to use a proper filesystem in the guest that supports shared read/write " "access." msgstr "" #: ../../:1157 msgid "" "This release contains a fix for `bug 1748697`_ which distinguishes between " "resize and cold migrate such that the ``allow_resize_to_same_host`` config " "option is no longer used to determine if a server can be cold migrated to " "the same compute service host. Now when requesting a cold migration the API " "will check if the source compute node resource provider has the " "``COMPUTE_SAME_HOST_COLD_MIGRATE`` trait and if so the scheduler can select " "the source host. Note that the only in-tree compute driver that supports " "cold migration to the same host is ``VMwareVCDriver``." msgstr "" #: ../../:315 stable/ussuri>:1223 msgid "" "This release contains a fix for `bug 1856925`_ such that ``resize`` and " "``migrate`` server actions will be rejected with a 409 ``HTTPConflict`` " "response if the source compute service is down." msgstr "" #: ../../:735 msgid "" "This release contains a fix for `bug 1874032`_ which delegates snapshot " "upload into a dedicated thread. This ensures nova compute service stability " "on busy environment during snapshot, when concurrent snapshots or any other " "tasks slow down storage performance." msgstr "" #: ../../:95 stable/train>:304 stable/ussuri>:1202 msgid "" "This release contains a fix for a `regression`__ introduced in 15.0.0 " "(Ocata) where server create failing during scheduling would not result in an " "instance action record being created in the cell0 database. Now when " "creating a server fails during scheduling and is \"buried\" in cell0 a " "``create`` action will be created with an event named " "``conductor_schedule_and_build_instances``." msgstr "" #: ../../:265 #: stable/pike>:333 msgid "" "This release contains a schema migration for the ``nova_api`` database in " "order to address bug 1738094:" msgstr "" #: ../../:17 stable/pike>:17 #: stable/queens>:87 stable/rocky>:179 stable/stein>:325 stable/train>:1271 msgid "" "This release contains a security fix for `bug 1837877`_ where users without " "the admin role can be exposed to sensitive error details in the server " "resource fault ``message``." msgstr "" #: ../../:311 #: stable/pike>:430 stable/queens>:1741 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 "" #: ../../:151 origin/stable/ocata>:407 stable/pike>:220 #: stable/pike>:584 msgid "This release includes fixes for security vulnerabilities." msgstr "" #: ../../:649 msgid "" "This release includes work in progress support for Keystone's unified limits." " This should not be used in production. It is included so we can collect " "early feedback from operators around the performance of the new limits " "system. There is currently no way to export your existing quotas and import " "them into Keystone. There is also no proxy API to allow you to update " "unified limits via Nova APIs. All the update APIs behave as if you are using " "the noop driver when the unified limits quota driver is configured." msgstr "" #: ../../:1044 msgid "" "This release moves the ``vrouter`` VIF plug and unplug code to a separate " "package called ``contrail-nova-vif-driver``. This package is a requirement " "on compute nodes when using Contrail, OpenContrail or Tungsten Fabric as a " "Neutron plugin. At this time, the reference plugin is hosted on OpenContrail " "at https://github.com/Juniper/contrail-nova-vif-driver but is expected to " "transition to Tungsten Fabric in the future. Release ``r5.1.alpha0`` or " "later of the plugin is required, which will be included in Tungsten Fabric 5." "1." msgstr "" #: ../../:1568 msgid "" "This release moves the livirt driver ``IVS`` VIF plug-unplug to a separate " "package called ``os-vif-bigswitch``. This package is a requirement on " "compute nodes when using ``networking-bigswitch`` as neutron ML2 and L3 " "driver. Releases are available on https://pypi.org/project/os-vif-bigswitch/." " Major version for the package matches upstream neutron version number. " "Minor version tracks compatiblity with Big Cloud Fabric (BCF) releases, and " "typically is set to the lowest supported BCF release." msgstr "" #: ../../:989 msgid "" "This requires that the Placement API version 1.17 is available before the " "``nova-scheduler`` service can use this feature." msgstr "" #: ../../:857 msgid "" "This requires that the Placement API version 1.22 is available before the " "``nova-scheduler`` service can use this feature." msgstr "" #: ../../:199 unmaintained/wallaby>:955 msgid "" "This resolves `bug 1905701`_ where instances with ``LUKSv1`` encrypted " "volumes could not be restarted automatically by the ``nova-compute`` service " "after a host reboot when the ``[DEFAULT]/resume_guests_state_on_host_boot`` " "configurable was enabled." msgstr "" #: ../../:1614 msgid "" "This starts the Python interactive interpreter. It is a clone of the same " "functionality found in Django's `django-manage` command. This command hasn't " "been actively maintained in a long time and is not tested. It will simply be " "removed." msgstr "" #: ../../:896 msgid "" "This will be resolved in a future patch release. For more information, refer " "to `bug 1845986`__" msgstr "" #: ../../:1428 msgid "This workaround does not currently support extending attached volumes." msgstr "" #: ../../:1407 stable/ussuri>:1430 msgid "" "This workaround is temporary and will be removed during the W release once " "all impacted distributions have been able to update their versions of the " "libgcrypt library." msgstr "" #: ../../:126 unmaintained/zed>:391 msgid "" "This workaround will be deprecated and removed once Nova replaces the older " "libvirt APIs with their newer counterparts. The work is being tracked via " "this `blueprint cpu-selection-with-hypervisor-consideration`_." msgstr "" #: ../../:1683 msgid "" "Those server actions can be replaced by calling the Neutron API directly." msgstr "" #: ../../:1181 msgid "" "Three live-migration related configuration options were restricted by " "minimum values since 16.0.0 and will now raise a ValueError if these " "configuration options' values less than minimum values, instead of logging " "warning before. These configuration options are:" msgstr "" #: ../../:932 msgid "" "Throughout the Placement API, in microversion 1.15, 'last-modified' headers " "have been added to GET responses and those PUT and POST responses that have " "bodies. The value is either the actual last modified time of the most " "recently modified associated database entity or the current time if there is " "no direct mapping to the database. In addition, 'cache-control: no-cache' " "headers are added where the 'last-modified' header has been added to prevent " "inadvertent caching of resources." msgstr "" #: ../../:765 msgid "" "To address backwards compatibility, the new rules added to the flavor_manage." "py policy file, default to the existing rule, ``os_compute_api:os-flavor-" "manage``, if it is set to a non-default value." msgstr "" #: ../../:1021 msgid "" "To allow access to the versions REST API from diverse origins, CORS support " "has been added to the 'oscomputeversions' pipeline in '/etc/nova/api-paste." "ini'. Existing deployments that wish to enable support should add the 'cors' " "filter at the start of the 'oscomputeversions' pipeline." msgstr "" #: ../../:259 msgid "" "To enable this, provide `hw:viommu_model` in flavor extra spec or equivalent " "image metadata property `hw_viommu_model` and with the guest CPU " "architecture and OS allows, we will enable viommu in Libvirt driver. Support " "values intel|smmuv3|virtio|auto. Default to ``auto``. Which ``auto`` will " "automatically select ``virtio`` if Libvirt supports it, else ``intel`` on " "X86 (Q35) and ``smmuv3`` on AArch64. vIOMMU config will raise invalid " "exception if the guest architecture is neither X86 (Q35) or AArch64." msgstr "" #: ../../:21 unmaintained/zed>:435 msgid "" "To facilitate the transition to no Nova default for ````, " "its value will be removed during live migration unless a value is set in the " "``quota:cpu_shares`` extra spec. This can cause temporary CPU starvation for " "the live migrated instance if other instances on the destination host still " "have the old default ```` value. To fix this, hard reboot, " "cold migrate, or live migrate the other instances." msgstr "" #: ../../:362 unmaintained/xena>:732 msgid "" "To fix `device detach issues`__ in the libvirt driver the detach logic has " "been changed from a sleep based retry loop to waiting for libvirt domain " "events. During this change we also introduced two new config options to " "allow fine tuning the retry logic. For details see the description of the " "new ``[libvirt]device_detach_attempts`` and " "``[libvirt]device_detach_timeout`` config options." msgstr "" #: ../../:696 msgid "To implement the reader roles, Below policies are made more granular" msgstr "" #: ../../:683 msgid "To know each policy scope_type, please refer the `Policy Reference`_" msgstr "" #: ../../:1608 msgid "" "To make live-migration consistent with resize, confirm-resize and revert-" "resize operations, the migration status is changed to 'error' instead of " "'failed' in case of live-migration failure. With this change the periodic " "task '_cleanup_incomplete_migrations' is now able to remove orphaned " "instance files from compute nodes in case of live-migration failures. There " "is no impact since migration status 'error' and 'failed' refer to the same " "failed state." msgstr "" #: ../../:1133 msgid "" "To make use of VeNCrypt, configuration steps are required for both the `nova-" "novncproxy` service and libvirt on all the compute nodes. The ``/etc/libvirt/" "qemu.conf`` file should be modified to set the ``vnc_tls`` option to ``1``, " "and optionally the ``vnc_tls_x509_verify`` option to ``1``. Certificates " "must also be deployed on the compute node." msgstr "" #: ../../:1114 msgid "" "To migrate from the CachingScheduler to the FilterScheduler, operators can " "leverage the ``nova-manage placement heal_allocations`` command:" msgstr "" #: ../../:324 stable/rocky>:1948 msgid "" "To mitigate potential issues with compute nodes disabling themselves in " "response to failures that were either non-fatal or user-generated, the " "consecutive build failure counter functionality in the compute service has " "been changed to advise the scheduler of the count instead of self-disabling " "the service upon exceeding the threshold. The ``[compute]/" "consecutive_build_service_disable_threshold`` configuration option still " "controls whether the count is tracked, but the action taken on this value " "has been changed to a scheduler weigher. This allows the scheduler to be " "configured to weigh hosts with consecutive failures lower than other hosts, " "configured by the ``[filter_scheduler]/build_failure_weight_multiplier`` " "option. If the compute threshold option is nonzero, computes will report " "their failure count for the scheduler to consider. If the threshold value is " "zero, then computes will not report this value and the scheduler will assume " "the number of failures for non-reporting compute nodes to be zero. By " "default, the scheduler weigher is enabled and configured with a very large " "multiplier to ensure that hosts with consecutive failures are scored low by " "default." msgstr "" #: ../../:964 msgid "" "To mitigate this issue Nova no longer generates an empty path attribute to " "the script element when defining an interface. This resolves the issue with " "regards to virtual machine creation. To resolve the issue with regards to " "existing virtual machines a change to Libvirt is required, this is being " "tracked in `Bugzilla 1412834`_" msgstr "" #: ../../:811 msgid "" "To place a workload's emulator threads on a set of isolated physical CPUs, " "set the ``[compute]/cpu_shared_set`` configuration option to the set of host " "CPUs that should be used for best-effort CPU resources. Then set a flavor " "extra spec to ``hw:emulator_threads_policy=share`` to instruct nova to place " "that workload's emulator threads on that set of host CPUs." msgstr "" #: ../../:1690 msgid "" "To query attached neutron interfaces for a specific server, the API `GET /" "servers/{server_uuid}/os-interface` can be used." msgstr "" #: ../../:1189 msgid "" "To resolve `bug 1805659`_ the default value of ``[notifications]/" "notification_format`` is changed from ``both`` to ``unversioned``. For more " "information see the `documentation of the config option`_. If you are using " "versioned notifications, you will need to adjust your config to " "``versioned``\"" msgstr "" #: ../../:1166 msgid "" "To support rolling upgrades with N-1 computes if a node does not report the " "trait and is old the API will fallback to the ``allow_resize_to_same_host`` " "config option value. That compatibility will be removed in a subsequent " "release." msgstr "" #: ../../:789 msgid "To verify if hiding hypervisor id is working on Linux based system::" msgstr "" #: ../../:1843 msgid "" "Track volume attachment state in the block storage service rather than the " "compute service (separation of duties, simplicity, etc)" msgstr "" #: ../../:1181 msgid "" "Trait names which are empty, do not exist, or are otherwise invalid will " "result in a 400 error." msgstr "" #: ../../:870 msgid "Traits are added to the placement with Microversion 1.6." msgstr "" #: ../../:610 msgid "" "Traits-based scheduling is now available for the ironic compute driver. For " "more details, see the `ironic docs for scheduling based on traits`_." msgstr "" #: ../../:301 msgid "" "Turn off threading in the web server. For example, if using ``mod_wsgi`` or " "``uwsgi``, set ``threads=1`` in their respective configurations." msgstr "" #: ../../:1842 msgid "Two keymap-related configuration options have been deprecated:" msgstr "" #: ../../:309 msgid "" "Two new ``nova-manage`` CLI commands can be used for `checking`__ the volume " "attachment connection information and for `refreshing`__ it if the " "connection is stale (for example with a Ceph backing store and MON IP " "addresses). Some documentation on how to use them can be found `here`__." msgstr "" #: ../../:599 msgid "" "Two new options ``--enable`` and ``--disable`` have been added to the ``nova-" "manage cell_v2 update_cell`` command. Using these flags users can enable or " "disable scheduling to a cell." msgstr "" #: ../../:126 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 "" #: ../../:1477 msgid "" "TypeAffinityFilter is deprecated for removal in the 17.0.0 Queens release. " "There is no replacement planned for this filter. It is fundamentally flawed " "in that it relies on the ``flavors.id`` primary key and if a flavor " "\"changed\", i.e. deleted and re-created with new values, it will result in " "this filter thinking it is a different flavor, thus breaking the usefulness " "of this filter." msgstr "" #: ../../:463 msgid "" "Unfortunately the ``nova-manage project quota_usage_refresh`` command will " "not reset the usages to fix this problem once encountered." msgstr "" #: ../../:1347 msgid "" "Unsetting '[DEFAULT] dhcp_domain' will now correctly result in the metadata " "service/config drive providing an instance hostname of '${hostname}' instead " "of '${hostname}None', as was previously seen." msgstr "" #: ../../:915 msgid "" "Until all the ``nova-compute`` services that run the ironic driver are " "upgraded to the Train code that handles the ``power-update`` callbacks from " "ironic, the ``[nova]/send_power_notifications`` config option can be kept " "disabled in ironic." msgstr "" #: ../../:1379 msgid "" "Update the way QEMU cache mode is configured for Nova guests: If the file " "system hosting the directory with Nova instances is capable of Linux's " "O_DIRECT, use ``none``; otherwise fallback to ``writeback`` cache mode. " "This improves performance without compromising data integrity. `Bug " "1818847`_." msgstr "" #: ../../:568 msgid "" "Updates the network metadata that is passed to configdrive by the Ironic " "virt driver. The metadata now includes network information about port groups " "and their associated ports. It will be used to configure port groups on the " "baremetal instance side." msgstr "" #: ../../:157 origin/stable/ocata>:261 origin/stable/ocata>:985 #: stable/2023.1>:117 stable/2023.1>:290 stable/2023.2>:221 stable/2024.1>:192 #: stable/pike>:121 stable/pike>:294 stable/pike>:493 stable/pike>:526 #: stable/pike>:1050 stable/queens>:130 stable/queens>:284 stable/queens>:408 #: stable/queens>:538 stable/queens>:1193 stable/rocky>:10 stable/rocky>:274 #: stable/rocky>:374 stable/rocky>:460 stable/rocky>:1458 stable/stein>:10 #: stable/stein>:876 stable/train>:151 stable/train>:351 stable/train>:905 #: stable/ussuri>:119 stable/ussuri>:174 stable/ussuri>:280 stable/ussuri>:650 #: unmaintained/victoria>:230 unmaintained/victoria>:474 #: unmaintained/wallaby>:10 unmaintained/wallaby>:251 unmaintained/wallaby>:623 #: unmaintained/xena>:10 unmaintained/xena>:474 unmaintained/yoga>:10 #: unmaintained/yoga>:54 unmaintained/yoga>:512 unmaintained/zed>:67 #: unmaintained/zed>:402 msgid "Upgrade Notes" msgstr "" #: ../../:355 stable/ussuri>:801 msgid "" "Upgrading to Train on a deployment with a large database may hit `bug " "1862205`_, which results in instance records left in a bad state, and " "manifests as instances not being shown in list operations. Users upgrading " "to Train for the first time will definitely want to apply a version which " "includes this fix. Users already on Train should upgrade to a version " "including this fix to ensure the problem is addressed." msgstr "" #: ../../:389 msgid "" "Usage data can also be later retrieved by calling the ``/os-" "instance_usage_audit_log`` REST API [1]." msgstr "" #: ../../:260 msgid "Use the eventlet wsgi server instead of uWSGI or mod_wsgi, or" msgstr "" #: ../../:183 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 "" #: ../../:437 msgid "" "Users are now able to create servers with Neutron ports that have QoS " "minimum bandwidth rules when using the 2.72 compute API microversion. See " "the `using ports with resource request`_ documentation for more details." msgstr "" #: ../../:742 msgid "" "Users can also use ``changes-since`` filter to filter the results based on " "the last time the migration record was updated." msgstr "" #: ../../:427 msgid "" "Users can now specify a volume type when creating servers when using the 2." "67 compute API microversion. See the `block device mapping`_ documentation " "for more details." msgstr "" #: ../../:550 msgid "" "Usually, disk bus is determined automatically from the device type or disk " "device, and the virtualization type. However, disk bus can also be specified " "via a block device mapping or an image property. See the ``disk_bus`` field " "in https://docs.openstack.org/nova/latest/user/block-device-mapping.html for " "more information about specifying disk bus in a block device mapping, and " "see https://docs.openstack.org/glance/latest/admin/useful-image-properties." "html for more information about the ``hw_disk_bus`` image property." msgstr "" #: ../../:1240 msgid "" "Utilizing recent changes in oslo.messaging, the `rpc_response_timeout` value " "can now be increased significantly if needed or desired to solve issues with " "long-running RPC calls timing out before completing due to legitimate " "reasons (such as live migration prep). If `rpc_response_timeout` is " "increased beyond the default, nova will request active call monitoring from " "oslo.messaging, which will effectively heartbeat running activities to avoid " "a timeout, while still detecting failures related to service outages or " "message bus congestion in a reasonable amount of time. Further, the " "`[DEFAULT]/long_rpc_timeout` option has been added which allows setting an " "alternate timeout value for longer-running RPC calls which are known to take " "a long time. The default for this is 1800 seconds, and the " "`rpc_response_timeout` value will be used for the heartbeat frequency " "interval, providing a similar failure-detection experience for these calls " "despite the longer overall timeout. Currently, only the live migration RPC " "call uses this longer timeout value." msgstr "" #: ../../:359 msgid "" "VDPA Hot-plug live migration requires all compute services to be upgraded to " "service level 63 to be enabled. Similarly suspend resume need service level " "63 and attach/detach require service level 62. As such it will not be " "available to use during a rolling upgrade but will become available when all " "host are upgraded to the 26.0.0 (Zed) release." msgstr "" #: ../../:878 msgid "VLAN tags are currently only supported via the Libvirt driver." msgstr "" #: ../../:869 msgid "" "VLAN tags associated with instance network interfaces are now exposed via " "the metadata API and instance config drives and can be consumed by the " "instance. This is an extension of the device tagging mechanism added in past " "releases. This is useful for instances utilizing SR-IOV physical functions " "(PFs). The VLAN configuration for the guest's virtual interfaces associated " "with these devices cannot be configured inside the guest OS from the host, " "but nonetheless must be configured with the VLAN tags of the device to " "ensure packet delivery. This feature makes this possible." msgstr "" #: ../../:175 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 "" #: ../../:1102 msgid "" "VMware serial console log is completed. `VSPC`_ must be deployed along with " "nova-compute and configured properly. The ``[vmware]/serial_log_dir`` config " "option must have the same value in both nova.conf and vspc.conf." msgstr "" #: ../../:382 msgid "" "Validation for `known flavor extra specs with recognized namespaces`__." msgstr "" #: ../../:608 msgid "" "Version 1.0.0 of the `osc-placement plugin`_ has been released which " "provides CLI support for interacting directly with the Placement API." msgstr "" #: ../../:902 msgid "" "Versioned instance.update notification will be sent when server's tags field " "is updated." msgstr "" #: ../../:599 msgid "Virtuozzo hypervisor now supports ephemeral disks for containers." msgstr "" #: ../../:647 msgid "" "Virtuozzo hypervisor now supports libvirt callback to set admin password. " "Requires libvirt>=2.0.0." msgstr "" #: ../../:193 msgid "" "Volume-backed instances (instances with root disk attached as a volume) can " "now be rebuilt by specifying a 2.93 microversion instead of returning a " "HTTP400 exception." msgstr "" #: ../../:519 msgid "" "Volume-backed instances will no longer report ``root_gb`` usage for new " "instances and existing instances will heal during move operations." msgstr "" #: ../../:1463 msgid "" "WSGI application scripts ``nova-api-wsgi`` and ``nova-metadata-wsgi`` are " "now available. They allow running the compute and metadata APIs using a WSGI " "server of choice (for example nginx and uwsgi, apache2 with mod_proxy_uwsgi " "or gunicorn). The eventlet-based servers are still available, but the WSGI " "options will allow greater deployment flexibility." msgstr "" #: ../../:702 msgid "" "We are working actively to remove or workaround those caveats, but please " "understand that for the moment this feature is experimental given all the " "above." msgstr "" #: ../../:288 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 "" #: ../../:282 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 "" #: ../../:948 msgid "" "We now attempt to mirror the association of compute host to host aggregate " "into the placement API. When administrators use the ``POST /os-aggregates/" "{aggregate_id}/action`` Compute API call to add or remove a host from an " "aggregate, the nova-api service will attempt to ensure that a corresponding " "record is created in the placement API for the resource provider (compute " "host) and host aggregate UUID." msgstr "" #: ../../:313 msgid "" "We recommend to enable the both scope as well new defaults together " "otherwise you may experience some late failures with unclear error messages." msgstr "" #: ../../:1061 msgid "" "When ``IP address substring filtering`` extension is available in Neutron, " "Nova will proxy the instance list with ``ip`` or ``ip6`` filter to Neutron " "for better performance." msgstr "" #: ../../:598 msgid "" "When ``enable_dhcp`` is set on a subnet but there is no DHCP port on neutron " "then the ``dhcp_server`` value in meta hash will contain the subnet gateway " "IP instead of being absent." msgstr "" #: ../../:1344 msgid "" "When ``url`` is not used, ``region_name`` no longer defaults to " "``RegionOne``." msgstr "" #: ../../:834 msgid "" "When cold migrating a server, the ``host`` parameter is available as of " "microversion 2.56. The target host is checked by the scheduler." msgstr "" #: ../../:770 msgid "" "When creating a baremetal instance with volumes, the ironic driver will now " "pass an IP address of an iSCSI initiator to the block storage service " "because the volume backend may require the IP address for access control. If " "an IP address is set to an ironic node as a volume connector resource, the " "address is used. If a node has MAC addresses as volume connector resources, " "an IP address is retrieved from VIFs associated with the MAC addresses. IPv4 " "addresses are given priority over IPv6 addresses if both are available." msgstr "" #: ../../:1028 msgid "" "When creating a server using a multiattach volume, the API will check if the " "compute services have all been upgraded to a minimum level of support and " "will fail with a 409 HTTPConflict response if the computes are not yet " "upgraded." msgstr "" #: ../../:1135 stable/pike>:1165 msgid "" "When enabled, libvirt applies IPTables rules to all interface ports that " "provide MAC, IP, and ARP spoofing protection." msgstr "" #: ../../:555 stable/queens>:1722 msgid "" "When forcing a specified destination host during evacuate, the scheduler is " "bypassed but resource allocations will still be made in the Placement " "service against the forced destination host. If the resource allocation " "against the destination host fails, the evacuate operation will fail, " "regardless of the ``force`` flag being specified in the API. The guest will " "be unchanged on the source host. For more details, see `bug 1713786`_." msgstr "" #: ../../:543 stable/queens>:1710 msgid "" "When forcing a specified destination host during live migration, the " "scheduler is bypassed but resource allocations will still be made in the " "Placement service against the forced destination host. If the resource " "allocation against the destination host fails, the live migration operation " "will fail, regardless of the ``force`` flag being specified in the API. The " "guest will be unchanged on the source host. For more details, see `bug " "1712008`_." msgstr "" #: ../../:948 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 (`