Jump to: navigation, search

Difference between revisions of "Network/Meetings"

(Neutron Tempest (anteaya))
(Neutron Tempest (anteaya))
Line 69: Line 69:
 
** EmilienM is working on https://review.openstack.org/#/c/55846/
 
** EmilienM is working on https://review.openstack.org/#/c/55846/
 
*** https://blueprints.launchpad.net/tempest/+spec/negative-tests
 
*** https://blueprints.launchpad.net/tempest/+spec/negative-tests
 +
*** tempest needs the negative test coverage from -neutron and needs a +1 from a neutron core to accept the patch
 
** rossella_s is working on https://review.openstack.org/#/c/56349/
 
** rossella_s is working on https://review.openstack.org/#/c/56349/
 
** Neutron Tempest code sprint: 2nd week of January in Montreal, QC, Canada
 
** Neutron Tempest code sprint: 2nd week of January in Montreal, QC, Canada

Revision as of 20:49, 18 November 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:

Bugs

Critical Open Bugs

API Docs (salv-orlando)

Docs (emagana)

FWaaS (snaiksat)

Programming note - we will have weekly FWaaS meetings on Wed 18:00 UTC (11 AM PDT). Main agenda for the next two weeks will be the 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

Neutron Tempest (anteaya)

Other team reports (e.g. Open Source Plugins)

Open Discussion

The "advance services" common requirements meeting will be weekly 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