Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(Agenda for next meeting)
(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 [[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 September 9th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130909T1900).
+
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
* Greeting and roll-call.
+
** Open Infrastructure Summit next week - October 19-23rd
* Improvements of testing
+
** PTG the following week - October 26th to 30th
** Devstack integration
+
*** Wallaby PTG etherpad - https://etherpad.opendev.org/p/ironic-wallaby-ptg
*** Review [https://review.openstack.org/#/c/41053/ 41053] LANDED!
+
*** Please add details to your proposals!
** diskimage-builder element
+
** Victoria final releases in the community expected on the 14th. Please keep an eye out for bug fixes this week.
*** Review [https://review.openstack.org/44494 44494] LANDED!
+
** PTL on PTO first week in November.
*** Review [https://review.openstack.org/44500 44500] update.
+
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2020/
*** Review [https://review.openstack.org/44516 44516] update.
+
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
*** Review [https://review.openstack.org/44566 44566] LANDED!
+
* Deciding on priorities for the coming week
* Outstanding or in-progress tasks:
+
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
** Keystone authentication. admin-only done. v3 domains not working yet.
+
* Baremetal SIG (https://etherpad.opendev.org/p/bare-metal-sig)
** PXE driver
+
** Next meeting scheduled for Tue Nov 10 2pm UTC
*** image services patch LANDED! [https://review.openstack.org/#/c/35272/ 35272]
+
* RFE review
*** Review [https://review.openstack.org/#/c/33616/ 33616] LANDED!
+
** (xinliang) [RFE] Boot from volume -- PXE iSCSI boot  Story: https://storyboard.openstack.org/#!/story/2008023 spec: https://review.opendev.org/759839
** python-ironicclient
+
* Open discussion
*** Yes we have a client repo too! [https://github.com/openstack/python-ironicclient Repo]
+
** https://review.opendev.org/#/c/756708/ `baremetal vs openstack baremetal`
*** initial import [https://review.openstack.org/#/c/45144 45144]
+
** Weekly meeting (Oct19 / Oct 26) should we skip?
*** intra review to enable pypy and python 3.3 as VOTING checks!! [https://review.openstack.org/#/c/45327 45327]
 
* API discussion:
 
** PUT vs PATCH in the API (PUT AND PATCH)
 
*** Review [https://review.openstack.org/42690 42690]
 
** vendor_passthru: return values and HTTP methods allowed for this resource [https://review.openstack.org/#/c/41976 41976]
 
*** decided that clients will do something like  POST '{"foo": "bar"}' /nodes/1/vendor_passthru/<method>
 
**** where method doesn't exist in the api code
 
**** allow POST and GET
 
**** rpc side? general 'notify' or single 'passthru' method?
 
***** single passthru
 
**** what should it return?
 
***** return something like 202 and say that the request is fine but it is async so there's no ret value
 
***** use GET to retrive status
 
**** we are not introspecting the user data at all!
 
*****  only driver should veryfy data
 
***** should data have any requirments / limits? (ie. size < 1k, must be json, etc..)
 
* Food For Thought:
 
** How will Ironic integrate / interface with nova?
 
*** can we replace nova baremetal incrementally?
 
** How will Ironic handle networking / Ip's / neutron?
 
** Use models instead of migrations for creating a DB.
 
** Keystone options not reflected in sample.conf [http://paste.openstack.org/show/T5bZNvawbA0r9D34Nk97/ Missing Options]
 
** Inform node of ironic's api url?
 
*** Kernel param
 
*** Dhcp option tag
 
*** Dns name
 
*** Other?
 
** How will Ironic handle > then 1 conductor
 
*** can / should we pin chassis and nodes to a conductor?
 
*** How will Ironic handle HA and scaling over all?
 
*** how will Ironic fit in / scale with other openstack stories (Ie. TripleO)
 
* 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 10:03, 28 October 2020

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

Previous meetings

Logs from previous meetings can be found here.

Related meetings

<none>