Revision as of 13:50, 19 December 2013

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. The next meeting is scheduled for December 16th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131216T1900).

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:
  • https://blueprints.launchpad.net/ironic/+spec/instance-mapping-by-consistent-hash
• 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: https://review.openstack.org/#/c/48109
      • Enable tempest tests in check and gate pipelines for Ironic: https://review.openstack.org/#/c/53917
  • diskimage-builder element - Out of date! (NobodyCam to update)
    • • HowTo now updated with ironicclient
      • element_with_client
  • Integration testing scheme.
    • • PoC https://review.openstack.org/62410
• 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
• API discussion:
  • Should chassis_uuid be a mandatory field in the node resource? (It might complicate the migration/auto-discovery)
  • 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

Logs from previous meetings can be found here.