ReleaseNotes/Kilo

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)

Known Issues

None

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

• Add config drive support ( https://review.openstack.org/#/c/144792/ )

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

• After fully upgrading to kilo (i.e. all nodes are running kilo code), you should start a background migration of flavor information from its old home to its new home. Kilo conductor nodes will do this on the fly when necessary, but the rest of the idle data needs to be migrated in the the background. This is critical to complete before the Liberty release, where support for the old location will be dropped. Use "nova-manage migrate-flavor-data" to perform this transition.

OpenStack Image Service (Glance)

Key New Features

• TBD

OpenStack Dashboard (Horizon)

Key New Features

• TBD

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)

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.

• The default value of api_workers is now equal to the number of CPUs in the host. If you currently use the default, ensure you set api_workers to a reasonable number for your installation. (https://review.openstack.org/#/c/140493/)
• The neutron.allow_duplicate_networks config option is deprecated in Kilo and will be removed in Liberty where the default behavior will be to just allow multiple ports attached to an instance on the same network in Neutron. (https://review.openstack.org/163581)
• The linuxbridge agent now enables VXLAN by default (https://review.openstack.org/160826)
• neutron-ns-metadata-proxy can now be run as non-root (https://review.openstack.org/147437)

OpenStack Block Storage (Cinder)

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.

OpenStack Telemetry (Ceilometer)

Key New Features

• TBD

Known Issues

• TBD

OpenStack Orchestration (Heat)

WIP (will move here) https://etherpad.openstack.org/p/heat-kilo-releasenotes

Known Issues

None yet

Upgrade Notes

None yet

OpenStack Database service (Trove)

Known Issues

None yet

Upgrade Notes

None yet

OpenStack Documentation

Key New Features

• TBD

Upgrade Notes

None yet