Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Docs (emagana))
Line 22: Line 22:
 
=== Docs (emagana)===
 
=== Docs (emagana)===
 
* Current list of bugs against neutron docs: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=neutron
 
* Current list of bugs against neutron docs: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=neutron
 +
* API doc bugs: https://bugs.launchpad.net/openstack-api-site/+bugs?field.tag=netconn-api
 
* Mellanox Plugin - Done!
 
* Mellanox Plugin - Done!
 
* Chasing bugs in openstack-manuals (openstack-network-connectivity-admin) - WIP
 
* Chasing bugs in openstack-manuals (openstack-network-connectivity-admin) - WIP

Revision as of 21:13, 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