Jump to: navigation, search

Meetings/Ironic-neutron

< Meetings
Revision as of 16:33, 31 July 2015 by Sukhdev (talk | contribs)

Weekly meeting on Mondays at 1600 UTC on #openstack-meeting-4

Tracking Ironic/Neutron integration Discussions

In this meeting we will discuss the integration between Ironic and Neutron (ML2). Following two etherpads are the for the background purposes


Meeting August 3, 2015

Agenda

  • Open Discussion
    • Please add if you would like to discuss anything


Meeting July 27, 2015

Agenda

  • Open Discussion
    • Please add if you would like to discuss anything


Meeting July 20, 2015

Agenda

  • Open Discussion
    • Please add if you would like to discuss anything


Meeting July 13, 2015

Agenda

  • Open Discussion
    • Please add if you would like to discuss anything


Meeting July 6, 2015

Agenda

  • Open Discussion
    • Please add if you would like to discuss anything


Meeting June 29, 2015

Agenda

(Opened up the doc to Edit for everyone - please feel free to post comments)

  • Open Discussion
    • A random thought based upon discussion with Armando during Neutron mid-cycle sprint -
      • possibility of using device owner for Bare metal hosts as " Compute:Ironic"
    • Please add if you would like to discuss anything

Meeting June 22, 2015

Agenda


Meeting June 15, 2015

Agenda

Meeting June 8, 2015

Agenda

Initial Kick off Meeting June 1, 2015

Agenda

  • Announcements
    • We need contributors to help with implementation. Please identify as to what will you be willing to help with
  • Discuss Team Goals
  • Progress on the spec for modification to Ironic Port API
  • Nova/Neutron interaction proposal (jroll) -- let's add an optional parameter to the Neutron API to control whether or not to plumb the network immediately, and use it like this https://review.openstack.org/#/c/186855/
  • Open Discussion
    • Please add if you would like to discuss anything


Team Charter/Goals - for Liberty release

  • Create a spec with the details of Bare Metal physical connectivity information model and Ironic Port API modification
    • Generate a patch to implement this spec
  • Define the details of the network flip orchestration logic
    • Finalize as to what is the best way to refactor Nova code to facilitate this functionality
  • CI for testing this functionality
    • this includes a plan as well implementation
  • Initially this feature will be 'experimental' for Liberty for both Neutron and Ironic.
    • As the feature stabilizes in both Ironic and Neutron in 'M' release, we will move it out of 'experimental'.

Initial Charter will not cover the following

  • Automated discovery of the ports physical connectivity
    • Initial functionality will be tested by using modified Ironic Port IP to specify the physical connectivity information

Long term items (not covered in initial charter)

  • Enhancement to the flavor type based upon the Lag'ed ports for Bare metal servers - for better bandwidth
  • Ability for an operator to specify/select a port (from multiple ports connecting a BM server) to connect to a given network - e.g. an option in "nova boot" to specify a specific port
  • We will consider utilizing other ways to pass the physical connectivity information to Neutron (if it presents additional flexibility to support additional features) - such as resource labels, using an Ironic specific table in port-binding, etc.
  • Feel free to add additional items

Previous meetings Logs