Difference between revisions of "Meetings/QoS"
< Meetings
| Line 16: | Line 16: | ||
* Free discussion / use case gathering | * Free discussion / use case gathering | ||
* Agenda definition for first meeting : https://etherpad.openstack.org/p/neutron-qos-agenda | * Agenda definition for first meeting : https://etherpad.openstack.org/p/neutron-qos-agenda | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* Flavor framework coordination | * Flavor framework coordination | ||
:* how do flavors work? , does QoSes fit as flavors? | :* how do flavors work? , does QoSes fit as flavors? | ||
:* or can they be used to enforce QoS policies on tenants? | :* or can they be used to enforce QoS policies on tenants? | ||
| + | |||
| + | '''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? | * 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. | ||
== Announcements == | == Announcements == | ||
| Line 32: | Line 35: | ||
<br /><br /> | <br /><br /> | ||
| − | |||
| − | |||
| − | |||
== Blueprints == | == Blueprints == | ||
| − | * | + | * https://review.openstack.org/#/c/88599/ |
== Meeting Commands == | == Meeting Commands == | ||
Revision as of 14:37, 20 April 2015
Contents
Meetings
- 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-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?
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.
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
