Difference between revisions of "Meetings/QoS"
< Meetings
m (→Agenda) |
(→Agenda) |
||
Line 12: | Line 12: | ||
= Agenda = | = Agenda = | ||
+ | '''2015-05-06''' 14:00 UTC | ||
+ | * [http://lists.openstack.org/pipermail/openstack-dev/2015-May/063382.html API microversioning] spec implications | ||
+ | * [https://review.openstack.org/#/c/88599/9..10/specs/liberty/qos-api-extension.rst Changes to the QoS API spec]: scoping into bandwidth limiting | ||
+ | * [https://review.openstack.org/#/c/88599/9..10/specs/liberty/qos-api-extension.rst 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 | '''2015-04-29''' 14:00 UTC | ||
− | |||
* High level api/cmdline overview, to share with operators. https://etherpad.openstack.org/p/neutron-qos-api-preview | * High level api/cmdline overview, to share with operators. https://etherpad.openstack.org/p/neutron-qos-api-preview | ||
* Update on latest changes. | * Update on latest changes. | ||
Line 22: | Line 30: | ||
* ML2-OVS, ML2-SRIOV, ML2-LB specs | * ML2-OVS, ML2-SRIOV, ML2-LB specs | ||
* IPv6 flow labels proposal conflict with other proposed IPv6 flow labels usage (tenant isolation -ianwells-) | * IPv6 flow labels proposal conflict with other proposed IPv6 flow labels usage (tenant isolation -ianwells-) | ||
+ | |||
'''2015-04-21''' 14:00 UTC (please note it was 2015-04-22 previously) | '''2015-04-21''' 14:00 UTC (please note it was 2015-04-22 previously) | ||
− | |||
* Anounce coding sprint for QoS: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint | * 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 | * Update to the API spec: https://review.openstack.org/#/c/88599 |
Revision as of 13:19, 6 May 2015
Contents
Meetings
- Weekly Wednesdays at 1400 UTC
- IRC channel:
#openstack-meeting-3
- Chair: sc68cal / ajo (Sean Collins / Miguel Ángel Ajo)
Coding Sprint: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint
Logs and Minutes
Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/neutron_qos
Agenda
2015-05-06 14:00 UTC
- 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
- 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 (please note it was 2015-04-22 previously)
- 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
- 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?
Announcements
- Etherpad from summit: https://etherpad.openstack.org/p/neutron-qos
Blueprints
Meeting Commands
/join #openstack-meeting
#startmeeting neutron_qos
#topic Announcements
#link https://wiki.openstack.org/wiki/Meetings/NeutronQoS
#action ajo will get something specific done this week.
...
#endmeeting