Difference between revisions of "Meetings/QoS"
< Meetings
Line 3: | Line 3: | ||
* IRC channel: <code><nowiki>#openstack-meeting-2</nowiki></code> | * IRC channel: <code><nowiki>#openstack-meeting-2</nowiki></code> | ||
* Chair: sc68cal / ajo (Sean Collins / Miguel Ángel Ajo) | * Chair: sc68cal / ajo (Sean Collins / Miguel Ángel Ajo) | ||
+ | |||
+ | Coding Sprint: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint | ||
== Logs and Minutes == | == Logs and Minutes == | ||
Line 11: | Line 13: | ||
'''2015-04-15''' | '''2015-04-15''' | ||
+ | * Coding sprint for QoS: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint | ||
+ | * Free discussion / use case gathering. | ||
* Agenda definition for first meeting | * Agenda definition for first meeting | ||
− | |||
'''2015-04-22''' | '''2015-04-22''' | ||
+ | * Coding sprint for QoS: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint | ||
* Current ideas for design | * Current ideas for design | ||
* 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 | + | :* or can they be used to enforce QoS policies on tenants? |
* 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? | ||
Revision as of 09:45, 15 April 2015
Contents
Meetings
- IRC channel:
#openstack-meeting-2
- 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
- Coding sprint for QoS: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint
- Free discussion / use case gathering.
- Agenda definition for first meeting
2015-04-22
- Coding sprint for QoS: https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint
- Current ideas for design
- Flavor framework coordination
- how do flavors work? , does QoSes fit as flavors?
- or can they be used to enforce QoS policies on tenants?
- QoS types we can think of: bandwidth limiting, guarantees, traffic marking, traffic shaping (per proto flags), ... what are we yet missing?
Announcements
- Etherpad from summit: https://etherpad.openstack.org/p/neutron-qos
Bugs
Not there yet... ;)
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