Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Docs (emagana))
(Python Client (gongysh))
Line 39: Line 39:
 
Programming note - we will have FWaaS meeting on Wed 18:00 UTC (11 AM PDT). Main agenda will be pre-summit discussion.
 
Programming note - we will have FWaaS meeting on Wed 18:00 UTC (11 AM PDT). Main agenda will be pre-summit discussion.
  
=== Python Client (gongysh) ===
+
=== Python Client ===
 
* Release 2.3.1 released [https://pypi.python.org/pypi/python-neutronclient/2.3.1 PyPI] [http://tarballs.openstack.org/python-neutronclient/python-neutronclient-2.3.1.tar.gz tarball]
 
* Release 2.3.1 released [https://pypi.python.org/pypi/python-neutronclient/2.3.1 PyPI] [http://tarballs.openstack.org/python-neutronclient/python-neutronclient-2.3.1.tar.gz tarball]
  

Revision as of 20:54, 14 October 2013


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

Apologies for Absence

Agenda for Next Neutron Team Meeting

Announcements / Reminders:

  • --markmcclain (talk) 20:51, 14 October 2013 (UTC)
  • Release Candidate 2 is now available for testing.
    • This is intended to be the last RC. If you find a critical bug, please let me know.
  • Technical Committee Elections are open

Bugs

Critical Open Bugs

API Docs (salv-orlando)

Docs (emagana)

FWaaS (snaiksat)

Programming note - we will have FWaaS meeting on Wed 18:00 UTC (11 AM PDT). Main agenda will be pre-summit discussion.

Python Client

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

There will be a followup IRC meeting today immediately after this meeting to discuss common requirements for advanced services like service insertion/chaining, service agents, service VMs.

Previous meeting logs