Revision as of 19:00, 30 September 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 September 30th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130930T1900).

Following this meeting is the TripleO team meeting, which often also discusses issues related to bare metal deployments.

Agenda for next meeting

• Greeting, roll-call and announcements.
  • Hong Kong design summit: call for papers!
    • submit here!
    • view proposed Ironic talks here!
• Integration and testing
  • diskimage-builder element - on hold?
    • Hyjack OoO to test Ironic
      • HowTo now updated with ironicclient
      • element_with_client
    • Review 48541 : correct register-endpoint script
• Outstanding or in-progress tasks:
  • python-ironicclient
    • Yes we have a client repo too! [1]
  • What should Ironic's service_type be when registering with keystone?
    • baremetal
  • Ironic: The Real Java Driver what_is_it?
• API discussion:
  • vendor_passthru: return values and HTTP methods allowed for this resource 41976 Merged! Woot!
    • decided that clients will do something like POST '{"foo": "bar"}' /nodes/1/vendor_passthru/<method>
      • where method doesn't exist in the api code
      • allow POST and GET
      • rpc side? general 'notify' or single 'passthru' method?
        • single passthru
      • what should it return?
        • return something like 202 and say that the request is fine but it is async so there's no ret value
        • use GET to retrive status
      • we are not introspecting the user data at all!
        • only driver should verify data
        • should data have any requirements / limits? (ie. size < 1k, must be json, etc..)
• Food For Thought:
  • How will Ironic integrate / interface with nova?
    • can we replace nova baremetal incrementally?
      • No. Once we have a python client library, a nova driver can be written that replaces the old baremetal driver.
  • How will Ironic handle networking / Ip's / neutron?
    • Don's ( dkehn ) Neutron patches have Landed! How will this impact Ironic?
      • This work is being integrated in the current Nova driver. That will also need to be integrated in the nova-ironic driver.
  • Keystone options not reflected in sample.conf Missing Options
  • How should we inform deploy ramdisk of ironic's api url?
    • Kernel param
    • Dhcp option tag
    • Dns name
    • Other?
  • How will Ironic handle > then 1 conductor
    • Let's talk about it at the summit!
  • how will Ironic fit in / scale with other openstack stories (Ie. TripleO)
• open discussion

Previous meetings

Logs from previous meetings can be found here.