Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(Agenda for next meeting)
(Agenda for next meeting)
Line 27: Line 27:
* Python-IronicClient  
* Python-IronicClient  
** [https://github.com/openstack/python-ironicclient python-ironicclient]
** [https://github.com/openstack/python-ironicclient python-ironicclient]
** Are we ready for nova bindings?
** Nova bindings:
*** https://review.openstack.org/#/c/51328/
* API discussion:
* API discussion:
** vendor_passthru
** vendor_passthru

Revision as of 17:58, 14 October 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 October 14th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=2013114T1900).

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.
    • Hoodies are still in process.. (Thank you: Mark AtWood and HP for these)
  • Hong Kong design summit: discuss summit papers
  • Outstanding, in-progress or Action Item updates:
    • ACTION(10/07/2013): devananda to write framework for noav-ironic driver
    • ACTION(10/07/2013): lucasagomes to add CLI docs to ironic developer doc pages
    • ACTION(9/30/2013): romcheg to propose a non-gating job to -infra
    • ACTION(9/30/2013): romcheg to add python-ironicclient to devstack install scripts
    • ACTION(9/16/2013): devananda to think about a Transifex project for Ironic
    • ACTION(9/16/2013): romcheg looking at Ukrainian and Russian transifex translations
    • ACTION(9/16/2013): romcheg Check how i18n conplient we are
  • Integration and testing
  • Python-IronicClient
  • 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..)
    • WSME reponse codes
  • Ironic: The Real Java Driver what_is_it?
  • Food For Thought:
    • How will Ironic integrate / interface with nova?
      • new driver to be written: nova/virt/ironic/driver.py
    • 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.
    • Should Ironic send PXE information directly to Neutron? Or, should this information flow through the Nova driver (this is how other hypervisor drivers work)?
    • 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
    • how will Ironic fit in / scale with other openstack stories (Ie. TripleO)
  • open discussion

Previous meetings

Logs from previous meetings can be found here.