Meetings/Ironic-neutron
Weekly meeting on Mondays at 1600 UTC on #openstack-meeting-4
Contents
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
- https://etherpad.openstack.org/p/YVR-neutron-ironic
- https://etherpad.openstack.org/p/liberty-ironic-network-isolation
Note: Items to be considered for long term solution, but, are not covered in initial charter are listed [Long term items (not covered in initial charter) here]
Meeting June 15, 2015
Agenda
- Announcements
- Thanks to Jim and Laura for pushing updated versions of the specs.
- If anybody wants to make any announcement, feel free to add here
- Specs under review
- Spec for Physical connectivity information as well as API
- Spec for Network Flip
- Open Discussion
- Please add if you would like to discuss anything
Meeting June 8, 2015
Agenda
- Announcements
- Priority for this week is to finalize the specs so that we can move to the implementation
- Specs under review
- Spec for Physical connectivity information as well as API
- Spec for Network Flip
- Open Discussion
- Please add if you would like to discuss anything
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
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
- Feel free to add additional items
