[openstack-dev] [Nova] Meetup Summary

Sylvain Bauza sylvain.bauza at gmail.com
Mon Feb 17 23:25:54 UTC 2014


Hi Russell and Don,


2014-02-17 23:41 GMT+01:00 Russell Bryant <rbryant at redhat.com>:

> Greetings,
>
>
> 2) Gantt  - We discussed the progress of the Gantt effort.  After
> discussing the problems encountered so far and the other scheduler work
> going on, the consensus was that we really need to focus on decoupling
> the scheduler from the rest of Nova while it's still in the Nova tree.
>
> Don was still interested in working on the existing gantt tree to learn
> what he can about the coupling of the scheduler to the rest of Nova.
> Nobody had a problem with that, but it doesn't sound like we'll be ready
> to regenerate the gantt tree to be the "real" gantt tree soon.  We
> probably need another cycle of development before it will be ready.
>
> As a follow-up to this, I wonder if we should rename the current gantt
> repository from openstack/gantt to stackforge/gantt to avoid any
> possible confusion.  We should make it clear that we don't expect the
> current repo to be used yet.
>

There is currently no precise meeting timeslot for Gantt but the one with
Nova scheduler subteam. Would it be possible to have a status on the
current path for Gantt so that people interested in joining the effort
would be able to get in ?

There is currently a discussion on how Gantt and Nova should interact, in
particular regarding HostState and how Nova Computes could update their
status so as Gantt would be able to filter on them. There are also other
discussions about testing, API, etc. so I'm just wondering how to help and
where.

On a side note, if Gantt is becoming a Stackforge project planning to have
Nova scheduling first, could we also assume that we could also implement
this service for being used by other projects (such as Climate) in parallel
with Nova ?
The current utilization-aware-scheduling blueprint is nearly done so that
it can be used for other queries than just Nova scheduling, but
unfortunately as the scheduler is still part of Nova and without a REST
API, it can't be leveraged on third-party projects.


Thanks,
-Sylvain

[1] :
https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140218/2a1e888e/attachment.html>


More information about the OpenStack-dev mailing list