<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><base href="x-msg://1598/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 4, 2013, at 3:59 AM, Hans Lindgren <<a href="mailto:hanlind@kth.se">hanlind@kth.se</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div fpstyle="1" ocsi="0" style="font-family: Menlo; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="direction: ltr; font-family: Tahoma; font-size: 10pt; "><div style="margin-top: 0px; margin-bottom: 0px; ">This is in regard to comments in the code review for blueprint utilization-based-scheduling found at<span class="Apple-converted-space"> </span><a href="https://review.openstack.org/#/c/18462/">https://review.openstack.org/#/c/18462/</a></div><p style="margin-top: 0px; margin-bottom: 0px; "> </p><div style="margin-top: 0px; margin-bottom: 0px; ">This blueprint is currently blocked over naming of new filters added to the scheduler.</div><p style="margin-top: 0px; margin-bottom: 0px; "> </p><div style="margin-top: 0px; margin-bottom: 0px; ">Some background:</div><div style="margin-top: 0px; margin-bottom: 0px; ">Current scheduling is done based on static allocation of resources, like the number of vCPUs or the amount of memory that has been granted to an instance. With this blueprint we introduce alternative criteria to base scheduling decisions on to allow for more effective use of resources. This is done by collecting actual resource consumption of the host (currently CPU+memory) and by complementing existing filters and weighers with new ones that acts upon the added stats.</div><p style="margin-top: 0px; margin-bottom: 0px; "> </p><div style="margin-top: 0px; margin-bottom: 0px; ">The good thing with this approach is that the default behaviour of the scheduler doesn't change with the introduction of this blueprint. You must actively choose to enable this new scheduling policy by configuring filters and weighers to be used.</div><p style="margin-top: 0px; margin-bottom: 0px; "> </p><div style="margin-top: 0px; margin-bottom: 0px; ">Now to the problem.</div><div style="margin-top: 0px; margin-bottom: 0px; ">Since we end up having dual filters acting on the same resource (ex. RamFilter/RamUsageFilter), we need to figure out the best way to name them to avoid confusion.</div><p style="margin-top: 0px; margin-bottom: 0px; "> </p><div style="margin-top: 0px; margin-bottom: 0px; ">During review, it was proposed that existing filters (RamFilter and CoreFilter) should also be renamed to end up with *StaticFilter/*DynamicFilter or *PredictiveFilter/*UsageFilter. Later on an objection was made that this would break existing configs, forcing upgraders to change configs over such a change.</div></div></div></blockquote><blockquote type="cite"><div fpstyle="1" ocsi="0" style="font-family: Menlo; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="direction: ltr; font-family: Tahoma; font-size: 10pt; "><p style="margin-top: 0px; margin-bottom: 0px; "> </p><div style="margin-top: 0px; margin-bottom: 0px; ">To be able to move on with the review I would like to hear your opinions on this matter. The filters affected, and their current names are:</div><div style="margin-top: 0px; margin-bottom: 0px; ">CoreFilter (existing filter)</div><div style="margin-top: 0px; margin-bottom: 0px; ">RAMFilter (existing filter)</div><div style="margin-top: 0px; margin-bottom: 0px; ">CPUUsageFilter</div><div style="margin-top: 0px; margin-bottom: 0px; ">RAMUsageFilter</div></div></div></blockquote><br></div><div><br></div><div>There is no reason to break existing configs so I suggest keeping the names of the existing filters the same</div><div><br></div><div>Vish</div></body></html>