Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Networking in Horizon (amotoki))
(Open Discussion)
Line 64: Line 64:
  
 
=== Open Discussion ===
 
=== 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.
+
The "advance services" common requirements meeting will be on Tuesday 15.30 UTC (8.30 AM PDT). The agenda will be pre-summit discussion on topics like service insertion/chaining, service agents, service VMs, extension APIs.
  
 
== Previous meeting logs ==
 
== Previous meeting logs ==

Revision as of 18:03, 21 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)

  • Design Summit (Horizon session)
    • I haven't propose Neutron session in Horizon. If you feel we have topics to be discussed in Neutron-Horizon session.
    • Please let me know if you have a plan to add Neutron related Horizon BPs. It is important to share our plan with Horizon teams to prioritize BPs. I just would like to gather Neutron related topics for better input. (Note that there is no need to register BPs soon.)
  • Quota related (just a reminder for Icehouse)

IceHouse OpenStack Design Summit

  • Summit Submissions
  • Deadline is October 17th. If you have not filed, please do so now.
  • 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 than proposals with vague descriptions.
  • 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 Additional Features
    • Community Projects 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

The "advance services" common requirements meeting will be on Tuesday 15.30 UTC (8.30 AM PDT). The agenda will be pre-summit discussion on topics like service insertion/chaining, service agents, service VMs, extension APIs.

Previous meeting logs