OpenStack - User contributions [en]

Meetings/Ironic

2016-06-13T19:37:02Z

Nobodycam: /* Next Meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==

No meeting on June 20th since the midcycle is happening that day/week.

The next meeting will be on June 27, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160627T1700).

== Agenda for next meeting ==
* Announcements / Reminders
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]

Meetings/Ironic

2016-04-11T16:05:14Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be on April 11, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160411T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** 19 days until summit
** jroll traveling
** quick comment on sub-team status updates.
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** Summit session plan (jroll): https://etherpad.openstack.org/p/ironic-newton-summit
*** We have 5 fishbowls, 5 workrooms, Friday morning meetup
*** jroll has selected 6 sessions for sure, help me choose the rest :)
* RFE review
* Open discussion
** (zhenguo_) Add nova serial console support, two options:
*** Add a new custom HTTP proxy on nova side to leverage the existing shellinabox console (this may also benefit for other nova drivers' web based terminal)
*** A new console driver which replaces shellinabox to compatible with nova websocketproxy to provide serial console
** Node name updates fixes https://review.openstack.org/300983 (vdrok)
*** Return code 200 is changed to 400, and it seems to require a microversion.
*** Name removal in 1.1-1.4 versions is not that bad, but not validating name at all I think is.

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]

Meetings/Ironic

2016-04-11T15:54:30Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be on April 11, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160411T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** 19 days until summit
** jroll traveling
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** Summit session plan (jroll): https://etherpad.openstack.org/p/ironic-newton-summit
*** We have 5 fishbowls, 5 workrooms, Friday morning meetup
*** jroll has selected 6 sessions for sure, help me choose the rest :)
* RFE review
* Open discussion
** (zhenguo_) Add nova serial console support, two options:
*** Add a new custom HTTP proxy on nova side to leverage the existing shellinabox console (this may also benefit for other nova drivers' web based terminal)
*** A new console driver which replaces shellinabox to compatible with nova websocketproxy to provide serial console
** Node name updates fixes https://review.openstack.org/300983 (vdrok)
*** Return code 200 is changed to 400, and it seems to require a microversion.
*** Name removal in 1.1-1.4 versions is not that bad, but not validating name at all I think is.

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]

Meetings/Ironic

2016-03-28T16:46:07Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be on March 28, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160328T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** Congratulations to jroll.
** Summit schedule is out. Wednesday is out heavy meeting day.
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* RFE review
** Centralize config options in Ironic - https://bugs.launchpad.net/ironic/+bug/1561100
* Open discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]

Meetings/Ironic

2016-01-04T16:33:23Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be on January 4, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160104T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** Announcement (NobodyCam): Welcome back from the holidays and happy new year.
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
* Open Discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]

Meetings/Ironic

2015-09-28T15:43:53Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be on September 28, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150928T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** congrats to our new PTL, jroll
** 4.2.0 released - any backports between now and "Liberty final" will be released as 4.2.x
** Mitaka open for dev
** Reminder to propose summit sessions (don't forget to add your name!); deadline for having our schedule done is oct 15 per ttx https://etherpad.openstack.org/p/mitaka-ironic-design-summit-ideas
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Discussion
** Deprecation policy - do/should we follow OpenStack's new deprecation policy? https://review.openstack.org/#/c/228489/ https://github.com/openstack/governance/blob/master/reference/tags/assert_follows-standard-deprecation.rst
* Open Discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]

Meetings/Ironic

2015-08-31T14:12:13Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be on August 31, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150831T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** Devananda is out burning things, Not expected back until Sept., 8th.
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
** Nova/Ironic subteam: https://bugs.launchpad.net/nova/+bug/1405131 Is this a High priority for Liberty? If so, can someone volunteer? (mrda/jlvillal)
* Open Discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]

Meetings/Ironic

2015-08-13T21:53:34Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be on August 17, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150817T1700).

== Agenda for next meeting ==
* Announcements / Reminders
**
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Scripts / add-ons that do not fit into Ironic or it's repo (NobodyCam)
**Proposed: create a Wiki page list that links to repositories from those contributing the items to open source, however those items are not maintained by the Ironic community.

* Open Discussion

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]

== Future Meetings ==
* Meeting on 10-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150810T1700).
* Meeting on 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).
* Meeting on 24-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150824T1700).
* Meeting on 1-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150901T0500).
* Meeting on 7-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T1700).
* Meeting on 15-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150915T0500).
* Meeting on 21-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150921T1700).
* Meeting on 29-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150929T0500).
* Meeting on 5-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151005T1700).
* Meeting on 13-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151013T0500).
* Meeting on 19-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151019T1700).
* Meeting on 27-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151027T0500).
* Meeting on 2-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151102T1700).
* Meeting on 10-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151110T0500).
* Meeting on 16-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151116T1700).
* Meeting on 24-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151124T0500).
* Meeting on 30-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151130T1700).
* Meeting on 8-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151208T0500).
* Meeting on 14-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151214T1700).
* Meeting on 22-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151222T0500).
* Meeting on 28-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151228T1700).
* Meeting on 5-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160105T0500).
* Meeting on 11-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160111T1700).
* Meeting on 19-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160119T0500).
* Meeting on 25-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160125T1700).
* Meeting on 2-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160202T0500).
* Meeting on 8-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160208T1700).
* Meeting on 16-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160216T0500).
* Meeting on 22-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160222T1700).
* Meeting on 1-March-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T0500).

Meetings/Ironic

2015-06-15T16:54:49Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! Meetings are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda or Chris Krelle (NobodyCam).

The Meeting time alternates between '''1700 UTC on Monday''' and '''0500 UTC on Tuesday''', to accommodate contributors from around the world.

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

An ''unofficial'' Google Calendar for the meeting is here: [https://www.google.com/calendar/embed?showPrint=0&showCalendars=0&mode=WEEK&height=600&wkst=1&bgcolor=%23FFFFFF&src=sodarock.com_fepuqkqe2333htb41n2n9qmue8%40group.calendar.google.com&color=%235229A3 Google Calendar] This calendar may only show things for the Pacific Time Zone :(

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be June 15, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150615T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** Devananda is traveling and currently in Tel Aviv... may not make it to the meeting.
** NobodyCam and BadCub also traveling this week. will have spotty connections at best.
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* dashboard proposed by huawei: https://github.com/niuzhenguo/ironic-dashboard // https://review.openstack.org/191131
* Mircoversion guideline in API-WG https://review.openstack.org/187112
* Open Discussion
**

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]

== Future Meetings ==
* Meeting on 15-June-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150615T1700).
* Meeting on 23-June-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150623T0500).
* Meeting on 29-June-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150629T1700).
* Meeting on 7-July-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150707T0500).
* Meeting on 13-July-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150713T1700).
* Meeting on 21-July-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150721T0500).
* Meeting on 27-July-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150727T1700).
* Meeting on 4-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150804T0500).
* Meeting on 10-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150810T1700).
* Meeting on 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).
* Meeting on 24-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150824T1700).
* Meeting on 1-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150901T0500).
* Meeting on 7-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T1700).
* Meeting on 15-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150915T0500).
* Meeting on 21-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150921T1700).
* Meeting on 29-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150929T0500).
* Meeting on 5-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151005T1700).
* Meeting on 13-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151013T0500).
* Meeting on 19-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151019T1700).
* Meeting on 27-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151027T0500).
* Meeting on 2-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151102T1700).
* Meeting on 10-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151110T0500).
* Meeting on 16-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151116T1700).
* Meeting on 24-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151124T0500).
* Meeting on 30-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151130T1700).
* Meeting on 8-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151208T0500).
* Meeting on 14-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151214T1700).
* Meeting on 22-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151222T0500).
* Meeting on 28-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151228T1700).
* Meeting on 5-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160105T0500).
* Meeting on 11-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160111T1700).
* Meeting on 19-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160119T0500).
* Meeting on 25-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160125T1700).
* Meeting on 2-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160202T0500).
* Meeting on 8-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160208T1700).
* Meeting on 16-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160216T0500).
* Meeting on 22-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160222T1700).
* Meeting on 1-March-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T0500).

Meetings/Ironic

2015-06-15T15:34:30Z

Nobodycam: /* Agenda for next meeting */

= Weekly Ironic Project Team Meeting =

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! Meetings are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda or Chris Krelle (NobodyCam).

The Meeting time alternates between '''1700 UTC on Monday''' and '''0500 UTC on Tuesday''', to accommodate contributors from around the world.

NOTE: Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries. 

An ''unofficial'' Google Calendar for the meeting is here: [https://www.google.com/calendar/embed?showPrint=0&showCalendars=0&mode=WEEK&height=600&wkst=1&bgcolor=%23FFFFFF&src=sodarock.com_fepuqkqe2333htb41n2n9qmue8%40group.calendar.google.com&color=%235229A3 Google Calendar] This calendar may only show things for the Pacific Time Zone :(

Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra

== Next Meeting ==
The next meeting will be June 15, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150615T1700).

== Agenda for next meeting ==
* Announcements / Reminders
** Devananda is traveling and currently in Tel Aviv... may not make it to the meeting.
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* dashboard proposed by huawei: https://github.com/niuzhenguo/ironic-dashboard // https://review.openstack.org/191131
* Mircoversion guideline in API-WG https://review.openstack.org/187112
* Open Discussion
**

== Previous meetings ==

[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]

== Related meetings ==

[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]

== Future Meetings ==
* Meeting on 15-June-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150615T1700).
* Meeting on 23-June-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150623T0500).
* Meeting on 29-June-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150629T1700).
* Meeting on 7-July-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150707T0500).
* Meeting on 13-July-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150713T1700).
* Meeting on 21-July-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150721T0500).
* Meeting on 27-July-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150727T1700).
* Meeting on 4-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150804T0500).
* Meeting on 10-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150810T1700).
* Meeting on 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).
* Meeting on 24-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150824T1700).
* Meeting on 1-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150901T0500).
* Meeting on 7-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T1700).
* Meeting on 15-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150915T0500).
* Meeting on 21-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150921T1700).
* Meeting on 29-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150929T0500).
* Meeting on 5-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151005T1700).
* Meeting on 13-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151013T0500).
* Meeting on 19-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151019T1700).
* Meeting on 27-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151027T0500).
* Meeting on 2-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151102T1700).
* Meeting on 10-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151110T0500).
* Meeting on 16-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151116T1700).
* Meeting on 24-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151124T0500).
* Meeting on 30-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151130T1700).
* Meeting on 8-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151208T0500).
* Meeting on 14-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151214T1700).
* Meeting on 22-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151222T0500).
* Meeting on 28-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151228T1700).
* Meeting on 5-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160105T0500).
* Meeting on 11-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160111T1700).
* Meeting on 19-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160119T0500).
* Meeting on 25-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160125T1700).
* Meeting on 2-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160202T0500).
* Meeting on 8-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160208T1700).
* Meeting on 16-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160216T0500).
* Meeting on 22-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160222T1700).
* Meeting on 1-March-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T0500).

Meetings/Ironic

2015-06-01T16:31:22Z

Nobodycam: add neutron meeting recap.

Ironic/Drivers

2015-05-29T18:04:56Z

Nobodycam: update drac contact email

== Drivers ==

Ironic supports pluggable back-end drivers for different types of hardware to enable features specific to unique hardware platforms and leverage divergent capabilities via a common API . This API is divided into three sections: core, common, and vendor. While authors of vendor drivers may break new ground in the designated "vendor_passthru" section of the API, they are strongly encouraged to converge on a common API across vendors. More details may be found under the [http://docs.openstack.org/developer/ironic/dev/architecture.html#drivers system architecture] description.

Hardware drivers must undergo CI testing so as to ensure their continued functionality. Some drivers will be tested upstream, while many will require third-party CI testing due to the unique nature of their hardware (and the unmanageable complexity of a single team required to maintain a test infrastructure encompassing hardware from many diverse vendors). Guidelines on that testing can be found on the [[Ironic/Testing]] wiki page.

Out-of-tree drivers are supported by Ironic and may be loaded via python entrypoints. Here is a list of known out-of-tree drivers:

{| class="wikitable"
|-
! Name !! Link
|-
| Cisco UCS || https://communities.cisco.com/docs/DOC-56373
|}

The table below describes the CI test coverage of the current set of drivers. Note that drivers are composed of more than one interface (eg, power and deploy). Not all combinations of interfaces are necessarily tested together, but we are striving to get test coverage for each interface in at least one driver.

{| class="wikitable"
|-
! Interface Type !! Interface Name !! Test coverage provided by driver name
|-
| deploy || agent || agent_ssh; agent_ipmitool is used in production for Rackspace OnMetal
|-
| deploy || pxe || pxe_ssh
|-
| deploy || iscsi || none
|-
| power || drac || None
|-
| power || ilo || None
|-
| power || ipminative || pxe_ipminative (provided by ibm-xcat-ci)
|-
| power || ipmitool || ** most widely used power driver in production, but lacks upstream CI
|-
| power || seamicro || None
|-
| power || snmp || None
|-
| power || ssh || pxe_ssh
|-
| power || amt|| None
|-
| power || irmc|| None
|-
| power || iboot || None
|-
| power || virtualbox || None
|}

Links to graphs of the CI system's current status should be included in the table below, when available.

{| class="wikitable"
|-
! Driver Name !! Primary Contact Email and IRC handle !! Testing Status
|-
| pxe_ssh || devananda (devananda dot vdv at gmail) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]
|-
| pxe_ipminative || Yuan Y Bai <bybai at cn dot ibm dot com> / Long LA Cheng <chenglch at cn dot ibm dot com> / Jarrod Johnson (jjohnson2 at lenovo dot com) || Third-party CI: "ibm-xcat-ci" <xcat@cn.ibm.com>
|-
| pxe_ipmitool || devananda (devananda dot vdv at gmail) || used by TripleO, but not CI tested
|-
| agent_ssh || jroll (jim at jimrollenhagen dot com) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]
|-
| agent_ipmitool || jroll (jim at jimrollenhagen dot com) || used by Rackspace OnMetal, not CI tested upstream
|-
| PXEDracDriver || cdearborn Christopher Dearborn (Christopher_Dearborn at dell dot com) || Not CI tested
|}

== 3rd Party Drivers ==

iLO drivers: https://wiki.openstack.org/wiki/Ironic/Drivers/iLODrivers

Ironic/Drivers

2015-05-29T15:55:26Z

Nobodycam: add drac contact

== Drivers ==

Ironic supports pluggable back-end drivers for different types of hardware to enable features specific to unique hardware platforms and leverage divergent capabilities via a common API . This API is divided into three sections: core, common, and vendor. While authors of vendor drivers may break new ground in the designated "vendor_passthru" section of the API, they are strongly encouraged to converge on a common API across vendors. More details may be found under the [http://docs.openstack.org/developer/ironic/dev/architecture.html#drivers system architecture] description.

Hardware drivers must undergo CI testing so as to ensure their continued functionality. Some drivers will be tested upstream, while many will require third-party CI testing due to the unique nature of their hardware (and the unmanageable complexity of a single team required to maintain a test infrastructure encompassing hardware from many diverse vendors). Guidelines on that testing can be found on the [[Ironic/Testing]] wiki page.

Out-of-tree drivers are supported by Ironic and may be loaded via python entrypoints. Here is a list of known out-of-tree drivers:

{| class="wikitable"
|-
! Name !! Link
|-
| Cisco UCS || https://communities.cisco.com/docs/DOC-56373
|}

The table below describes the CI test coverage of the current set of drivers. Note that drivers are composed of more than one interface (eg, power and deploy). Not all combinations of interfaces are necessarily tested together, but we are striving to get test coverage for each interface in at least one driver.

{| class="wikitable"
|-
! Interface Type !! Interface Name !! Test coverage provided by driver name
|-
| deploy || agent || agent_ssh; agent_ipmitool is used in production for Rackspace OnMetal
|-
| deploy || pxe || pxe_ssh
|-
| deploy || iscsi || none
|-
| power || drac || None
|-
| power || ilo || None
|-
| power || ipminative || pxe_ipminative (provided by ibm-xcat-ci)
|-
| power || ipmitool || ** most widely used power driver in production, but lacks upstream CI
|-
| power || seamicro || None
|-
| power || snmp || None
|-
| power || ssh || pxe_ssh
|-
| power || amt|| None
|-
| power || irmc|| None
|-
| power || iboot || None
|-
| power || virtualbox || None
|}

Links to graphs of the CI system's current status should be included in the table below, when available.

{| class="wikitable"
|-
! Driver Name !! Primary Contact Email and IRC handle !! Testing Status
|-
| pxe_ssh || devananda (devananda dot vdv at gmail) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]
|-
| pxe_ipminative || Yuan Y Bai <bybai at cn dot ibm dot com> / Long LA Cheng <chenglch at cn dot ibm dot com> / Jarrod Johnson (jjohnson2 at lenovo dot com) || Third-party CI: "ibm-xcat-ci" <xcat@cn.ibm.com>
|-
| pxe_ipmitool || devananda (devananda dot vdv at gmail) || used by TripleO, but not CI tested
|-
| agent_ssh || jroll (jim at jimrollenhagen dot com) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]
|-
| agent_ipmitool || jroll (jim at jimrollenhagen dot com) || used by Rackspace OnMetal, not CI tested upstream
|-
| PXEDracDriver || cdearborn Christopher Dearborn (cdearbor at comcast dot net) || Not CI tested
|}

== 3rd Party Drivers ==

iLO drivers: https://wiki.openstack.org/wiki/Ironic/Drivers/iLODrivers

Ironic

2015-05-22T18:21:24Z

Nobodycam: /* IRC */

= OpenStack Bare Metal Provisioning Program =

OpenStack Bare Metal Provisioning a.k.a '''Ironic''' is an integrated OpenStack project which aims to provision bare metal machines instead of virtual machines, forked from the Nova Baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [http://docs.openstack.org/developer/ironic/deploy/user-guide.html| Introduction to Ironic]

== Projects ==

=== Ironic ===
==== Api and conductor ====

{| border="1" cellpadding="2"
| 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
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Core team
| https://wiki.openstack.org/wiki/Ironic/CoreTeam
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

=== python-ironicclient ===
==== Cli and Python client ====

{| border="1" cellpadding="2"
| 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
|}

=== ironic-python-agent ===
==== Deployment ram disk ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-python-agent
|-
| Bug tracker
| https://bugs.launchpad.net/ironic tag: "agent"
|-
| IPA - Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

=== pyghmi ===
==== an alternative to IpmiTool ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/pyghmi
|}

=== ironic-discoverd===
==== Hardware introspection tool ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/ironic-discoverd
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-discoverd/
|-
| Feature tracker
| https://blueprints.launchpad.net/ironic-discoverd/
|}

=== bifrost ===
==== Ansible play books to run Ironic standalone ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/bifrost
|}

=== Ironic-lib ===
==== Common lib of functions ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-lib
|}

== Status ==

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 completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially Integrated OpenStack project.
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno
* Kilo, 2015.1: https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Bare_Metal_service_.28Ironic.29

Information on the latest 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 [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]

== Etherpads ==

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

== IRC ==

Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start you Ironic Adventure.

== Developers ==

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 [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

== Pixie Boots, the Ironic drummer bear ==

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

[[category: baremetal]]
[[category: ironic]]

Ironic

2015-05-22T18:11:00Z

Nobodycam: clean up and updates

= OpenStack Bare Metal Provisioning Program =

OpenStack Bare Metal Provisioning a.k.a '''Ironic''' is an integrated OpenStack project which aims to provision bare metal machines instead of virtual machines, forked from the Nova Baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [http://docs.openstack.org/developer/ironic/deploy/user-guide.html| Introduction to Ironic]

== Projects ==

=== Ironic ===
==== Api and Conductor ====

{| border="1" cellpadding="2"
| 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
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Core team
| https://wiki.openstack.org/wiki/Ironic/CoreTeam
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

=== python-ironicclient ===
==== Cli and Python client ====

{| border="1" cellpadding="2"
| 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
|}

=== ironic-python-agent ===
==== Deployment ram disc ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-python-agent
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic tag: "agent"
|-
| IPA - Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

=== pyghmi ===
==== an Alternative to IpmiTool ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/pyghmi
|}

=== ironic-discoverd===
==== Hardware introspection tool ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/ironic-discoverd
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-discoverd/
|-
| Feature tracker
| https://blueprints.launchpad.net/ironic-discoverd/
|}

=== bifrost ===
==== Ansible play books to run Ironic standalone ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/bifrost
|}

=== Ironic-lib ===
==== Common Lib of functions ====
{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-lib
|}

== Status ==

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 completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially Integrated OpenStack project.
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno
* Kilo, 2015.1: https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Bare_Metal_service_.28Ironic.29

Information on the latest 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 [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]

== Etherpads ==

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

== IRC ==

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

== Developers ==

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 [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

== Pixie Boots, the Ironic drummer bear ==

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

[[category: baremetal]]
[[category: ironic]]

Ironic

2015-05-22T16:44:41Z

Nobodycam: Add Ironic-lib link

= OpenStack Bare Metal Provisioning Program =

OpenStack Bare Metal Provisioning a.k.a '''Ironic''' is an integrated OpenStack project which aims to provision bare metal machines instead of virtual machines, forked from the Nova Baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality.

== Projects ==

=== Ironic ===

{| border="1" cellpadding="2"
| 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
|-
| Weekly meetings
| https://wiki.openstack.org/wiki/Meetings/Ironic
|-
| Core team
| https://wiki.openstack.org/wiki/Ironic/CoreTeam
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

=== python-ironicclient ===

{| border="1" cellpadding="2"
| 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
|}

=== ironic-python-agent ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-python-agent
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic tag: "agent"
|-
| IPA - Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

=== pyghmi ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/pyghmi
|}

=== ironic-discoverd===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/ironic-discoverd
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-discoverd/
|-
| Feature tracker
| https://blueprints.launchpad.net/ironic-discoverd/
|}

=== bifrost ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/bifrost
|}

=== Ironic-lib ===
{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-lib
|}

== Status ==

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 completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially Integrated OpenStack project.
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno
* Kilo, 2015.1: https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Bare_Metal_service_.28Ironic.29

Information on the latest 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 [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]

== Etherpads ==

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

== IRC ==

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

== Developers ==

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 [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

== Pixie Boots, the Ironic drummer bear ==

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

[[category: baremetal]]
[[category: ironic]]

Meetings/Ironic

2015-05-06T20:53:37Z

Nobodycam: /* Agenda for next meeting */

ReleaseNotes/Kilo

2015-04-29T19:30:55Z

Nobodycam: update link to driver / node vendor pass thru docs

= OpenStack 2015.1.0 (Kilo) Release Notes =

{| style="color:#000000; border:solid 3px #A8A8A8; padding:2em; margin:2em 0; background-color:#FFFFFF; vertical-align:middle;"
| style="padding:1em" | The Kilo release of OpenStack is dedicated to the loving memory of '''Chris Yeoh''', who left his family and us way too soon.
|}

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__TOC__
</div>

== General Upgrade Notes ==

* TBD

== OpenStack Object Storage (Swift) ==

=== Key New Features ===

==== Erasure Code (beta) ====
Swift now supports an erasure-code (EC) storage policy type. This allows deployers to achieve very high durability with less raw capacity as used in replicated storage. However, EC requires more CPU and network resources, so it is not good for every use case. EC is great for storing large, infrequently accessed data in a single region.

Swift's implementation of erasure codes is meant to be transparent to end users. There is no API difference between replicated storage and EC storage.

To support erasure codes, Swift now depends on PyECLib and liberasurecode. liberasurecode is a pluggable library that allows for the actual EC algorithm to be implemented in a library of your choosing.

Full docs are at http://swift.openstack.org/overview_erasure_code.html

==== Composite tokens ====
Composite tokens allow other OpenStack services to store data in Swift on behalf of a client so that neither the client nor the service can update the data without both party's consent.

An example of this is that a user requests that Nova save a snapshot of a VM. Nova passes the request to Glance, Glance writes the image to a Swift container as a set of objects. In this case, the user cannot modify the snapshot without also having a valid token from the service. Nor can the service update the data without a valid token from the user. But the data is still stored in the user's account in Swift, which makes accounting simpler.

Full docs are at http://swift.openstack.org/overview_backing_store.html

==== Data placement updates for smaller, unbalanceable clusters ====
Swift's data placement now accounts for device weight. This allows operators to gradually add new zones and regions without immediately causing a large amount of data to be moved. Also, if a cluster is inbalanced (eg a two-zone cluster where one zone has twice the capacity of the other), Swift will more efficiently use the available space and warn when replicas are placed without enough dispersion in the cluster.

==== Global cluster replication improvements ====
Replication between regions will now only move one replica per replication run. This gives the remote region a chance to replicate internally and thus avoid more data moving over the WAN

=== Known Issues ===
* As a beta release, EC support is nearly fully feature complete, but it is lacking support for some features (like multi-range reads) and has not had a full performance characterization. This feature relies on ssync for durability. Deployers are urged to do extensive testing and not deploy production data using an erasure code storage policy.

=== Upgrade Notes ===
As always, you can upgrade to this version of Swift with no end-user downtime

* In order to support erasure codes, Swift has a new dependency on PyECLib (and liberasurecode, transitively). Also, the minimum required version of eventlet has been raised.

== OpenStack Compute (Nova) ==

=== Key New Features ===

==== API v2.1 ====

* We have the first release of the next generation of the Nova API, v2.1. The v2.1 is designed to be backwards compatible with v2.0 with the addition of strong API validation. All changes to the API are discoverable via the advertised microversion. For more details see: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/api-microversions.html

* For kilo, by default we are still using v2.0 API code to server v2.0 API requests. It is hoped that in liberty that v2.1 will be used to serve requests for both v2.0 and v2.1.

* For liberty v2.0 is now frozen, and all new features will now be added into the v2.1 API using the microversions mechanism. Microversion increments released with kilo are:
** Extending the keypair API to support for x509 certificates, to be used with Windows WinRM, is one of the first API features added as a microversion in the v2.1 API.
** Exposing additional attributes in os-extended-server-attributes

* python-novaclient does not yet have support for the v2.1 API

* The policy enforcement of Nova v2.1 API get improvement.
** Policy only enforce at the entry of API.
** Without duplicated rules for single one API anymore.
** All the v2.1 API policy rule use 'os_compute_api' as prefix which distinguish with v2 API.
** Due to hard-code permission checks at db layer, part of Nova API isn't configurable by policy before. It's always required admin user. Part of Nova v2.1 API's hard-code permission checks is removed which make API policy configurable. The rest of hard-code permission checks will be removed at Liberty.

==== Upgrade Support ====

* We have reduced the data migrations that happen in the DB migration scripts, this now happens in a "lazy" way inside the DB objects code. There are nova-manage commands to help force migration of the data. For more details see: http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/flavor-from-sysmeta-to-blob.html

* Change https://review.openstack.org/#/c/97946/ adds database migration 267 which scans for null instances.uuid records and will fail if any are found since the migrate ultimately needs to make instances.uuid non-nullable and adds a UniqueConstraint on that column. A helper script is provided to search for null instances.uuid records before running the database migrations. Before running 'nova-manage db sync', run the helper script 'nova-manage db null_instance_uuid_scan' which, by default, will just search and dump results, it does not change anything. Pass the --delete option to the null_instance_uuid_scan command to automatically remove any null records were instances.uuid is null.

==== Scheduler ====

* A selection of performance optimisations
* We are in the process of making structural changes to the scheduler that will help improve our ability to evolve and improve scheduling. This should not be visible from an end user perspective.

==== Cells v2 ====

* There are some initial parts of cell v2 supported added, but this feature is not yet ready to use.
* new 'nova-manage api_db sync' and 'nova-manage api_db version' commands for working with the new api database for cells, but nothing is using this database yet so it is not necessary to set it up.

==== Compute Drivers ====

===== Hyper-V =====

* Support for generation 2 VMs: https://blueprints.launchpad.net/nova/+spec/hyper-v-generation-2-vms
* Support for SMB based volumes, to sit along side existing iSCSI volume support: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/hyper-v-smbfs-volume-support.html
* Support for x509 certificate based key pairs: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/keypair-x509-certificates.html
* Host power actions now work with Hyper-V: https://blueprints.launchpad.net/nova/+spec/hyper-v-host-power-actions

===== Libvirt (KVM) =====

* NFV related features:
** NUMA based scheduling: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/input-output-based-numa-scheduling.html
** Pinning guest vCPUs: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/virt-driver-cpu-pinning.html
** Large page support: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/virt-driver-large-pages.html
* vhostuser VIF driver: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/libvirt_vif_vhostuser.html
* Support for running KVM on IBM System z: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/libvirt-kvm-systemz.html
* Support for parallels: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/pcs-support.html
* Support for SMB based volumes: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/libvirt-smbfs-volume-support.html
* Quiesce using QEMU guest agent: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/quiesced-image-snapshots-with-qemu-guest-agent.html
* Quobyte volume support: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/quobyte-nova-driver.html
* Support for QEMU iSCSI initiator: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/qemu-built-in-iscsi-initiator.html

===== VMware =====

* Support for Ephemeral disks: http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/vmware-ephemeral-disk-support.html
* Support fo vSAN: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/vmware-vsan-support.html
* Support for based OVA images: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/vmware-driver-ova-support.html
* Support for SPBM based storage policies: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/vmware-spbm-support.html

===== Ironic =====

* Support to pass flavor capabilities to ironic: http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/pass-flavor-capabilities-to-ironic-virt-driver.html

=== 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. NOTE: This is not a regression and has been a flaw in the design of the evacuate feature since its introduction. There is no easy fix for this, hence this workaround to limit the potential for damage. The proposed fix in liberty is here: https://review.openstack.org/#/c/161444/.

* The generate config examples possibly missing some oslo related configuration

=== Upgrade Notes ===

Below are changes you should be aware of when upgrading. Where possible, The git commit hash is provided for you to find more information:

* Neutron ports are no longer deleted after your server is deleted, if you created them outside of Nova: 1153a46738fc3ffff98a1df9d94b5a55fdd58777
* EC2 API support has been deprecated, and is likely to be removed in kilo, see f098398a836e3671c49bb884b4a1a1988053f4b2
* Websocket proxies need to be upgraded in a lockstep with the API nodes, as older API nodes will not be sending the access_url when authorizing console access, and newer proxy services (this commit and onward) would fail to authorize such requests 9621ccaf05900009d67cdadeb1aac27368114a61
* 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.
* Due to the improvement on Nova v2.1 API policy enforcement. There are a lot of change happened to v2.1 API policy. Because v2.1 API didn't released before, those change won't keep back-compatible. It is better to use policy sample configuration instead of old one.
* VMware rescue VM behaviour no longer creates a new VM and instead happens in place: cd1765459a24e52e1b933c8e05517fed75ac9d41
* force_config_drive = always has been deprecated, and force_config_drive = True should be used instead: c12a78b35dc910fa97df888960ef2b9a64557254
* Running hyper-v, if you deployed code that was past this commit: b4d57ab65836460d0d9cb8889ec2e6c3986c0a9b but before this commit: c8e9f8e71de64273f10498c5ad959634bfe79975 you make have problems to manually resolve see: c8e9f8e71de64273f10498c5ad959634bfe79975
* Changed the default value of: multi_instance_display_name_template see: 609b2df339785bff9e30a9d67d5c853562ae3344
* Please use "nova-manage db null_instance_uuid_scan" to ensure the DB migrations will apply cleanly, see: c0ea53ce353684b48303fc59393930c3fa5ade58

== 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 ===

* Keystone now supports Hierarchical Multitenancy. Projects can be nested under other projects via the <code>parent_id</code> optional attribute when creating a project.
** TBD - More info.
* Fernet tokens - TBD - More Info
* WebSSO - TBD - More info
* Pluggable Assignment Model - TBD - More Info
* Assignment / Resource Split - TBD - More Info
* Extensions to Core functionality - TBD - More Info
* (Experimental) Per-Domain Identity Backend Configuration can be stored in SQL - TBD More Info
* [http://docs.openstack.org/developer/keystone/configure_federation.html#keystone-as-an-identity-provider-idp Keystone-to-Keystone Identity Federation] is now considered stable.
** IDP Registration - TBD - More Info
** ECP Wrapped Assertions Endpoint - TBD - More Info
* Keystone now supports [http://docs.openstack.org/developer/keystone/extensions/openidc.html OpenID Connect] as a federated identity authentication mechanism.
* Trusts now support redelegation. If allowed when the trust is created, a trustee can redelegate the roles from the trust via another trust.
* It is now possible to request an explicitly unscoped token from Keystone.

=== 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 [https://github.com/openstack/keystone/blob/master/etc/keystone-paste.ini 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.
* [http://specs.openstack.org/openstack/openstack-specs/specs/no-downward-sql-migration.html SQL Schema Downgrades are no longer supported]. This change is the result of evaluation that downward SQL migrations are not well tested and become increasingly difficult to support with the volume of data-change that occurs in many of the migrations.

== OpenStack Network Service (Neutron) ==
=== Key New Features ===
* DVR now supports VLANs in addition to VXLAN/GRE
* ML2 Hierarchical Port Binding
* New LBaaS Version 2 API
* Portsecurity support for the OVS ML2 Driver

* New Plugins supported in Kilo include the following:
** A10 Networks LBaaS V2 Driver
** Brocade LBaaS V2 Driver
** Brocade ML2 driver for MLX and ICX switches
** Brocade L3 routing plugin for MLX switch
** Brocade Vyatta vRouter L3 Plugin
** Brocade Vyatta vRouter Firewall Driver
** Brocade Vyatta vRouter VPN Driver
** Cisco CSR VPNaaS Driver
** Dragonflow SDN based Distributed Virtual Router L3 Plugin
** Freescale FWaaS Driver
** Intel Mcafee NGFW FWaaS Driver
** IPSEC Strongswan VPNaaS Driver

=== Known Issues ===
* The Firewall-as-a-Service project is still marked as experimental for the Kilo release.
* Bug [https://bugs.launchpad.net/neutron/+bug/1438819 1438819]
** When a new subnet is created on an external network, all existing routers with gateways on the network will get a new address allocated from it. For IPv4 networks, this could consume the entire subnet for router gateway ports.

=== 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)

=== Other Notes (Deprecation/EOL etc) ===

* Deprecation
** Brocade Classic plugin for Brocade's VDX/VCS series of hardware switches will be deprecated in the L-Release. The functionality provided by this plugin is now addressed by the ML2 Driver available for the VDX series of hardware. The plugin is slated for removal after this release cycle.

== OpenStack Block Storage (Cinder) ==
=== Key New Features ===
* From this point forward any new database schema upgrades will not require restarting Cinder services right away. The services are now independent of schema upgrades. This is part one to Cinder supporting rolling upgrades!
* Ability to add/remove volumes from an existing consistency group. [http://docs.openstack.org/admin-guide-cloud/content/consistency-groups.html Read docs for more info].
* Ability to create a consistency group from an existing consistency group snapshot. [http://docs.openstack.org/admin-guide-cloud/content/consistency-groups.html Read docs for more info].
* Create more fine tuned filters/weighers to set how the scheduler will choose a volume backend. [http://docs.openstack.org/admin-guide-cloud/content/driver_filter_weighing.html Read the docs for more info].
* Encrypted volumes can now be backed up using the Cinder backup service. [http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore.html Read the docs for more info].
* Ability to create private volume types. This is perfect when you want to make volume types available to only a specific tenant or to test it before making available to your cloud. To do so use the ''cinder type-create <name> --is-public''.
* Oversubscription with thin provision is configurable. [http://docs.openstack.org/admin-guide-cloud/content/over_subscription.html Read docs for more info].
* Ability to add descriptions to volume types. To do so use ''cinder type-create <name> <description>
* Cinder now can return multiple iSCSI paths information so that the connector can attach volumes even when the primary path is down ([https://review.openstack.org/#/c/134681/ when connector's multipath feature is enabled] or [https://review.openstack.org/#/c/140877/ not enabled]).

=== 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 ===
* Support to add jitter to polling cycles to ensure pollsters are not querying service's api at the same time
* Ceilometer API RBAC support
* Improved Event support:
** Multi-pipeline support to enable unique processing and publishing of events
** Enabled ability to capture raw notification messages for auditing and postmortem analysis
** Support for persisting events into ElasticSearch
** Publishing support to database, http, file, kafa and oslo.messaging supported message queues
** Option to split off the events persistence into a separate database
** Telemetry now supports to collect and store all the event type meters as events. A new option, ''disable_non_metric_meters'', was added to the configuration in order to provide the possibility to turn off storing these events as samples. For further information please see the [http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html Telemetry Configuration Reference]
** The Administrator Guide in OpenStack Manuals was updated with a new [http://docs.openstack.org/admin-guide-cloud/content/section_telemetry-events.html Events section], where you can find further information about this functionality.
* Improved pipeline publishing support:
** Support to publish events and samples to Kafka or HTTP targets
** Publish data to multiple queues
* Additional meters
** memory and disk meters for Hyper-V
** disk meters for LibVirt
** power and thermal related IPMI meters, more meters from NodeManager
** ability to meter Ceph
* IPv6 support enabled in Ceilometer udp publisher and collector
* [http://launchpad.net/gnocchi Gnocchi] dispatch support for ceilometer-collector
* Self-disabled pollster mechanism

=== Known Issues ===
* TBD

=== Upgrade Notes ===
* Deprecated meters:
** The instance:<flavor> meter is deprecated in the Kilo release. In order to retrieve samples or statistics based on flavor you can use the following queries:
statistics:
ceilometer statistics -m instance -g resource_metadata.instance_type

samples:
ceilometer sample-list -m instance -q metadata.instance_type=<value>
* Middleware used to meter Swift was previously packaged in Ceilometer and is now deprecated. It is now separated into it's own library: ceilometermiddleware.
** Juno configuration: http://docs.openstack.org/juno/install-guide/install/apt/content/ceilometer-swift.html
** Kilo configuration: http://docs.openstack.org/kilo/install-guide/install/apt/content/ceilometer-swift.html

== OpenStack Orchestration (Heat) ==

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

=== 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 Data Processing service (Sahara) ==
=== Key New Features ===
TBD

=== Known Issues ===
TBD

=== Upgrade Notes ===
TBD

== OpenStack Bare Metal service (Ironic) ==

=== Key New Features ===

==== State Machine ====
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>

==== Version Headers ====
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.

==== Hardware Driver Changes ====
The following new drivers were added:
* [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)]

The following enhancements were made to existing drivers:
* [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.
* 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.
* ''vendor_passthru'' methods now support additional HTTP methods (eg, PUT and POST).
* ''vendor_passthru'' methods are now discoverable in the REST API. See [http://docs.openstack.org/developer/ironic/dev/drivers.html#node-vendor-passthru node vendor passthru] and [http://docs.openstack.org/developer/ironic/dev/drivers.html#driver-vendor-passthru driver vendor passthru]

==== Other Changes ====
* [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.

=== 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 ===
* IPMI Passwords are now obfuscated in REST API responses. This may be disabled by changing API policy settings.
* The "agent" class of drivers now support both whole-disk and partition based images.
* The driver_info parameters of "pxe_deploy_kernel" and "pxe_deploy_ramdisk" are deprecated in favour of "deploy_kernel" and "deploy_ramdisk".
* Drivers implementing their own version of the vendor_passthru() method has been deprecated in favour of the new @passthru decorator.

==== 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

== OpenStack Documentation ==

* New [http://docs.openstack.org docs.openstack.org] landing page and new web design for [http://docs.openstack.org/user-guide/ End User Guide] and [http://docs.openstack.org/user-guide-admin/ Admin User Guide]
* First release of the [http://docs.openstack.org/networking-guide/ Networking Guide]
* Migration to RST for [http://docs.openstack.org/user-guide/ End User Guide] and [http://docs.openstack.org/user-guide-admin/ Admin User Guide]
* New specialty teams:
** Install Guides
** Networking Guide
** High Availability Guide
** Networking Guide
** User Guides (Admin and End User)
* First App Tutorial sprint
* Driver documentation clarification and connections

Ironic/ReleaseNotes/Kilo

2015-04-29T14:33:24Z

Nobodycam: remove Logical name and maintenance mode TODO's

== 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.<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.

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

Ironic/ReleaseNotes/Kilo

2015-04-28T18:48:26Z

Nobodycam: removed SeaMicro TODO

== 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.<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.
* Logical names may be used to address Nodes, in addition to their canonical UUID. "TODO: Add example of name usage and link here"
* 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 ''maintenance mode'' via REST API calls. An optional ''maintenance reason'' may be specified when doing so. "TODO: Add example and link here"

=== 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.

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

Ironic/ReleaseNotes/Kilo

2015-04-27T15:32:54Z

Nobodycam: /* 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.<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: ''TODO: add link to SeaMicro doc.''
** 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.
* Logical names may be used to address Nodes, in addition to their canonical UUID. "TODO: Add example of name usage and link here"
* 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 ''maintenance mode'' via REST API calls. An optional ''maintenance reason'' may be specified when doing so. "TODO: Add example and link here"

=== 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.

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

Ironic/ReleaseNotes/Kilo

2015-04-23T22:50:52Z

Nobodycam: /* 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.<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: ''TODO: add link to SeaMicro doc.''
** 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.
* Logical names may be used to address Nodes, in addition to their canonical UUID. "TODO: Add example of name usage and link here"
* 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. "TODO: Add example and link here"
* Nodes may be placed into ''maintenance mode'' via REST API calls. An optional ''maintenance reason'' may be specified when doing so. "TODO: Add example and link here"

=== 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.

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

Ironic/ReleaseNotes/Kilo

2015-04-23T22:33:02Z

Nobodycam: /* 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.<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: ''TODO: add link to SeaMicro doc.''
** 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.
* 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.
* Nodes may be placed into ''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.

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

Ironic/ReleaseNotes/Kilo

2015-04-23T21:31:07Z

Nobodycam: /* 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.<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: ''TODO: add link to SeaMicro doc.''
** 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????''

* Configdrives may be used with the "agent" drivers in lieu of a metadata service, if desired.
* 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.
* Nodes may be placed into ''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.

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

Ironic/ReleaseNotes/Kilo

2015-04-23T21:12:15Z

Nobodycam: /* 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.<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: ''TODO: add link to SeaMicro doc.''
** 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????''

* Configdrives may be used with the "agent" drivers in lieu of a metadata service, if desired.
* Logical names may be used to address Nodes, in addition to their canonical UUID.
* For servers with varied local disks, ''hints'' may be supplied that affect which disk device the OS is provisioned to. ''TODO: add doc link here''
* Support for fetching kernel, ramdisk, and instance images from HTTP[S] sources directly has been added to remove the dependency on Glance.
* Nodes may be placed into ''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.

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

Ironic

2015-04-22T18:04:40Z

Nobodycam: /* ironic-python-agent */

= OpenStack Bare Metal Provisioning Program =

OpenStack Bare Metal Provisioning a.k.a '''Ironic''' is an integrated OpenStack project which aims to provision bare metal machines instead of virtual machines, forked from the Nova Baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality.

== Projects ==

=== Ironic ===

{| border="1" cellpadding="2"
| 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
|-
| Core team
| https://wiki.openstack.org/wiki/Ironic/CoreTeam
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

=== python-ironicclient ===

{| border="1" cellpadding="2"
| 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
|}

=== ironic-python-agent ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-python-agent
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic tag: "agent"
|-
| IPA - Wiki page
| https://wiki.openstack.org/wiki/Ironic-python-agent
|}

=== pyghmi ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/pyghmi
|}

=== ironic-discoverd===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/ironic-discoverd
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-discoverd/
|-
| Feature tracker
| https://blueprints.launchpad.net/ironic-discoverd/
|}

== Status ==

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 completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially Integrated OpenStack project.
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno

Information on the latest 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 [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]

== Etherpads ==

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

== IRC ==

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

== Developers ==

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 [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

== Pixie Boots, the Ironic drummer bear ==

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

[[category: baremetal]]
[[category: ironic]]

Ironic

2015-04-22T17:57:46Z

Nobodycam: /* Ironic */

= OpenStack Bare Metal Provisioning Program =

OpenStack Bare Metal Provisioning a.k.a '''Ironic''' is an integrated OpenStack project which aims to provision bare metal machines instead of virtual machines, forked from the Nova Baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality.

== Projects ==

=== Ironic ===

{| border="1" cellpadding="2"
| 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
|-
| Core team
| https://wiki.openstack.org/wiki/Ironic/CoreTeam
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|-
| Drivers
| https://wiki.openstack.org/wiki/Ironic/Drivers
|}

=== python-ironicclient ===

{| border="1" cellpadding="2"
| 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
|}

=== ironic-python-agent ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-python-agent
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic tag: "agent"
|}

=== pyghmi ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/pyghmi
|}

=== ironic-discoverd===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/ironic-discoverd
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-discoverd/
|-
| Feature tracker
| https://blueprints.launchpad.net/ironic-discoverd/
|}

== Status ==

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 completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially Integrated OpenStack project.
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno

Information on the latest 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 [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]

== Etherpads ==

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

== IRC ==

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

== Developers ==

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 [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

== Pixie Boots, the Ironic drummer bear ==

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

[[category: baremetal]]
[[category: ironic]]

Ironic

2015-04-22T17:55:31Z

Nobodycam: /* Ironic */

= OpenStack Bare Metal Provisioning Program =

OpenStack Bare Metal Provisioning a.k.a '''Ironic''' is an integrated OpenStack project which aims to provision bare metal machines instead of virtual machines, forked from the Nova Baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality.

== Projects ==

=== Ironic ===

{| border="1" cellpadding="2"
| 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
|-
| Core team
| https://wiki.openstack.org/wiki/Ironic/CoreTeam
|-
| Testing
| https://wiki.openstack.org/wiki/Ironic/Testing
|}

=== python-ironicclient ===

{| border="1" cellpadding="2"
| 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
|}

=== ironic-python-agent ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-python-agent
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic tag: "agent"
|}

=== pyghmi ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/pyghmi
|}

=== ironic-discoverd===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/ironic-discoverd
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic-discoverd/
|-
| Feature tracker
| https://blueprints.launchpad.net/ironic-discoverd/
|}

== Status ==

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 completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially Integrated OpenStack project.
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno

Information on the latest 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 [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]

== Etherpads ==

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

== IRC ==

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

== Developers ==

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 [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

== Pixie Boots, the Ironic drummer bear ==

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

[[category: baremetal]]
[[category: ironic]]

Ironic/ReleaseNotes/Kilo

2015-04-20T23:17:17Z

Nobodycam: /* Additional Features */

Meetings/Ironic

2015-04-20T16:39:20Z

Nobodycam: /* Agenda for next meeting */

Meetings/Ironic

2015-04-20T15:28:48Z

Nobodycam: /* Agenda for next meeting */

Ironic/Drivers

2015-04-17T17:30:58Z

Nobodycam: /* Drivers */

== Drivers ==

Ironic supports pluggable back-end drivers for different types of hardware to enable features specific to unique hardware platforms and leverage divergent capabilities via a common API . This API is divided into three sections: core, common, and vendor. While authors of vendor drivers may break new ground in the designated "vendor_passthru" section of the API, they are strongly encouraged to converge on a common API across vendors. More details may be found under the [http://docs.openstack.org/developer/ironic/dev/architecture.html#drivers system architecture] description.

Hardware drivers must undergo CI testing so as to ensure their continued functionality. Some drivers will be tested upstream, while many will require third-party CI testing due to the unique nature of their hardware (and the unmanageable complexity were a single team required to maintain a test infrastructure encompassing hardware from many diverse vendors). Guidelines on that testing can be found on the [[Ironic/Testing]] wiki page.

Out-of-tree drivers are supported by Ironic and may be loaded via python entrypoints. Here is a list of known out-of-tree drivers:

{| class="wikitable"
|-
! Name !! Link
|-
| Cisco UCS || https://communities.cisco.com/docs/DOC-56373
|}

The table below describes the CI test coverage of the current set of drivers. Note that drivers are composed of more than one interface (eg, power and deploy). Not all combinations of interfaces are necessarily tested together, but we are striving to get test coverage for each interface in at least one driver.

{| class="wikitable"
|-
! Interface Type !! Interface Name !! Test coverage provided by driver name
|-
| deploy || agent || agent_ssh; agent_ipmitool is used in production for Rackspace OnMetal
|-
| deploy || pxe || pxe_ssh
|-
| deploy || iscsi || none
|-
| power || drac || None
|-
| power || ilo || None
|-
| power || ipminative || pxe_ipminative (provided by ibm-xcat-ci)
|-
| power || ipmitool || ** most widely used power driver in production, but lacks upstream CI
|-
| power || seamicro || None
|-
| power || snmp || None
|-
| power || ssh || pxe_ssh
|-
| power || amt|| None
|-
| power || irmc|| None
|-
| power || iboot || None
|-
| power || virtualbox || None
|}

Links to graphs of the CI system's current status should be included in the table below, when available.

{| class="wikitable"
|-
! Driver Name !! Primary Contact Email and IRC handle !! Testing Status
|-
| pxe_ssh || devananda (devananda dot vdv at gmail) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]
|-
| pxe_ipminative || Yuan Y Bai <bybai at cn dot ibm dot com> / Long LA Cheng <chenglch at cn dot ibm dot com> / Jarrod Johnson (jjohnson2 at lenovo dot com) || Third-party CI: "ibm-xcat-ci" <xcat@cn.ibm.com>
|-
| pxe_ipmitool || devananda (devananda dot vdv at gmail) || used by TripleO, but not CI tested
|-
| agent_ssh || jroll (jim at jimrollenhagen dot com) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]
|-
| agent_ipmitool || jroll (jim at jimrollenhagen dot com) || used by Rackspace OnMetal, not CI tested upstream
|-
|}

== 3rd Party Drivers ==

iLO drivers: https://wiki.openstack.org/wiki/Ironic/Drivers/iLODrivers

Meetings/Ironic

2015-04-09T17:12:13Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-04-06T14:51:40Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-03-30T15:25:47Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-03-23T16:30:36Z

Nobodycam: /* Agenda for next meeting */

Ironic

2015-03-11T18:16:34Z

Nobodycam: Add core team link

= OpenStack Bare Metal Provisioning Program =

== Projects ==

=== Ironic ===

{| border="1" cellpadding="2"
| 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
|-
| Core team
| https://wiki.openstack.org/wiki/Ironic/CoreTeam
|}

=== python-ironicclient ===

{| border="1" cellpadding="2"
| 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
|}

=== ironic-python-agent ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/openstack/ironic-python-agent
|-
| Bug Tracker
| https://bugs.launchpad.net/ironic tag: "agent"
|}

=== pyghmi ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/pyghmi
|}

== Status ==

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.
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno

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 [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]

== Etherpads ==

Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]

== IRC ==

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

== Developers ==

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 [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]

== Pixie Boots, the Ironic drummer bear ==

Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.

High-resolution PNGs versions are available by clicking on the images below:

<gallery>
Ironic_mascot_color.png|Colored
Ironic_mascot_outline.png|Outlined
</gallery>

You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]

All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].

[[category: baremetal]]
[[category: ironic]]

Meetings/Ironic

2015-02-23T16:44:25Z

Nobodycam: /* Agenda for next meeting */

Meetings/Ironic

2015-02-18T17:00:49Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-02-18T16:59:53Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-02-17T04:28:47Z

Nobodycam: /* Agenda for next meeting */

Meetings/Ironic

2015-02-17T04:19:07Z

Nobodycam: /* Agenda for next meeting */

Meetings/Ironic

2015-02-16T23:51:38Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-02-09T16:55:01Z

Nobodycam: /* Agenda for next meeting */

Meetings/Ironic

2015-02-09T16:25:37Z

Nobodycam: /* Agenda for next meeting */

Meetings/Ironic

2015-02-09T15:25:21Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-02-02T21:16:48Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2015-01-20T22:09:22Z

Nobodycam: /* Agenda for next meeting */

Meetings/Ironic

2015-01-05T14:19:32Z

Nobodycam: /* Weekly Ironic Project Team Meeting */

Meetings/Ironic

2014-12-18T17:45:47Z

Nobodycam: /* Agenda for next meeting */