<font size=2 face="sans-serif">Just to update those who are interested
in this feature but were not able to follow the recent commits, we made
good progress converging towards a simplified design, based on combination
of aggregates and flavors (both of which are API-drvien), addressing some
of the concerns expressed in this thread (at least to certain extent).</font>
<br><font size=2 face="sans-serif">The current design and possible usage
scenario has been updated at </font><a href=https://wiki.openstack.org/wiki/Nova/MultipleSchedulerPolicies><font size=3 color=blue><u>https://wiki.openstack.org/wiki/Nova/MultipleSchedulerPolicies</u></font></a><font size=3>
</font>
<br><font size=2 face="sans-serif">Comments are welcome (as well as code
reviews at </font><a href=https://review.openstack.org/#/c/37407/><font size=3 color=blue><u>https://review.openstack.org/#/c/37407/</u></font></a><font size=3>).</font>
<br>
<br><font size=2 face="sans-serif">Thanks, </font>
<br><font size=3>Alex</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Joe Gordon <joe.gordon0@gmail.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">OpenStack Development
Mailing List <openstack-dev@lists.openstack.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">27/07/2013 01:22 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
[Nova] support for multiple active scheduler policies/drivers</font>
<br>
<hr noshade>
<br>
<br>
<br>
<br><font size=3><br>
</font>
<br><font size=3>On Wed, Jul 24, 2013 at 6:18 PM, Alex Glikson <</font><a href=mailto:GLIKSON@il.ibm.com target=_blank><font size=3 color=blue><u>GLIKSON@il.ibm.com</u></font></a><font size=3>>
wrote:</font>
<br><tt><font size=3>Russell Bryant <</font></tt><a href=mailto:rbryant@redhat.com target=_blank><tt><font size=3 color=blue><u>rbryant@redhat.com</u></font></tt></a><tt><font size=3>>
wrote on 24/07/2013 07:14:27 PM:</font></tt>
<br><tt><font size=3><br>
> <br>
> I really like your point about not needing to set things up via a
config<br>
> file. That's fairly limiting since you can't change it on the
fly via<br>
> the API.</font></tt>
<br><font size=3><br>
</font><tt><font size=3><br>
True. As I pointed out in another response, the ultimate goal would be
to have policies as 'first class citizens' in Nova, including a DB table,
API, etc. Maybe even a separate policy service? But in the meantime, it
seems that the approach with config file is a reasonable compromise in
terms of usability, consistency and simplicity.</font></tt><font size=3>
</font>
<br>
<br><font size=3>I do like your idea of making policies first class citizens
in Nova, but I am not sure doing this in nova is enough. Wouldn't
we need similar things in Cinder and Neutron? Unfortunately
this does tie into how to do good scheduling across multiple services,
which is another rabbit hole all together.</font>
<br>
<br><font size=3>I don't like the idea of putting more logic in the config
file, as it is the config files are already too complex, making running
any OpenStack deployment require some config file templating and
some metadata magic (like heat). I would prefer to keep things like
this in aggregates, or something else with a REST API. So why not
build a tool on top of aggregates to push the appropriate metadata into
the aggregates. This will give you a central point to manage policies,
that can easily be updated on the fly (unlike config files). In
the long run I am interested in seeing OpenStack itself have a strong solution
for for policies as a first class citizen, but I am not sure if your proposal
is the best first step to do that.</font>
<br>
<br>
<br><font size=3> </font>
<br><tt><font size=3><br>
Regards,</font></tt><font size=3> </font><tt><font size=3><br>
Alex</font></tt><font size=3> </font><tt><font size=3><br>
<br>
> -- <br>
> Russell Bryant</font></tt>
<br><font size=3><br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org"><font size=3 color=blue><u>OpenStack-dev@lists.openstack.org</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target=_blank><font size=3 color=blue><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size=3><br>
</font>
<br><tt><font size=2>_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>