Jump to: navigation, search

Difference between revisions of "Ironic/ReleaseNotes/Kilo"

(remove Logical name and maintenance mode TODO's)
 
Line 1: Line 1:
 
== Kilo Release Notes ==
 
== Kilo Release Notes ==
  
'''''*** DRAFT ***'''''
+
Release notes can be found on the main release notes page for OpenStack Kiloː
  
'''''A complete log of work completed during Kilo will be available once Kilo release is finalized.'''''
+
[[ReleaseNotes/Kilo#OpenStack_Bare_Metal_service_.28Ironic.29|https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Bare_Metal_service_.28Ironic.29]]
  
=== Key Features ===
+
== Documentation ==
 
 
Ironic now uses a formal model for the logical state of each node it manages.<ref name="states">[http://specs.openstack.org/openstack/ironic-specs/specs/kilo/new-ironic-state-machine.html#proposed-change]New Ironic State Machine</ref> 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.<ref name="cleaning">[http://docs.openstack.org/developer/ironic/deploy/cleaning.html]Node Cleaning</ref>
 
* Both in-band and out-of-band methods are available to '''inspect''' hardware. These methods may be used to update Node properties automatically.<ref name="inspect">[http://docs.openstack.org/developer/ironic/deploy/install-guide.html#hardware-inspection]Hardware Inspection</ref>
 
 
 
 
 
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.<ref name="api-version">[http://specs.openstack.org/openstack/ironic-specs/specs/kilo/api-microversions.html]REST API "micro" versions </ref> 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 ===
 
 
 
* Several new hardware drivers:
 
** [http://docs.openstack.org/developer/ironic/drivers/amt.html AMT]
 
** [http://docs.openstack.org/developer/ironic/deploy/drivers.html#irmc iRMC]
 
** [http://docs.openstack.org/developer/ironic/drivers/vbox.html VirtualBox (testing driver only)]
 
 
 
* New features of existing hardware drivers:
 
** SeaMicro driver supports serial console
 
** [http://docs.openstack.org/developer/ironic/drivers/ilo.html#uefi-secure-boot-support iLO driver supports UEFI secure boot]
 
** [http://docs.openstack.org/developer/ironic/drivers/ilo.html#hardware-inspection iLO driver supports out-of-band node inspection]
 
** [http://docs.openstack.org/developer/ironic/drivers/ilo.html#ilo-node-cleaning iLO driver supports resetting ilo and bios during cleaning]
 
 
 
* 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.
 
* Drivers are further enhanced by the following changes to the ''vendor passthrough'' API
 
** ''vendor_passthru'' methods now support additional HTTP methods (eg, PUT and POST).
 
** ''vendor_passthru'' methods are now discoverable in the REST API. ''TODO: where are docs for this????''
 
 
 
* [http://docs.openstack.org/developer/ironic/deploy/install-guide.html#enabling-the-configuration-drive-configdrive Configdrives] may be used with the "agent" drivers in lieu of a metadata service, if desired.
 
* [http://docs.openstack.org/developer/ironic/deploy/install-guide.html#logical-names Logical names] may be used to address Nodes, in addition to their canonical UUID.
 
* For servers with varied local disks, [http://docs.openstack.org/developer/ironic/deploy/install-guide.html#specifying-the-disk-for-deployment ''hints''] may be supplied that affect which disk device the OS is provisioned to.
 
* Support for fetching kernel, ramdisk, and instance images from HTTP[S] sources directly has been added to remove the dependency on Glance. [http://docs.openstack.org/developer/ironic/deploy/install-guide.html#using-ironic-as-a-standalone-service Using ironic as a standalone service]
 
* Nodes may be placed into ''[http://docs.openstack.org/developer/ironic/deploy/install-guide.html#maintenance-mode maintenance mode]'' via REST API calls. An optional ''maintenance reason'' may be specified when doing so.
 
 
 
=== 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:
 
* http://docs.openstack.org/developer/ironic/deploy/upgrade-guide.html#upgrading-from-juno-to-kilo
 
 
 
==== 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:
 
# Icehouse Nova "baremetal" -> Juno Nova "baremetal"
 
# Juno Nova "baremetal" -> Juno Ironic
 
# Juno Ironic -> Kilo Ironic
 
 
 
Documentation for steps 1 and 2 is available at: https://wiki.openstack.org/wiki/Ironic/NovaBaremetalIronicMigration
 
 
 
 
 
=== Documentation ===
 
  
 
Official documentation and guides have not been produced as part of the OpenStack Documentation program for this release.
 
Official documentation and guides have not been produced as part of the OpenStack Documentation program for this release.
Line 74: Line 11:
 
An install guide, produced by Ironic's developers, is included within the released code at doc/source/deploy/install-guide.rst.
 
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
+
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

Latest revision as of 19:15, 29 April 2015

Kilo Release Notes

Release notes can be found on the main release notes page for OpenStack Kiloː

https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Bare_Metal_service_.28Ironic.29

Documentation

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