<div dir="ltr">Andrew,<div><br></div><div>Thank you for clarification!</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 10, 2014 at 3:47 PM, Andrew Laski <span dir="ltr"><<a href="mailto:andrew.laski@rackspace.com" target="_blank">andrew.laski@rackspace.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<br></div>
The scheduler as it currently exists is a placement engine. There is sufficient complexity in the scheduler with just that responsibility so I would prefer to see anything that's making runtime decisions separated out. Perhaps it could just be another service within the scheduler project once it's broken out, but I think it will be beneficial to have a clear distinction between placement decisions and runtime monitoring.</blockquote>
<div><br></div><div>Do you think that auto-scaling could be considered another facet of this 'runtime monitoring' functionality? Now it is a combination of Heat and Ceilometer. Does it worth moving to hypothetical runtime mobility service as well?</div>
<div><br></div><div>--</div><div>Best regards,</div><div>Oleg Gelbukh</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
Best regards,<br>
Oleg Gelbukh<br>
<br>
<br>
On Wed, Apr 9, 2014 at 7:47 PM, Jay Lau <<a href="mailto:jay.lau.513@gmail.com" target="_blank">jay.lau.513@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
@Oleg, Till now, I'm not sure the target of Gantt, is it for initial<br>
placement policy or run time policy or both, can you help clarify?<br>
<br>
@Henrique, not sure if you know IBM PRS (Platform Resource Scheduler) [1],<br>
we have finished the "dynamic scheduler" in our Icehouse version (PRS 2.2),<br>
it has exactly the same feature as your described, we are planning a live<br>
demo for this feature in Atlanta Summit. I'm also writing some document for<br>
run time policy which will cover more run time policies for OpenStack, but<br>
not finished yet. (My shame for the slow progress). The related blueprint<br>
is [2], you can also get some discussion from [3]<br>
<br>
[1]<br>
<a href="http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS213-590&appname=USN" target="_blank">http://www-01.ibm.com/common/<u></u>ssi/cgi-bin/ssialias?infotype=<u></u>AN&subtype=CA&htmlfid=897/<u></u>ENUS213-590&appname=USN</a><br>
[2]<br>
<a href="https://blueprints.launchpad.net/nova/+spec/resource-optimization-service" target="_blank">https://blueprints.launchpad.<u></u>net/nova/+spec/resource-<u></u>optimization-service</a><br>
[3] <a href="http://markmail.org/~jaylau/OpenStack-DRS" target="_blank">http://markmail.org/~jaylau/<u></u>OpenStack-DRS</a><br>
<br>
Thanks.<br>
<br>
<br>
2014-04-09 23:21 GMT+08:00 Oleg Gelbukh <<a href="mailto:ogelbukh@mirantis.com" target="_blank">ogelbukh@mirantis.com</a>>:<br>
<br>
Henrique,<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
You should check out Gantt project [1], it could be exactly the place to<br>
implement such features. It is a generic cross-project Scheduler as a<br>
Service forked from Nova recently.<br>
<br>
[1] <a href="https://github.com/openstack/gantt" target="_blank">https://github.com/openstack/<u></u>gantt</a><br>
<br>
--<br>
Best regards,<br>
Oleg Gelbukh<br>
Mirantis Labs<br>
<br>
<br>
On Wed, Apr 9, 2014 at 6:41 PM, Henrique Truta <<br>
<a href="mailto:henriquecostatruta@gmail.com" target="_blank">henriquecostatruta@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello, everyone!<br>
<br>
I am currently a graduate student and member of a group of contributors<br>
to OpenStack. We believe that a dynamic scheduler could improve the<br>
efficiency of an OpenStack cloud, either by rebalancing nodes to maximize<br>
performance or to minimize the number of active hosts, in order to minimize<br>
energy costs. Therefore, we would like to propose a dynamic scheduling<br>
mechanism to Nova. The main idea is using the Ceilometer information (e.g.<br>
RAM, CPU, disk usage) through the ceilometer-client and dinamically decide<br>
whether a instance should be live migrated.<br>
<br>
This might me done as a Nova periodic task, which will be executed every<br>
once in a given period or as a new independent project. In both cases, the<br>
current Nova scheduler will not be affected, since this new scheduler will<br>
be pluggable. We have done a search and found no such initiative in the<br>
OpenStack BPs. Outside the community, we found only a recent IBM<br>
announcement for a similiar feature in one of its cloud products.<br>
<br>
A possible flow is: In the new scheduler, we periodically make a call to<br>
Nova, get the instance list from a specific host and, for each instance, we<br>
make a call to the ceilometer-client (e.g. $ ceilometer statistics -m<br>
cpu_util -q resource=$INSTANCE_ID) and then, according to some specific<br>
parameters configured by the user, analyze the meters and do the proper<br>
migrations.<br>
<br>
Do you have any comments or suggestions?<br>
<br>
--<br>
Ítalo Henrique Costa Truta<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
<br>
</blockquote>
<br>
<br>
--<br>
Thanks,<br>
<br>
Jay<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
<br>
</blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>