Jump to: navigation, search


< Ironic‎ | ReleaseNotes
Revision as of 23:17, 20 April 2015 by Nobodycam (talk | contribs) (Additional Features)

Kilo Release Notes

*** DRAFT ***

A complete log of work completed during Kilo will be available once Kilo release is finalized.

Key Features

Ironic now uses a formal model for the logical state of each node it manages.[1] This has enabled the addition of two new processes: cleaning and inspection.

  • Automatic disk erasure between tenants is now enabled by default. This may be extended to perform additional cleaning steps, such as re-applying firmware, resetting BIOS settings, etc.[2]
  • Both in-band and out-of-band methods are available to inspect hardware. These methods may be used to update Node properties automatically.[3]

The Ironic REST API expects a new X-OpenStack-Ironic-API-Version header be passed with each HTTP[S] request. This header allows client and server to negotiate a mutually supported interface.[4] In the absence of this header, the REST service will default to a compatibility mode and yield responses compatible with Juno clients. This mode, however, prevents access to most features introduced in Kilo.

Additional Features

  • Logical names may be used to address Nodes, in addition to their canonical UUID.
  • Several new hardware drivers:
  • Support for third-party and out-of-tree drivers is enhanced by the following two changes:
    • Drivers may store their own "internal" information about Nodes.
    • Drivers may register their own periodic tasks to be run by the Conductor.

Noteworthy Fixes and Improvements over Juno

  • IPMI Passwords are now obfuscated in REST responses. This may be disabled by a config option.
  • The "agent" class of drivers now support both whole-disk and partition based images.

Known Issues

  • Running more than one nova-compute process is not officially supported.
    • While Ironic does include a ClusteredComputeManager, which allows running more than one nova-compute process with Ironic, it should be considered experimental and has many known problems.
  • Drivers using the "agent" deploy mechanism do not support "rebuild --preserve-ephemeral"

Upgrade Notes

Juno to Kilo

The recommended upgrade process is documented here:

Upgrading from Icehouse "nova-baremetal"

An upgrade from an Icehouse Nova installation using the "baremetal" driver directly to Kilo Ironic is untested and unsupported. Instead, please follow the following upgrade path:

  1. Icehouse Nova "baremetal" -> Juno Nova "baremetal"
  2. Juno Nova "baremetal" -> Juno Ironic
  3. Juno Ironic -> Kilo Ironic

Documentation for steps 1 and 2 is available at: https://wiki.openstack.org/wiki/Ironic/NovaBaremetalIronicMigration


Official documentation and guides have not been produced as part of the OpenStack Documentation program for this release.

An install guide, produced by Ironic's developers, is included within the released code at doc/source/deploy/install-guide.rst.

Note that the online version of these docs are kept up to date based on the current tip of development, not the latest release. The link below may therefore refer to features not available in the Kilo release. http://docs.openstack.org/developer/ironic/deploy/install-guide.html
  1. [1]New Ironic State Machine
  2. [2]Node Cleaning
  3. [3]Hardware Inspection
  4. [4]REST API "micro" versions