Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(Agenda for next meeting)
(378 intermediate revisions by 18 users not shown)
Line 1: Line 1:
 
= Weekly Ironic Project Team 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 Dmitry Tantsur (dtantsur), Jim Rollenhagen (jroll), and Julia Kreger (TheJulia).
+
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).
  
 
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>
Line 14: Line 14:
 
== Next Meeting ==
 
== Next Meeting ==
  
The next meeting will be on March 13, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170313T1700).
+
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 / Reminders
+
* Announcements / Reminder
** Reminder about https://etherpad.openstack.org/p/ops-adopt-a-project-pike
+
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2019/
** Pike priorities up: http://specs.openstack.org/openstack/ironic-specs/priorities/pike-priorities.html
 
 
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
 
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
 
* Deciding on priorities for the coming week
 
* Deciding on priorities for the coming week
** Stuck specs for current and potential priorities
 
** Appointing a bug liaison for the next week
 
* 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')
 
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** (rloo) Boston summit/forum brainstorming: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html
+
** (TheJulia) Creating more categories for release notes
** (soliosg) Impressions about third party CI gate jobs that usually fail, reasons they fail, and how we can help to fix them.
+
*** 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".
** '''(jlvillal)''' Moving 'enable_plugin ironic' out of ironic/devstack/upgrade/settings. This is because we should not have it there as it won't work for multi-node grenade. Problem is that it breaks the gate when we remove it.
+
*** 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.
*** My proposal on how to do this:
+
* Baremetal SIG
**** Merge the change to '''master''' ironic to only enable the ironic devstack plugin in grenade if it is not yet enabled https://review.openstack.org/#/c/444335/
+
** Whitepaper
**** Backport and merge https://review.openstack.org/#/c/444335/ to stable/ocata and stable/newton
+
** User stories
**** Change project-config to add ‘enable_plugin ironic’ to the grenade jobs. https://review.openstack.org/#/c/443348/
 
**** Remove all enabling of the ironic devstack plugin in the grenade settings file: https://review.openstack.org/#/c/444509/
 
**** Profit...
 
** (dtantsur) Status check on having a local copy of tempest manager.py (https://review.openstack.org/#/c/439252/)
 
 
* RFE review
 
* RFE review
 +
** https://storyboard.openstack.org/#!/story/2003594
 
* Open discussion
 
* Open discussion
  
Line 45: Line 38:
 
== Related meetings ==
 
== Related meetings ==
  
* Boot From Volume meeting: TBD, poll at http://doodle.com/poll/qwhnpqazmf7fn5ik
+
<none>
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui
 

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>