<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Apr 6, 2015, at 11:56 , Miguel Ángel Ajo <<a href="mailto:majopela@redhat.com" class="">majopela@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class=""><span style="font-size: 14px;" class="">I’d like to co-organized a QoS weekly meeting with Sean M. Collins,</span></div>
<div class=""><span style="font-size: 14px;" class=""><br class="">
</span></div>
<div class=""><span style="font-size: 14px;" class=""> In the last few years, the interest for QoS support has increased, Sean has been leading</span></div>
<div class=""><span style="font-size: 14px;" class="">this effort [1] and we believe we should get into a consensus about how to model an extension</span></div>
<div class=""><span style="font-size: 14px;" class="">to let vendor plugins implement QoS capabilities on network ports and tenant networks, and</span></div>
<div class=""><span style="font-size: 14px;" class="">how to extend agents, and the reference implementation & others [2]</span></div>
</div>
</blockquote>
<div><br class="">
</div>
I’m very interested in seeing this feature mature. Sean was writing this code initialy while working with our team here at Comcast and we’re still carrying the patches he wrote through to new versions of Neutron. I’d very much like to discuss ways to bering
them back into mailine.<br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><span style="font-size: 14px;" class=""><br class="">
</span></div>
<div class=""><span style="font-size: 14px;" class=""> As per discussion we’ve had during the last few months [3], I believe we should start simple, but</span></div>
<div class=""><span style="font-size: 14px;" class="">prepare a model allowing future extendibility, </span><span style="font-size: 14px;" class="">to allow for example specific traffic rules (per port,</span></div>
<div class=""><span style="font-size: 14px;" class="">per IP, etc..), congestion notification support [4], </span><span style="font-size: 14px;" class="">…</span></div>
</div>
</blockquote>
<div><br class="">
</div>
<div>I agree with starting simple. We’ve implemented basic DSCP marking only at this point to allow hardware switches to to queue and filter based on the marks. It would be great to bring the queueing down into the vSwitch and then extend this to things like
minimum guaranteed bandwidth. I have a fair few applications that would benefit from these kinds of features.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><span style="font-size: 14px;" class=""><br class="">
</span></div>
<div class=""><span style="font-size: 14px;" class=""> It’s the first time I’m trying to organize an openstack/neutron meeting, so, I don’t know what’s the</span></div>
<div class=""><span style="font-size: 14px;" class="">best way to do it, or find the best timeslot. I guess interested people may have a saying, so I’ve </span></div>
<div class=""><span style="font-size: 14px;" class="">looped anybody I know is interested in the CC of this mail. </span></div>
</div>
</blockquote>
<div><br class="">
</div>
<div>There’s no best way. Just pick an open meeting timeslot, email out the meeting details and get your notes/meeting minutes onto the wiki. Hopefully this works out and I’d be glad to help!</div>
<div>-Anthony</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
</div>
<div class=""><span style="font-size: 14px;" class=""><br class="">
</span></div>
<div class="">
<div class=""><span style="font-size: 10pt;" class="">Miguel Ángel Ajo</span></div>
<div class=""><br class="">
</div>
<div class=""><span style="font-size: 14px;" class="">[1] </span><a href="https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api" class="">https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api</a></div>
<div class=""><span style="font-size: 14px;" class="">[2] </span><a href="https://drive.google.com/file/d/0B2XATqL7DxHFRHNjU3k1UFNYRjQ/view?usp=sharing" class="">https://drive.google.com/file/d/0B2XATqL7DxHFRHNjU3k1UFNYRjQ/view?usp=sharing</a></div>
<div class=""><span style="font-size: 14px;" class="">[3] </span><a href="https://docs.google.com/document/d/1xUx0Oq-txz_qVA2eYE1kIAJlwxGCSqXHgQEEGylwlZE/edit#heading=h.2pdgqfl3a231" class="">https://docs.google.com/document/d/1xUx0Oq-txz_qVA2eYE1kIAJlwxGCSqXHgQEEGylwlZE/edit#heading=h.2pdgqfl3a231</a></div>
<div class=""><span style="font-size: 14px;" class="">[4] </span><a href="https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification" class="">https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification</a></div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</body>
</html>