<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://2/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 6, 2012, at 10:03 AM, "Dugger, Donald D" <<a href="mailto:donald.d.dugger@intel.com">donald.d.dugger@intel.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" 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 class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">The compute code currently defines a set of capabilities (info about disk & memory consumption, cpuinfo and a few other things) that are periodically reported up to the scheduler. You can then use the extra_specs to specify key/value pairs for a flavor that will be used by the scheduler’s compute_capabilities’ filter to make decisions based upon these capabilities. Note you can do relational comparisons on these capabilities, look at:<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> <span class="Apple-converted-space"> </span><a href="http://docs.openstack.org/developer/nova/devref/filter_scheduler.html" style="color: purple; text-decoration: underline; ">http://docs.openstack.org/developer/nova/devref/filter_scheduler.html</a><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">for details.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Currently, you are limited to the capabilities that are hard coded into the compute node code. I’m thinking about, and intend to create a blueprint in the not too distant future, adding a plugin into the compute code so that you can add support for new capabilities.</span></div></div></div></blockquote><br></div><div>You should be able to add in capabilities via host aggregates as well if you enable this AggregateInstanceExtraSpecs filter. This means you can change them at run time.</div><div><br></div><div>Vish</div></body></html>