Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Docs (emagana))
Line 32: Line 32:
 
** [https://blueprints.launchpad.net/openstack-manuals/+spec/neutron-ml2-docs ML2 Doc Blueprint]
 
** [https://blueprints.launchpad.net/openstack-manuals/+spec/neutron-ml2-docs ML2 Doc Blueprint]
 
* [https://bugs.launchpad.net/openstack-manuals/+bug/1202967 Metering Docs]
 
* [https://bugs.launchpad.net/openstack-manuals/+bug/1202967 Metering Docs]
 +
 +
=== FWaaS (snaiksat) ===
 +
Bugs:
 +
[https://review.openstack.org/#/c/43936 Allow sharing of firewall rules and policies in policy.json]
 +
[https://review.openstack.org/#/c/47659 Fix FWaaS plugin to allow one firewall per tenant]
  
 
=== Python Client (gongysh) ===
 
=== Python Client (gongysh) ===

Revision as of 19:40, 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

Docs (emagana)

FWaaS (snaiksat)

Bugs: Allow sharing of firewall rules and policies in policy.json Fix FWaaS plugin to allow one firewall per tenant

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)

Open Discussion

Previous meeting logs