Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(Agenda for next meeting)
(Agenda for next meeting)
Line 23: Line 23:
 
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)
 
* Stuck specs (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] Is network_interface part of a hardware_type's interface?
 +
*** In the multi-tenant networking feature patch [1], a 'network interface' is added to the base driver class. The idea was to code this so that when the driver composition work was done [2], this new network_interface would be one of the hardware_type's *_interfaces. HOWEVER, there are some inconsistencies/issues:
 +
**** the patch [1] proposes a 'default_network_interface', which is inconsistent with the driver reform spec, in particular: "For hardware types setting <interface_name>_interface field to None means using the vendor default defined in the hardware type. If the vendor default is None, the interface will be disabled."
 +
**** Makes me/dtantsur wonder whether network_interface should be part of a hardware_type's interface at all, since it is really operator/environment driven.
 +
****[1] https://review.openstack.org/#/c/285852
 +
****[2] http://specs.openstack.org/openstack/ironic-specs/specs/approved/driver-composition-reform.html
 
* RFE review
 
* RFE review
 
* Open discussion
 
* Open discussion

Revision as of 14:44, 11 July 2016

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 1700 UTC on Mondays, are held in the #openstack-meeting-3 room on irc.freenode.net, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).

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

No meeting on July 4th since that is a US holiday and a lot of people will be away that day.

The next meeting will be on July 11, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160711T1700).

Agenda for next meeting

  • Announcements / Reminders
  • Review subteam status reports (capped at ten minutes)
  • Stuck specs (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')
    • [rloo] Is network_interface part of a hardware_type's interface?
      • In the multi-tenant networking feature patch [1], a 'network interface' is added to the base driver class. The idea was to code this so that when the driver composition work was done [2], this new network_interface would be one of the hardware_type's *_interfaces. HOWEVER, there are some inconsistencies/issues:
  • RFE review
  • Open discussion

Previous meetings

Logs from previous meetings can be found here.

Related meetings