Jump to: navigation, search

Difference between revisions of "ReleaseNotes/Liberty"

(Deprecated and Removed Plugins and Drivers)
Line 29: Line 29:
* The metaplugin is removed in the Liberty release.
* The metaplugin is removed in the Liberty release.
* The IBM SDN-VE monolithic plugin is removed in the Liberty release.
* The IBM SDN-VE monolithic plugin is removed in the Liberty release.
* The Cisco N1kV monolithic plugin is removed in the Liberty release (replaced by the ML2 mechanism driver).
=== Deprecated Features ===
=== Deprecated Features ===

Revision as of 21:11, 28 September 2015

Other languages:
Deutsch • ‎English • ‎日本語 • ‎한국어 • ‎中文(简体)‎ • ‎中文(台灣)‎

OpenStack Liberty Release Notes

OpenStack Networking (Neutron)

New Features

  • Neutron now supports IPv6 Prefix Delegation for the automatic assignment of CIDRs to IPv6 subnets. For more information on the usage and configuration of this feature, see the OpenStack Networking Guide.
  • Neutron now exposes a QoS API, initially offering bandwidth limitation on the port level. The API, CLI, configuration and additional information may be found here [1].
  • Router high availability (L3 HA / VRRP) now works when layer 2 population (l2pop) is enabled [2].
  • VPNaaS reference drivers now work with HA routers.
  • Networks used for VRRP traffic for HA routers may now be configured to use a specific segmentation type or physical network tag [3].
  • The OVS agent may now be restarted without affecting data plane connectivity.
  • Neutron now offers role base access control for networks [4].
  • LBaaS V2 reference driver is now based on Octavia, an operator grade scalable, reliable Load Balancer platform
  • LBaaS V2 API is no longer experimental. It is now stable.
  • Neutron now supports a way that an agent can start without selectable for auto-scheduling but manual-scheduling available so that a deployer can test an agent manually [5].
  • Neutron now has a pluggable IP address management framework, enabling the use of alternate or third-party IPAM. The original, non-pluggable version of IPAM is enabled by default.

Deprecated and Removed Plugins and Drivers

  • The metaplugin is removed in the Liberty release.
  • The IBM SDN-VE monolithic plugin is removed in the Liberty release.
  • The Cisco N1kV monolithic plugin is removed in the Liberty release (replaced by the ML2 mechanism driver).

Deprecated Features

  • The FWaaS API is marked as experimental for Liberty. Further, the current API will be removed in Mitaka and replaced with a new FWaaS API which the team is in the process of developing.
  • The LBaaS V1 API is marked as deprecated and is planned to be removed in some future release. Going forward the LBaaS V2 API should be used.

Performance Considerations

  • The stock Trusty Tahr kernel (3.13) shows linear performance degradation when running "ip netns exec" as the number of namespaces increases. In cases where scale is important, a later version kernel (e.g. 3.19) should be used.
  • Creating Neutron-LBaaS load balancers in environments without hardware virtualization may be slow when using the Octavia driver. This is due to QEMU using the TCG accelerator versus the KVM accelerator in environments without hardware virtualization available. We recommend enabling hardware virtualization on your compute nodes or enabling nested virtualization when using the Octavia driver inside a virtual environment. See the following link for details on setting up nested virtualization for DevStack running inside KVM: http://docs.openstack.org/developer/devstack/guides/devstack-with-nested-kvm.html

OpenStack Compute (Nova)

Upgrade Notes

  • If you are coming from Kilo stable, please make sure you have fully upgraded to the latest release of that lineage before deploying Liberty. Due to bug https://bugs.launchpad.net/nova/+bug/1474074 versions of Kilo from before the fix will be problematic when talking to Liberty nodes.
  • Allocation ratios for RAM and CPU are now defined within the nova-compute service (so per compute node), thus need to be also provided for the scheduler service. Depending on whether a compute node is running Kilo or Liberty, the allocation ratios will behave differently : if the compute node is running Kilo then the CPU and RAM allocation ratios for that compute node will be the ones defaulted in the controller's nova.conf file.Or, if the compute node is Liberty then you'll be able to set a per-compute allocation ratio for both CPU and RAM. In order to leave the operator providing the allocation ratios to all the compute nodes, the default allocation ratio will be set in nova.conf to 0.0 (even for the controller). That doesn't mean that allocation ratios will actually be 0.0, just that the operator needs to provide those before the next release (ie. Mitaka). To be clear, the default allocation ratios are still 16.0 for cpu_allocation_ratio and 1.5 for ram_allocation_ratio.
  • nova-compute should be upgraded to Liberty code before upgrading Neutron services per the new "network-vif-deleted" event: https://review.openstack.org/#/c/187871/
  • Rootwrap filters must be updated after release to add the touch command.
    • There is a race condition between imagebackend and imagecache mentioned in the Launchpad Bug 1256838.
    • In this case if base image is deleted by ImageCacheManager while imagebackend is copying the image to instance path, then instance goes in to error state.
    • In order to resolve this issue, there is a need to add 'touch' command in compute.filters along with the change https://review.openstack.org/#/c/217579/.
    • In case of a race condition 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. To resolve this error we need to update the base file access time with root user privileges using touch command.
  • The DiskFilter is now part of the scheduler_default_filters in Liberty per https://review.openstack.org/#/c/207942/ .
  • Per https://review.openstack.org/#/c/103916/ you can now only map one vCenter cluster to a single nova-compute node.


  • The novaclient.v1_1 module has been deprecated [[6]][[7]] since 2.21.0 and we are going to remove it in the first python-novaclient release in Mitaka.
  • Method `novaclient.client.get_client_class` is deprecated [[8]] since 2.29.0 and we are going to remove it in Mitaka.

OpenStack Telemetry (Ceilometer)

Key New Features

Upgrade Notes

  • The name of some middleware used by ceilometer changed in a backwards-incompatible way. Before upgrading, edit the paste.ini file for ceilometer to change "oslo.middleware" to "oslo_middleware". For example using sed -ri 's/oslo\.middleware/oslo_middleware/' api_paste.ini

OpenStack Identity (Keystone)

Key New Features

Release notes based on blueprints and wishlist bugs are being collaboratively drafted on Etherpad. The version presented below was updated by samueldmq and this note will be removed once it's reviewed by core-reviewers.

  • Keystone now supports tokenless authorization with X.509 SSL client certificate;
  • Configuring per-Identity Provider WebSSO is now supported;
  • openstack_user_domain and openstack_project_domain attributes were added to SAML assertion in order to map user and project domains, respectively;
  • Credentials list call can now have its results filtered by credential type;
  • Domain name information is now available to be used in policy rules with the attribute domain_name;
  • Keystone now shows available choices for string configuration options;
  • Support was improved for out-of-tree drivers by defining stable Driver Interfaces;
  • Several features were hardened, including Fernet tokens, Federation, Domain specific configurations from database and Role Assignments.

Upgrade Notes

  • The EC2 token middleware, deprecated in Juno, is no longer available;
  • The compute_port configuration option, deprecated in Juno, is no longer available;
  • External authentication plugins, deprecated in Icehouse, are no longer available.


  • Using LDAP as the resource backend, i.e for projects and domains, is now deprecated and will be removed in the Mitaka release;
  • Not specifying a domain during a create user, group or project call, which relied on falling back to the default domain, is now deprecated and will be removed in the N release.