Difference between revisions of "Meetings/Ironic"
< Meetings
(→Agenda for next meeting) |
(→Agenda for next meeting) |
||
| Line 34: | Line 34: | ||
* What to expect in J | * What to expect in J | ||
* Open Discussion: | * Open Discussion: | ||
| + | ** Getting metrics from other devices, we will do it on Nodes via IPMI and expose it back to ceilometer, what about other devices? | ||
** Adds max retry limit to sync_power_state task(should we rely on driver health or no when preventing infinite syncs?) https://review.openstack.org/#/c/77420/7/ironic/conductor/manager.py | ** Adds max retry limit to sync_power_state task(should we rely on driver health or no when preventing infinite syncs?) https://review.openstack.org/#/c/77420/7/ironic/conductor/manager.py | ||
** Functional/Integration testing of vendor drivers (Tempest?) | ** Functional/Integration testing of vendor drivers (Tempest?) | ||
Revision as of 12:31, 10 March 2014
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 project, an evolution of the 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.
Meetings are held in the #openstack-meeting room on irc.freenode.net at 19:00 UTC on Mondays, and chaired by either Devananda or NobodyCam. The next meeting is scheduled for February 24th, 2014 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140224T1900).
The related TripleO project has its team meeting on Tuesday at the same time, in the #openstack-meeting-alt room.
Agenda for next meeting
- Greeting, roll-call and announcements.
- Regular Topics:
- blueprint status check: https://blueprints.launchpad.net/ironic
- bug status check: https://wiki.openstack.org/wiki/BugTriage
- Call-outs:
- I-3 planning
- Graduation requirements
- nova driver needs to land
- we need full CI ( https://review.openstack.org/#/c/70348/ is a start )
- feature freeze
- what work / reviews need to be prioritized
- what can we realistically land
- code cleanup
- "with mock" vs "@mock"
- "node['property']" vs "node.property"
- Graduation requirements
- Sunnyvalle summary
- What have been postponed from icehouse to J
- What to expect in J
- Open Discussion:
- Getting metrics from other devices, we will do it on Nodes via IPMI and expose it back to ceilometer, what about other devices?
- Adds max retry limit to sync_power_state task(should we rely on driver health or no when preventing infinite syncs?) https://review.openstack.org/#/c/77420/7/ironic/conductor/manager.py
- Functional/Integration testing of vendor drivers (Tempest?)
- Driver architecture for Chassis object (Allow vendors to define behavior for the Chassis object like Auto node discovery etc)
