Jump to: navigation, search


Revision as of 18:39, 25 November 2014 by Devananda (talk | contribs) (minor updates / corrections / link additions)

OpenStack Bare Metal Provisioning Program



Official name OpenStack Bare Metal Provisioning
Source code https://github.com/openstack/ironic
Developer doc http://docs.openstack.org/developer/ironic/
Bug tracker https://bugs.launchpad.net/ironic
Feature tracker https://blueprints.launchpad.net/ironic
Specifications http://specs.openstack.org/openstack/ironic-specs
Latest Release Notes https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno
Weekly meetings https://wiki.openstack.org/wiki/Meetings/Ironic


Source code https://github.com/openstack/python-ironicclient
Bug tracker https://bugs.launchpad.net/python-ironicclient
Feature tracker https://blueprints.launchpad.net/python-ironicclient
Developer doc http://docs.openstack.org/developer/python-ironicclient


Source code https://github.com/openstack/ironic-python-agent
Bug Tracker https://bugs.launchpad.net/ironic tag: "agent"


Source code https://github.com/stackforge/pyghmi


Ironic was first available as an Incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic is officially Integrated with OpenStack beginning with the "Kilo" release.

Information on the status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing

For a list of current drivers and the status of their CI testing, see the wiki page we maintain and the Stackalytics page which tracks third-party CI


Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.


Discussion of the project also takes place in #openstack-ironic on irc.freenode.net


Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines Please note that for any non-trivial change that does not fix some bug, you have to go through specs review process