Open Stack

> Agreed. I'm just thinking on the opportunity of providing a REST API

> on top of the scheduler RPC API with a 1:1 matching, so that the Gantt

> project would step up by itself. I don't think it's a hard stuff,
provided I

> already did that stuff for Climate (providing Pecan/WSME API). What

> do you think about it ? Even if it's not top priority, that's a
quickwin.



Well, I’m not sure about “quickwin”, though J I think that we should focus
on the main objective of having a self-contained Gantt working with Nova
first. Some of the interaction issues still worry me, especially the
host_state & host_update queries. These issues will have impact on the
Gantt API (at least for Nova to use), so I’m not sure the current RPC API
will hold up either. But I will not discourage any personal effort J







De : Sylvain Bauza [mailto:sylvain.bauza at gmail.com]
Envoyé : mardi 18 février 2014 22:41
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Nova] Meetup Summary



Hi Don,





2014-02-18 21:28 GMT+01:00 Dugger, Donald D <donald.d.dugger at intel.com>:

Sylvain-



As you can tell from the meeting today the scheduler sub-group is really
not the gantt group meeting, I try to make sure that messages for things
like the agenda and what not include both `gantt’ and `scheduler’ in the
subject so it’s clear we’re talking about the same thing.





That's the main reason why I was unable to attend the previous scheduler
meetings...

Now that I attended this today meeting, that's quite clear to me. I
apologize for this misunderstanding, but as I can't dedicate all my time
on Gantt/Nova, I have to make sure the time I'm taking on it can be worth
it.



Now that we agreed on a plan for next steps, I think it's important to put
the infos on Gantt blueprints, even if most of the changes are related to
Nova. The current etherpad is huge, and frightening people who would want
to contribute IMHO.





Note that our ultimate goal is to create a scheduler that is usable by
other projects, not just nova, but that is a second task.  The first task
is to create a separate scheduler that will be usable by nova at a
minimum.  (World domination will follow later J





Agreed. I'm just thinking on the opportunity of providing a REST API on
top of the scheduler RPC API with a 1:1 matching, so that the Gantt
project would step up by itself. I don't think it's a hard stuff, provided
I already did that stuff for Climate (providing Pecan/WSME API). What do
you think about it ? Even if it's not top priority, that's a quickwin.



-Sylvain



--

Don Dugger

"Censeo Toto nos in Kansa esse decisse." - D. Gale

Ph: 303/443-3786 <tel:303%2F443-3786>



From: Sylvain Bauza [mailto:sylvain.bauza at gmail.com]
Sent: Monday, February 17, 2014 4:26 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Meetup Summary



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




_______________________________________________
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/20140219/aa016c3a/attachment.html>