Jump to: navigation, search

Difference between revisions of "Meetings/QoS"

(→‎Agenda)
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
= Meetings =
 
= Meetings =
 +
* Weekly Wednesdays at 1400 UTC
 +
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
 +
* 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 ==
  
−
* IRC channel: <code><nowiki>#openstack-meeting-2</nowiki></code>
+
* https://review.openstack.org/#/c/88599/
−
* Chair: sc68cal / ajo (Sean Collins / Miguel Ángel Ajo)
 
  
 
== Logs and Minutes ==
 
== Logs and Minutes ==
Line 10: Line 19:
 
= Agenda =
 
= Agenda =
  
−
'''2015-04-15'''
+
=== '''2015-06-03''' 14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-06-03-14.01.html meeting log] ===
−
* Agenda definition for first meeting
+
* Etherpad with ideas, and work distribution at the end: https://etherpad.openstack.org/p/neutron-qos-jun-3-2015
−
* Free discussion / use case gathering.
+
 
 +
=== '''2015-05-27''' 14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-27-14.01.html meeting log] ===
 +
* Impressions from the summit session: https://etherpad.openstack.org/p/YVR-neutron-qos
 +
* people from comcast to prepare ovs/dscp + spec in parallel
 +
* where do we stand
 +
* open agenda
 +
 
 +
interesting stuff (future): https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/supporting-network-bandwidth-guarantees-with-openstack-an-implementation-perspective
  
−
'''2015-04-22'''
+
=== '''2015-05-21''' (Summit session)===
 +
Summit session: https://etherpad.openstack.org/p/YVR-neutron-qos
 +
=== '''2015-05-13''' 14:00 UTC 14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.html meeting log]===
 +
* 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
  
−
* Current ideas for design
+
=== '''2015-05-06'''  14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.html meeting log]=== 
−
* Flavor framework coordination
+
* [http://lists.openstack.org/pipermail/openstack-dev/2015-May/063382.html API microversioning] spec implications
−
:* how do flavors work? , does QoSes fit as flavors?
+
* [https://review.openstack.org/#/c/88599/9..10/specs/liberty/qos-api-extension.rst Changes to the QoS API spec]:  scoping into bandwidth limiting
−
:* or can they be used to enforce QoS policies on tenant ports?
+
* [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)
−
* QoS types we can think of: bandwidth limiting, guarantees, traffic marking, traffic shaping (per proto flags), ... what are we yet missing?
+
* Discuss multiple API end points (per rule type) vs single.
 +
* Traffic Classification considerations
 +
* The ingress vs egress differences and issues.
  
  
−
== Announcements ==
 
  
−
* Etherpad from summit:  https://etherpad.openstack.org/p/neutron-qos
+
==='''2015-04-29'''  14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-29-14.01.html meeting log] ===
−
<br /><br />
+
* 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-)
  
−
== Bugs ==
 
  
−
Not there yet... ;)
+
==='''2015-04-21'''  14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-21-14.03.html 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.
  
−
== Blueprints ==
 
  
−
*  
+
==='''2015-04-15''' 14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-15-14.07.html 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 ==
+
= Meeting Commands =
  
−
<nowiki>/join #openstack-meeting</nowiki><br />
+
<nowiki>/join #openstack-meeting-3</nowiki><br />
 
<nowiki>#startmeeting neutron_qos</nowiki><br />
 
<nowiki>#startmeeting neutron_qos</nowiki><br />
 
<nowiki>#topic Announcements</nowiki><br />
 
<nowiki>#topic Announcements</nowiki><br />
Line 45: Line 85:
 
<nowiki>#action ajo will get something specific done this week.</nowiki><br />
 
<nowiki>#action ajo will get something specific done this week.</nowiki><br />
 
...<br />
 
...<br />
 +
<br />
 +
<nowiki>#undo</nowiki>
 
<br />
 
<br />
 
<nowiki>#endmeeting</nowiki><br />
 
<nowiki>#endmeeting</nowiki><br />
  
 
<br /><br /><br />
 
<br /><br /><br />

Latest revision as of 13:15, 10 June 2015

Meetings

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

Announcements

Blueprints

Logs and Minutes

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

Agenda

2015-06-03 14:00 UTC meeting log

2015-05-27 14:00 UTC meeting log

interesting stuff (future): https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/supporting-network-bandwidth-guarantees-with-openstack-an-implementation-perspective

2015-05-21 (Summit session)

Summit session: https://etherpad.openstack.org/p/YVR-neutron-qos

2015-05-13 14:00 UTC 14:00 UTC meeting log

2015-05-06 14:00 UTC meeting log


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


2015-04-15 14:00 UTC meeting log

  • 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




Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/QoS&oldid=83114"