diff options
| author | Doug Hellmann <doug@doughellmann.com> | 2018-08-15 12:40:14 -0400 |
|---|---|---|
| committer | Doug Hellmann <doug@doughellmann.com> | 2018-08-15 16:50:18 -0400 |
| commit | 857b5003ccc0b37f4642ed77d9f0d08f9ee28dfb (patch) | |
| tree | 4604afbf03b6a4898860e4888f941cd715026e5c /releasenotes/source | |
| parent | 89470970474357b23ab691ee534b34806fdf40af (diff) | |
| download | nova-857b5003ccc0b37f4642ed77d9f0d08f9ee28dfb.tar.gz | |
use static pages for mitaka and newton release notes
The liberty, mitaka, and newton branches are closed so there is no
reason to scan for release notes dynamically. Use static content for
those pages to speed up the release notes build a little bit.
Change-Id: I983346c97df96fda988a2fefec89c3f0d6c14498
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Diffstat (limited to 'releasenotes/source')
| -rw-r--r-- | releasenotes/source/liberty.rst | 128 | ||||
| -rw-r--r-- | releasenotes/source/mitaka.rst | 716 | ||||
| -rw-r--r-- | releasenotes/source/newton.rst | 1133 |
3 files changed, 1968 insertions, 9 deletions
diff --git a/releasenotes/source/liberty.rst b/releasenotes/source/liberty.rst index 91c1a35784..10af4c4f06 100644 --- a/releasenotes/source/liberty.rst +++ b/releasenotes/source/liberty.rst @@ -2,6 +2,128 @@ Liberty Series Release Notes ============================== -.. release-notes:: - :branch: origin/stable/liberty - :earliest-version: 12.0.1 +.. _Release Notes_12.0.5_stable_liberty: + +12.0.5 +====== + +.. _Release Notes_12.0.5_stable_liberty_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/apply-limits-to-qemu-img-8813f7a333ebdf69.yaml @ b'6bc37dcceca823998068167b49aec6def3112397' + +- The qemu-img tool now has resource limits applied which prevent it from using more than 1GB of address space or more than 2 seconds of CPU time. This provides protection against denial of service attacks from maliciously crafted or corrupted disk images. oslo.concurrency>=2.6.1 is required for this fix. + + +.. _Release Notes_12.0.4_stable_liberty: + +12.0.4 +====== + +.. _Release Notes_12.0.4_stable_liberty_Upgrade Notes: + +Upgrade Notes +------------- + +.. releasenotes/notes/bug-1559026-47c3fa3468d66b07.yaml @ b'79a49b3d6a4221ca3e09cb16008cc423f1902fe7' + +- The ``record`` configuration option for the console proxy services (like VNC, serial, spice) is changed from boolean to string. It specifies the filename that will be used for recording websocket frames. + + +.. _Release Notes_12.0.4_stable_liberty_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/vhost-user-mtu-23d0af36a8adfa56.yaml @ b'98464d54d0fcdba452191bc0291d59957c9cdae6' + +- When plugging virtual interfaces of type vhost-user the MTU value will not be applied to the interface by nova. vhost-user ports exist only in userspace and are not backed by kernel netdevs, for this reason it is not possible to set the mtu on a vhost-user interface using standard tools such as ifconfig or ip link. + + +.. _Release Notes_12.0.3_stable_liberty: + +12.0.3 +====== + +.. _Release Notes_12.0.3_stable_liberty_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/12.0.3-cve-bugs-reno-561a450b346edf5e.yaml @ b'0b194187db9da28225cb5e62be3b45aff5a1c793' + +- [OSSA 2016-007] Host data leak during resize/migrate for raw-backed instances (CVE-2016-2140) + + * `Bug 1548450 <https://bugs.launchpad.net/nova/+bug/1548450>`_ + * `Announcement <http://lists.openstack.org/pipermail/openstack-announce/2016-March/001009.html>`__ + + +.. _Release Notes_12.0.1_stable_liberty: + +12.0.1 +====== + +.. _Release Notes_12.0.1_stable_liberty_Prelude: + +Prelude +------- + +.. releasenotes/notes/12.0.1-cve-bugs-7b04b2e34a3e9a70.yaml @ b'9c3cce75de6069edca35ce5046d4ce25a11b6337' + +The 12.0.1 release contains fixes for two security issues. + + +.. _Release Notes_12.0.1_stable_liberty_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/12.0.1-cve-bugs-7b04b2e34a3e9a70.yaml @ b'9c3cce75de6069edca35ce5046d4ce25a11b6337' + +- [OSSA 2016-001] Nova host data leak through snapshot (CVE-2015-7548) + + * `Bug 1524274 <https://bugs.launchpad.net/nova/+bug/1524274>`_ + * `Announcement <http://lists.openstack.org/pipermail/openstack-announce/2016-January/000911.html>`__ + + [OSSA 2016-002] Xen connection password leak in logs via StorageError (CVE-2015-8749) + + * `Bug 1516765 <https://bugs.launchpad.net/nova/+bug/1516765>`_ + * `Announcement <http://lists.openstack.org/pipermail/openstack-announce/2016-January/000916.html>`__ + + +.. _Release Notes_12.0.1_stable_liberty_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/bug-1505471-28ef47bdc9487a31.yaml @ b'821f644e98475d0af53f621ba13930b3dffc6e7b' + +- Fixes a bug where Nova services won't recover after a temporary DB + connection issue, when service group DB driver is used together with + local conductor, as the driver only handles RPC timeout errors. + + For more info see https://bugs.launchpad.net/nova/+bug/1505471 + +.. releasenotes/notes/bug-1517926-ed0dda23ea525306.yaml @ b'821f644e98475d0af53f621ba13930b3dffc6e7b' + +- Fixes a bug where Nova services won't recover after a temporary DB / MQ + connection issue, when service group DB driver is used together with + remote conductor, as the driver only handles RPC timeout errors and does + not account for other types of errors (e.g. wrapped DB errors on the + remote conductor transported over RPC) + + For more info see https://bugs.launchpad.net/nova/+bug/1517926 + + +.. _Release Notes_12.0.1_stable_liberty_Other Notes: + +Other Notes +----------- + +.. releasenotes/notes/start-using-reno-e4ea112d593415da.yaml @ b'70fbad45d9d8459b141b81820ea12b27900a3bab' + +- Start using reno to manage release notes. + + diff --git a/releasenotes/source/mitaka.rst b/releasenotes/source/mitaka.rst index 496867ae2c..43a3e6ea6c 100644 --- a/releasenotes/source/mitaka.rst +++ b/releasenotes/source/mitaka.rst @@ -2,6 +2,716 @@ Mitaka Series Release Notes =================================== -.. release-notes:: - :branch: origin/stable/mitaka - :earliest-version: 13.0.0 +.. _Release Notes_13.1.4_stable_mitaka: + +13.1.4 +====== + +.. _Release Notes_13.1.4_stable_mitaka_Prelude: + +Prelude +------- + +.. releasenotes/notes/bug-1673569-cve-2017-7214-2d7644b356015c93.yaml @ b'e193201fa1de5b08b29adefd8c149935c5529598' + +This release includes fixes for security vulnerabilities. + + +.. _Release Notes_13.1.4_stable_mitaka_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/bug-1673569-cve-2017-7214-2d7644b356015c93.yaml @ b'e193201fa1de5b08b29adefd8c149935c5529598' + +- [CVE-2017-7214] Failed notification payload is dumped in logs with auth secrets + + * `Bug 1673569 <https://bugs.launchpad.net/nova/+bug/1673569>`_ + + +.. _Release Notes_13.1.3_stable_mitaka: + +13.1.3 +====== + +.. _Release Notes_13.1.3_stable_mitaka_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/bug-1662699-06203e7262e02aa6.yaml @ b'9b3c4736a35b0db6ceff38786fb706a6a312a7ab' + +- 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. + + .. _bug 1662699: https://bugs.launchpad.net/nova/+bug/1662699 + + +.. _Release Notes_13.1.2_stable_mitaka: + +13.1.2 +====== + +.. _Release Notes_13.1.2_stable_mitaka_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/list-server-bad-status-fix-7db504b38c8d732f.yaml @ b'9a97047850e6febce090cee9a5f2224cdf02a2c3' + +- Fixed bug #1579706: "Listing nova instances with invalid status raises 500 + InternalServerError for admin user". Now passing an invalid status as a + filter will return an empty list. A subsequent patch will then correct this + to raise a 400 Bad Request when an invalid status is received. + + +.. _Release Notes_13.1.1_stable_mitaka: + +13.1.1 +====== + +.. _Release Notes_13.1.1_stable_mitaka_Known Issues: + +Known Issues +------------ + +.. releasenotes/notes/known-issue-on-api-1efca45440136f3e.yaml @ b'84d5697c9e614c2bf299e213f5398e4ecf160400' + +- When using Neutron extension 'port_security' and booting an instance on a network with 'port_security_enabled=False' the Nova API response says there is a 'default' security group attached to the instance which is incorrect. However when listing security groups for the instance there are none listed, which is correct. The API response will be fixed separately with a microversion. + + +.. _Release Notes_13.1.0_stable_mitaka: + +13.1.0 +====== + +.. _Release Notes_13.1.0_stable_mitaka_Upgrade Notes: + +Upgrade Notes +------------- + +.. releasenotes/notes/bug-1559026-47c3fa3468d66b07.yaml @ b'3c008718e15f0d2da717f04ff211e9da6d80ff2d' + +- The ``record`` configuration option for the console proxy services (like VNC, serial, spice) is changed from boolean to string. It specifies the filename that will be used for recording websocket frames. + + +.. _Release Notes_13.1.0_stable_mitaka_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/apply-limits-to-qemu-img-8813f7a333ebdf69.yaml @ b'c8ec9ebf379c61d73c5671a75dd2a4e4ae1403fb' + +- The qemu-img tool now has resource limits applied which prevent it from using more than 1GB of address space or more than 2 seconds of CPU time. This provides protection against denial of service attacks from maliciously crafted or corrupted disk images. + + +.. _Release Notes_13.0.0_stable_mitaka: + +13.0.0 +====== + +.. _Release Notes_13.0.0_stable_mitaka_Prelude: + +Prelude +------- + +.. releasenotes/notes/add-aggregate-type-extra-specs-affinity-filter-79a2d3ee152b8ecd.yaml @ b'a5486b32a3c476f3ad584d8ff7c4eda2bb3e400d' + + + +.. releasenotes/notes/api_servers_no_scheme-e4aa216d251022f2.yaml @ b'1c18f1838526de11ddd2ab42b4a49ab8df2ee8d1' + + + +.. releasenotes/notes/disable_ec2_api_by_default-0ec0946433fc7119.yaml @ b'7b1fb84f68bbcef0c496d3990e5d6b99a5360bc8' + + + +.. releasenotes/notes/lock_policy-75bea372036acbd5.yaml @ b'a5486b32a3c476f3ad584d8ff7c4eda2bb3e400d' + + + +.. releasenotes/notes/mitaka_prelude-c8b955ed78a5ad65.yaml @ b'f4a8cdb91f96f7b5674a06c00c881fcae864b062' + +Nova 13.0.0 release is including a lot of new features and bugfixes. It can +be extremely hard to mention all the changes we introduced during that +release but we beg you to read at least the upgrade section which describes +the required modifications that you need to do for upgrading your cloud +from 12.0.0 (Liberty) to 13.0.0 (Mitaka). + +That said, a few major changes are worth to notice here. This is not an +exhaustive list of things to notice, rather just important things you need +to know : + + - Latest API microversion supported for Mitaka is v2.25 + - Nova now requires a second database (called 'API DB'). + - A new nova-manage script allows you to perform all online DB + migrations once you upgrade your cloud + - EC2 API support is fully removed. + + +.. releasenotes/notes/new-oslo-reports-option-619c3dbf3ae320fb.yaml @ b'a5486b32a3c476f3ad584d8ff7c4eda2bb3e400d' + + + +.. releasenotes/notes/reserved-hugepages-per-nodes-f36225d5fca807e4.yaml @ b'7b1fb84f68bbcef0c496d3990e5d6b99a5360bc8' + + + +.. releasenotes/notes/switch-to-oslo-cache-7114a0ab2dea52df.yaml @ b'205fb7c8b34e521bdc14b5c3698d1597753b27d4' + + + +.. _Release Notes_13.0.0_stable_mitaka_New Features: + +New Features +------------ + +.. releasenotes/notes/1516578-628b417b372f4f0f.yaml @ b'1a2443ce67700c494275a3ea51e584c551f7490f' + +- Enables NUMA topology reporting on PowerPC architecture + from the libvirt driver in Nova but with a caveat as mentioned below. + NUMA cell affinity and dedicated cpu pinning + code assumes that the host operating system is exposed to threads. + PowerPC based hosts use core based scheduling for processes. + Due to this, the cores on the PowerPC architecture are treated as + threads. Since cores are always less than or equal + to the threads on a system, this leads to non-optimal resource usage + while pinning. This feature is supported from libvirt version 1.2.19 + for PowerPC. + +.. releasenotes/notes/abort-live-migration-cb902bb0754b11b6.yaml @ b'fa002925460e70d988d1b4dd1ea594c680a43740' + +- A new REST API to cancel an ongoing live migration has been added in microversion 2.24. Initially this operation will only work with the libvirt virt driver. + +.. releasenotes/notes/attach-detach-vol-for-shelved-and-shelved-offloaded-instances-93f70cfd49299f05.yaml @ b'cf34a32820cc21dd9b9075d5476e050ecd8b34ac' + +- It is possible to call attach and detach volume API operations for instances which are in shelved and shelved_offloaded state. For an instance in shelved_offloaded state Nova will set to None the value for the device_name field, the right value for that field will be set once the instance will be unshelved as it will be managed by a specific compute manager. + +.. releasenotes/notes/block-live-migrate-with-attached-volumes-ee02afbfe46937c7.yaml @ b'f99077cf24ceee79d0abe84b5a53b82c7d64c5cb' + +- It is possible to block live migrate instances with additional cinder volumes attached. This requires libvirt version to be >=1.2.17 and does not work when live_migration_tunnelled is set to True. + +.. releasenotes/notes/bp-add-project-and-user-id-a560d087656157d4.yaml @ b'6c74a145bc3f412b0f5ef1965b00c8542963ed26' + +- Project-id and user-id are now also returned in + the return data of os-server-groups APIs. In order + to use this new feature, user have to contain the + header of request microversion v2.13 in the API + request. + +.. releasenotes/notes/bp-boot-from-uefi-b413b96017db76dd.yaml @ b'9e2dfb61ed1c8f8c891c34ca4da2b46b69abd661' + +- Add support for enabling uefi boot with libvirt. + +.. releasenotes/notes/bp-get-valid-server-state-a817488f4c8d3822.yaml @ b'9345d5835fb8ff6a3534122c3c13620547862e95' + +- A new host_status attribute for servers/detail and servers/{server_id}. + In order to use this new feature, user have to contain the header of + request microversion v2.16 in the API request. A new policy + ``os_compute_api:servers:show:host_status`` added to enable the feature. + By default, this is only exposed to cloud administrators. + +.. releasenotes/notes/bp-instance-crash-dump-7ccbba7799dc66f9.yaml @ b'30c6f498175112048bef3efdabe6bb979dd694f7' + +- A new server action trigger_crash_dump has been added to the REST API in microversion 2.17. + +.. releasenotes/notes/bp-rbd-instance-snapshots-130e860b726ddc16.yaml @ b'824c3706a3ea691781f4fcc4453881517a9e1c55' + +- When RBD is used for ephemeral disks and image storage, make snapshot use Ceph directly, and update Glance with the new location. In case of failure, it will gracefully fallback to the "generic" snapshot method. This requires changing the typical permissions for the Nova Ceph user (if using authx) to allow writing to the pool where vm images are stored, and it also requires configuring Glance to provide a v2 endpoint with direct_url support enabled (there are security implications to doing this). See http://docs.ceph.com/docs/master/rbd/rbd-openstack/ for more information on configuring OpenStack with RBD. + +.. releasenotes/notes/bp-split-network-plane-for-live-migration-40bc127734173759.yaml @ b'af41accff9456748a3106bc1206cfc22d10a8cf4' + +- A new option "live_migration_inbound_addr" has been added + in the configuration file, set None as default value. + If this option is present in pre_migration_data, the ip + address/hostname provided will be used instead of + the migration target compute node's hostname as the + uri for live migration, if it's None, then the + mechanism remains as it is before. + +.. releasenotes/notes/bp-virt-driver-cpu-thread-pinning-1aaeeb6648f8e009.yaml @ b'6769460156b3de48093b078a668d94e179ca2d39' + +- Added support for CPU thread policies, which can be used to control how the libvirt virt driver places guests with respect to CPU SMT "threads". These are provided as instance and image metadata options, 'hw:cpu_thread_policy' and 'hw_cpu_thread_policy' respectively, and provide an additional level of control over CPU pinning policy, when compared to the existing CPU policy feature. These changes were introduced in commits '83cd67c' and 'aaaba4a'. + +.. releasenotes/notes/cinder-backend-report-discard-1def1c28140def9b.yaml @ b'6bc074587a96ca5810ca6674ad0710bcd8de6b58' + +- Add support for enabling discard support for block devices with libvirt. This will be enabled for Cinder volume attachments that specify support for the feature in their connection properties. This requires support to be present in the version of libvirt (v1.0.6+) and qemu (v1.6.0+) used along with the configured virtual drivers for the instance. The virtio-blk driver does not support this functionality. + +.. releasenotes/notes/compute_upgrade_levels_auto-97acebc7b45b76df.yaml @ b'86fb45c0724ae0afd39a0e44314b74b31327ea63' + +- A new ``auto`` value for the configuration option + ``upgrade_levels.compute`` is accepted, that allows automatic determination + of the compute service version to use for RPC communication. By default, we + still use the newest version if not set in the config, a specific version + if asked, and only do this automatic behavior if 'auto' is + configured. When 'auto' is used, sending a SIGHUP to the service + will cause the value to be re-calculated. Thus, after an upgrade + is complete, sending SIGHUP to all services will cause them to + start sending messages compliant with the newer RPC version. + +.. releasenotes/notes/disco_volume_libvirt_driver-916428b8bd852732.yaml @ b'caac64f1a73aa9cf973e37ce4f4628f55ffa379d' + +- Libvirt driver in Nova now supports Cinder DISCO volume driver. + +.. releasenotes/notes/disk-weight-scheduler-98647f9c6317d21d.yaml @ b'818c5064a5cad693873254605dfbf45962b317cc' + +- A disk space scheduling filter is now available, which prefers compute nodes with the most available disk space. By default, free disk space is given equal importance to available RAM. To increase the priority of free disk space in scheduling, increase the disk_weight_multiplier option. + +.. releasenotes/notes/force-live-migration-be5a10cd9c8eb981.yaml @ b'c9091d0871948377685feca0eb2e41d8ad38228a' + +- A new REST API to force live migration to complete has been added in microversion 2.22. + +.. releasenotes/notes/instance-actions-read-deleted-instances-18bbb327924b66c7.yaml @ b'934a0e4ede41a9a132bb22f7f3fcf15f8c72e66b' + +- The os-instance-actions methods now read actions from deleted instances. This means that 'GET /v2.1/{tenant-id}/servers/{server-id}/os-instance-actions' and 'GET /v2.1/{tenant-id}/servers/{server-id}/os-instance-actions/{req-id}' will return instance-action items even if the instance corresponding to '{server-id}' has been deleted. + +.. releasenotes/notes/instance-hostname-used-to-populate-ports-dns-name-08341ec73dc076c0.yaml @ b'997d8f516cee99b4e16429d13ca5cf7fc05166aa' + +- When booting an instance, its sanitized 'hostname' attribute is now used to populate the 'dns_name' attribute of the Neutron ports the instance is attached to. This functionality enables the Neutron internal DNS service to know the ports by the instance's hostname. As a consequence, commands like 'hostname -f' will work as expected when executed in the instance. When a port's network has a non-blank 'dns_domain' attribute, the port's 'dns_name' combined with the network's 'dns_domain' will be published by Neutron in an external DNS as a service like Designate. As a consequence, the instance's hostname is published in the external DNS as a service. This functionality is added to Nova when the 'DNS Integration' extension is enabled in Neutron. The publication of 'dns_name' and 'dns_domain' combinations to an external DNS as a service additionaly requires the configuration of the appropriate driver in Neutron. When the 'Port Binding' extension is also enabled in Neutron, the publication of a 'dns_name' and 'dns_domain' combination to the external DNS as a service will require one additional update operation when Nova allocates the port during the instance boot. This may have a noticeable impact on the performance of the boot process. + +.. releasenotes/notes/libvirt-live-migration-new-tunneled-option-d7ebb1eb1e95e683.yaml @ b'621594fc41d0e07fd63dfe7c3c5cfee9edc380ad' + +- The libvirt driver now has a live_migration_tunnelled configuration option which should be used where the VIR_MIGRATE_TUNNELLED flag would previously have been set or unset in the live_migration_flag and block_migration_flag configuration options. + +.. releasenotes/notes/libvirt_hardware_policy_from_libosinfo-19e261851d1ad93a.yaml @ b'fd34e0cda4a5ef0841e04dee27d0d857167a1076' + +- For the libvirt driver, by default hardware properties will be retrieved from the Glance image and if such haven't been provided, it will use a libosinfo database to get those values. If users want to force a specific guest OS ID for the image, they can now use a new glance image property ``os_distro`` (eg. ``--property os_distro=fedora21``). In order to use the libosinfo database, you need to separately install the related native package provided for your operating system distribution. + +.. releasenotes/notes/neutron-ovs-bridge-name-7b3477103622f4cc.yaml @ b'e912f5e54785d77b4fabd1113c16b19d0981f003' + +- Add support for allowing Neutron to specify the bridge name for the OVS, Linux Bridge, and vhost-user VIF types. + +.. releasenotes/notes/online-data-migrations-48dde6a1d8661e47.yaml @ b'c2bd7e4cdcb3c81700977155c93561f50c6b415d' + +- Added a `nova-manage db online_data_migrations` command for forcing online data migrations, which will run all registered migrations for the release, instead of there being a separate command for each logical data migration. Operators need to make sure all data is migrated before upgrading to the next release, and the new command provides a unified interface for doing it. + +.. releasenotes/notes/optional_project_id-6aebf1cb394d498f.yaml @ b'eea7169474d3cf6b9ac27036ae3ca5a95b461b8d' + +- Provides API 2.18, which makes the use of project_ids in API urls optional. + +.. releasenotes/notes/parallels_support_snapshot-29b4ffae300c1f05.yaml @ b'f615bfa572ca701259421a053ac4efd48053cc06' + +- Libvirt with Virtuozzo virtualisation type now supports snapshot operations + +.. releasenotes/notes/remove-on-shared-storage-flag-from-evacuate-api-76a3d58616479fe9.yaml @ b'c01d16e81af6cd9453ffe7133bdc6a4c82e4f6d5' + +- Remove ``onSharedStorage`` parameter from server's evacuate action in microversion 2.14. Nova will automatically detect if the instance is on shared storage. Also adminPass is removed from the response body which makes the response body empty. The user can get the password with the server's os-server-password action. + +.. releasenotes/notes/server_migrations-30519b35d3ea6763.yaml @ b'98e4a64ad3f1f975e78224d19e729787b902e84c' + +- Add two new list/show API for server-migration. + The list API will return the in progress live migratons + information of a server. The show API will return + a specified in progress live migration of a server. + This has been added in microversion 2.23. + +.. releasenotes/notes/service-status-notification-e137297f5d5aa45d.yaml @ b'05adc8d006b482e0aed2fcc9dc4885924aca74d0' + +- A new service.status versioned notification has been introduced. When the status of the Service object is changed nova will send a new service.update notification with versioned payload according to bp versioned-notification-api. The new notification is documented in http://docs.openstack.org/developer/nova/notifications.html + +.. releasenotes/notes/soft-affinity-for-server-group-f45e191bd8cdbd15.yaml @ b'5dcbc848514adde7d3907e436d8cca08a6ad800a' + +- Two new policies soft-affinty and soft-anti-affinity have been implemented for the server-group feature of Nova. This means that POST /v2.1/{tenant_id}/os-server-groups API resource now accepts 'soft-affinity' and 'soft-anti-affinity' as value of the 'policies' key of the request body. + +.. releasenotes/notes/user-settable-server-description-89dcfc75677e31bc.yaml @ b'4841cab03e9b9052b1d8f786fb2d31166dc5e4fd' + +- In Nova Compute API microversion 2.19, you can specify a "description" attribute when creating, rebuilding, or updating a server instance. This description can be retrieved by getting server details, or list details for servers. + Refer to the Nova Compute API documentation for more information. + Note that the description attribute existed in prior Nova versions, but was set to the server name by Nova, and was not visible to the user. So, servers you created with microversions prior to 2.19 will return the description equals the name on server details microversion 2.19. + +.. releasenotes/notes/versioned-notifications-423f4d8d2a3992c6.yaml @ b'05adc8d006b482e0aed2fcc9dc4885924aca74d0' + +- As part of refactoring the notification interface of Nova a new config option 'notification_format' has been added to specifies which notification format shall be used by nova. The possible values are 'unversioned' (e.g. legacy), 'versioned', 'both'. The default value is 'both'. The new versioned notifications are documented in http://docs.openstack.org/developer/nova/notifications.html + +.. releasenotes/notes/vmware_limits-16edee7a9ad023bc.yaml @ b'd0264372fee4fde1fe07852a5835d739ee4c9f9b' + +- For the VMware driver, the flavor extra specs for quotas has been extended + to support: + + - quota:cpu_limit - The cpu of a virtual machine will not + exceed this limit, even if there are available resources. This is + typically used to ensure a consistent performance of virtual machines + independent of available resources. Units are MHz. + - quota:cpu_reservation - guaranteed minimum reservation (MHz) + - quota:cpu_shares_level - the allocation level. This can be + 'custom', 'high', 'normal' or 'low'. + - quota:cpu_shares_share - in the event that 'custom' is used, + this is the number of shares. + - quota:memory_limit - The memory utilization of a virtual + machine will not exceed this limit, even if there are available + resources. This is typically used to ensure a consistent performance of + virtual machines independent of available resources. Units are MB. + - quota:memory_reservation - guaranteed minimum reservation (MB) + - quota:memory_shares_level - the allocation level. This can be + 'custom', 'high', 'normal' or 'low'. + - quota:memory_shares_share - in the event that 'custom' is used, + this is the number of shares. + - quota:disk_io_limit - The I/O utilization of a virtual machine + will not exceed this limit. The unit is number of I/O per second. + - quota:disk_io_reservation - Reservation control is used to + provide guaranteed allocation in terms of IOPS + - quota:disk_io_shares_level - the allocation level. This can be + 'custom', 'high', 'normal' or 'low'. + - quota:disk_io_shares_share - in the event that 'custom' is used, + this is the number of shares. + - quota:vif_limit - The bandwidth limit for the virtual network + adapter. The utilization of the virtual network adapter will not exceed + this limit, even if there are available resources. Units in Mbits/sec. + - quota:vif_reservation - Amount of network bandwidth that is + guaranteed to the virtual network adapter. If utilization is less than + reservation, the resource can be used by other virtual network adapters. + Reservation is not allowed to exceed the value of limit if limit is set. + Units in Mbits/sec. + - quota:vif_shares_level - the allocation level. This can be + 'custom', 'high', 'normal' or 'low'. + - quota:vif_shares_share - in the event that 'custom' is used, + this is the number of shares. + + +.. _Release Notes_13.0.0_stable_mitaka_Upgrade Notes: + +Upgrade Notes +------------- + +.. releasenotes/notes/add-novnc-proxy-config-to-vnc-group-f5bb68740f623744.yaml @ b'11a42d40306f56105447a32cc521bb44f6678b59' + +- All noVNC proxy configuration options have been added to the 'vnc' group. They should no longer be included in the 'DEFAULT' group. + +.. releasenotes/notes/add-xvp-config-to-vnc-group-349cca99f05fcfd3.yaml @ b'e17be81ed87a90dfb28f23f75133d225df3f1acc' + +- All VNC XVP configuration options have been added to the 'vnc' group. They should no longer be included in the 'DEFAULT' group. + +.. releasenotes/notes/aggregate-uuid-generation-1f029af7a9af519b.yaml @ b'67324e61e052de96e2df8c1f47ea8241730c519a' + +- Upon first startup of the scheduler service in Mitaka, all defined aggregates will have UUIDs generated and saved back to the database. If you have a significant number of aggregates, this may delay scheduler start as that work is completed, but it should be minor for most deployments. + +.. releasenotes/notes/api-database-now-required-6245f39d36885d1c.yaml @ b'7b1fb84f68bbcef0c496d3990e5d6b99a5360bc8' + +- During an upgrade to Mitaka, operators must create and initialize a database for the API service. Configure this in [api_database]/connection, and then run ``nova-manage api_db sync`` + +.. releasenotes/notes/bp-making-live-migration-api-friendly-3b547f4e0958ee05.yaml @ b'f18a46c072b964b6c9ceffc9832e4221f64dc9c4' + +- We can not use microversion 2.25 to do live-migration during upgrade, nova-api will raise bad request if there is still old compute node in the cluster. + +.. releasenotes/notes/config_scheduler_driver-e751ae392bc1a1d0.yaml @ b'33d906a2e060447778e95449a78e6583f18afcfd' + +- The option ``scheduler_driver`` is now changed to use entrypoint instead of + full class path. Set one of the entrypoints under the namespace + 'nova.scheduler.driver' in 'setup.cfg'. Its default value is + 'host_manager'. The full class path style is still supported in current + release. But it is not recommended because class path can be changed and + this support will be dropped in the next major release. + +.. releasenotes/notes/config_scheduler_host_manager_driver-a543a74ea70f5e90.yaml @ b'158c6d64c2da48ec5fb3382eb64cd5c5e9c5c2d9' + +- The option ``scheduler_host_manager`` is now changed to use entrypoint + instead of full class path. Set one of the entrypoints under the namespace + 'nova.scheduler.host_manager' in 'setup.cfg'. Its default value is + 'host_manager'. The full class path style is still supported in current + release. But it is not recommended because class path can be changed and + this support will be dropped in the next major release. + +.. releasenotes/notes/deprecate-local-conductor-9cb9f45728281eb0.yaml @ b'a067a4c9be524c90677f511c96764ab327a4da4c' + +- The local conductor mode is now deprecated and may be removed as early as + the 14.0.0 release. + If you are using local conductor mode, plan on deploying remote conductor + by the time you upgrade to the 14.0.0 release. + +.. releasenotes/notes/deprecate_ert-449b16638c008457.yaml @ b'2274fd1f87ff8cc0cb3ce49aa40aee0018e5d1dd' + +- The Extensible Resource Tracker is deprecated and will be removed in the + 14.0.0 release. + If you use this functionality and have custom resources that are managed + by the Extensible Resource Tracker, please contact the Nova development + team by posting to the openstack-dev mailing list. + There is no future planned support for the tracking of custom resources. + +.. releasenotes/notes/disk_ratio_to_rt-b6224ab8c0272d86.yaml @ b'ad6654eaa7c44267ae3a4952a8359459fbec4c0c' + +- For Liberty compute nodes, the disk_allocation_ratio works as before, you must set it on the scheduler if you want to change it. For Mitaka compute nodes, the disk_allocation_ratio set on the compute nodes will be used only if the configuration is not set on the scheduler. This is to allow, for backwards compatibility, the ability to still override the disk allocation ratio by setting the configuration on the scheduler node. In Newton, we plan to remove the ability to set the disk allocation ratio on the scheduler, at which point the compute nodes will always define the disk allocation ratio, and pass that up to the scheduler. None of this changes the default disk allocation ratio of 1.0. This matches the behaviour of the RAM and CPU allocation ratios. + +.. releasenotes/notes/drop_instancev1_obj-4447ddd2bea644fa.yaml @ b'ae57abf3015b29294b429997db5a9261fdaf301e' + +- (Only if you do continuous deployment) + 1337890ace918fa2555046c01c8624be014ce2d8 drops support for an instance + major version, which means that you must have deployed at least commit + 713d8cb0777afb9fe4f665b9a40cac894b04aacb before deploying this one. + +.. releasenotes/notes/ebtables-version-fde659fe18b0e0c0.yaml @ b'9f3d8e62ed24659105a8e86c511928f1805325cd' + +- nova now requires ebtables 2.0.10 or later + +.. releasenotes/notes/ebtables-version-fde659fe18b0e0c0.yaml @ b'9f3d8e62ed24659105a8e86c511928f1805325cd' + +- nova recommends libvirt 1.2.11 or later + +.. releasenotes/notes/filters_use_reqspec-9f92b9c0ead76093.yaml @ b'aeae7040c7b4533fd4d5521d4c5172cb2fb598e7' + +- Filters internal interface changed using now the RequestSpec NovaObject + instead of an old filter_properties dictionary. + In case you run out-of-tree filters, you need to modify the host_passes() + method to accept a new RequestSpec object and modify the filter internals + to use that new object. You can see other in-tree filters for getting the + logic or ask for help in #openstack-nova IRC channel. + +.. releasenotes/notes/force_config_drive_opt-e087055e14c40d88.yaml @ b'2941d88ef28166cd0ebd677c4de8176e1befe044' + +- The ``force_config_drive`` configuration option provided an ``always`` + value which was deprecated in the previous release. That ``always`` value + is now no longer accepted and deployments using that value have to change + it to ``True`` before upgrading. + +.. releasenotes/notes/hyperv_2k8_drop-fb309f811767c7c4.yaml @ b'c3628d7a91bcab14ed795f8b89c9afc6ed15abe5' + +- Support for Windows / Hyper-V Server 2008 R2 has been deprecated in Liberty (12.0.0) and it is no longer supported in Mitaka (13.0.0). If you have compute nodes running that version, please consider moving the running instances to other compute nodes before upgrading those to Mitaka. + +.. releasenotes/notes/libvirt-live-migration-flags-mangling-a2407a31ddf17427.yaml @ b'3fd24ba528314b45fe5f91110638ada7bf7fcb96' + +- The libvirt driver will now correct unsafe and invalid values for the live_migration_flag and block_migration_flag configuration options. The live_migration_flag must not contain VIR_MIGRATE_SHARED_INC but block_migration_flag must contain it. Both options must contain the VIR_MIGRATE_PEER2PEER, except when using the 'xen' virt type this flag is not supported. Both flags must contain the VIR_MIGRATE_UNDEFINE_SOURCE flag and not contain the VIR_MIGRATE_PERSIST_DEST flag. + +.. releasenotes/notes/live_migration_uri-dependent-on-virt_type-595c46c2310f45c3.yaml @ b'3159c8fd5bea80c820e58bd38d96f5f8fe8f4503' + +- The libvirt driver has changed the default value of the 'live_migration_uri' flag, that now is dependent on the 'virt_type'. The old default 'qemu+tcp://%s/system' now is adjusted for each of the configured hypervisors. For Xen this will be 'xenmigr://%s/system', for kvm/qemu this will be 'qemu+tcp://%s/system'. + +.. releasenotes/notes/min_libvirt_bump-d9916d9c4512dd11.yaml @ b'5a359a3d241bf33dd8dd30c4b554240e2a88c9af' + +- The minimum required libvirt is now version 0.10.2. The minimum libvirt for the N release has been set to 1.2.1. + +.. releasenotes/notes/optional_project_id-6aebf1cb394d498f.yaml @ b'eea7169474d3cf6b9ac27036ae3ca5a95b461b8d' + +- In order to make project_id optional in urls, we must constrain the set of allowed values for project_id in our urls. This defaults to a regex of ``[0-9a-f\-]+``, which will match hex uuids (with / without dashes), and integers. This covers all known project_id formats in the wild. + If your site uses other values for project_id, you can set a site specific validation with ``project_id_regex`` config variable. + +.. releasenotes/notes/remove-deprecated-neutron-options-5f3a782aa9082fb5.yaml @ b'a67394a05872c89699487fc3e1e6a1801a7714c2' + +- The old neutron communication options that were slated for removal in Mitaka are no longer available. This means that going forward communication to neutron will need to be configured using auth plugins. + +.. releasenotes/notes/remove_ec2_and_objectstore_api-4ccb539db1d171fa.yaml @ b'c711c6519a9dd97fd23a9d5417f99334bfdd16a5' + +- All code and tests for Nova's EC2 and ObjectStore API support which + was deprecated in Kilo + (https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#Upgrade_Notes_2) has + been completely removed in Mitaka. This has been replaced by the new + ec2-api project (http://git.openstack.org/cgit/openstack/ec2-api/). + + .. warning:: Some installation tools (such as ``packstack``) hardcode the + value of ``enabled_apis`` in your nova.conf. While the defaults + for ``enabled_apis`` dropped ``ec2`` as a value, if that is hard + coded in your nova.conf, you will need to remove it before + restarting Nova's API server, or it will not start. + +.. releasenotes/notes/request-spec-api-db-b9cc6e0624d563c5.yaml @ b'8e8e839ef748be242fd0ad02e3ae233cc98da8b2' + +- The commit with change-id Idd4bbbe8eea68b9e538fa1567efd304e9115a02a + requires that the nova_api database is setup and Nova is configured to use + it. Instructions on doing that are provided below. + + Nova now requires that two databases are available and configured. The + existing nova database needs no changes, but a new nova_api database needs + to be setup. It is configured and managed very similarly to the nova + database. A new connection string configuration option is available in the + api_database group. An example:: + + [api_database] + connection = mysql+pymysql://user:secret@127.0.0.1/nova_api?charset=utf8 + + And a new nova-manage command has been added to manage db migrations for + this database. "nova-manage api_db sync" and "nova-manage api_db version" + are available and function like the parallel "nova-manage db ..." version. + +.. releasenotes/notes/rm_volume_manager-78fed5be43d285b3.yaml @ b'6e8e322718529e50bf2035507b970058ddaa836a' + +- A new ``use_neutron`` option is introduced which replaces the obtuse ``network_api_class`` option. This defaults to 'False' to match existing defaults, however if ``network_api_class`` is set to the known Neutron value Neutron networking will still be used as before. + +.. releasenotes/notes/scheduling-to-disabled-hosts-79f5b5d20a42875a.yaml @ b'214b7550bca6b78c99660f257fc63d6ea4ccf212' + +- The FilterScheduler is now including disabled hosts. Make sure you include the ComputeFilter in the ``scheduler_default_filters`` config option to avoid placing instances on disabled hosts. + +.. releasenotes/notes/upgrade_rootwrap_compute_filters-428ca239f2e4e63d.yaml @ b'ec9d5e375e208686d33b9259b039cc009bded42e' + +- Upgrade the rootwrap configuration for the compute service, so that patches requiring new rootwrap configuration can be tested with grenade. + +.. releasenotes/notes/vmware_integration_bridge-249567087da5ecb2.yaml @ b'0c04dffcc43a3fa8eb32cd8ec09e703615bbd1b2' + +- For backward compatible support the setting ``CONF.vmware.integration_bridge`` needs to be set when using the Neutron NSX|MH plugin. The default value has been set to ``None``. + +.. releasenotes/notes/xen_rename-03edd9b78f3e81e5.yaml @ b'd8410950e130d09cd86a73da27e1305c0c3a9662' + +- XenServer hypervisor type has been changed from ``xen`` to ``XenServer``. It could impact your aggregate metadata or your flavor extra specs if you provide only the former. + +.. releasenotes/notes/xenserver-glance-plugin-1.3-11c3b70b8c928263.yaml @ b'89de4ed5e94620f7ca3716a888d7e26a0d23e98f' + +- The glance xenserver plugin has been bumped to version 1.3 which includes new interfaces for referencing glance servers by url. All dom0 will need to be upgraded with this plugin before upgrading the nova code. + + +.. _Release Notes_13.0.0_stable_mitaka_Deprecation Notes: + +Deprecation Notes +----------------- + +.. releasenotes/notes/api_servers_no_scheme-e4aa216d251022f2.yaml @ b'1c18f1838526de11ddd2ab42b4a49ab8df2ee8d1' + +- It is now deprecated to use [glance] api_servers without a protocol scheme (http / https). This is required to support urls throughout the system. Update any api_servers list with fully qualified https / http urls. + +.. releasenotes/notes/deprecate-conductor-manager-class-03620676d939b0eb.yaml @ b'e683c41521647d1c67bbdeb9c7e126c603676fb4' + +- The conductor.manager configuration option is now deprecated and will be removed. + +.. releasenotes/notes/deprecate_compute_stats_class-229abfcb8816bdbd.yaml @ b'3be36fcb7bdc0f48eae06f5378f3ba2e4a4975bd' + +- Deprecate ``compute_stats_class`` config option. This allowed loading an alternate implementation for collecting statistics for the local compute host. Deployments that felt the need to use this facility are encoraged to propose additions upstream so we can create a stable and supported interface here. + +.. releasenotes/notes/deprecate_db_driver-91c76ca8011d663c.yaml @ b'c87ae92be56fa7f0f75749df5b8cbd527f539dcf' + +- Deprecate the ``db_driver`` config option. Previously this let you replace our SQLAlchemy database layer with your own. This approach is deprecated. Deployments that felt the need to use the facility are encourage to work with upstream Nova to address db driver concerns in the main SQLAlchemy code paths. + +.. releasenotes/notes/deprecate_glance_opts-eab01aba5dcda38a.yaml @ b'26262b7943542e8b2ffe93db165977e9f58da5a2' + +- The host, port, and protocol options in the [glance] configuration section are deprecated, and will be removed in the N release. The api_servers value should be used instead. + +.. releasenotes/notes/deprecate_hooks-6f6d60ac206a6da6.yaml @ b'7be56442703d071c9256267abb8acfabae642a1a' + +- Deprecate the use of nova.hooks. This facility used to let arbitrary out of tree code be executed around certain internal actions, but is unsuitable for having a well maintained API. Anyone using this facility should bring forward their use cases in the Newton cycle as nova-specs. + +.. releasenotes/notes/deprecate_pluggable_managers-ca0224bcd779454c.yaml @ b'7b1fb84f68bbcef0c496d3990e5d6b99a5360bc8' + +- Nova used to support the concept that ``service managers`` were + replaceable components. There are many config options where you can + replace a manager by specifying a new class. This concept is + deprecated in Mitaka as are the following config options. + + * [cells] manager + * metadata_manager + * compute_manager + * console_manager + * consoleauth_manager + * cert_manager + * scheduler_manager + + Many of these will be removed in Newton. Users of these options + are encouraged to work with Nova upstream on any features missing + in the default implementations that are needed. + +.. releasenotes/notes/deprecate_security_group_api-3d96d683a3723e2c.yaml @ b'ef957eedde019f255ce363d71a644604cca8d8df' + +- Deprecate ``security_group_api`` configuration option. The current values are ``nova`` and ``neutron``. In future the correct security_group_api option will be chosen based on the value of ``use_neutron`` which provides a more coherent user experience. + +.. releasenotes/notes/deprecate_vendordata_driver-eefc745365a881c3.yaml @ b'21da1babce0a3f6a2e8e2b802e9cc0e8f491526b' + +- Deprecate the ``vendordata_driver`` config option. This allowed creating a different class loader for defining vendordata metadata. The default driver loads from a json file that can be arbitrarily specified, so is still quite flexible. Deployments that felt the need to use this facility are encoraged to propose additions upstream so we can create a stable and supported interface here. + +.. releasenotes/notes/ironic_api_version_opt_deprecated-50c9b0486e78fe6e.yaml @ b'05df44f2413e400b005abeab117afde3b3521c65' + +- The configuration option ``api_version`` in the ``ironic`` group was marked as deprecated and will be removed in the future. The only possible value for that configuration was "1" (because Ironic only has 1 API version) and the Ironic team came to an agreement that setting the API version via configuration option should not be supported anymore. As the Ironic driver in Nova requests the Ironic v1.8 API, that means that Nova 13.0.0 ("Mitaka") requires Ironic 4.0.0 ("Liberty") or newer if you want to use the Ironic driver. + +.. releasenotes/notes/libvirt-deprecate-migration-flags-config-4ba1e2d6c9ef09ff.yaml @ b'89dcf9d1d487b489b5c29301c57efced4538be25' + +- The libvirt live_migration_flag and block_migration_flag + config options are deprecated. These options gave too + fine grained control over the flags used and, in some + cases, misconfigurations could have dangerous side + effects. Please note the availability of a new + live_migration_tunnelled configuration option. + +.. releasenotes/notes/neutron-mtu-6a7edd9e396107d7.yaml @ b'b3c64d1c64faf933243b53275d5e63e7e2e0fecb' + +- The ``network_device_mtu`` option in Nova is deprecated for removal since network MTU should be specified when creating the network with nova-network. With Neutron networks, the MTU value comes from the ``segment_mtu`` configuration option in Neutron. + +.. releasenotes/notes/os-migrations-ef225e5b309d5497.yaml @ b'98e4a64ad3f1f975e78224d19e729787b902e84c' + +- The old top-level resource `/os-migrations` is deprecated, it won't be extended anymore. And migration_type for /os-migrations, also add ref link to the /servers/{uuid}/migrations/{id} for it when the migration is an in-progress live-migration. This has been added in microversion 2.23. + +.. releasenotes/notes/rm_volume_manager-78fed5be43d285b3.yaml @ b'6e8e322718529e50bf2035507b970058ddaa836a' + +- Deprecate ``volume_api_class`` and ``network_api_class`` config options. We only have one sensible backend for either of these. These options will be removed and turned into constants in Newton. + +.. releasenotes/notes/switch-to-oslo-cache-7114a0ab2dea52df.yaml @ b'205fb7c8b34e521bdc14b5c3698d1597753b27d4' + +- Option ``memcached_servers`` is deprecated in Mitaka. Operators should use oslo.cache configuration instead. Specifically ``enabled`` option under [cache] section should be set to True and the url(s) for the memcached servers should be in [cache]/memcache_servers option. + +.. releasenotes/notes/zookeeper-servicegroup-driver-removed-c3bcaa6f9fe976ed.yaml @ b'7b1fb84f68bbcef0c496d3990e5d6b99a5360bc8' + +- The Zookeeper Service Group driver has been removed. + + The driver has no known users and is not actively mantained. A warning log + message about the driver's state was added for the Kilo release. Also, + evzookeeper library that the driver depends on is unmaintained and + `incompatible with recent eventlet releases`_. + + A future release of Nova will `use the Tooz library to track + service liveliness`_, and Tooz supports Zookeeper. + + .. _`incompatible with recent eventlet releases`: https://bugs.launchpad.net/nova/+bug/1443910 + .. _`use the Tooz library to track service liveliness`: http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/service-group-using-tooz.html + + +.. _Release Notes_13.0.0_stable_mitaka_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/13.0.0-cve-bugs-fe43ef267a82f304.yaml @ b'9c0bbda07fdcf134308371644d09becbb18c62b1' + +- [OSSA 2016-001] Nova host data leak through snapshot (CVE-2015-7548) + + * `Bug 1524274 <https://bugs.launchpad.net/nova/+bug/1524274>`_ + * `Announcement <http://lists.openstack.org/pipermail/openstack-announce/2016-January/000911.html>`__ + + [OSSA 2016-002] Xen connection password leak in logs via StorageError (CVE-2015-8749) + + * `Bug 1516765 <https://bugs.launchpad.net/nova/+bug/1516765>`_ + * `Announcement <http://lists.openstack.org/pipermail/openstack-announce/2016-January/000916.html>`__ + + [OSSA 2016-007] Host data leak during resize/migrate for raw-backed instances (CVE-2016-2140) + + * `Bug 1548450 <https://bugs.launchpad.net/nova/+bug/1548450>`_ + * `Announcement <http://lists.openstack.org/pipermail/openstack-announce/2016-March/001009.html>`__ + + +.. _Release Notes_13.0.0_stable_mitaka_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/upgrade_rootwrap_compute_filters-428ca239f2e4e63d.yaml @ b'ec9d5e375e208686d33b9259b039cc009bded42e' + +- In a race condition if base image is deleted by ImageCacheManager while imagebackend is copying the image to instance path, then the instance goes in to error state. In this case when libvirt has changed the base file ownership to libvirt-qemu while imagebackend is copying the image, then we get permission denied error on updating the file access time using os.utime. Fixed this issue by updating the base file access time with root user privileges using 'touch' command. + +.. releasenotes/notes/vhost-user-mtu-23d0af36a8adfa56.yaml @ b'c7eb823fe73e3db5dca48df5879db18cbab5bd8d' + +- When plugging virtual interfaces of type vhost-user the MTU value will not be applied to the interface by nova. vhost-user ports exist only in userspace and are not backed by kernel netdevs, for this reason it is not possible to set the mtu on a vhost-user interface using standard tools such as ifconfig or ip link. + + +.. _Release Notes_13.0.0_stable_mitaka_Other Notes: + +Other Notes +----------- + +.. releasenotes/notes/conductor_rpcapi_v2_drop-9893c27bb32d9786.yaml @ b'116cd3c0916630b53b31ee7494f412ac7a17fafb' + +- Conductor RPC API no longer supports v2.x. + +.. releasenotes/notes/deprecate-nova-manage-service-subcommand-7626f7692bd62e41.yaml @ b'df840b34570022c5e9f1c6024cbd895f43eac1ff' + +- The service subcommand of nova-manage is deprecated. Use the nova service-* commands from python-novaclient instead or the os-services REST resource. The service subcommand will be removed in the 14.0 release. + +.. releasenotes/notes/neutron-mtu-6a7edd9e396107d7.yaml @ b'b3c64d1c64faf933243b53275d5e63e7e2e0fecb' + +- The Neutron network MTU value is now used when plugging virtual interfaces in nova-compute. If the value is 0, which is the default value for the ``segment_mtu`` configuration option in Neutron before Mitaka, then the (deprecated) ``network_device_mtu`` configuration option in Nova is used, which defaults to not setting an MTU value. + +.. releasenotes/notes/policy-sample-defaults-changed-b5eea1daeb305251.yaml @ b'83467b8c68607d2f7551eaf283a354e1b0bb27fa' + +- The sample policy file shipped with Nova contained many policies set to ""(allow all) which was not the proper default for many of those checks. It was also a source of confusion as some people thought "" meant to use the default rule. These empty policies have been updated to be explicit in all cases. + Many of them were changed to match the default rule of "admin_or_owner" which is a more restrictive policy check but does not change the restrictiveness of the API calls overall because there are similar checks in the database already. + This does not affect any existing deployment, just the sample file included for use by new deployments. + +.. releasenotes/notes/remove-ec2-api-service-c17a35ed297355b8.yaml @ b'eec7a55319b3f22949735227199ce49b851519b8' + +- Nova's EC2 API support which was deprecated in Kilo (https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#Upgrade_Notes_2) is removed from Mitaka. This has been replaced by the new ec2-api project (http://git.openstack.org/cgit/openstack/ec2-api/). + + diff --git a/releasenotes/source/newton.rst b/releasenotes/source/newton.rst index fb164d01f1..e757f15bed 100644 --- a/releasenotes/source/newton.rst +++ b/releasenotes/source/newton.rst @@ -2,6 +2,1133 @@ Newton Series Release Notes =================================== -.. release-notes:: - :branch: origin/stable/newton - :earliest-version: 14.0.0 +.. _Release Notes_14.1.0_stable_newton: + +14.1.0 +====== + +.. _Release Notes_14.1.0_stable_newton_Upgrade Notes: + +Upgrade Notes +------------- + +.. releasenotes/notes/bug-1738094-request_specs.spec-migration-22d3421ea1536a37.yaml @ b'e4e7b8da563e1fe4c2713dad55788f5ba3a86057' + +- This release contains a schema migration for the ``nova_api`` database + in order to address bug 1738094: + + https://bugs.launchpad.net/nova/+bug/1738094 + + 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. + + +.. _Release Notes_14.1.0_stable_newton_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/bug-1664931-refine-validate-image-rebuild-6d730042438eec10.yaml @ b'4cbfcc590c17134fd14e3aab90ffbb7c17006a95' + +- 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. + + Therefore this release contains a fix for those regressions in scheduling + behavior on rebuild while maintaining the original fix for CVE-2017-16239. + + .. note:: 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. + +.. releasenotes/notes/bug-1733886-os-quota-sets-force-2.36-5866924621ecc857.yaml @ b'9de9faa0f6080e0e01e676330eff293c3d15ffb2' + +- 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. + + .. _bug 1733886: https://bugs.launchpad.net/nova/+bug/1733886 + + +.. _Release Notes_14.0.10_stable_newton: + +14.0.10 +======= + +.. _Release Notes_14.0.10_stable_newton_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/bug-1664931-validate-image-rebuild-9c5b05a001c94a4d.yaml @ b'698b261a5a2a6c0f31ef5059046ef7196d5cba30' + +- `OSSA-2017-005`_: Nova Filter Scheduler bypass through rebuild action + + 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. + + The fix is in the `nova-api` and `nova-conductor` services. + + .. _OSSA-2017-005: https://security.openstack.org/ossa/OSSA-2017-005.html + + +.. _Release Notes_14.0.7_stable_newton: + +14.0.7 +====== + +.. _Release Notes_14.0.7_stable_newton_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/bug-1673613-7357d40ba9ab1fa6.yaml @ b'e3076f5ff6fea598dc4ad2de9b5cb88eb083688b' + +- 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. + + .. _bug 1673613: https://launchpad.net/bugs/1673613 + +.. releasenotes/notes/bug-1691545-1acd6512effbdffb.yaml @ b'd6a628da62f810310ab1bdc2e04222d8010e7b62' + +- 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. + + .. _bug 1691545: https://bugs.launchpad.net/nova/+bug/1691545 + +.. releasenotes/notes/fix-default-cell0-db-connection-f9717053cc34778e.yaml @ b'f9a3c3fcff89828b7df45149c2d0ee188f439e46' + +- 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``. + + +.. _Release Notes_14.0.5_stable_newton: + +14.0.5 +====== + +.. _Release Notes_14.0.5_stable_newton_Prelude: + +Prelude +------- + +.. releasenotes/notes/bug-1673569-cve-2017-7214-2d7644b356015c93.yaml @ b'c2c91ce44592fc5dc2aacee1cf7f5b5cfd2e9a0a' + +This release includes fixes for security vulnerabilities. + + +.. _Release Notes_14.0.5_stable_newton_Known Issues: + +Known Issues +------------ + +.. releasenotes/notes/live-migration-progress-known-issue-20176f49da4d3c91.yaml @ b'64a482c24d4dfc2aae42672de160ea38e948304c' + +- The live-migration progress timeout controlled by the configuration option + ``[libvirt]/live_migration_progress_timeout`` has been discovered to + frequently cause live-migrations to fail with a progress timeout error, + even though the live-migration is still making good progress. + To minimize problems caused by these checks we recommend setting the value + to 0, which means do not trigger a timeout. (This has been made the + default in Ocata and Pike.) + To modify when a live-migration will fail with a timeout error, please now + look at ``[libvirt]/live_migration_completion_timeout`` and + ``[libvirt]/live_migration_downtime``. + + +.. _Release Notes_14.0.5_stable_newton_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/bug-1673569-cve-2017-7214-2d7644b356015c93.yaml @ b'c2c91ce44592fc5dc2aacee1cf7f5b5cfd2e9a0a' + +- [CVE-2017-7214] Failed notification payload is dumped in logs with auth secrets + + * `Bug 1673569 <https://bugs.launchpad.net/nova/+bug/1673569>`_ + + +.. _Release Notes_14.0.4_stable_newton: + +14.0.4 +====== + +.. _Release Notes_14.0.4_stable_newton_Known Issues: + +Known Issues +------------ + +.. releasenotes/notes/libvirt-script-with-empty-path-2b49caa68b05278d.yaml @ b'99f8a3c4e9d903d48e5c7e245bcb2d3299b7904d' + +- 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 + (`<script path=''/>`) of the interface. + + 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". + + 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. + + 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`_ + + .. _commit: https://libvirt.org/git/?p=libvirt.git;a=commit;h=9c17d665fdc5f0ab74500a14c30627014c11b2c0 + .. _Bugzilla 1412834: https://bugzilla.redhat.com/show_bug.cgi?id=1412834 + + +.. _Release Notes_14.0.4_stable_newton_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/bug-1662699-06203e7262e02aa6.yaml @ b'dce8618166d80dc6cf2854920f6275eee73b8d84' + +- 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. + + .. _bug 1662699: https://bugs.launchpad.net/nova/+bug/1662699 + + +.. _Release Notes_14.0.2_stable_newton: + +14.0.2 +====== + +.. _Release Notes_14.0.2_stable_newton_Prelude: + +Prelude +------- + +.. releasenotes/notes/bug-1635446-newton-2351fe93f9af67e5.yaml @ b'867661d51bdb0cf2a6f326cb18f26bbc1f04eb15' + +A new database schema migration is included in this release to fix `bug 1635446 <https://bugs.launchpad.net/nova/+bug/1635446>`_. + + +.. _Release Notes_14.0.2_stable_newton_Known Issues: + +Known Issues +------------ + +.. releasenotes/notes/bug_1632723-2a4bd74e4a942a06.yaml @ b'92ca31b27d892e5aa9a6ffb990c7ea17b26fa991' + +- Use of the newly introduced optional placement RESTful API in Newton requires WebOb>=1.6.0. This requirement was not reflected prior to the release of Newton in requirements.txt with the lower limit being set to WebOb>=1.2.3. + + +.. _Release Notes_14.0.2_stable_newton_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/bug-1635446-newton-2351fe93f9af67e5.yaml @ b'867661d51bdb0cf2a6f326cb18f26bbc1f04eb15' + +- Contains database schema migration + ``021_build_requests_instance_mediumtext`` which increases the size of the + ``build_requests.instance`` column on MySQL backends. This is needed to + create new instances which have very large ``user_data`` fields. + + +.. _Release Notes_14.0.1_stable_newton: + +14.0.1 +====== + +.. _Release Notes_14.0.1_stable_newton_Prelude: + +Prelude +------- + +.. releasenotes/notes/newton_prelude-6a6566c8753d147c.yaml @ b'0c6c2dd59184590cae2b6964042250e4ec0a5021' + +Nova 14.0.0 release is including a lot of new features and bugfixes. It can be extremely hard to mention all the changes we introduced during that release but we beg you to read at least the upgrade section which describes the required modifications that you need to do for upgrading your cloud from 13.0.0 (Mitaka) to 14.0.0 (Newton). +That said, a few major changes are worth to notice here. This is not an exhaustive list of things to notice, rather just important things you need to know : + + - Latest API microversion supported for Newton is v2.38 + - Nova now provides a new placement RESTful API endpoint that is for + the moment optional where Nova compute nodes use it for providing + resources. For the moment, the nova-scheduler is not using it but we + plan to check the placement resources for Ocata. In case you plan to + rolling-upgrade the compute nodes between Newton and Ocata, please + look in the notes below how to use the new placement API. + - Cells V2 now supports booting instances for one cell v2 only. We plan + to add a multi-cell support for Ocata. You can prepare for Ocata now + by creating a cellv2 now using the nova-manage related commands, but + configuring Cells V2 is still fully optional for this cycle. + - Nova is now using Glance v2 API for getting image resources. + - API microversions 2.36 and above now deprecate the REST resources in + Nova used to proxy calls to other service type APIs (eg. /os-volumes). + We'll still supporting those until we raise our minimum API version + to 2.36 which is not planned yet (we're supporting v2.1 as of now) but + you're encouraged to stop using those resources and rather calling the + other services that provide those natively. + + +.. _Release Notes_14.0.0_stable_newton: + +14.0.0 +====== + +.. _Release Notes_14.0.0_stable_newton_New Features: + +New Features +------------ + +.. releasenotes/notes/add-perf-event-e1385b6b6346fbda.yaml @ b'a2d0b8d1b0954c6fdc622dda8fe8777e41566d92' + +- Add perf event support for libvirt driver. This can be done by adding new configure option 'enabled_perf_events' in libvirt section of nova.conf. This feature requires libvirt>=2.0.0. + +.. releasenotes/notes/async-live-migration-rest-check-675ec309a9ccc28e.yaml @ b'2a1aad9de7e33ee7bcb496de482d325915373a1a' + +- Starting from REST API microversion 2.34 pre-live-migration checks are performed asynchronously. ``instance-actions`` should be used for getting information about the checks results. New approach allows to reduce rpc timeouts amount, as previous workflow was fully blocking and checks before live-migration make blocking rpc request to both source and destination compute node. + +.. releasenotes/notes/automatic-live-migration-completion-auto-converge-3ddd3a40eaf3ef5b.yaml @ b'0c0f60031acba11d0bab0617f68b95d9b5eb8d1d' + +- New configuration option live_migration_permit_auto_converge has been added to allow hypervisor to throttle down CPU of an instance during live migration in case of a slow progress due to high ratio of dirty pages. Requires libvirt>=1.2.3 and QEMU>=1.6.0. + +.. releasenotes/notes/automatic-live-migration-completion-post-copy-a7a3a986961c93d8.yaml @ b'2de3879afabb3738df3a6ae86774eb203332600f' + +- New configuration option live_migration_permit_post_copy has been added to start live migrations in a way that allows nova to switch an on-going live migration to post-copy mode. Requires libvirt>=1.3.3 and QEMU>=2.5.0. If post copy is permitted and version requirements are met it also changes behaviour of 'live_migration_force_complete', so that it switches on-going live migration to post-copy mode instead of pausing an instance during live migration. + +.. releasenotes/notes/bp-fix-console-auth-tokens-16b1b1b402dca362.yaml @ b'3c3925e71a3a06dc8a47483d90cdc585476b1538' + +- Fix os-console-auth-tokens API to return connection info for all types of tokens, not just RDP. + +.. releasenotes/notes/bp-hyper-v-remotefx-1474ef1a082ad1b0.yaml @ b'2d94ae597af349c577b33e785664c9205b12dcc0' + +- Hyper-V RemoteFX feature. + + Microsoft RemoteFX enhances the visual experience in RDP connections, + including providing access to virtualized instances of a physical GPU to + multiple guests running on Hyper-V. + + In order to use RemoteFX in Hyper-V 2012 R2, one or more DirectX 11 + capable display adapters must be present and the RDS-Virtualization + server feature must be installed. + + To enable this feature, the following config option must be set in + the Hyper-V compute node's 'nova.conf' file:: + + [hyperv] + enable_remotefx = True + + To create instances with RemoteFX capabilities, the following flavor + extra specs must be used: + + **os:resolution**. Guest VM screen resolution size. Acceptable values:: + + 1024x768, 1280x1024, 1600x1200, 1920x1200, 2560x1600, 3840x2160 + + '3840x2160' is only available on Windows / Hyper-V Server 2016. + + **os:monitors**. Guest VM number of monitors. Acceptable values:: + + [1, 4] - Windows / Hyper-V Server 2012 R2 + [1, 8] - Windows / Hyper-V Server 2016 + + **os:vram**. Guest VM VRAM amount. Only available on + Windows / Hyper-V Server 2016. Acceptable values:: + + 64, 128, 256, 512, 1024 + + There are a few considerations that needs to be kept in mind: + + * Not all guests support RemoteFX capabilities. + * Windows / Hyper-V Server 2012 R2 does not support Generation 2 VMs + with RemoteFX capabilities. + * Per resolution, there is a maximum amount of monitors that can be + added. The limits are as follows: + + For Windows / Hyper-V Server 2012 R2:: + + 1024x768: 4 + 1280x1024: 4 + 1600x1200: 3 + 1920x1200: 2 + 2560x1600: 1 + + For Windows / Hyper-V Server 2016:: + + 1024x768: 8 + 1280x1024: 8 + 1600x1200: 4 + 1920x1200: 4 + 2560x1600: 2 + 3840x2160: 1 + +.. releasenotes/notes/bp-instance-tags-3acb227083320796.yaml @ b'537df23d85e0f7c461643efe6b6501d267ae99d0' + +- Microversion v2.26 allows to create/update/delete simple string tags. They can be used for filtering servers by these tags. + +.. releasenotes/notes/bp-keypairs-pagination-634c46aaa1058161.yaml @ b'47358449d359a287d21426b4e1f18479a4d1fd36' + +- Added microversion v2.35 that adds pagination support for keypairs with the help of new optional parameters 'limit' and 'marker' which were added to GET /os-keypairs request. + +.. releasenotes/notes/bp-nova-api-hypervsor-cpu-info-b84cddf8b70b88d2.yaml @ b'228e916cdd54f8ea716728709793c6c1f2189ff1' + +- Added microversion v2.28 from which hypervisor's 'cpu_info' field returned as JSON object by sending GET /v2.1/os-hypervisors/{hypervisor_id} request. + +.. releasenotes/notes/bp-virtuozzo-cloud-storage-support-4f4cda52ca41538e.yaml @ b'e58e11127b3b7748b6a42cf7349010a93d434a1e' + +- Virtuozzo Storage is available as a volume backend in + libvirt virtualization driver. + + .. note:: Only qcow2/raw volume format supported, but not ploop. + +.. releasenotes/notes/bp-virtuozzo-instance-resize-support-b523e6e8a0de0fbc.yaml @ b'd4aa455d53c91c6dfebbf9a9850f7b6c3fef4545' + +- Virtuozzo ploop disks can be resized now during "nova resize". + +.. releasenotes/notes/bp-virtuozzo-rescue-support-a0f69357a93e5e92.yaml @ b'd60d70598ec0ebdb6eda95fa5ceb7d17b6111c70' + +- Virtuozzo instances with ploop disks now support the rescue operation + +.. releasenotes/notes/cells-discover-hosts-06a3079ba687e092.yaml @ b'3eb4d1fd1d94dc830f7e3420c49117e01df6451a' + +- A new nova-manage command has been added to discover any new hosts that are added to a cell. If a deployment has migrated to cellsv2 using either the simple_cell_setup or the map_cell0/map_cell_and_hosts/map_instances combo then anytime a new host is added to a cell this new "nova-manage cell_v2 discover_hosts" needs to be run before instances can be booted on that host. If multiple hosts are added at one time the command only needs to be run one time to discover all of them. This command should be run from an API host, or a host that is configured to use the nova_api database. + Please note that adding a host to a cell and not running this command could lead to build failures/reschedules if that host is selected by the scheduler. The discover_hosts command is necessary to route requests to the host but is not necessary in order for the scheduler to be aware of the host. It is advised that nova-compute hosts are configured with "enable_new_services=False" in order to avoid failures before the hosts have been discovered. + +.. releasenotes/notes/check_destination_when_evacuating-37b52ebe8b5b086c.yaml @ b'86706785ff251b841dff3590dc60f6b4834d7b7e' + +- On evacuate actions, the default behaviour when providing a host in the request body changed. Now, instead of bypassing the scheduler when asking for a destination, it will instead call it with the requested destination to make sure the proposed host is accepted by all the filters and the original request. In case the administrator doesn't want to call the scheduler when providing a destination, a new request body field called ``force`` (defaulted to False) will modify that new behaviour by forcing the evacuate operation to the destination without verifying the scheduler. + +.. releasenotes/notes/check_destination_when_livemig-e69d32e02d7a18c9.yaml @ b'7aa2285e724345717a3f333adc13660d7b97dfcd' + +- On live-migrate actions, the default behaviour when providing a host in the request body changed. Now, instead of bypassing the scheduler when asking for a destination, it will instead call it with the requested destination to make sure the proposed host is accepted by all the filters and the original request. In case the administrator doesn't want to call the scheduler when providing a destination, a new request body field called ``force`` (defaulted to False) will modify that new behaviour by forcing the live-migrate operation to the destination without verifying the scheduler. + +.. releasenotes/notes/get-me-a-network-992eabc81b5e5347.yaml @ b'd727795d6668abaf17b5afe01d2e1757aebe7e2e' + +- The 2.37 microversion adds support for automatic allocation of network + resources for a project when ``networks: auto`` is specified in a server + create request. If the project does not have any networks available to it + and the ``auto-allocated-topology`` API is available in the Neutron + networking service, Nova will call that API to allocate resources for the + project. There is some setup required in the deployment for the + ``auto-allocated-topology`` API to work in Neutron. See the + `Additional features`_ section of the OpenStack Networking Guide + for more details for setting up this feature in Neutron. + + .. note:: The API does not default to 'auto'. However, python-novaclient + will default to passing 'auto' for this microversion if no specific + network values are provided to the CLI. + + .. note:: This feature is not available until all of the compute services + in the deployment are running Newton code. This is to avoid sending a + server create request to a Mitaka compute that can not understand a + network ID of 'auto' or 'none'. If this is the case, the API will treat + the request as if ``networks`` was not in the server create request body. + Once all computes are upgraded to Newton, a restart of the nova-api + service will be required to use this new feature. + + .. _Additional features: http://docs.openstack.org/networking-guide/intro-os-networking-features.html + +.. releasenotes/notes/glance_v2-15b080e361804976.yaml @ b'f71cd2ca03693655efdbd1109f406ab6f3b58ee6' + +- Nova now defaults to using the glance version 2 protocol for all backend operations for all virt drivers. A ``use_glance_v1`` config option exists to revert to glance version 1 protocol if issues are seen, however that will be removed early in Ocata, and only glance version 2 protocol will be used going forward. + +.. releasenotes/notes/ironic-driver-hash-ring-7d763d87b9236e5d.yaml @ b'6047d790a32ef5a65d4d6b029f673ce53c3d4141' + +- Adds a new feature to the ironic virt driver, which allows + multiple nova-compute services to be run simultaneously. This uses + consistent hashing to divide the ironic nodes between the nova-compute + services, with the hash ring being refreshed each time the resource tracker + runs. + + Note that instances will still be owned by the same nova-compute service + for the entire life of the instance, and so the ironic node that instance + is on will also be managed by the same nova-compute service until the node + is deleted. This also means that removing a nova-compute service will + leave instances managed by that service orphaned, and as such most + instance actions will not work until a nova-compute service with the same + hostname is brought (back) online. + + When nova-compute services are brought up or down, the ring will eventually + re-balance (when the resource tracker runs on each compute). This may + result in duplicate compute_node entries for ironic nodes while the + nova-compute service pool is re-balancing. However, because any + nova-compute service running the ironic virt driver can manage any ironic + node, if a build request goes to the compute service not currently managing + the node the build request is for, it will still succeed. + + There is no configuration to do to enable this feature; it is always + enabled. There are no major changes when only one compute service is + running. If more compute services are brought online, the bigger changes + come into play. + + Note that this is tested when running with only one nova-compute service, + but not more than one. As such, this should be used with caution for + multiple compute hosts until it is properly tested in CI. + +.. releasenotes/notes/ironic-multitenant-networking-6f124964831d4a6c.yaml @ b'e55cf73890aa104281775c0d2fe4f9f75ab2ec97' + +- Multitenant networking for the ironic compute driver is now supported. To enable this feature, ironic nodes must be using the 'neutron' network_interface. + +.. releasenotes/notes/libvirt-uses-os-vif-plugins-31a0617de0c248b9.yaml @ b'745f5fbb3a1b0a42eb54e2be2ecfffca3cbbb872' + +- The Libvirt driver now uses os-vif plugins for handling plug/unplug actions for the Linux Bridge and OpenVSwitch VIF types. Each os-vif plugin will have its own group in nova.conf for configuration parameters it needs. These plugins will be installed by default as part of the os-vif module installation so no special action is required. + +.. releasenotes/notes/libvirt_ppc64le_hugepage_support-b9fd39cf20c8e91d.yaml @ b'abc24acfa1982a0ffccbe08a006ac7c7a9f4ecda' + +- Added hugepage support for POWER architectures. + +.. releasenotes/notes/modern-microversions-964ae9a17df8c4b3.yaml @ b'bd199e3f9b7336b2cbc583fc6ab352f6e5b4d143' + +- Microversions may now (with microversion 2.27) be requested with the "OpenStack-API-Version: compute 2.27" header, in alignment with OpenStack-wide standards. The original format, "X-OpenStack-Nova-API-Version: 2.27", may still be used. + +.. releasenotes/notes/mutable-config-e7e82b3d7c38f3a5.yaml @ b'49f547bd2874af9b400ad3dae68c70579489fbe2' + +- Nova has been enabled for mutable config. Certain options may be reloaded + by sending SIGHUP to the correct process. Live migration options will apply + to live migrations currently in progress. Please refer to the configuration + manual. + + * DEFAULT.debug + * libvirt.live_migration_completion_timeout + * libvirt.live_migration_progress_timeout + +.. releasenotes/notes/notification-transformation-newton-29a9324d1428b7d3.yaml @ b'6a2a1a7d630e4fc0b17af834c2a6750f1553019c' + +- + The following legacy notifications have been been transformed to + a new versioned payload: + + * instance.delete + * instance.pause + * instance.power_on + * instance.shelve + * instance.suspend + * instance.restore + * instance.resize + * instance.update + * compute.exception + + 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. + +.. releasenotes/notes/oslopolicy-scripts-957b364b8ffd7c3f.yaml @ b'3b609a52fb4ac030eef95dd8588e7d54abcc0615' + +- Nova is now configured to work with two oslo.policy CLI scripts that have been added. + The first of these can be called like "oslopolicy-list-redundant --namespace nova" and will output a list of policy rules in policy.[json|yaml] that match the project defaults. These rules can be removed from the policy file as they have no effect there. + The second script can be called like "oslopolicy-policy-generator --namespace nova --output-file policy-merged.yaml" and will populate the policy-merged.yaml file with the effective policy. This is the merged results of project defaults and config file overrides. + +.. releasenotes/notes/pagination-for-hypervisor-9c3393cd58149791.yaml @ b'ec53c6c0ec283a4c179bd2845cf0356c27fa5301' + +- Added microversion v2.33 which adds paging support for hypervisors, the admin is able to perform paginate query by using limit and marker to get a list of hypervisors. The result will be sorted by hypervisor id. + +.. releasenotes/notes/placement-config-section-59891ba38e0749e7.yaml @ b'a6ad102c9d73c300d4ec45d80dbf914ca9d9ec77' + +- The nova-compute worker now communicates with the new placement API service. Nova determines the placement API service by querying the OpenStack service catalog for the service with a service type of 'placement'. If there is no placement entry in the service catalog, nova-compute will log a warning and no longer try to reconnect to the placement API until the nova-worker process is restarted. + +.. releasenotes/notes/placement-config-section-59891ba38e0749e7.yaml @ b'a6ad102c9d73c300d4ec45d80dbf914ca9d9ec77' + +- A new [placement] section is added to the nova.conf configuration file for configuration options affecting how Nova interacts with the new placement API service. This contains the usual keystone auth and session options. + +.. releasenotes/notes/pointer-model-b4a1828c43e8d523.yaml @ b'ed6a82ee227acd0c3d4294e8a868fe6b7f7b313f' + +- The pointer_model configuration option and hw_pointer_model image property was added to specify different pointer models for input devices. This replaces the now deprecated use_usb_tablet option. + +.. releasenotes/notes/policy-discover-cli-a14a115cacbdc9c6.yaml @ b'9864801d468de5dde79141cbab4374bd2310bef2' + +- The nova-policy command line is implemented as a tool to experience the under-development feature policy discovery. User can input the credentials infomation and the instance info, the tool will return a list of API which can be allowed to invoke. There isn't any contract for the interface of the tool due to the feature still under-development. + +.. releasenotes/notes/refresh-quotas-usage-362b239171c75f5f.yaml @ b'8d25383ad2a1bdde22e306bf9daa52508c90dd3d' + +- Add a nova-manage command to refresh the quota usages for a project or user. This can be used when the usages in the quota-usages database table are out-of-sync with the actual usages. For example, if a resource usage is at the limit in the quota_usages table, but the actual usage is less, then nova will not allow VMs to be created for that project or user. The nova-manage command can be used to re-sync the quota_usages table with the actual usage. + +.. releasenotes/notes/set_guest_time-736939fe725cbdab.yaml @ b'0376da0627b022bc6aeb3e423250f9e29181f9ab' + +- Libvirt driver will attempt to update the time of a suspended and/or a migrated guest in order to keep the guest clock in sync. This operation will require the guest agent to be configured and running in order to be able to run. However, this operation will not be disruptive. + +.. releasenotes/notes/vendordata-reboot-ad1130444a63f2d0.yaml @ b'2c49b1e442272b71be68e156f12fd7f8df26d968' + +- This release includes a new implementation of the vendordata metadata system. Please see the blueprint at http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/vendordata-reboot.html for a detailed description. There is also documentation in the Nova source tree in vendordata.rst. + +.. releasenotes/notes/virtual-device-role-tagging-ec0c36226a3f2e4d.yaml @ b'2a1aad9de7e33ee7bcb496de482d325915373a1a' + +- The 2.32 microversion adds support for virtual device + role tagging. Device role tagging is an answer to the + question 'Which device is which, inside the guest?' When + booting an instance, an optional arbitrary 'tag' + parameter can be set on virtual network interfaces + and/or block device mappings. This tag is exposed to the + instance through the metadata API and on the config + drive. Each tagged virtual network interface is listed + along with information about the virtual hardware, such + as bus type (ex: PCI), bus address (ex: 0000:00:02.0), + and MAC address. For tagged block devices, the exposed + hardware metadata includes the bus (ex: SCSI), bus + address (ex: 1:0:2:0) and serial number. + + The 2.32 microversion also adds the 2016-06-30 version + to the metadata API. Starting with 2016-06-30, the + metadata contains a 'devices' sections which lists any + devices that are tagged as described in the previous + paragraph, along with their hardware metadata. + + +.. _Release Notes_14.0.0_stable_newton_Known Issues: + +Known Issues +------------ + +.. releasenotes/notes/cells-discover-hosts-06a3079ba687e092.yaml @ b'3eb4d1fd1d94dc830f7e3420c49117e01df6451a' + +- If a deployer has updated their deployment to using cellsv2 using either the simple_cell_setup or the map_cell0/map_cell_and_hosts/map_instances combo and they add a new host into the cell it may cause build failures or reschedules until they run the "nova-manage cell_v2 discover_hosts" command. This is because the scheduler will quickly become aware of the host but nova-api will not know how to route the request to that host until it has been "discovered". In order to avoid that it is advised that new computes are disabled until the discover command has been run. + +.. releasenotes/notes/known-issue-on-api-1efca45440136f3e.yaml @ b'ee7a01982611cdf8012a308fa49722146c51497f' + +- When using Neutron extension 'port_security' and booting an instance on a network with 'port_security_enabled=False' the Nova API response says there is a 'default' security group attached to the instance which is incorrect. However when listing security groups for the instance there are none listed, which is correct. The API response will be fixed separately with a microversion. + +.. releasenotes/notes/os-brick-lock-dir-c659089679aac50f.yaml @ b'65978582e01c37a9972bf9e979c651523f0f1889' + +- When running Nova Compute and Cinder Volume or Backup services on the same host they must use a shared lock directory to avoid rare race conditions that can cause volume operation failures (primarily attach/detach of volumes). This is done by setting the "lock_path" to the same directory in the "oslo_concurrency" section of nova.conf and cinder.conf. This issue affects all previous releases utilizing os-brick and shared operations on hosts between Nova Compute and Cinder data services. + +.. releasenotes/notes/virtual-device-role-tagging-ec0c36226a3f2e4d.yaml @ b'2a1aad9de7e33ee7bcb496de482d325915373a1a' + +- When using virtual device role tagging, the metadata on the config drive lags behind the metadata obtained from the metadata API. For example, if a tagged virtual network interface is detached from the instance, its tag remains in the metadata on the config drive. This is due to the nature of the config drive, which, once written, cannot be easily updated by Nova. + + +.. _Release Notes_14.0.0_stable_newton_Upgrade Notes: + +Upgrade Notes +------------- + +.. releasenotes/notes/add-cloudpipe-config-to-cloudpipe-group-ab96ebcb3ffc5d82.yaml @ b'512fb41c4e4a5affd774f70d6d51a1992ec68f59' + +- All cloudpipe configuration options have been added to the 'cloudpipe' group. They should no longer be included in the 'DEFAULT' group. + +.. releasenotes/notes/add-crypto-config-to-crypto-group-ac6c75ccf3c815f1.yaml @ b'e301ed2457996d5143e8a6a8cba1a97b29098485' + +- All crypto configuration options have been added to the 'crypto' group. They should no longer be included in the 'DEFAULT' group. + +.. releasenotes/notes/add-wsgi-config-to-wsgi-group-712b8cd9ada65b2e.yaml @ b'0b9e378cca2be4e034ad401d71fbe4470907f93a' + +- All WSGI configuration options have been added to the 'wsgi' group. They should no longer be included in the 'DEFAULT' group. + +.. releasenotes/notes/aggregates-moved-to-api-database-e1bd30909aaf79d3.yaml @ b'7f82c5e6816b3763cde5aee8ba97c56184aeb2aa' + +- Aggregates are being moved to the API database for CellsV2. In this release, the online data migrations will move any aggregates you have in your main database to the API database, retaining all attributes. Until this is complete, new attempts to create aggregates will return an HTTP 409 to avoid creating aggregates in one place that may conflict with aggregates you already have and are yet to be migrated. + +.. releasenotes/notes/aggregates-moved-to-api-database-e1bd30909aaf79d3.yaml @ b'7f82c5e6816b3763cde5aee8ba97c56184aeb2aa' + +- Note that aggregates 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 aggregates are not migrated and the behavior users will experience will be the same as if a purge of deleted records was performed. + +.. releasenotes/notes/bp-cells-instance-groups-api-db-910a44ef5f2f7769.yaml @ b'd35e1577c9510827b2a4802a294714340ccdee7c' + +- The nova-manage db online_data_migrations command will now migrate server groups to the API database. New server groups will be automatically created in the API database but existing server groups must be manually migrated using the nova-manage command. + +.. releasenotes/notes/bp-memory-bw-4ceb971cfe1a2fd0.yaml @ b'2a53063679346ce91b417e65d0bd1a9c3029d618' + +- The get_metrics API has been replaced by populate_metrics in nova.compute.monitors.base module. This change is introduced to allow each monitor plugin to have the flexibility of setting it's own metric value types. The in-tree metrics plugins are modified as a part of this change. However, the out-of-tree plugins would have to adapt to the new API in order to work with nova. + +.. releasenotes/notes/bp-virtuozzo-cloud-storage-support-4f4cda52ca41538e.yaml @ b'e58e11127b3b7748b6a42cf7349010a93d434a1e' + +- For the Virtuozzo Storage driver to work with os-brick <1.4.0, you need to allow "pstorage-mount" in rootwrap filters for nova-compute. + +.. releasenotes/notes/bp-virtuozzo-instance-resize-support-b523e6e8a0de0fbc.yaml @ b'd4aa455d53c91c6dfebbf9a9850f7b6c3fef4545' + +- You must update the rootwrap configuration for the compute service if you use ploop images, so that "ploop grow" filter is changed to "prl_disk_tool resize". + +.. releasenotes/notes/bug-1559026-47c3fa3468d66b07.yaml @ b'c5311439d6526006dd1354e09f2bfb86505d550d' + +- The ``record`` configuration option for the console proxy services (like VNC, serial, spice) is changed from boolean to string. It specifies the filename that will be used for recording websocket frames. + +.. releasenotes/notes/cell-id-db-sync-nova-manage-8504b54dd115a2e9.yaml @ b'24f0c5b9d6136fe18c3fba0ddd64dab99f6f1aa5' + +- 'nova-manage db sync' can now sync the cell0 database. + The cell0 db is required to store instances that cannot be scheduled to + any cell. Before the 'db sync' command is called a cell mapping + for cell0 must have been created using 'nova-manage cell_v2 map_cell0'. + This command only needs to be called when upgrading to CellsV2. + +.. releasenotes/notes/cells-single-migration-command-0e98d66e31e02a50.yaml @ b'f9a3c3fcff89828b7df45149c2d0ee188f439e46' + +- A new nova-manage command has been added which will upgrade a deployment to cells v2. Running the command will setup a single cell containing the existing hosts and instances. No data or instances will be moved during this operation, but new data will be added to the nova_api database. New instances booted after this point will be placed into the cell. Please note that this does not mean that cells v2 is fully functional at this time, but this is a significant part of the effort to get there. The new command is "nova-manage cell_v2 simple_cell_setup --transport_url <transport_url>" where transport_url is the connection information for the current message queue used by Nova. 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 `<main database name>_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. + +.. releasenotes/notes/config-ironic-client_log_level-2bb84f12154417ca.yaml @ b'a924b1db46149d2928731f59afb7fef18deed54d' + +- The deprecated configuration option ``client_log_level`` of the section ``[ironic]`` has been deleted. Please use the config options ``log_config_append`` or ``default_log_levels`` of the ``[DEFAULT]`` section. + +.. releasenotes/notes/create-cell0-mapping-60a9229c223a7516.yaml @ b'17b57250c269036a8e2c104ee79c0390f0afd3f0' + +- A new nova-manage command 'nova-manage cell_v2 map_cell0' is + now available. Creates a cell mapping for cell0, which is used for + storing instances that cannot be scheduled to any cell. This command + only needs to be called when upgrading to CellsV2. + +.. releasenotes/notes/default-value-pointer-model-cb3d9a3e9c51e503.yaml @ b'f04dd04342705c8dc745308662b698bb54debf69' + +- The default value of the ``pointer_model`` configuration option has been set to 'usbtablet'. + +.. releasenotes/notes/extensions_remove-37e9d4092981abbe.yaml @ b'76b58b8f895bb9b8afedeed6f01a6117f9194379' + +- + The following policy enforcement points have been removed as part + of the restructuring of the Nova API code. The attributes that + could have been hidden with these policy points will now always be + shown / accepted. + + * os_compute_api:os-disk-config - show / accept + ``OS-DCF:diskConfig`` parameter on servers + + * os-access-ips - show / accept ``accessIPv4`` and ``accessIPv6`` + parameters on servers + + The following entry points have been removed + + * nova.api.v21.extensions.server.resize - allowed accepting + additional parameters on server resize requests. + + * nova.api.v21.extensions.server.update - allowed accepting + additional parameters on server update requests. + + * nova.api.v21.extensions.server.rebuild - allowed accepting + additional parameters on server rebuild requests. + +.. releasenotes/notes/flavors-moved-to-api-database-b33489ed3b1b246b.yaml @ b'17a8e8a68cbe4045a1bc2889d1bf51f2db7ebcca' + +- Flavors are being moved to the API database for CellsV2. In this release, the online data migrations will move any flavors you have in your main database to the API database, retaining all attributes. Until this is complete, new attempts to create flavors will return an HTTP 409 to avoid creating flavors in one place that may conflict with flavors you already have and are yet to be migrated. + +.. releasenotes/notes/flavors-moved-to-api-database-b33489ed3b1b246b.yaml @ b'17a8e8a68cbe4045a1bc2889d1bf51f2db7ebcca' + +- Note that flavors 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 flavors are not migrated and the behavior users will experience will be the same as if a purge of deleted records was performed. + +.. releasenotes/notes/get-me-a-network-992eabc81b5e5347.yaml @ b'd727795d6668abaf17b5afe01d2e1757aebe7e2e' + +- The 2.37 microversion enforces the following: + + * ``networks`` is required in the server create request body for the API. + Specifying ``networks: auto`` is similar to not requesting specific + networks when creating a server before 2.37. + * The ``uuid`` field in the ``networks`` object of a server create request + is now required to be in UUID format, it cannot be a random string. More + specifically, the API used to support a nic uuid with a "br-" prefix but + that is a legacy artifact which is no longer supported. + +.. releasenotes/notes/glance_v2-15b080e361804976.yaml @ b'f71cd2ca03693655efdbd1109f406ab6f3b58ee6' + +- It is now required that the glance environment used by Nova exposes the version 2 REST API. This API has been available for many years, but previously Nova only used the version 1 API. + +.. releasenotes/notes/imageRef-as-uuid-only-0164c04206a42683.yaml @ b'cbd3ec476f769c42e5b2a0ef8c996b60935e7f6c' + +- imageRef input to the REST API is now restricted to be UUID or an empty string only. imageRef input while create, rebuild and rescue server etc must be a valid UUID now. Previously, a random image ref url containing image UUID was accepted. But now all the reference of imageRef must be a valid UUID (with below exception) otherwise API will return 400. + Exception- In case boot server from volume. Previously empty string was allowed in imageRef and which is ok in case of boot from volume. Nova will keep the same behavior and allow empty string in case of boot from volume only and 400 in all other case. + +.. releasenotes/notes/instance-path-2efca507456d8a70.yaml @ b'1e0b2b582251c401745e0e2813ececeff8ed60a2' + +- Prior to Grizzly release default instance directory names were based on + instance.id field, for example directory for instance could be named + ``instance-00000008``. In Grizzly this mechanism was changed, + instance.uuid is used as an instance directory name, e.g. path to instance: + + ``/opt/stack/data/nova/instances/34198248-5541-4d52-a0b4-a6635a7802dd/``. + + In Newton backward compatibility is dropped. For instances that haven't + been restarted since Folsom and earlier maintanance should be scheduled + before upgrade(stop, rename directory to instance.uuid, then start) so Nova + will start using new paths for instances. + +.. releasenotes/notes/ironic-multitenant-networking-6f124964831d4a6c.yaml @ b'e55cf73890aa104281775c0d2fe4f9f75ab2ec97' + +- The ironic driver now requires python-ironicclient>=1.5.0 (previously >=1.1.0), and requires the ironic service to support API version 1.20 or higher. As usual, ironic should be upgraded before nova for a smooth upgrade process. + +.. releasenotes/notes/ironic-resource-class-6496fed067df629f.yaml @ b'7b8195a8a8f2ca61b97a1c4329525bed1848b09d' + +- The ironic driver now requires python-ironicclient>=1.6.0, and requires the ironic service to support API version 1.21. + +.. releasenotes/notes/keypairs-moved-to-api-9cde30acac6f76b6.yaml @ b'b8aac794d4620aca341b269c6db71ea9e70d2210' + +- Keypairs have been moved to the API database, using an online data migration. During the first phase of the migration, instances will be given local storage of their key, after which keypairs will be moved to the API database. + +.. releasenotes/notes/libvirt-change-default-value-of-live-migration-tunnelled-4248cf76df605fdf.yaml @ b'61f122637b8c9952e28983de81638941dc4e7bc4' + +- Default value of live_migration_tunnelled config option in libvirt section has been changed to False. After upgrading nova to Newton all live migrations will be non-tunnelled unless live_migration_tunnelled is explicitly set to True. It means that, by default, the migration traffic will not go through libvirt and therefore will no longer be encrypted. + +.. releasenotes/notes/libvirt-uses-os-vif-plugins-31a0617de0c248b9.yaml @ b'745f5fbb3a1b0a42eb54e2be2ecfffca3cbbb872' + +- With the introduction of os-vif, some networking related configuration options have moved, and users will need to update their ``nova.conf``. + For OpenVSwitch users the following options have moved from ``[DEFAULT]`` to ``[vif_plug_ovs]`` + - network_device_mtu - ovs_vsctl_timeout + For Linux Bridge users the following options have moved from ``[DEFAULT]`` to ``[vif_plug_linux_bridge]`` + - use_ipv6 - iptables_top_regex - iptables_bottom_regex - iptables_drop_action - forward_bridge_interface - vlan_interface - flat_interface - network_device_mtu + For backwards compatibility, and ease of upgrade, these options will continue to work from ``[DEFAULT]`` during the Newton release. However they will not in future releases. + +.. releasenotes/notes/min-required-libvirt-b948948949669b02.yaml @ b'6b2cad6e1283ed7dc2b45a026b0d4a524486deaf' + +- The minimum required version of libvirt has been increased to 1.2.1 + +.. releasenotes/notes/min-required-qemu-c987a8a5c6c4fee0.yaml @ b'07e4a90cfea56a9513d476769190d488e33ac8b0' + +- The minimum required QEMU version is now checked and has been set to 1.5.3 + +.. releasenotes/notes/network-api-class-removed-a4a754ca24c02bde.yaml @ b'd82db52a093527c7978648c30870faa64043a752' + +- The network_api_class option was deprecated in Mitaka and is removed in Newton. The use_neutron option replaces this functionality. + +.. releasenotes/notes/newton-has-many-online-migrations-38066facfe197382.yaml @ b'd83c2772da4c1a059c4906d8ea7a5cf942e8e41b' + +- The newton release has a lot of online migrations that must be performed before you will be able to upgrade to ocata. Please take extra note of this fact and budget time to run these online migrations before you plan to upgrade to ocata. These migrations can be run without downtime with `nova-manage db online_data_migrations`. + +.. releasenotes/notes/notify_on_state_change_opt-e3c6f6664e143993.yaml @ b'5f4dcdce16837e28af18964f533a1eba738b9f34' + +- The ``notify_on_state_change`` configuration option was StrOpt, which would accept + any string or None in the previous release. Starting in the Newton release, + it allows only three values: None, ``vm_state``, ``vm_and_task_state``. The default + value is None. + +.. releasenotes/notes/remove-auth-admin-token-support-1b59ae7739b06bc2.yaml @ b'2ea2399ec3e4b976beadfbcd1cab78b94382eca3' + +- The deprecated auth parameter `admin_auth_token` was removed from the [ironic] config option group. The use of `admin_auth_token` is insecure compared to the use of a proper username/password. + +.. releasenotes/notes/remove-config-serial-listen-2660be1c0863ea5a.yaml @ b'3495330a94e4728ba44077f0585b34b8c74112b0' + +- The previously deprecated config option ``listen```of the group + ``serial_console`` has been removed, as it was never used in the code. + +.. releasenotes/notes/remove-deprecated-cells-manager-option-d9d20691c08d2752.yaml @ b'28803fa40b6195b152668da4e1f0feec53df533b' + +- The 'manager' option in [cells] group was deprecated in Mitaka and now it is removed completely in newton. There is no impact. + +.. releasenotes/notes/remove-deprecated-cinder-options-newton-fc3dce6856101ef8.yaml @ b'fb15c00aa1561973804819d111d52b6d25842293' + +- The following deprecated configuration options have been removed from the + ``cinder`` section of nova.conf: + + - ca_certificates_file + - api_insecure + - http_timeout + +.. releasenotes/notes/remove-deprecated-destroy_after_evacuate-option-2557d0634e78abd1.yaml @ b'50b1f1fc267517b5eb4d3da567d6d76c83568f7f' + +- The 'destroy_after_evacuate' workaround option has been removed as the workaround is no longer necessary. + +.. releasenotes/notes/remove-deprecated-legacy_api-config-options-f3f096df3a03d956.yaml @ b'c05d08b6fda348e48c92eef1aecd386f460a9158' + +- The config options 'osapi_compute_ext_list' and 'osapi_compute_extension' were deprecated in mitaka. Hence these options were completely removed in newton, as v2 API is removed and v2.1 API doesn't provide the option of configuring extensions. + +.. releasenotes/notes/remove-deprecated-remove_unused_kernels-b663aa6829761f1e.yaml @ b'547dc45044e3c0b8d25ab8f584e8a5141f541547' + +- The deprecated config option ``remove_unused_kernels`` has been removed from the ``[libvirt]`` config section. No replacement is required, as this behaviour is no longer relevant. + +.. releasenotes/notes/remove-extensible-resource-tracker-37e8fdac46ec6eba.yaml @ b'49d9433c62d74f6ebdcf0832e3a03e544b1d6c83' + +- The extensible resource tracker was deprecated in the 13.0.0 release and has now been removed. Custom resources in the nova.compute.resources namespace selected by the compute_resources configuration parameter will not be loaded. + +.. releasenotes/notes/remove-legacy-v2-api-7ac6d74edaedf011.yaml @ b'58bac4735d96aebc2af4da256f8616ce79e5d076' + +- The legacy v2 API code was deprecated since Liberty release. The legacy v2 API code was removed in Newton release. We suggest that users should move to v2.1 API which compatible v2 API with more restrict input validation and microversions support. If users are still looking for v2 compatible API before switch to v2.1 API, users can use v2.1 API code as v2 API compatible mode. That compatible mode is closer to v2 API behaviour which is v2 API compatible without restrict input validation and microversions support. So if using openstack_compute_api_legacy_v2 in /etc/nova/api-paste.ini for the API endpoint /v2, users need to switch the endpoint to openstack_compute_api_v21_legacy_v2_compatible instead. + +.. releasenotes/notes/remove-libvirt-migration-flags-config-8bf909c1295cc53f.yaml @ b'a48b6146af93dd0cb1b43ec7d83867df8b347df2' + +- The 'live_migration_flag' and 'block_migration_flag' options in libvirt section that were deprecated in Mitaka have been completely removed in Newton, because nova automatically sets correct migration flags. New config options has been added to retain possibility to turn tunnelling, auto-converge and post-copy on/off, respectively named `live_migration_tunnelled`, `live_migration_permit_auto_converge` and `live_migration_permit_post_copy`. + +.. releasenotes/notes/remove-memcached-default-option-e0e50d54cef17ac4.yaml @ b'505bc44615d922c0e9054c3ca48721b26b924caa' + +- The 'memcached_server' option in DEFAULT section which was deprecated in Mitaka has been completely removed in Newton. This has been replaced by options from oslo cache section. + +.. releasenotes/notes/remove-nova-manage-service-subcommand-2a11ed662864341c.yaml @ b'0fca575bc779962a7dfb97443f49e27c43d93039' + +- The service subcommand of nova-manage was deprecated in 13.0. Now in 14.0 the service subcommand is removed. Use service-* commands from python-novaclient or the os-services REST resource instead. + +.. releasenotes/notes/remove_config_network_device_mtu-75780f727c322ff3.yaml @ b'14da85ac95ce63e11ad2ba63053f122de9a066ec' + +- The network_device_mtu option in Nova is deprecated for removal in 13.0.0 since network MTU should be specified when creating the network. + +.. releasenotes/notes/remove_legacy_v2_api_policy_rules-033fa77420ed6362.yaml @ b'31547f551c3d081b0d88cd6af8e6f1045fab948f' + +- Legacy v2 API code is already removed. A set of policy rules in the policy.json, which are only used by legacy v2 API, are removed. Both v2.1 API and v2.1 compatible mode API are using same set of new policy rules which are with prefix `os_compute_api`. + +.. releasenotes/notes/remove_security_group_api-6fefb1a355876e83.yaml @ b'34eed4a4d48772e509261d9098a09185061a0ce0' + +- Removed the ``security_group_api`` configuration option that was deprecated in Mitaka. The correct security_group_api option will be chosen based on the value of ``use_neutron`` which provides a more coherent user experience. + +.. releasenotes/notes/remove_volume_api_class-a3c618228c89f57b.yaml @ b'6af8d2c8e9bd66956b03f946a86daf1c567821a2' + +- The deprecated ``volume_api_class`` config option has been removed. We only have one sensible backend for it, so don't need it anymore. + +.. releasenotes/notes/rename-iscsi-multipath-opt-eabbafccd2b74a0a.yaml @ b'720e5af1e08cc829e98db10da4b93795771a927e' + +- The libvirt option 'iscsi_use_multipath' has been renamed to 'volume_use_multipath'. + +.. releasenotes/notes/rename-wsgi-prefixed-opts-9075ff9c2215e61c.yaml @ b'235864008ba7c58159918620040d2425f48a8a8f' + +- The 'wsgi_default_pool_size' and 'wsgi_keep_alive' options have been renamed to 'default_pool_size' and 'keep_alive' respectively. + +.. releasenotes/notes/rm-deprecated-neutron-opts-newton-a09ecfb0775339e6.yaml @ b'efe193ceed05474ba959cae5311c516c360f5d25' + +- The following deprecated configuration options have been removed from the + ``neutron`` section of nova.conf: + + - ca_certificates_file + - api_insecure + - url_timeout + +.. releasenotes/notes/rm-sched-host-mgr-class-load-2a86749a38f0688d.yaml @ b'7e2f5c7d340a0131ac083ed036e417976d6342da' + +- The ability to load a custom scheduler host manager via the ``scheduler_host_manager`` configuration option was deprecated in the 13.0.0 Mitaka release and is now removed in the 14.0.0 Newton release. + +.. releasenotes/notes/rm_db2-926e38cbda44a55f.yaml @ b'cdf74c57a6755619acaabd2e3a2559f25b2fbe0f' + +- DB2 database support was removed from tree. This is a non open source database that had no 3rd party CI, and a set of constraints that meant we had to keep special casing it in code. It also made the online data migrations needed for cells v2 and placement engine much more difficult. With 0% of OpenStack survey users reporting usage we decided it was time to remove this to focus on features needed by the larger community. + +.. releasenotes/notes/rm_glance_opts-360c94ac27328dc9.yaml @ b'b90f2bb4fcb3f980644a952543770684c8aa3b8c' + +- Delete the deprecated ``glance.host``, ``glance.port``, ``glance.protocol`` configuration options. ``glance.api_servers`` must be set to have a working config. There is currently no default for this config option, so a value must be set. + +.. releasenotes/notes/rm_import_object_ns-5344a390b0af465e.yaml @ b'ed308b99ca3c2e92ce8def4e8fe1ba1648f9a68d' + +- Only virt drivers in the nova.virt namespace may be loaded. This has been the case according to nova docs for several releases, but a quirk in some library code meant that loading things outside the namespace continued to work unintentionally. That has been fixed, which means "compute_driver = nova.virt.foo" is invalid (and now enforced as such), and should be "compute_driver = foo" instead. + +.. releasenotes/notes/swap-volume-policy-9464e97aba12d1e0.yaml @ b'f738483e843fc27379b85c5401859ccc854adc5e' + +- The default policy for updating volume attachments, commonly referred to as swap volume, has been changed from ``rule:admin_or_owner`` to ``rule:admin_api``. This is because it is called from the volume service when migrating volumes, which is an admin-only operation by default, and requires calling an admin-only API in the volume service upon completion. So by default it would not work for non-admins. + +.. releasenotes/notes/v21enable-8454d6eca3ec604f.yaml @ b'e65557c1933a563a106763e06d0d4f564d7a4174' + +- The deprecated osapi_v21.enabled config option has been removed. This previously allowed you a way to disable the v2.1 API. That is no longer something we support, v2.1 is mandatory. + +.. releasenotes/notes/vmware_disk_enableuuid_true-99b88e00fc168dd3.yaml @ b'2a6bdf8f0e0e22fc7703faa9669ace7380dc73c3' + +- Now VMwareVCDriver will set disk.EnableUUID=True by default in all guest VM configuration file. To enable udev to generate /dev/disk/by-id + + +.. _Release Notes_14.0.0_stable_newton_Deprecation Notes: + +Deprecation Notes +----------------- + +.. releasenotes/notes/deprecate-barbican-config-options-68ae65643ac41e2f.yaml @ b'899a140f32880cf33472f792e542ba0db15b4aac' + +- All barbican config options in Nova are now deprecated and may be removed as early as 15.0.0 release. All of these options are moved to the Castellan library. + +.. releasenotes/notes/deprecate-cells-driver-options-473893e4e87f95c2.yaml @ b'579c98a2eba26d65031385e6e46bda96e2f5131d' + +- The cells.driver configuration option is now deprecated and + will be removed at Ocata cycle. + +.. releasenotes/notes/deprecate-config-image-file-url-46c20999756afce0.yaml @ b'9931ef9ca23dfaba3fc69d1e0f0d1913e4236009' + +- The feature to download *Glance* images via file transfer instead of HTTP is now deprecated and may be removed as early as the 15.0.0 release. The config options ``filesystems`` in the section ``image_file_url`` are affected as well as the derived sections ``image_file_url:<list entry name>`` and their config options ``id`` and ``mountpoint``. + +.. releasenotes/notes/deprecate-config-s3-image-adb7c86c9b9220a5.yaml @ b'be86b27e020438566da9e05516654b5a2aea47ab' + +- As mentioned in the release notes of the Mitaka release (version 13.0.0), the EC2API support was fully removed. The *s3* image service related config options were still there but weren't used anywhere in the code since Mitaka. These are now deprecated and may be removed as early as the 15.0.0 release. This affects ``image_decryption_dir``, ``s3_host``, ``s3_port``, ``s3_access_key``, ``s3_secret_key``, ``s3_use_ssl``, ``s3_affix_tenant``. + +.. releasenotes/notes/deprecate-default-flavor-6c144f67f8032dfa.yaml @ b'b7660e0d7bba3c4d0aaf22e7235f2643109477d2' + +- The ``default_flavor`` config option is now deprecated and may be removed as early as the 15.0.0 release. It is an option which was only relevant for the deprecated EC2 API and is not used in the Nova API. + +.. releasenotes/notes/deprecate-fatal-exception-format-errors-a5d2bf64e3404c39.yaml @ b'6919b25ce0b9ae780074c6e2efe5c4b9fdead8c9' + +- The ``fatal_exception_format_errors`` config option is now deprecated and may be removed as early as the 15.0.0 release. It is an option which was only relevant for Nova internal testing purposes to ensure that errors in formatted exception messages got detected. + +.. releasenotes/notes/deprecate-image-cache-checksumming-80e52279881ebc71.yaml @ b'2c389ccc8c266175a71a29358bec7fe219e64fe0' + +- The ``image_info_filename_pattern``, ``checksum_base_images``, and ``checksum_interval_seconds`` options have been deprecated in the ``[libvirt]`` config section. They are no longer used. Any value given will be ignored. + +.. releasenotes/notes/deprecate-nova-manage-network-commands-212726e67bffdfc4.yaml @ b'b82b987b76f8d67b058a7c902d1124a3d16f63f5' + +- The following nova-manage commands are deprecated for removal in the + Nova 15.0.0 Ocata release: + + * nova-maange account scrub + * nova-manage fixed * + * nova-manage floating * + * nova-manage network * + * nova-manage project scrub + * nova-manage vpn * + + These commands only work with nova-network which is itself deprecated in + favor of Neutron. + +.. releasenotes/notes/deprecate-nova-manage-vm-list-571162f55173cccc.yaml @ b'5a5b06fb24fc6e392eb5381f1348e475f1302e1e' + +- The ``nova-manage vm list`` command is deprecated and will be removed in the 15.0.0 Ocata release. Use the ``nova list`` command from python-novaclient instead. + +.. releasenotes/notes/deprecate-old-auth-parameters-948d70045335b312.yaml @ b'2ea2399ec3e4b976beadfbcd1cab78b94382eca3' + +- The auth parameters `admin_username`, `admin_password`, `admin_tenant_name` and `admin_url` of the [ironic] config option group are now deprecated and will be removed in a future release. Using these parameters will log a warning. Please use `username`, `password`, `project_id` (or `project_name`) and `auth_url` instead. If you are using Keystone v3 API, please note that the name uniqueness for project and user only holds inside the same hierarchy level, so you must also specify domain information for user (i.e. `user_domain_id` or `user_domain_name`) and for project, if you are using `project_name` (i.e. `project_domain_id` or `project_domain_name`). + +.. releasenotes/notes/deprecate-snapshot-name-template-46966b0f5e6cabeb.yaml @ b'aeee4547b80013564e634cb7c1bde63f3c55d1f1' + +- The config option ``snapshot_name_template`` in the ``DEFAULT`` group + is now deprecated and may be removed as early as the 15.0.0 release. + The code which used this option isn't used anymore since late 2012. + +.. releasenotes/notes/deprecate_nova_all-eee03c2b0e944699.yaml @ b'5f996d4786c11a587364cfa9a6acf5922f5245a6' + +- The ``nova-all`` binary is deprecated. This was an all in one binary for nova services used for testing in the early days of OpenStack, but was never intended for real use. + +.. releasenotes/notes/deprecate_nova_network-093e937dcdb7fc57.yaml @ b'7d5fc486823117ba7a0a9005142ef87059ef74cd' + +- Nova network is now deprecated. Based on the results of the current OpenStack User Survey less than 10% of our users remain on Nova network. This is the signal that it is time migrate to Neutron. No new features will be added to Nova network, and bugs will only be fixed on a case by case basis. + +.. releasenotes/notes/deprecate_os_cert-f0aa07bab1a229aa.yaml @ b'5afc8e5745fff1caa31aeb23aae25e30819cd736' + +- The ``/os-certificates`` API is deprecated, as well as the ``nova-cert`` service which powers it. The related config option ``cert_topic`` is also now marked for deprecation and may be removed as early as 15.0.0 Ocata release. This is a vestigial part of the Nova API that existed only for EC2 support, which is now maintained out of tree. It does not interact with any of the rest of nova, and should not just be used as a certificates as a service, which is all it is currently good for. + +.. releasenotes/notes/deprecates-proxy-apis-5e11d7c4ae5227d2.yaml @ b'4a7deee95f70aed22e64a1f1ecbfe2e31c14a19f' + +- All the APIs which proxy to other services were deprecated in this API + version. Those APIs will return 404 on Microversion 2.36 or higher. The API + user should use native API as instead of using those pure proxy for other + REST APIs. The quotas and limits related to network resources 'fixed_ips', + 'floating ips', 'security_groups', 'security_group_rules', 'networks' are + filtered out of os-quotas and limit APIs respectively and those quotas + should be managed through OpenStack network service. For using + nova-network, you only can use API and manage quotas under Microversion + '2.36'. The 'os-fping' API was deprecated also, this API is only related to + nova-network and depend on the deployment. The deprecated APIs are as + below: + + - /images + - /os-networks + - /os-fixed-ips + - /os-floating-ips + - /os-floating-ips-bulk + - /os-floating-ip-pools + - /os-floating-ip-dns + - /os-security-groups + - /os-security-group-rules + - /os-security-group-default-rules + - /os-volumes + - /os-snapshots + - /os-baremetal-nodes + - /os-fping + +.. releasenotes/notes/pointer-model-b4a1828c43e8d523.yaml @ b'ed6a82ee227acd0c3d4294e8a868fe6b7f7b313f' + +- Nova option 'use_usb_tablet' will be deprecated in favor of the global 'pointer_model'. + +.. releasenotes/notes/quota-driver-is-deprecated-a915edf8777f3ddb.yaml @ b'430638888c987a99e537e2ac956087a7310ecdc6' + +- The quota_driver configuration option is now deprecated and will be removed in a subsequent release. + + +.. _Release Notes_14.0.0_stable_newton_Security Issues: + +Security Issues +--------------- + +.. releasenotes/notes/apply-limits-to-qemu-img-8813f7a333ebdf69.yaml @ b'068d851561addfefb2b812d91dc2011077cb6e1d' + +- The qemu-img tool now has resource limits applied which prevent it from using more than 1GB of address space or more than 2 seconds of CPU time. This provides protection against denial of service attacks from maliciously crafted or corrupted disk images. + + +.. _Release Notes_14.0.0_stable_newton_Bug Fixes: + +Bug Fixes +--------- + +.. releasenotes/notes/list-invalid-status-af07af378728bc57.yaml @ b'984d00919ffe5ac5d41edb194740f6f33ca3e78f' + +- Corrected response for the case where an invalid status value is passed as a filter to the list servers API call. As there are sufficient statuses defined already, any invalid status should not be accepted. As of microversion 2.38, the API will return 400 HTTPBadRequest if an invalid status is passed to list servers API for both admin as well as non admin user. + +.. releasenotes/notes/list-server-bad-status-fix-7db504b38c8d732f.yaml @ b'ee4d69e28dfb3d4764186d0c0212d53c99bda3ca' + +- Fixed bug #1579706: "Listing nova instances with invalid status raises 500 + InternalServerError for admin user". Now passing an invalid status as a + filter will return an empty list. A subsequent patch will then correct this + to raise a 400 Bad Request when an invalid status is received. + +.. releasenotes/notes/multiqueue-on-tap-interface-2c9e1504fa4590f4.yaml @ b'b9303e67640ac2052c0a79189b29f60bde6b8fdc' + +- When instantiating an instance based on an image with the metadata + hw_vif_multiqueue_enabled=true, if flavor.vcpus is less than the limit + of the number of queues on a tap interface in the kernel, nova uses + flavor.vcpus as the number of queues. if not, nova uses the limit. + The limits are as follows: + + * kernels prior to 3.0: 1 + * kernels 3.x: 8 + * kernels 4.x: 256 + +.. releasenotes/notes/set_migration_status_to_error_on_live-migration_failure-d1f6f29ceafdd598.yaml @ b'6641852b8ed63bad0917d355f9563f5e9e9bbf75' + +- 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. + +.. releasenotes/notes/vhost-user-mtu-23d0af36a8adfa56.yaml @ b'adf7ba61dd73fe4bfffa20295be9a4b1006a1fe6' + +- When plugging virtual interfaces of type vhost-user the MTU value will not be applied to the interface by nova. vhost-user ports exist only in userspace and are not backed by kernel netdevs, for this reason it is not possible to set the mtu on a vhost-user interface using standard tools such as ifconfig or ip link. + + +.. _Release Notes_14.0.0_stable_newton_Other Notes: + +Other Notes +----------- + +.. releasenotes/notes/empty-sample-policy-abfb7d467d2ebd4c.yaml @ b'625f203610f17f2b968e5f78a46d398953637174' + +- The API policy defaults are now defined in code like configuration options. + Because of this, the sample policy.json file that is shipped with Nova is + empty and should only be necessary if you want to override the API policy + from the defaults in the code. To generate the policy file you can run:: + + oslopolicy-sample-generator --config-file=etc/nova/nova-policy-generator.conf + +.. releasenotes/notes/network-allocate-retries-min-a5288476b11bfe55.yaml @ b'883bae38c329abe4a54fba88b642c20a11529193' + +- network_allocate_retries config param now allows only + positive integer values or 0. + +.. releasenotes/notes/remove-api-rate-limit-option-91a17e057081381a.yaml @ b'3dd9d05d0e5facd8704e056c6af4c73847cedbe4' + +- The ``api_rate_limit`` configuration option has been removed. The option was disabled by default back in the Havana release since it's effectively broken for more than one API worker. It has been removed because the legacy v2 API code that was using it has also been removed. + +.. releasenotes/notes/remove-default-flavors-5238c2d9673c61e2.yaml @ b'1a1a41bdbe0dc16ca594236925e77ce99f432b9d' + +- The default flavors that nova has previously had are no longer created as part of the first database migration. New deployments will need to create appropriate flavors before first use. + +.. releasenotes/notes/remove-unused-config-opt-fake-call-37a56f6ec15f7d90.yaml @ b'b8fea0351895f468d0b5e72087adde5e8a788ab1' + +- The network configuration option 'fake_call' has been removed. It hasn't been used for several cycles, and has no effect on any code, so there should be no impact. + +.. releasenotes/notes/remove-unused-config-opt-iqn_prefix-defb44120dae93e3.yaml @ b'9c238c113008df459b7e24bb32f618a7e9386a05' + +- The XenServer configuration option 'iqn_prefix' has been removed. It was not used anywhere and has no effect on any code, so there should be no impact. + +.. releasenotes/notes/rm_import_object_ns-5344a390b0af465e.yaml @ b'ed308b99ca3c2e92ce8def4e8fe1ba1648f9a68d' + +- Virt drivers are no longer loaded with the import_object_ns function, which means that only virt drivers in the nova.virt namespace can be loaded. + +.. releasenotes/notes/sync_power_state_pool_size-81d2d142bffa055b.yaml @ b'386812e287198cd2d340d273753ef06075f7c05d' + +- New configuration option sync_power_state_pool_size has been added to set the number of greenthreads available for use to sync power states. Default value (1000) matches the previous implicit default value provided by Greenpool. This option can be used to reduce the number of concurrent requests made to the hypervisor or system with real instance power states for performance reasons. + + |