<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 10:45 PM, 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="color: rgb(160, 160, 168);" class="">On Tuesday, 7 de April de 2015 at 3:14, Kyle Mestery wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class="">
<span class="">On Mon, Apr 6, 2015 at 6:04 PM, Salvatore Orlando <span dir="ltr" class=""><<a href="mailto:sorlando@nicira.com" target="_blank" class="">sorlando@nicira.com</a>></span> wrote:<br class=""><br class=""><br class="">On 7 April 2015 at 00:33, Armando M. <span dir="ltr" class=""><<a href="mailto:armamig@gmail.com" target="_blank" class="">armamig@gmail.com</a>></span> wrote:<br class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><br class=""><div class=""><span class="">On 6 April 2015 at 08:56, Miguel Ángel Ajo <span dir="ltr" class=""><<a href="mailto:majopela@redhat.com" target="_blank" class="">majopela@redhat.com</a>></span> wrote:<br class=""><blockquote type="cite" class=""><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></span></div></div></div></blockquote><div class=""><br class=""></div><div class="">As you surely know, so far every attempt to achieve a consensus has failed in a pretty miserable way.</div><div class="">This mostly because "QoS" can be interpreted in a lot of different ways, both from the conceptual and practical perspective.</div></span></blockquote><div class=""><span style="font-size: 14px;" class="">Yes, I’m fully aware of it, it was also a new feature, so it was out of scope for Kilo.</span> </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">It is important in my opinion to clearly define the goals first. For instance a simple extensions for bandwidth limiting could be a reasonable target for the Liberty release.</div></div></div></div></blockquote></div></div></div></div></div></span></blockquote><div class=""><span style="font-size: 14px;" class="">I quite agree here, but IMHO, as you said it’s a quite open field (limiting, guaranteeing, </span></div><div class=""><span style="font-size: 14px;" class="">marking, traffic shaping..), we should do our </span><span style="font-size: 14px;" class="">best in trying to define a model allowing us </span></div><div class=""><span style="font-size: 14px;" class="">to build that up in the future without huge changes, on the API side I guess micro versioning</span></div><div class=""><span style="font-size: 14px;" class="">is going to help in the API evolution.</span></div><div class=""><span style="font-size: 14px;" class=""><br class=""></span></div><div class=""><span style="font-size: 14px;" class="">Also, at some point, we should/could need to involve the nova folks, for example, to define</span></div><div class=""><span style="font-size: 14px;" class="">port flavors that can be associated to nova</span></div><div class=""><span style="font-size: 14px;" class="">instance flavors, providing them </span></div><div class=""><span style="font-size: 14px;" class="">1) different types of network port speeds/guarantees/priorities, </span></div><div class=""><span style="font-size: 14px;" class="">2) being able to schedule instance/ports in coordination to be able to met specified guarantees.</span></div><div class=""><span style="font-size: 14px;" class=""><br class=""></span></div><div class=""><span style="font-size: 14px;" class="">yes, complexity can sky rocket fast, </span></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">Moving things such as ECN into "future works" is the right thing to do in my opinion. Attempting to define a flexible framework that can deal with advanced QoS policies specification is a laudable effort, but I am a bit skeptical about its feasibility.</div><span class=""><div class=""><br class=""></div></span></div></div></div></blockquote><div class="">++, I think focusing on perhaps bandwidth limiting may make a lot of sense </div></div></div></div></div></div></span></blockquote><div class=""><span style="font-size: 14px;" class="">Yes, I believe we should look into the future , but at the same pick our very first feature (or a</span></div><div class=""><span style="font-size: 14px;" class="">very simple set of them) for L, </span><span style="font-size: 14px;" class="">stick to it, and try to make a design that can be extended.</span></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""></div><div class=""> <br class=""></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><div class=""> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><span 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></span></div></div></div></blockquote><div class=""><br class=""></div></span><div class="">"Simple" in my mind is even more extreme then what you're proposing here... I'd start with bare APIs for specifying bandwidth limiting, and then phase them out once this "framework" is in place.</div><div class="">Also note that this kind of design bears some overlap with the flavor framework which is probably going to be another goal for Liberty.</div><div class=""><br class=""></div></div></div></div></blockquote><div class="">Indeed, and the flavor framework is something I'm hoping we can land by Liberty-1 (yes, I just said Liberty-1).<br class=""></div></div></div></div></div></div></span></blockquote><div class=""><span style="font-size: 14px;" class="">Yes it’s something I looked at, I must admit I wasn’t able to see it work together (It doesn’t </span></div><div class=""><span style="font-size: 14px;" class="">mean it doesn’t play </span><span style="font-size: 14px;" class="">well, but most probably I was silly enough not to see it :) ),</span></div><div class=""><span style="font-size: 14px;" class=""><br class=""></span></div><div class=""><span style="font-size: 14px;" class="">I didn’t want to distract attention </span><span style="font-size: 14px;" class="">from the Kilo cycle focus </span><span style="font-size: 14px;" class="">making questions, so it should</span></div><div class=""><span style="font-size: 14px;" class="">be a good thing to talk </span><span style="font-size: 14px;" class="">about during the first meetings. </span></div><div class=""><span style="font-size: 14px;" class=""><br class=""></span></div><div class=""><span style="font-size: 14px;" class="">Who are the flavor fathers/mothers? ;)</span></div></div></blockquote><div><br class=""></div><div>The parentage is kind of like a west virginia non-branching family tree. You can find the specs here:</div><div><br class=""></div><div><a href="https://review.openstack.org/#/c/168988/" class="">https://review.openstack.org/#/c/168988/</a></div><div><a href="http://docs-draft.openstack.org/88/168988/1/check/gate-neutron-specs-docs/cf024a5//doc/build/html/" class="">http://docs-draft.openstack.org/88/168988/1/check/gate-neutron-specs-docs/cf024a5//doc/build/html/</a></div><div><br class=""></div><div>Let’s sync up on IRC.</div><div><br class=""></div><div>Thanks,</div><div>doug</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""> </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""> <br class=""></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">Morever, consider using "common" tools such as the specs repo to share and discuss design documents.</div><span class=""><div class=""> </div></span></div></div></div></blockquote><div class="">Also a good idea.<br class=""></div></div></div></div></div></div></span></blockquote><div class="">Yes, that was the plan now, we didn’t use it before to avoid creating unnecessary noise during this cycle.</div><div class=""><br class=""></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""> <br class=""></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class=""><div class=""><br class=""></div><div class=""><div class=""><span style="font-size:14px" 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 class=""><br class=""></div></span><div class="">I think that's a good idea. Incidentally I was speaking with Sean regarding Summit session [1], and we were hoping we could get some folks together either prior or during the summit, to try and get some momentum going behind this initiative, once again.</div></div></div></div></blockquote></span></div></div></div></blockquote></div></div></div></div></div></span></blockquote><div class=""><span style="font-size: 14px;" class="">Very interesting [1]!, nice to see we start to have a bunch of people with an interest in QoS.</span> </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><div class=""><br class=""></div></span><div class="">I think is a good idea as well. I was thinking that perhaps it might be a good idea to grab a design summit session as well (surely not a fishbowl one as they're totally unfit for this purpose).</div><div class="">However, it might be good to achieve some sort of consensus before the summit, as as we know fairly well now the summit is probably the worst place where consensus can be achieved!</div></div></div></div></blockquote></div></div></div></div></div></span></blockquote><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><div class=""><br class=""></div></span></div></div></div></blockquote><div class="">And finally, agreed here as well.<br class=""> </div></div></div></div></div></div></span></blockquote><div class=""><span style="font-size: 14px;" class="">Yes, a bit of preliminary discussion, and a “deadline” and final discussion on summit. Sounds good.</span></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><br class=""></div><div class="">We'd need to fill in page [2], and find an empty slot on [3]</div></div></div></div></blockquote></span></div></div></div></blockquote></div></div></div></div></div></span></blockquote><div class=""><span style="font-size: 14px;" class=""><br class=""></span></div><div class=""><span style="font-size: 14px;" class="">[2] done, and Meetings/QoS created </span></div><div class=""><span style="font-size: 14px;" class=""><br class=""></span></div><div class=""><span style="font-size: 14px;" class="">About [3]</span></div><div class=""><span style="font-size: 14px;" class="">Do any of those sound reasonable: </span></div><div class=""><span style="font-size: 14px;" class="">a) Thursdays / 19:00 CEST</span></div><div class=""><span style="font-size: 14px;" class="">b) Wednesdays / 16:00 CEST </span></div><div class=""><br class=""></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">One thing I had proposed to Miguel was to use the meeting as an initial starting point, and then once momentum is achieved to naturally end it and move any further meeting needs to the regular Neutron meeting.<br class=""></div></div></div></div></div></div></span></blockquote><div class=""><br class=""></div><div class=""><span style="font-size: 14px;" class="">Correct, that seems a natural thing to do once the meetings can be done under a certain</span></div><div class=""><span style="font-size: 14px;" class="">amount of time we could move them to a weekly meeting timeslot for details/progress tracking.</span></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""> <br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">Thanks for starting this thread!</div></div></div></div></div></blockquote></span></div></div></div></div></blockquote></div></div></div></div></div></span></blockquote><div class=""><span style="font-size: 14px;" class="">Thank you all :)</span> </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><br class=""></div><div class="">[1] <a href="https://openstacksummitmay2015vancouver.sched.org/event/27eeef71d5f57997ac09b4c7783c72fe#.VSMIzJT-NhM" target="_blank" class="">https://openstacksummitmay2015vancouver.sched.org/event/27eeef71d5f57997ac09b4c7783c72fe#.VSMIzJT-NhM</a> </div></div></div></div></div></blockquote></span></div></div></div></div></blockquote></div></div></div></div></div></span></blockquote><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;" class=""><span class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><span class=""><div class="">[2] <a href="https://wiki.openstack.org/wiki/NeutronSubTeams" target="_blank" class="">https://wiki.openstack.org/wiki/NeutronSubTeams</a></div><div class="">[3] <a href="https://wiki.openstack.org/wiki/Meetings" target="_blank" class="">https://wiki.openstack.org/wiki/Meetings</a></div><div class=""><br class=""></div><div class=""><br class=""></div><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" target="_blank" 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" target="_blank" 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" target="_blank" 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" target="_blank" class="">https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification</a></div></div>
<br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""><br class="">
<br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></span></div><br class=""></div></div>
<br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></div></blockquote></div><br class=""></div></div>
</div><div class=""><div class="">__________________________________________________________________________</div><div class="">OpenStack Development Mailing List (not for usage questions)</div><div class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></div><div 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></div></div></div></span>
</blockquote>
<div class="">
<br class="">
</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>