Difference between revisions of "Network/Meetings"
(→Bugs) |
(→Apologies for Absence) |
||
Line 5: | Line 5: | ||
== Apologies for Absence == | == Apologies for Absence == | ||
We expect core members to attend on a regular basis, especially during the meeting that is friendly to your timezone. If you can't, please add a note here. | We expect core members to attend on a regular basis, especially during the meeting that is friendly to your timezone. If you can't, please add a note here. | ||
+ | |||
+ | * amotoki -- will join late and cannot join first 20 minutes or some. | ||
=== Announcements / Reminders === | === Announcements / Reminders === |
Revision as of 13:26, 1 December 2015
Date | ihrachys | regXboi | markmcclain | armax | mestery | mangelajo | garyk | rossella_s | dougwig |
---|---|---|---|---|---|---|---|---|---|
Oct-05-2015 | x | ||||||||
Oct-12-2015 | x | ||||||||
Oct-19-2015 | x | ||||||||
Oct-24-2015 | x | ||||||||
Nov-02-2015 | x | ||||||||
Nov-09-2015 | x | ||||||||
Nov-16-2015 | x | ||||||||
Nov-23-2015 | x | ||||||||
Nov-30-2015 | x |
Docs (emagana)
Open Items for Liberty: (reviews needed)
Networking Guide
- Discuss providing ability to attach VMs directly to public/external networks. (Sam-I-Am)
- Etherpad: https://etherpad.openstack.org/p/networking-guide
- ToC: https://wiki.openstack.org/wiki/NetworkingGuide/TOC
- Gerrit: https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide
On Demand Agenda
We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:
- Gate hook enabled job: do we want another gate job?
- we need a job to enable QoS service and allow tempest scenarios for that.
- we have other services that may require something similar (flavor?)
- we have gate hook enabled job proposed for neutron gate: https://review.openstack.org/#/q/status:open+branch:master+topic:neutron-tempest-gate-hook,n,z
- are we ok with another job in gate? or we better enable services in existing integrated jobs?
- if we want it in integrated jobs, then we are forced to move qos devstack stuff back from devstack plugin into devstack (as per infra folks). While initially we were requested to do it vice versa.
- we need a job to enable QoS service and allow tempest scenarios for that.
- Topic for the meeting:
- <Topic title> <submitter> <date submitted>
- <brief description>
- <Topic title> <submitter> <date submitted>
- Topic for the meeting:
- Add here
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
- Older meeting notes are here: ../MeetingLogs.