Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(Weekly Ironic Project Team 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 November 25th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131125T1900).
+
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>
  
The related [[Meetings/TripleO|TripleO]] project has its team meeting on Tuesday at the same time, in the #openstack-meeting-alt room.
+
* [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 ==
* Greeting, roll-call and announcements.
+
* Announcements / Reminder
**  
+
** New goal landed for Wallaby - https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
* Outstanding, in-progress or Action Item updates:
+
** iLO CI will be down ~3 weeks due end of year shutdown. Power will be offline to the servers due to the shutdown. Please be extremely cautious with ilo related changes during this time window.
** consistent hashing to map instance to conductor
+
* Review action items from previous meeting: http://eavesdrop.openstack.org/meetings/ironic/2020/
* Integration and testing
+
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)
** devstack & tempest
+
* Deciding on priorities for the coming week
**** Tempest tests for Ironic API: https://review.openstack.org/#/c/48109
+
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')
**** Enable tempest tests in check and gate pipelines for Ironic: https://review.openstack.org/#/c/53917
+
** (TheJulia) UEFI boot failures - What about when we can't add entries
** diskimage-builder element - Out of date! (NobodyCam to update)
+
*** 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?
**** [https://wiki.openstack.org/wiki/Ironic#Using_Disk_Image_Builder HowTo] now updated with ironicclient
+
** (TheJulia) RBAC goal - https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
**** [https://github.com/NoBodyCam/ironic-element element_with_client]
+
*** This leads to the secure rbac disccussions
** Integration testing scheme.
+
*** Seems like we may need to consider additional validation code for cases like vif transactions and crossing the boundary between tasks. Meaning later tasks won't have context into the initial task.
**** PoC based on https://github.com/mirantis/devops
+
* Baremetal SIG (https://etherpad.opendev.org/p/bare-metal-sig)
**** Future openstack based scheme (requires PXE booting in nova libvirt driver https://blueprints.launchpad.net/nova/+spec/libvirt-empty-vm-boot-pxe).
+
** Next meeting scheduled for Tue December 8th 2pm UTC <-- When is the December meeting?
* [https://github.com/openstack/python-ironicclient python-ironicclient]
+
* RFE review
*** How will the nova driver initiate a deploy?
+
** https://storyboard.openstack.org/#!/story/2008380 Configdrive with virtual media ramdisk ISO deploy
* [https://review.openstack.org/#/c/51328/ Nova driver]
+
** https://storyboard.openstack.org/#!/story/2008366 BMC event framework
** NobodyCam has been working on the nova driver and has found:
+
* Open discussion
*** Ironic will need to handle dhcp for pxe deploys
 
*** Ironic client will need a method to initiate a deploy
 
*** PXE driver should update Neutron DHCP OPTs directly
 
** dkehn working on porting a portion of neutron client to Ironic
 
* API discussion:
 
** Exposing node deploy()
 
** vendor_passthru
 
*** HTTP response body
 
*** PUT "{data}" to /v1/nodes/{UUID}/vendor_passthru/{method}
 
*** initial work done: call conductor to validate. cast to start the work. return 202-in-progress. some functionality still to add.
 
*** should we allow POST and GET?
 
*** should data have any requirements / limits? (ie. size < 1k, must be json, etc..)
 
* open discussion
 
**  is the API right to expose a way to break the lock of a node? If so, where in the API it should live?
 
  
 
== 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>

Latest revision as of 14:43, 23 November 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>