Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Bugs)
(IceHouse OpenStack Design Summit)
Line 63: Line 63:
  
 
=== IceHouse OpenStack Design Summit ===
 
=== IceHouse OpenStack Design Summit ===
 +
* [http://summit.openstack.org 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.
 
* 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.
 
* Blueprints or etherpads should be accompany your summit proposal.  Proposals with blueprints are more likely to be accepted.

Revision as of 20:59, 30 September 2013


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

Apologies for Absence

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)

  • 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