Revision as of 13:54, 13 May 2015

Meetings

• Weekly Wednesdays at 1400 UTC
• IRC channel: #openstack-meeting-3
• Chair: sc68cal / ajo (Sean Collins / Miguel Ángel Ajo)

Announcements

• Etherpad from summit: https://etherpad.openstack.org/p/neutron-qos
• Coding Sprint: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint

Blueprints

• https://review.openstack.org/#/c/88599/

Logs and Minutes

Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/neutron_qos

Agenda

2015-05-13 14:00 UTC

• Current shape of the spec: single api endpoint for rules, https://review.openstack.org/#/c/88599/11/specs/liberty/qos-api-extension.rst
• New spec for the ML2/OVS bits: https://review.openstack.org//#/c/182349/
• Focusing on egress for now
• Summit session planning: https://etherpad.openstack.org/p/YVR-neutron-qos

2015-05-06 14:00 UTC meeting log

• API microversioning spec implications
• Changes to the QoS API spec: scoping into bandwidth limiting
• Changes to the QoS API spec: modeling of rules (class hierarchy) (Guarantee split out)
• Discuss multiple API end points (per rule type) vs single.
• Traffic Classification considerations
• The ingress vs egress differences and issues.

2015-04-29 14:00 UTC meeting log

• High level api/cmdline overview, to share with operators. https://etherpad.openstack.org/p/neutron-qos-api-preview
• Update on latest changes.
• Service plugin discussion
• Ideas for generic RPC mechanisms to subscribe for "port related updates"
• Ideas for low-level implementation: "qos_driver" interface a'la firewall_driver ?
• ML2-OVS, ML2-SRIOV, ML2-LB specs
• IPv6 flow labels proposal conflict with other proposed IPv6 flow labels usage (tenant isolation -ianwells-)

2015-04-21 14:00 UTC meeting log

• Anounce coding sprint for QoS: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint
• Update to the API spec: https://review.openstack.org/#/c/88599
• Design as a service plugin: https://wiki.openstack.org/wiki/Neutron/ServiceTypeFramework for better separation?
• Separate specs for common ml2 bits + ml2-sriov design, ml2-ovs, somebody for linux bridge?
• QoS types we can think of: bandwidth limiting, guarantees, traffic marking, traffic shaping (per proto flags), ... what are we yet missing?
• Ratelimiting vs ratecontrol (max/min) ?
• Share API design with operators to get feedback.

2015-04-15 14:00 UTC meeting log

• Coding sprint for QoS: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint
• Free discussion / use case gathering
• Agenda definition for first meeting : https://etherpad.openstack.org/p/neutron-qos-agenda
• Flavor framework coordination

• how do flavors work? , does QoSes fit as flavors?
• or can they be used to enforce QoS policies on tenants?

Meeting Commands

/join #openstack-meeting-3
#startmeeting neutron_qos
#topic Announcements
#link https://wiki.openstack.org/wiki/Meetings/NeutronQoS

#action ajo will get something specific done this week.
...

#undo
#endmeeting