Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Apologies for Absence)
(Docs (emagana))
Line 53: Line 53:
=== Docs (emagana)===
=== Docs (emagana)===
Open Items for Juno:
Open Items for Kilo:
* https://etherpad.openstack.org/p/neutron-docs-juno
* New networking diagrams for DVR: https://github.com/ionosphere80/openstack-networking-guide/blob/master/scenario-dvr/scenario-dvr.md
(Need more volunteers)
High Priority Tickets:
Networking Guide:
* https://bugs.launchpad.net/openstack-manuals/+bug/1378148 - Unassigned
* ToC: https://wiki.openstack.org/wiki/NetworkingGuide/TOC
* https://bugs.launchpad.net/openstack-manuals/+bug/1380585 - Darren Chen
* Gerrit: https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide
* https://bugs.launchpad.net/openstack-manuals/+bug/1364283 - Edgar Magana
* https://bugs.launchpad.net/openstack-manuals/+bug/1357457 - Gauvain Pocentek
* Current list of bugs against neutron docs: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=neutron
** (review notes from Ryan Moats during mid-cycle sprint):
***https://bugs.launchpad.net/openstack-manuals/+bug/1336888 - Fix Released
***https://bugs.launchpad.net/openstack-manuals/+bug/1327700 - Invalid
***https://bugs.launchpad.net/openstack-manuals/+bug/1323894 - Unassigned (Low)
***https://bugs.launchpad.net/openstack-manuals/+bug/1321320 - Duplicated
***https://bugs.launchpad.net/openstack-manuals/+bug/1321037 - it is unclear to me where to document this - should we have specific ODL documentation?
***https://bugs.launchpad.net/openstack-manuals/+bug/1278281 - is there a patch for adding the "How to Perform an Upgrade from IceHouse to Juno" chapters to the ops guide?  if not, what is the strategy for adding these chapters?
***https://bugs.launchpad.net/openstack-manuals/+bug/1259811 - I wasn't able to find a grizzly branch within github, do we have one or is this going to require re-entering the necessary text?
***https://bugs.launchpad.net/openstack-manuals/+bug/1327489 - I was unable to find any reference to flows other than troubleshooting in the ops guide and this (imho) doesn't fit there
=== On Demand Agenda ===
=== On Demand Agenda ===

Revision as of 20:58, 8 December 2014

Meeting time: The OpenStack Networking Team (Neutron) holds public meetings alternating between Mondays at 2100 UTC (#openstack-meeting) and Tuesdays at 1400 UTC (#openstack-meeting). Everyone is encouraged to attend.

Apologies for Absence

  • Brent Eagles (beagles) - I've volunteered tech skills for an event. I've added some items to the bugs section.

Agenda for Next Neutron Team Meeting

Tuesday (12/16/2014) at 1400 UTC on #openstack-meeting

Announcements / Reminders


New issues discovered recently/having most hits in the gate:

    • [1] Race to delete shared subnet in Tempest neutron full jobs
    • [2] Failure to allocate tunnel id when creating networks concurrently
    • [3] br-tun lost ports/flows if openvswitch restart
    • [4] Security group rules errorneously applied to all ports having same ip addresses in different networks
    • [5] ping still working after security group rule is created, updated, or deleted (related to previous one)

These bugs are in nova but are related to neutron. It would be great if we could get neutron reviews on:

    • Merged [6] Remove unneeded call to fetch network info on shutdown - arosen
    • Merged [7] remove unneeded call to network_api on detach_interface - arosen
    • Merged [8] remove unneeded call to network_api on rebuild_instance - arosen
    • Merged [9] Optimize validate_networks to query neutron only when needed - arosen
    • [10] deallocate_for_instance should delete all neutron ports on error - arosen
    • [11] Fix port_security_enabled neutron extension - arosen
    • [12] Fix pre-created ports in neutron from being deleted by nova - arosen

This issue is still happening

As suggested in last weeks meeting, there is a new BZ https://bugs.launchpad.net/neutron/+bug/1398566. This needs confirmation so it can be given appropriate status. In the live systems where it shows up it is rather awkward to work around as you basically have to shutdown all of the agents before restarting the API server. I've put a patch up for review.

The steps to reproduce are very timing and order dependent. I've created video demonstration on how I've simulated a loaded environment and the steps to reproduce, a discussion of Vincent Untz's patch that my patch is derived from and a demonstration of the fix http://youtu.be/-nL1gyL3KL8 and http://youtu.be/XUY82_a7k5Q . I apologize for the blurry text quality - but the HD transcoding is completed now so if you set the playback to 1080p, it is what you see IRL.

Docs (emagana)

Open Items for Kilo:

Networking Guide:

On Demand Agenda

Previous meeting logs