Jump to: navigation, search


< Meetings
Revision as of 21:18, 17 November 2020 by Julia Kreger (talk | contribs) (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 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
    • Wallaby priorities document has merged
    • Etherpad updated to reflect new cycle priorities
  • Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2020/
  • 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) UEFI boot failures - What about when we can't add entries
      • tl;dr We've become aware of Converged Adapter firmware which injects new UEFI boot path entries for all luns presented to the machine, or at least that is what it is apparently doing by default. The issue here is there is no way to install grub or update the efi table without deleting an entry... which may not even work (we don't have direct hardware access), so the question was raised, what if there was a "ignore bootloader setup failure" ? Thoughs?
  • Baremetal SIG (https://etherpad.opendev.org/p/bare-metal-sig)
    • Next meeting scheduled for Tue Nov 10 2pm UTC <-- When is the December meeting?
  • RFE review
  • Open discussion

Previous meetings

Logs from previous meetings can be found here.

Related meetings