Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

(→‎Agenda for next meeting)
(→‎Agenda for next meeting)
Line 9: Line 9:
 
== Agenda for next meeting ==
 
== Agenda for next meeting ==
 
* Greeting, roll-call and announcements.
 
* Greeting, roll-call and announcements.
−
** if you got a email about a Ironic hoodie but do not have your hoodie please chat with NobodyCam!
+
**  
 
* Outstanding, in-progress or Action Item updates:
 
* Outstanding, in-progress or Action Item updates:
−
** Post summit BluePrint clean up / redo!
+
**  
−
*** https://etherpad.openstack.org/p/IcehouseIronicNextSteps
 
−
*** https://wiki.openstack.org/wiki/Summit/Icehouse/Etherpads#Ironic
 
−
** ACTION(10/07/2013): devananda to write framework for nova-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/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
 
* Integration and testing
 
** devstack & tempest
 
** devstack & tempest
Line 30: Line 22:
 
**** [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]
−
* Python-IronicClient
+
* [https://github.com/openstack/python-ironicclient python-ironicclient]
−
** [https://github.com/openstack/python-ironicclient python-ironicclient]
+
*** How will the nova driver initiate a deploy?
−
*** How will NOVA initiate a DEPLOY?????
+
* [https://review.openstack.org/#/c/51328/ Nova driver]
−
** Nova bindings:
+
** NobodyCam has been working on the nova driver and has found:
−
*** https://review.openstack.org/#/c/51328/
+
*** Ironic will need to handle dhcp for pxe deploys
−
**** NobodyCam has been working on the nova driver and has found:
+
*** Ironic client will need a method to initiate a deploy
−
***** Ironic will need to handle dhcp for pie deploys
+
*** Should Ironic send PXE information directly to Neutron? Or, should this information flow through the Nova driver (this is how other hypervisor drivers work)?
−
***** Ironic client will need a method to initiate a deploy
 
 
* API discussion:
 
* API discussion:
 
** vendor_passthru
 
** vendor_passthru
Line 45: Line 36:
 
*** should we allow POST and GET?
 
*** should we allow POST and GET?
 
*** should data have any requirements / limits? (ie. size < 1k, must be json, etc..)
 
*** should data have any requirements / limits? (ie. size < 1k, must be json, etc..)
−
** How the API should expose instances
 
−
* Ironic: The Real Java Driver [https://github.com/NoBodyCam/ironic/blob/master/README.rst 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 [http://paste.openstack.org/show/T5bZNvawbA0r9D34Nk97/ 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
 
−
*** [http://summit.openstack.org/cfp/details/112 Let's talk about it at the summit!]
 
−
** how will Ironic fit in / scale with other openstack stories (Ie. TripleO)
 
 
* open discussion
 
* open discussion
  

Revision as of 21:50, 18 November 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 November 18th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131118T1900).

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.
  • Outstanding, in-progress or Action Item updates:
  • Integration and testing
  • 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
      • Should Ironic send PXE information directly to Neutron? Or, should this information flow through the Nova driver (this is how other hypervisor drivers work)?
  • 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..)
  • open discussion

Previous meetings

Logs from previous meetings can be found here.

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/Ironic&oldid=35770"