Network/Meetings
Date | ihrachys | regXboi | markmcclain | armax | mestery | mangelajo | garyk | rossella_s | dougwig | HenryG | carl_baldwin | amotoki | kevinbenton | amuller |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Oct-05-2015 | x | |||||||||||||
Oct-12-2015 | x | |||||||||||||
Oct-19-2015 | x | |||||||||||||
Oct-24-2015 | x | |||||||||||||
Nov-02-2015 | x | |||||||||||||
Nov-09-2015 | x | |||||||||||||
Nov-16-2015 | x | |||||||||||||
Nov-23-2015 | x | |||||||||||||
Nov-30-2015 | x | |||||||||||||
Dec-07-2015 | x | |||||||||||||
Dec-14-2015 | x | |||||||||||||
Dec-21-2015 | x | |||||||||||||
Dec-28-2015 | x | |||||||||||||
Jan-04-2016 | x |
Docs
- Discuss proofing devref and spec patches. (Sam-I-Am)
Open Items for Liberty: (reviews needed)
Networking Guide
- Discuss versioning. (Sam-I-Am)
- Discuss providing ability to attach VMs directly to public/external networks. (Sam-I-Am)
- Discuss networking guide meeting schedule.
- Etherpad: https://etherpad.openstack.org/p/networking-guide
- ToC: https://wiki.openstack.org/wiki/NetworkingGuide/TOC
- Gerrit: https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide
On Demand Agenda
We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:
- Topic for the meeting:
- Pagination support in the agents, Brian Haley, Dec 17th
- There are currently two reviews adding "pagination" to the RPC calls to sync networks and routers on the DHCP and L3 agents (respectively). One has chosen a config variable, the other has chosen a large number, with backoff logic on failure. We need to discuss a common way these can move forward so we don't have two different solutions for the same problem. Brian (haleyb) might not be available Monday, but Zhi Chang and Oleg Bondarev are the respective authors.
- https://review.openstack.org/#/c/234067/
- https://review.openstack.org/#/c/257100/
- <armax> IMO, consistency is paramount; besides the config variable approach has been shot down a few times before and the patch is blocked since it's a duplicate. To prevent these from happening, I think we should wrap this into some sort of utility method, but it's probably best to have fixes to the related issues merged separately, and reconcile them later (in whichever shape they end up being)
- There are currently two reviews adding "pagination" to the RPC calls to sync networks and routers on the DHCP and L3 agents (respectively). One has chosen a config variable, the other has chosen a large number, with backoff logic on failure. We need to discuss a common way these can move forward so we don't have two different solutions for the same problem. Brian (haleyb) might not be available Monday, but Zhi Chang and Oleg Bondarev are the respective authors.
- Pagination support in the agents, Brian Haley, Dec 17th
- Live Migration Notifiers for Nova/Neutron, Swaminathan Vasudevan, Jan 4th 2016
- Nova VM instances can migrate from one compute host to another compute host. When Nova VM migrates,there is no notification messages sent to neutron and also nova migration task manager does not verify if the destination host has all L3 networking setup in place. Because of this issue, we are seeing issues with VM migration having L3 connectivity, especially with DVR routers, since DVR routers create routers on demand in a reactive manner. We have been discussing this issue with respect to a launchpad bug and also have a couple of patches up for review.
- https://bugs.launchpad.net/neutron/+bug/1456073
- https://review.openstack.org/#/c/246898/
- https://review.openstack.org/#/c/259299/
- https://review.openstack.org/#/c/259171/
- https://review.openstack.org/#/c/260738/
- This work requires a joint effort from Nova and Neutron team to fix this problem. I would like to get the Neutron teams feedback on this and to assign a core team to work on this feature.
- Nova VM instances can migrate from one compute host to another compute host. When Nova VM migrates,there is no notification messages sent to neutron and also nova migration task manager does not verify if the destination host has all L3 networking setup in place. Because of this issue, we are seeing issues with VM migration having L3 connectivity, especially with DVR routers, since DVR routers create routers on demand in a reactive manner. We have been discussing this issue with respect to a launchpad bug and also have a couple of patches up for review.
- Live Migration Notifiers for Nova/Neutron, Swaminathan Vasudevan, Jan 4th 2016
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
- Older meeting notes are here: ../MeetingLogs.