Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Networking in Horizon (amotoki))
Line 50: Line 50:
  
 
* https://bugs.launchpad.net/neutron/+bug/1189671 default quota driver not suitable for production
 
* https://bugs.launchpad.net/neutron/+bug/1189671 default quota driver not suitable for production
** Is it landed in Havana? Otherwise Horizon needs to disable quota-update by default (to avoid unnecessary bug reports)
+
** I proposed a patch: https://review.openstack.org/#/c/49424/ .
 +
** I hope it lands in RC2. With Config Quota Driver extension, "Create Project" in Horizon always display a message "Failed to update quotas".
  
* Status
+
* RC1 status: all pending reviews related to Neutron were successfully merged.
** Many bug fixes related to Neutron were fixed in Horizon :-) https://launchpad.net/horizon/+milestone/havana-rc1
 
*** Quota does not coming from Neutron, Security Group, VPNaaS, LBaaS...  a bit exhausted
 
** LBaaS provider support has been merged.
 
** RC1 bug under review.
 
*** Firewall rules are not added to policy when rules are selected in create firewall policy: https://review.openstack.org/#/c/49019/
 
*** FWaaS removing UUID from tables and detail pages: https://review.openstack.org/#/c/45901/
 
  
 
* Quota related (just a reminder for Icehouse)
 
* Quota related (just a reminder for Icehouse)

Revision as of 13:32, 7 October 2013


The OpenStack Networking Team (Neutron) holds public meetings in #openstack-meeting. Everyone is encouraged to attend.

Apologies for Absence

  • mestery (10-7-2013)
  • Gary (garyk)
  • Salvatore (salv-orlando)

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)

  • RC1 status: all pending reviews related to Neutron were successfully merged.
  • Quota related (just a reminder for Icehouse)

IceHouse OpenStack Design Summit

  • Summit Submissions
  • 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