Newton Series Release Notes

Newton Series Release Notes

9.7.0-3

New Features

  • Add the ability to set reserved_huge_pages on nova-computes via a string or a list of strings.

  • Added group parameter to configure qemu.conf

9.7.0

New Features

  • Added nova patching configuration parameters. These parameters are available in nova.conf, but are not configurable using puppet-nova. The monkey patching parameters allow patching a decorator for all functions in specified modules. This change create patch/config.pp file to make these parameters configurable.

  • The nova::api::pci_alias and nova::compute::pci_passthrough params now accept an array of hashes. A valid JSON encoded array of objects is also acceptable.

Deprecation Notes

  • Invalid JSON was previously accepted for the nova::api::pci_alias and nova::compute::pci_passthrough parameters. This format is now deprecated and may not be accepted in future.

9.6.0

New Features

  • Nova Placement API deployment in WSGI with Apache by using nova::wsgi::apache_placement.

  • Keystone resources support for Nova Placement API by using nova::keystone::auth_placement.

  • Allow to configure [placement] section in nova.conf by using nova::placement.

9.5.2

New Features

  • Add libvirt_hw_machine_type parameter to nova::compute::libvirt to allow setting the libvirt/hw_machine_type option in nova.conf

9.5.1

New Features

  • allow_resize_to_same_host can now be set in nova-api. For ephemeral nodes, this needs to only be set in nova-api and so including the other classes is overkill.

  • A new nova::compute::libvirt::qemu class has been added with the initial purpose of configuring the max_files and max_processes limits in qemu.conf

  • Add a new parameter, “nova::migration::libvirt::listen_address”, to control the address/interface that libvirtd binds to.

  • Add support for libvirt live-migration over SSH including the ability to override all libvirt options applicable to the SSH transport. For more info see https://libvirt.org/remote.html#Remote_URI_reference. Adds new parameter “nova::migration::libvirt::transport” Adds new parameter “nova::migration::libvirt::client_user” Adds new parameter “nova::migration::libvirt::client_port” Adds new parameter “nova::migration::libvirt::client_extraparams”

  • Case insensitive ‘libvirt_rbd_secret_uuid’ option for nova compute rbd.

Known Issues

  • Using nova::wsgi::apache_api to deploy Nova in WSGI with Apache is not recommended by Nova team. See bug 1661360.

Deprecation Notes

  • The “nova::migration::libvirt::use_tls” parameter is deprecated by the “nova::migration::libvirt::transport” parameter.

Bug Fixes

  • Fixes bug 1660099 so we don’t restrict vncserver_listen to be binded on 0.0.0.0, which has been wrong for long time. Nova allows to bind on any IP and live migration will be supported.

9.5.0

New Features

  • Adds the enable_new_services config parameter to nova conductor

  • Adds the resize_confirm_window parameter to nova configuration for compute service.

  • Adds the resume_guests_state_on_host_boot config parameter to nova compute

  • Passes parameter to keystone authtoken define to manage python-memcache package install.

  • All parameters from xenserver config have been added to class definition.

Upgrade Notes

  • The default value for nova::compute::libvirt::libvirt_cpu_mode when nova::compute::libvirt::libvirt_virt_type is set to ‘qemu’ has been changed from ‘host-model’ to ‘none’. The Nova gate does not really test the ‘host-model’ option in their CI, but ‘none’ due to Devstack configuration, and it is known to create issues with QEMU 2.6 (see https://bugzilla.redhat.com/show_bug.cgi?id=1404627).

Deprecation Notes

  • Following parameters gets deprecated xenapi_connection_url, xenapi_connection_username, xenapi_connection_password.

9.2.0

New Features

  • Adds support to configure the new vendordata plugins for nova.

  • Configure keystonemiddleware in a consistent way with all options required for Keystone v3.

  • Allow to configure Key Manager api class parameter to communicate with Barbican. If Barbican is enabled, cryptsetup will be deployed on compute nodes.

Upgrade Notes

  • Add MultiStrOpt for scheduler_available_filters parameter.

Deprecation Notes

  • nova::api::admin_tenant_name is deprecated in favor of nova::keystone::authtoken::project_name.

  • nova::api::admin_user is deprecated in favor of nova::keystone::authtoken::username.

  • nova::api::admin_password is deprecated in favor of nova::keystone::authtoken::password.

  • nova::api::identity_uri is deprecated in favor of nova::keystone::authtoken::auth_url.

  • nova::api::auth_version is deprecated in favor of nova::keystone::authtoken::auth_version

  • nova::api::auth_uri is deprecated in favor of nova::keystone::authtoken::auth_uri

  • nova::memcached_servers is deprecated in favor of nova::keystone::authtoken::memcached_servers.

  • The cells.driver configuration option is now deprecated and will be removed at Ocata cycle.

  • The following parameters moved from ::nova::scheduler::filter to ::nova so they can be configured at top level - cpu_allocation_ratio, ram_allocation_ratio and disk_allocation_ratio

  • quota_driver parameter was deprecated in Nova, so we also deprecate it in puppet-nova.

  • The ‘manager’ option in [cells] group was deprecated in Mitaka and now it is removed completely in newton. There is no impact.

  • The security_group_api option that was deprecated in Mitaka has been removed in Newton.

Bug Fixes

  • Fix vmware section name, should be vmware and not VMWARE.

  • Add missing insecure, ca_file and datastore_regex parameters

9.1.0

New Features

  • Add ability to configure cache parameters

  • Add oslo.messaging transport_url parameters via puppet-oslo resource

  • Enable puppet-nova to deploy micro-services where libvirt & nova-compute are separated. With a new class, nova::compute::libvirt::services, we’re now able to manage libvirt packages & services outside nova-compute. This class is included by default in nova::compute::libvirt for backward compatibility but can be disabled if you deploy compute services on containers.

Deprecation Notes

  • The live_migration_flag and block_migration_flag parameters are deprecated.

  • 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.

Bug Fixes

  • The keystone auth class has been updated to provide a default service_name to allow a user to specify a custom auth_name that may not contain the name of the service.

Other Notes

  • Switch nova upgrade parameters to $::os_service_default fact. This change will help to reduce lines of code and also by default all values have ‘undef’ value and can be easily switched to common fact.

9.0.0

New Features

  • Added flavor provider and type for creating and deleting because nova no longer comes with flavors by default. The provider can be used to add/delete flavors and manage flavor properties.

  • Add live_migration_tunnelled option in order to Whether to use tunnelled migration, where migration data is transported over the libvirtd connection.

  • Make the nova_api database creation default to “true” since it is now required in Mitaka

  • Add support for oslo_messaging_amqp backend via puppet-oslo resource

  • Using OpenStack client for Nova providers

  • Align nova/neutron configuration for Keystone v3.

  • Add WSGI support for Nova API with Apache.

  • Add support for CPU pinning.

  • Add support for IPv6 in VNC proxy.

  • Add support for new Nova API database.

  • Allow to enable/disable IPv6 support.

  • Add hooks for external install & svc management.

  • Extend quota support.

  • Nova Cells support for nova_aggregate provider.

  • Add missing parameters in nova.conf for SSL

  • Nova service management. Ability to remove services left behind by Nova after disabling or decommissioning a host. Provider can delete all (default) or an array of specified service names.

  • Support of PyMySQL driver for MySQL backend.

  • Add ability to manage security groups from a Puppet provider.

  • Configure oslo related sections using puppet-oslo module. Database, logging, policy and notification parameters are configured from oslo defines now.

  • Use oslo module for messaging (rabbit) configuration. Messaging related parameters were switched to $::os_service_default. Docs string for parameter were updated according to oslo module.

  • Release notes are no longer maintained by hand, we now use the reno tool to manage them.

Upgrade Notes

  • When upgrading, be aware that the default value of sync_db_api has changed from “false” to “true” for this database.

  • enabled_apis in api.pp now only accepts list values.

  • Change default values for scheduler_driver and scheduler_host_manager to match defaults values in Nova, so now we use entrypoints.

  • Change default Nova API endpoints from v2 to v2.1. v2 was deprecated in Liberty and will be removed in Newton.

Deprecation Notes

  • network_api_class parameter from nova::network::neutron doesn’t take effect anymore and will be removed in future. Set use_neutron always to true as nova::network::neutron is a Neutron-specific class

  • osapi_v3 parameter is deprecated, has no effect and will be removed in a future release..

  • In nova::keystone::auth, all parameters related to v3 endpoint are deprecated and have no effect, since we bumped the default version to v2.1 that is what v3 started out as. They’ll be dropped after Newton cycle.

  • listen parameter from nova::compute::serial has no effect anymore and will be removed in future.

  • Deprecating the management of rabbitmq resources. It will be dropped in the next release.

  • Preparation for default endpoint names rename. In a future release, service_name parameter default value will be changed to “Compute Service”.

  • Deprecate nova::utilities.

  • Remove EC2 support.

  • Drop use of deprecated neutron auth options.

  • Use identity_uri and auth_uri by default.

  • Remove installation of pm-utils.

  • Move availability zone parameters to a new class, with deprecation support. Parameters affected are default_availability_zone, default_schedule_zone, and internal_service_availability_zone.

  • volume_api_class, use_local and security_group_api parameters are deprecated. They have no effect and will be removed in a future release.

  • neutron_auth_plugin is deprecated but is still usable. It will be removed in a future release.

  • libvirt remove_unused_kernels, cells manager are deprecated. They have no effect and will be removed in a future release.

  • DEFAULT network_device_mtu/compute_manager are deprecated. Only compute_manager has effect, because Ironic use. They will be removed in a future release.

  • nova-network deployment is deprecated, since Nova deprecated it during Newton cycle. Its support will be removed in the future.

  • Remove QPID messaging support. Qpid messaging driver is removed from oslo.messaging so we won’t support anymore.

  • Drop all qpid references in code since it’s been deprecated already.

  • verbose option is now deprecated for removal, the parameter has no effect.

Bug Fixes

  • Manage virtlockd and virtlogd services as part of the nova::compute::libvirt as they are needed for nova. The virtlockd service is currently managed for RedHat and Ubuntu but skipped under Debian. The virtlogd service is Ubuntu specific but can be managed if the virtlog_service_name is provided to the nova::compute::libvirt class.

Other Notes

  • Drop all Qpid support, it was removed from Oslo in Mitaka.

  • Remove nova::utilities class and tests.

  • Rewrite nova_network provider with using only nova client.

  • Stop installing python-numpy for vncproxy. In the context of noVNC, numpy adds little performance according to websockify maintainer.

  • Add support of OpenStack client for Nova providers.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.