Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(Agenda for next meeting)
(Agenda for next meeting)
Line 14: Line 14:
 
*** [http://summit.openstack.org/cfp/topic/7 view proposed Ironic talks here!]
 
*** [http://summit.openstack.org/cfp/topic/7 view proposed Ironic talks here!]
 
* Integration and testing
 
* Integration and testing
 +
** devstack & tempest
 
** diskimage-builder element - on hold?  
 
** diskimage-builder element - on hold?  
*** Hyjack OoO to test Ironic
 
 
**** [https://wiki.openstack.org/wiki/Ironic#Using_Disk_Image_Builder HowTo] now updated with ironicclient
 
**** [https://wiki.openstack.org/wiki/Ironic#Using_Disk_Image_Builder HowTo] now updated with ironicclient
 
**** [https://github.com/NoBodyCam/ironic-element element_with_client]
 
**** [https://github.com/NoBodyCam/ironic-element element_with_client]
*** Review [https://review.openstack.org/48541 48541] : correct register-endpoint script
+
* Outstanding or in-progress tasks:  
* Outstanding or in-progress tasks:
+
** [https://github.com/openstack/python-ironicclient | python-ironicclient]
** python-ironicclient
 
*** Yes we have a client repo too! [https://github.com/openstack/python-ironicclient]
 
** What should Ironic's service_type be when registering with keystone?
 
*** baremetal
 
** Ironic: The Real Java Driver [https://github.com/NoBodyCam/ironic/blob/master/README.rst what_is_it?]
 
 
* API discussion:
 
* API discussion:
** vendor_passthru: return values and HTTP methods allowed for this resource [https://review.openstack.org/#/c/41976 41976] '''Merged! Woot!'''
+
** vendor_passthru
*** decided that clients will do something like  POST '{"foo": "bar"}' /nodes/1/vendor_passthru/<method>
+
*** PUT "{data}" to /v1/nodes/{UUID}/vendor_passthru/{method}
**** where method doesn't exist in the api code
+
*** initial work done: call conductor to validate. cast to start the work. return 202-in-progress. some functionality still to add.
**** allow POST and GET
+
*** should we allow POST and GET?
**** rpc side? general 'notify' or single 'passthru' method?
+
*** should data have any requirements / limits? (ie. size < 1k, must be json, etc..)
***** single passthru
+
* Ironic: The Real Java Driver [https://github.com/NoBodyCam/ironic/blob/master/README.rst what_is_it?]
**** 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:
 
* Food For Thought:
 
** How will Ironic integrate / interface with nova?
 
** How will Ironic integrate / interface with nova?
*** can we replace nova baremetal incrementally?
+
*** new driver to be written: nova/virt/ironic/driver.py
**** 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?
 
** How will Ironic handle networking / Ip's / neutron?
 
*** Don's ( dkehn ) Neutron patches have Landed! How will this impact Ironic?  
 
*** 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.
 
**** 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 [http://paste.openstack.org/show/T5bZNvawbA0r9D34Nk97/ Missing Options]
 
** Keystone options not reflected in sample.conf [http://paste.openstack.org/show/T5bZNvawbA0r9D34Nk97/ Missing Options]
 
** How should we inform deploy ramdisk of ironic's api url?
 
** How should we inform deploy ramdisk of ironic's api url?

Revision as of 20:57, 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.
  • Integration and testing
  • Outstanding or in-progress tasks:
  • API discussion:
    • vendor_passthru
      • 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..)
  • 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.