Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(Weekly Ironic Project Team Meeting: Add link to eavesdrop.openstack.org ICS file and meeting info.)
Line 7: Line 7:
 
NOTE: <span style="color:green">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.</span><br>
 
NOTE: <span style="color:green">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.</span><br>
  
An ''unofficial'' Google Calendar for the meeting is here: [https://www.google.com/calendar/embed?showPrint=0&amp;showCalendars=0&amp;mode=WEEK&amp;height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=sodarock.com_fepuqkqe2333htb41n2n9qmue8%40group.calendar.google.com&amp;color=%235229A3 Google Calendar] This calendar may only show things for the Pacific Time Zone :(
+
* [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.
 
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.
Line 44: Line 46:
  
 
== Future Meetings ==
 
== Future Meetings ==
* 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 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 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).

Revision as of 16:50, 10 August 2015

Weekly Ironic Project Team Meeting

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the Ironic project! Meetings are held in the #openstack-meeting-3 room on irc.freenode.net, 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.


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.

Next Meeting

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

Agenda for next meeting

  • Announcements / Reminders
  • Review subteam status reports (capped at ten minutes)
  • Nodes tagging https://review.openstack.org/#/c/192935/
  • (dtantsur) How to introduce Retry-After header?
    • Which status code to use? 406 designates client error, 503 designates the whole service is down...
    • How to determine a value to return?
    • How to treat this header in python-ironicclient?
  • (dtantsur) ironic-lib integration plan
    • release ironic-lib
    • start using in ironic
    • create dsvm gate for ironic-lib
    • ... anything else?
  • (dtantsur) Final battle on which version to use in client. 1.6 (last released) or 1.9 (git master)?
    • Also should we eventually go to 1.1?
  • Open Discussion

Previous meetings

Logs from previous meetings can be found here.

Related meetings

Ironic/Neutron integration meets weekly on Monday at 1600 UTC.

Future Meetings