Open Stack

Hi Khanh-Toan,

I only have one comment on your proposal : why are you proposing something
new for overcommitments with aggregates while the AggregateCoreFilter [1]
and AggregateRAMFilter [2]already exist, which AIUI provide same feature ?


I'm also concerned about the scope of changes for scheduler, as Gantt is
currently trying to replace it. Can we imagine such big changes to be
committed on the Nova side, while it's planned to have a Scheduler service
in the next future ?

-Sylvain


[1]
https://github.com/openstack/nova/blob/master/nova/scheduler/filters/core_filter.py#L74
[2]
https://github.com/openstack/nova/blob/master/nova/scheduler/filters/ram_filter.py#L75





2014-01-30 Khanh-Toan Tran <khanh-toan.tran at cloudwatt.com>

> There is an unexpected line break in the middle of the link, so I post it
> again:
>
> https://docs.google.com/document/d/1RfP7jRsw1mXMjd7in72ARjK0fTrsQv1bqolOri
> IQB2Y<https://docs.google.com/document/d/1RfP7jRsw1mXMjd7in72ARjK0fTrsQv1bqolOriIQB2Y>
>
> > -----Message d'origine-----
> > De : Khanh-Toan Tran [mailto:khanh-toan.tran at cloudwatt.com]
> > Envoyé : mercredi 29 janvier 2014 13:25
> > À : 'OpenStack Development Mailing List (not for usage questions)'
> > Objet : [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and
> Solver
> > Scheduler
> >
> > Dear all,
> >
> > As promised in the Scheduler/Gantt meeting, here is our analysis on the
> > connection between Policy Based Scheduler and Solver Scheduler:
> >
> > https://docs.google.com/document/d/1RfP7jRsw1mXMjd7in72ARjK0fTrsQv1bq
> > olOri
> > IQB2Y
> >
> > This document briefs the mechanism of the two schedulers and the
> possibility of
> > cooperation. It is my personal point of view only.
> >
> > In a nutshell, Policy Based Scheduler allows admin to define policies
> for different
> > physical resources (an aggregate, an availability-zone, or all
> > infrastructure) or different (classes of) users. Admin can modify
> > (add/remove/modify) any policy in runtime, and the modification effect
> is only
> > in the target (e.g. the aggregate, the users) that the policy is defined
> to. Solver
> > Scheduler solves the placement of groups of instances simultaneously by
> putting
> > all the known information into a integer linear system and uses Integer
> Program
> > solver to solve the latter. Thus relation between VMs and between VMs-
> > computes are all accounted for.
> >
> > If working together, Policy Based Scheduler can supply the filters and
> weighers
> > following the policies rules defined for different computes.
> > These filters and weighers can be converted into constraints & cost
> function for
> > Solver Scheduler to solve. More detailed will be found in the doc.
> >
> > I look forward for comments and hope that we can work it out.
> >
> > Best regards,
> >
> > Khanh-Toan TRAN
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140130/6b0ad01f/attachment.html>