Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Docs (emagana))
Line 48: Line 48:
 
** Get/Edit default quota through the API. Nova and Cinder support this feature and Horizon use it.
 
** Get/Edit default quota through the API. Nova and Cinder support this feature and Horizon use it.
 
** https://blueprints.launchpad.net/horizon/+spec/network-quotas : (begin fixed as bug fixes related to the above)
 
** https://blueprints.launchpad.net/horizon/+spec/network-quotas : (begin fixed as bug fixes related to the above)
 +
 +
=== 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) ===
 
=== Other team reports (e.g. Open Source Plugins) ===
 +
* Reminder: It is not the first to file, so if someone has an idea that is the same or similar please file anyway.
 +
* Blueprints should be accompany your summit proposal.  Proposals with blueprints are more likely to be accepted.
 +
  
 
=== Open Discussion ===
 
=== Open Discussion ===

Revision as of 20:53, 16 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

Docs (emagana)

Python Client (gongysh)

Networking in Horizon (amotoki)

(just a reminder)

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)

  • Reminder: It is not the first to file, so if someone has an idea that is the same or similar please file anyway.
  • Blueprints should be accompany your summit proposal. Proposals with blueprints are more likely to be accepted.


Open Discussion

Previous meeting logs