<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>I prefer Timeslot B, thanks for coordinating. I would be interested in helping out in any way with the design session let me know!</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Sandhya Dasu (sadasu)" <<a href="mailto:sadasu@cisco.com">sadasu@cisco.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, April 7, 2015 12:19 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Hi Miguel,</div>
<div> Both time slots work for me. Thanks for rekindling this effort.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sandhya</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Miguel Ángel Ajo <<a href="mailto:majopela@redhat.com">majopela@redhat.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, April 7, 2015 1:45 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting<br>
</div>
<div><br>
</div>
<div>
<div>
<div><span style="color: rgb(160, 160, 168);">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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>On Mon, Apr 6, 2015 at 6:04 PM, Salvatore Orlando <span dir="ltr"><<a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div><br>
<div><span>On 7 April 2015 at 00:33, Armando M. <span dir="ltr"><<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div><br>
<div><span>On 6 April 2015 at 08:56, Miguel Ángel Ajo <span dir="ltr"><<a href="mailto:majopela@redhat.com" target="_blank">majopela@redhat.com</a>></span> wrote:<br>
<blockquote type="cite">
<div>
<div><span style="font-size:14px">I’d like to co-organized a QoS weekly meeting with Sean M. Collins,</span></div>
<div><span style="font-size:14px"><br>
</span></div>
<div><span style="font-size:14px"> In the last few years, the interest for QoS support has increased, Sean has been leading</span></div>
<div><span style="font-size:14px">this effort [1] and we believe we should get into a consensus about how to model an extension</span></div>
<div><span style="font-size:14px">to let vendor plugins implement QoS capabilities on network ports and tenant networks, and</span></div>
<div><span style="font-size:14px">how to extend agents, and the reference implementation & others [2]</span></div>
</div>
</blockquote>
</span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>As you surely know, so far every attempt to achieve a consensus has failed in a pretty miserable way.</div>
<div>This mostly because "QoS" can be interpreted in a lot of different ways, both from the conceptual and practical perspective.</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</span></blockquote>
<div><span style="font-size: 14px;">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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>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><span style="font-size: 14px;">I quite agree here, but IMHO, as you said it’s a quite open field (limiting, guaranteeing, </span></div>
<div><span style="font-size: 14px;">marking, traffic shaping..), we should do our </span><span style="font-size: 14px;">best in trying to define a model allowing us </span></div>
<div><span style="font-size: 14px;">to build that up in the future without huge changes, on the API side I guess micro versioning</span></div>
<div><span style="font-size: 14px;">is going to help in the API evolution.</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">Also, at some point, we should/could need to involve the nova folks, for example, to define</span></div>
<div><span style="font-size: 14px;">port flavors that can be associated to nova</span></div>
<div><span style="font-size: 14px;">instance flavors, providing them </span></div>
<div><span style="font-size: 14px;">1) different types of network port speeds/guarantees/priorities, </span></div>
<div><span style="font-size: 14px;">2) being able to schedule instance/ports in coordination to be able to met specified guarantees.</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>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>
<div><br>
</div>
</span></div>
</div>
</div>
</blockquote>
<div>++, I think focusing on perhaps bandwidth limiting may make a lot of sense </div>
</div>
</div>
</div>
</div>
</div>
</span></blockquote>
<div><span style="font-size: 14px;">Yes, I believe we should look into the future , but at the same pick our very first feature (or a</span></div>
<div><span style="font-size: 14px;">very simple set of them) for L, </span><span style="font-size: 14px;">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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div></div>
<div> <br>
</div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div><span>
<div> </div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div><span>
<blockquote type="cite">
<div>
<div><span style="font-size:14px"><br>
</span></div>
<div><span style="font-size:14px"> As per discussion we’ve had during the last few months [3], I believe we should start simple, but</span></div>
<div><span style="font-size:14px">prepare a model allowing future extendibility, </span><span style="font-size:14px">to allow for example specific traffic rules (per port,</span></div>
<div><span style="font-size:14px">per IP, etc..), congestion notification support [4], </span><span style="font-size:14px">…</span></div>
</div>
</blockquote>
</span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>"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>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><br>
</div>
</div>
</div>
</div>
</blockquote>
<div>Indeed, and the flavor framework is something I'm hoping we can land by Liberty-1 (yes, I just said Liberty-1).<br>
</div>
</div>
</div>
</div>
</div>
</div>
</span></blockquote>
<div><span style="font-size: 14px;">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><span style="font-size: 14px;">mean it doesn’t play </span><span style="font-size: 14px;">well, but most probably I was silly enough not to see it :) ),</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">I didn’t want to distract attention </span><span style="font-size: 14px;">from the Kilo cycle focus </span><span style="font-size: 14px;">making questions, so it should</span></div>
<div><span style="font-size: 14px;">be a good thing to talk </span><span style="font-size: 14px;">about during the first meetings. </span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">Who are the flavor fathers/mothers? ;)</span></div>
<div> </div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div> <br>
</div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>Morever, consider using "common" tools such as the specs repo to share and discuss design documents.</div>
<span>
<div> </div>
</span></div>
</div>
</div>
</blockquote>
<div>Also a good idea.<br>
</div>
</div>
</div>
</div>
</div>
</div>
</span></blockquote>
<div>Yes, that was the plan now, we didn’t use it before to avoid creating unnecessary noise during this cycle.</div>
<div><br>
</div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div> <br>
</div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div><span>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div><span>
<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">
<div><br>
</div>
<div>
<div><span style="font-size:14px"></span></div>
<div><span style="font-size:14px"> 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><span style="font-size:14px">best way to do it, or find the best timeslot. I guess interested people may have a saying, so I’ve </span></div>
<div><span style="font-size:14px">looped anybody I know is interested in the CC of this mail. </span></div>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>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><span style="font-size: 14px;">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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div><span>
<div><br>
</div>
</span>
<div>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>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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div><span>
<div><br>
</div>
</span></div>
</div>
</div>
</blockquote>
<div>And finally, agreed here as well.<br>
</div>
</div>
</div>
</div>
</div>
</div>
</span></blockquote>
<div><span style="font-size: 14px;">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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div></div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div><span>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div><br>
</div>
<div>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><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">[2] done, and Meetings/QoS created </span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">About [3]</span></div>
<div><span style="font-size: 14px;">Do any of those sound reasonable: </span></div>
<div><span style="font-size: 14px;">a) Thursdays / 19:00 CEST</span></div>
<div><span style="font-size: 14px;">b) Wednesdays / 16:00 CEST </span></div>
<div><br>
</div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>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>
</div>
</div>
</div>
</div>
</div>
</div>
</span></blockquote>
<div><br>
</div>
<div><span style="font-size: 14px;">Correct, that seems a natural thing to do once the meetings can be done under a certain</span></div>
<div><span style="font-size: 14px;">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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div> <br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div><span>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>
<div>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><span style="font-size: 14px;">Thank you all :)</span> </div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div><span>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>
<div><br>
</div>
<div>[1] <a href="https://openstacksummitmay2015vancouver.sched.org/event/27eeef71d5f57997ac09b4c7783c72fe#.VSMIzJT-NhM" target="_blank">
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;">
<span>
<div>
<div>
<div dir="ltr">
<div>
<div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div><span>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>
<div>[2] <a href="https://wiki.openstack.org/wiki/NeutronSubTeams" target="_blank">https://wiki.openstack.org/wiki/NeutronSubTeams</a></div>
<div>[3] <a href="https://wiki.openstack.org/wiki/Meetings" target="_blank">https://wiki.openstack.org/wiki/Meetings</a></div>
<div><br>
</div>
<div><br>
</div>
<blockquote type="cite">
<div><span>
<div><br>
</div>
<div><span style="font-size:14px"><br>
</span></div>
<div>
<div><span style="font-size:10pt">Miguel Ángel Ajo</span></div>
<div><br>
</div>
<div><span style="font-size:14px">[1] </span><a href="https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api" target="_blank">https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api</a></div>
<div><span style="font-size:14px">[2] </span><a href="https://drive.google.com/file/d/0B2XATqL7DxHFRHNjU3k1UFNYRjQ/view?usp=sharing" target="_blank">https://drive.google.com/file/d/0B2XATqL7DxHFRHNjU3k1UFNYRjQ/view?usp=sharing</a></div>
<div><span style="font-size:14px">[3] </span><a href="https://docs.google.com/document/d/1xUx0Oq-txz_qVA2eYE1kIAJlwxGCSqXHgQEEGylwlZE/edit#heading=h.2pdgqfl3a231" target="_blank">https://docs.google.com/document/d/1xUx0Oq-txz_qVA2eYE1kIAJlwxGCSqXHgQEEGylwlZE/edit#heading=h.2pdgqfl3a231</a></div>
<div><span style="font-size:14px">[4] </span><a href="https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification" target="_blank">https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification</a></div>
</div>
<br>
</span>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div>
</blockquote>
</span></div>
<br>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<div>
<div>__________________________________________________________________________</div>
<div>OpenStack Development Mailing List (not for usage questions)</div>
<div>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></div>
<div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></div>
</div>
</div>
</span></blockquote>
<div><br>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>