Train Series Release Notes

15.6.0

New Features

  • Now puppet-nova supports configuration of libvirtd-tls.socket and libvirtd-tcp.socket, which should be enabled according to the transport protocol when libvirt is running under systemd. This feature is enforced since libvirt v5.8.

  • Add parameter query_placement_for_availability_zone that allows the scheduler to look up a host aggregate with metadata key of availability zone set to the value provided by incoming request, and request result from placement be limited to that aggregate. Default value for this parameter is false.

15.5.0

New Features

  • Adds –all-cells to the archive command based on an empty_table boolean flag. If true, it will run in archive command on all configured cells.

  • Adds –before to the archive command based on age parameter provided. If added, it will run with –before date –date=’today - age days’ +\%F

  • Add new parameter [compute] cpu_dedicated_set to specify list or range of physical CPU cores to reserve to be used for allocating PCPU resources to virtual machine processes. Defaults to $::os_service_default.

  • Add parameter enable_isolated_aggregate_filtering which allows the scheduler to restrict hosts in aggregates based on matching required traits in the aggregate metadata and the instance flavor/image. Default value for this parameter is False.

  • Add parameter placement_aggregate_required_for_tenants which controls whether or not a tenant with no aggregate affinity will be allowed to schedule to any available node, when limit_tenants_to_placement_aggregate is set to True. Default value for this parameter is False.

Deprecation Notes

  • The vcpu_pin_set parameter is deprecated and superseded by cpu_shared_set and cpu_dedicated_set parameters, where cpu_shared_set and cpu_dedicated_set is used to define list or range of VCPU and PCPU resources for virtual machine instances respectively. When used vcpu_pin_set can not be defined with cpu_dedicated_set parameter.

  • The nova::ironic::common::api_endpoint is deprecated and has no effect, because the corresponding [ironic]api_endpoint was removed in Nova. The nova::ironic::common::endpoint_override should be used instead.

15.2.0

New Features

  • New hieradata, nova::keystone::authtoken::service_token_roles, is introduced so that specific role can be assigned to the service user who can use service token feature.

  • New hieradata, nova::keystone::roles is introduced to configure customized role for nova user in keystone identity.

  • Adds log_filters parameter to nova::compute::libvirt. Defines a filter to select a different logging level for a given category log outputs, as specified in https://libvirt.org/logging.html . Default undef

  • Add tls_priority parameter to nova::compute::libvirt class to override the compile time default TLS priority string. The default is usually “NORMAL” unless overridden at build time. Only set this if it is desired for libvirt to deviate from the global default settings.

  • Allow users to run the RabbitMQ heartbeat over a native python thread in the oslo.messaging RabbitMQ driver, by using the rabbit_heartbeat_in_pthread option in configuration.

  • New class, nova::keystone::service_user, is introduced to configure parameters to service token feature.

Upgrade Notes

  • The deprecated pki related options check_revocations_for_cached and hash_algorithms option has been removed.

15.1.0

New Features

  • Add support to configure [oslo_middleware]/max_request_body_size with $max_request_body_size.

  • memcache_socket_timeout is changed to float value.

  • nova::metadata::dhcp_domain has been added back to configure api/dhcp_domain. nova::network::neutron::dhcp_domain has been removed and the metadata version of the variable should be used instead.

  • Add parameter mem_stats_period_seconds to specify number of seconds to memory usage statistics period, zero or negative value mean to disable memory usage statistics.

  • Add parameter limit_tenants_to_placement_aggregate which allows to have tenant isolation with placement. It ensures hosts are in tenant-isolated host aggregate and availability zones will only be available to specific set of tenants.

  • Add parmeter query_placement_for_image_type_support that causes the scheduler to ask placement only for compute hosts that support the disk_format of the image used in the request.

Upgrade Notes

  • The neutron_enabled and install_bridge_utils parameters in nova::compute is deprecated and has no effect. The bridge-utils package is no longer maintained by using the install_bridge_utils parameter.

Deprecation Notes

  • The neutron_enabled parameter in nova::compute is deprecated, it had no effect except for in conjunction with install_bridge_utils which is also deprecated.

  • The install_bridge_utils parameter in nova::compute is deprecated and has no effect. The bridge-utils package is now not managed by the nova::compute class.

  • Deprecates oslo::middleware parameters enable_proxy_headers_parsing and max_request_body_size in ::nova::metadata. Use ::nova::api instead.

  • Removes deprecated neutron_metadata_proxy_shared_secret and metadata_cache_expiration parameter from nova::api class.

  • The deprecated vendordata* config option has been removed from api and metadata class. Use ::nova::vendordata instead.

Bug Fixes

  • enabled_apis won’t get set in nova::api when nova_metadata_wsgi_enabled == true. But the enabled_apis list get also modified for this case, so we need to move setting the config outside the conditional. Since the config is right now also set in nova::metadata this deprecates it in nova::metadata to only use nova::api.

  • enable_proxy_headers_parsing should not only be configurabe if !$nova_metadata_wsgi_enabled , Therefore it needs to be moved outside the condition. But at the moment enable_proxy_headers_parsing can also be set via ::nova::metadata which conficts. This change deprecates oslo::middleware related parameters enable_proxy_headers_parsing and max_request_body_size in ::nova::metadata. In future ::nova::api should be used instead.

15.0.0

New Features

  • Adds the cross_az_attach parameter to allow configuring attach between instance and volume in different availability zones.

  • Add the log_file option for logging.

  • The ca_file is now configurable for the TLS transport in nova’s live migration options for libvirt.

  • The crl_file is now configurable for the TLS transport in nova’s live migration options for libvirt.

  • Add parameter num_pcie_ports to specify the number of PCIe ports an instance will get. Libvirt allows a custom number of PCIe ports (pcie-root-port controllers) a target instance will get. Some will be used by default, rest will be available for hotplug use.

  • Add parameter live_migration_wait_for_vif_plug to whether to wait for network-vif-plugged events before starting guest transfer.

  • Indicates that the nova-metadata API service has been deployed per-cell, so that we can have better performance and data isolation in a multi-cell deployment. Users should consider the use of this configuration depending on how neutron is setup. If networks span cells, you might need to run nova-metadata API service globally. If your networks are segmented along cell boundaries, then you can run nova-metadata API service per cell. When running nova-metadata API service per cell, you should also configure each Neutron metadata-agent to point to the corresponding nova-metadata API service.

  • The libvirt driver allows passing different mount options to the nfs client. [libvirt]/nfs_mount_options, defaulting to <None>.

Upgrade Notes

  • The default value for nova::metadata::novajoin::api::project_name has been changed from ‘service’ to ‘services’.

  • The nova-consoleauth service is now deprecated and not deployed. This means the nova::consoleauth has no effect now and does not manage the package or service for consoleauth. Deployments should stop this service and remove the package if it’s deployed.

  • The deprecated cells v1 classes nova::cells, nova::manage::cells and the nova_cells resource is removed.

  • The following deprecated parameters in nova::quota has been removed. Please see the name in paranthesis for the new proper name.

    • quota_instances (now instances)

    • quota_cores (now cores)

    • quota_ram (now ram)

    • quota_floating_ips (now floating_ips)

    • quota_fixed_ips (now fixed_ips)

    • quota_metadata_items (now metadata_items)

    • quota_injected_files (now injected_files)

    • quota_injected_file_content_bytes (now injected_file_content_bytes)

    • quota_injected_file_path_length (now injected_file_path_length)

    • quota_security_groups (now security_groups)

    • quota_security_group_rules (now security_group_rules)

    • quota_key_pairs (now key_pairs)

    • quota_server_groups (now server_groups)

    • quota_server_group_members (now server_group_members)

  • The deprecated nova-network classes nova::network::bridge, nova::network::flat, nova::network::flatdhcp and nova::network::vlan classes is now removed.

  • The deprecated nova_network resource is now removed.

  • The deprecated class nova::compute::neutron is now removed.

  • The deprecated class nova::manage::network is now removed.

  • The deprecated parameter nova::use_ipv6 is now removed.

Deprecation Notes

  • The nova-consoleauth service is deprecated. The nova::consoleauth class has no effect now and will be removed in the next release.

  • The nova::upgrade_level_consoleauth parameter is deprecated, has no effect and will be removed in the next release.

  • database_idle_timeout is deprecated and will be removed in a future release. Please use database_connection_recycle_time instead.

Bug Fixes

  • Add cinder credentials in cinder section of nova conf to fix issue when reclaim_instance_interval > 0 and delete instance which booted from volume ‘delete_on_termination’ set as true. The volume status showing attached and in-use, even after instance deletion, since the admin context didn’t have any token info hence call to cinder api failed. In case when context is is_admin and without token,added cinder creds used to do authentication with user/project info to call cinder api. [Bug 1734025]