Jump to: navigation, search

Difference between revisions of "Meetings/Ironic"

m (Weekly Ironic Project Team Meeting)
(Weekly Ironic Project Team Meeting: update info about tripleo meeting)
Line 5: Line 5:
 
Meetings are held in the <code><nowiki>#openstack-meeting</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code> at 19:00 UTC on Mondays. The next meeting is scheduled for November 25th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131125T1900).
 
Meetings are held in the <code><nowiki>#openstack-meeting</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code> at 19:00 UTC on Mondays. The next meeting is scheduled for November 25th, 2013 (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131125T1900).
  
Following this meeting is the [[Meetings/TripleO|TripleO team meeting]], which often also discusses issues related to bare metal deployments.
+
The related [[Meetings/TripleO|TripleO]] project has its team meeting on Tuesday at the same time, in the #openstack-meeting-alt room.
  
 
== Agenda for next meeting ==
 
== Agenda for next meeting ==

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

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:
  • 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.