Meetings/Ironic
< Meetings
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 January 6th, 2014 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140106T1900).
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.
- Outstanding, in-progress or Action Item updates:
- Regular Topics
- blueprint status: https://blueprints.launchpad.net/ironic
- bug status: https://wiki.openstack.org/wiki/BugTriage
- progress towards graduation: https://review.openstack.org/#/c/59454/2/reference/incubation-integration-requirements
- Integration and testing
- devstack & tempest
- Tempest tests for Ironic API and Ironic gate jobs [Done!]
- Whiteboard for functional testing: https://etherpad.openstack.org/p/IronicDevstackTesting
- PoC https://review.openstack.org/62410 [DO NOT MERGE] -- this should be done in devstack, not ironic.
- diskimage-builder element - Out of date! (NobodyCam to update)
- HowTo now updated with ironicclient
- element_with_client
- devstack & tempest
- python-ironicclient
- How will the nova driver initiate a deploy?
- Nova driver
- NobodyCam has been working on the nova driver and has found:
- 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
- NobodyCam has been working on the nova driver and has found:
- API discussion:
- 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..)
- vendor_passthru
- open discussion
- Using an intent/two-phase lock or a thread to solve the race condition problem when setting node's power state (https://review.openstack.org/#/c/65327)
- Seamicro proposing SM15K product drivers for Ironic (Power, Vendor passthru, Network, Storage, PXE)
- Dict-like behavior should be removed or stay (https://review.openstack.org/#/c/64336)