|
|
Line 18: |
Line 18: |
| [https://bugs.launchpad.net/neutron/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical Open Bugs] | | [https://bugs.launchpad.net/neutron/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical Open Bugs] |
| | | |
− | * [https://bugs.launchpad.net/neutron/+bug/1211915 Connection to neutron failed: Maximum attempts reached] - Needs an assigned author | + | * [https://bugs.launchpad.net/neutron/+bug/1211915 Connection to neutron failed: Maximum attempts reached] - marun |
| + | * [https://bugs.launchpad.net/neutron/+bug/1227091 ml2 fails to bind lbaas VIP] |
| | | |
| === API Docs (salv-orlando) === | | === API Docs (salv-orlando) === |
Revision as of 20:52, 23 September 2013
The OpenStack Networking Team (Neutron) holds public meetings in #openstack-meeting
. Everyone is encouraged to attend.
Apologies for Absence
Edgar (emagana)
Agenda for Next Neutron Team Meeting
Announcements / Reminders:
Bugs
Critical Open Bugs
API Docs (salv-orlando)
Docs (emagana)
FWaaS (snaiksat)
Bugs:
Python Client (gongysh)
Networking in Horizon (amotoki)
- Havana RC1 FFE blueprints
- FWaaS : The main patch has been merged. The subsequent patch for better navigation under review https://review.openstack.org/#/c/45901/ . Call for testing by Neutron team.
- VPNaaS : the main patch and subsequent patches have been merged. A better description of peer_id is under discussion with VPNaaS folks.
(just a reminder)
- Quota Extension in Neutron --> Delayed to Icehouse. Workaround has been merged for Havana (Limits are not displayed for Neutron resources)
Deprecation Announcements
ML2 has parity with OVS and Linuxbridge plugins. Should be deprecate those?
IceHouse OpenStack Design Summit
- Reminder: It is not the first to file, so if someone has an idea that is the same or similar please file anyway.
- Blueprints or etherpads should be accompany your summit proposal. Proposals with blueprints are more likely to be accepted.
- If you've got a mini topic please make a note in the proposal. This will help us allocate time.
- It is critical that have we have a healthy balance of Community Projects vs Shiny Features
- Community Features are things that benefit the whole community. For example: ML2, Metadata, DB migrations, API Handling
Other team reports (e.g. Open Source Plugins)
Open Discussion
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
- Older meeting notes are here: ../MeetingLogs.