Jump to: navigation, search

Difference between revisions of "ReleaseNotes/Kilo"

(Upgrade Notes)
(Known Issues)
Line 74: Line 74:
 
=== Known Issues ===
 
=== Known Issues ===
  
* TBD
+
* Evacuate recovery code has the potential to destroy data. On nova-compute startup, instances reported by the hypervisor are examined to see if they have moved (i.e. been evacuated) from the current host during the outage. If the determination is made that they were, then they are destroyed locally. This has the potential to choose incorrectly and destroy instances unexpectedly. On libvirt-like nodes, this can be triggered by changing the system hostname. On vmware-like nodes, this can be triggered by attempting to manage a single vcenter deployment from two different hosts (with different hostnames). This will be fixed properly in Liberty, but for now deployments that wish to disable this behavior as a preventive measure can set workarounds.destroy_after_evacuate=False.
  
 
=== Upgrade Notes ===
 
=== Upgrade Notes ===

Revision as of 14:33, 16 March 2015

Warning.svg Release Under Development

This release of OpenStack is under development and has yet to be completed. It will be released on April 30, 2015

The information on this page may not accurately reflect the state of release at the current point in time.

OpenStack 2015.1 (Kilo) Release Notes

General Upgrade Notes

  • TBD

OpenStack Object Storage (Swift)

Key New Features

Known Issues

None

Upgrade Notes

OpenStack Compute (Nova)

Key New Features

Upgrade Support

  • TBD

Cells v2

  • TBD
  • new 'nova-manage api_db sync' and 'nova-manage api_db version' commands for working with the new api database for cells.

Compute Drivers

Hyper-V
  • TBD
Libvirt (KVM)
  • TBD
VMware
  • TBD
XenServer
  • TBD
Ironic

API

  • TBD

Scheduler

  • TBD

Other Features

  • TBD

Known Issues

  • Evacuate recovery code has the potential to destroy data. On nova-compute startup, instances reported by the hypervisor are examined to see if they have moved (i.e. been evacuated) from the current host during the outage. If the determination is made that they were, then they are destroyed locally. This has the potential to choose incorrectly and destroy instances unexpectedly. On libvirt-like nodes, this can be triggered by changing the system hostname. On vmware-like nodes, this can be triggered by attempting to manage a single vcenter deployment from two different hosts (with different hostnames). This will be fixed properly in Liberty, but for now deployments that wish to disable this behavior as a preventive measure can set workarounds.destroy_after_evacuate=False.

Upgrade Notes

  • TBD

OpenStack Image Service (Glance)

Key New Features

  • TBD

Known Issues

Upgrade Notes

OpenStack Dashboard (Horizon)

Key New Features

  • TBD

Known Issues

Upgrade Notes

OpenStack Identity (Keystone)

Key New Features

  • TBD

Known Issues

  • TBD

Upgrade Notes

  • XML support in Keystone has been removed as of Kilo. When upgrading from Juno to Kilo, it is recommended that references to XML and XmlBodyMiddleware be removed from the Keystone Paste configuration. This includes removing the XML middleware filters and there references from the public_api, admin_api, api_v3, public_version_api, admin_version_api and any other pipelines that may contain the XML filters.

OpenStack Network Service (Neutron)

Key New Features

Known Issues

None yet.

Upgrade Notes

From Havana, Neutron no longer supported an explicit lease database (https://bugs.launchpad.net/bugs/1202392). This left dead code including unused environment variable. In order to remove the dead code (https://review.openstack.org/#/c/152398/), a change to the dhcp.filter is required, so that line:

dnsmasq: EnvFilter, dnsmasq, root, NEUTRON_NETWORK_ID=

Be replaced by:

dnsmasq: CommandFilter, dnsmasq, root

After advanced services were split into separate packages and received their own service configuration files (specifically, etc/neutron/neutron_lbaas.conf, etc/neutron/neutron_fwaas.conf and etc/neutron/neutron_vpnaas.conf), active service provider configuration can be different after upgrade (specifically, default load balancer (haproxy) and vpn (openswan) providers can be enabled for you even though you previously disabled them in neutron.conf). Please make sure you review configuration after upgrade so that it reflects the desired state of service providers.

Note: this will have no effect if the related service plugin is not loaded in neutron.conf.


OpenStack Block Storage (Cinder)

Key New Features

Known Issues

None yet

Upgrade Notes

  • The 'host' config option for multiple-storage backends in cinder.conf is renamed to 'backend_host' in order to avoid a naming conflict with the 'host' to locate redis. If you use this option, please ensure your configuration files are updated.
  • The openstack.common.middleware has graduated to oslo.middleware support. When upgrading from Juno to Kilo, it is needed that references to openstack.common.middleware.RequestIdMiddleware be changed to oslo.middleware.RequestId from the Cinder Paste configuration. This includes changing the middleware filter and it's references to oslo.middleware.RequestId.

OpenStack Telemetry (Ceilometer)

Key New Features

  • TBD

Known Issues

  • TBD

Upgrade Notes

OpenStack Orchestration (Heat)

Key New Features

Known Issues

None yet

Upgrade Notes

None yet

OpenStack Database service (Trove)

Key New Features

Known Issues

None yet

Upgrade Notes

None yet

OpenStack Documentation

Key New Features

  • TBD

Known Issues

Upgrade Notes

None yet