Jump to: navigation, search

Difference between revisions of "Meetings/QoS"

m
(Agenda)
Line 18: Line 18:
  
 
= Agenda =
 
= Agenda =
=== '''2015-05-06'''  14:00 UTC ===   
+
=== '''2015-05-06'''  14:00 UTC [http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.html meeting log]===   
 
* [http://lists.openstack.org/pipermail/openstack-dev/2015-May/063382.html API microversioning] spec implications
 
* [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]:  scoping into bandwidth limiting

Revision as of 18:14, 6 May 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-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