Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

m
(Agenda for next meeting)
Line 1: Line 1:
 
= Weekly Ironic Project Team Meeting =
 
= Weekly Ironic Project Team Meeting =
  
If you're interested in bare metal deployments with OpenStack, please join us. This meeting is where we'll talk about the [http://launchpad.com/ironic Ironic project], an evolution of the [[Baremetal|Nova Baremetal]] driver. Anyone is welcome to add items to the agenda below, or bring up their topic during the open discussion at the end of each 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 1500 UTC on Mondays (as of March 26, 2018), are held in the <code><nowiki>#openstack-ironic</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Julia Kreger (TheJulia) or Dmitry Tantsur (dtantsur).
  
Meetings are held in the <code><nowiki>#openstack-meeting</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code> at 19:00 UTC on Mondays. The next meeting is scheduled for July 29th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130729T1900).
+
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>
  
Following this meeting is the [[Meetings/TripleO|TripleO team meeting]], which often also discusses issues related to bare metal deployments.
+
* [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 ==
 +
 
 +
Meetings are held weekly. If one is cancelled, it will either be mentioned in the previous meeting or an email will be sent out to the openstack-discuss mailing list.
  
 
== Agenda for next meeting ==
 
== Agenda for next meeting ==
 
+
* Announcements / Reminder
* Improvements of testing
+
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2019/
** Devstack / tempest tests
+
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
* Outstanding or in-progress tasks:
+
* Deciding on priorities for the coming week
** Keystone authentication. Do we need to create a keystone role and auth admin_or_owner?
+
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** PXE driver and Image utils refactoring
+
** (TheJulia) Creating more categories for release notes
** diskimage-builder element status
+
*** In looking through our release notes for this last release, I found the notes to be somewhat jumbled and wondered "What if all of the API items were in one place?", and "iLO" or "iDRAC".
* API discussion:
+
*** Thoughts? It goes without saying that this would require some additional release notes clean-up at the end of cycle. We could treat ad-hoc and back-port items and at the end of cycle just retool the primary items before release.
** API vs RPC objects have different fields
+
* Baremetal SIG
** API vs RPC object class name confusion
+
** Whitepaper
** API returning related object UUIDs
+
** User stories
** API exposes some dicts as sub resources
+
* RFE review
** PUT vs PATCH in the API
+
** https://storyboard.openstack.org/#!/story/2003594
** API response code support in Pecan/WSME
+
* Open discussion
* open discussion
 
  
 
== Previous meetings ==
 
== Previous meetings ==
  
 
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]
 
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]
 +
 +
== Related meetings ==
 +
 +
<none>

Revision as of 13:47, 8 October 2019

Weekly Ironic Project Team Meeting

If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the Ironic project! The one-hour weekly meetings start at 1500 UTC on Mondays (as of March 26, 2018), are held in the #openstack-ironic room on irc.freenode.net, and are chaired by Julia Kreger (TheJulia) or Dmitry Tantsur (dtantsur).

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

Next Meeting

Meetings are held weekly. If one is cancelled, it will either be mentioned in the previous meeting or an email will be sent out to the openstack-discuss mailing list.

Agenda for next meeting

  • Announcements / Reminder
  • Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2019/
  • Review subteam status reports (capped at ten minutes)
  • Deciding on priorities for the coming week
  • Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
    • (TheJulia) Creating more categories for release notes
      • In looking through our release notes for this last release, I found the notes to be somewhat jumbled and wondered "What if all of the API items were in one place?", and "iLO" or "iDRAC".
      • Thoughts? It goes without saying that this would require some additional release notes clean-up at the end of cycle. We could treat ad-hoc and back-port items and at the end of cycle just retool the primary items before release.
  • Baremetal SIG
    • Whitepaper
    • User stories
  • RFE review
  • Open discussion

Previous meetings

Logs from previous meetings can be found here.

Related meetings

<none>