<div dir="ltr">Vish,<div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">and as I understand it the hope will be to do the no-db-scheduler blueprint.</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">There was quite a bit of debate on whether to do the no-db-scheduler stuff</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">before or after the forklift and I think the consensus was to do the forklift</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">first.</span><br style="font-family:arial,sans-serif;font-size:13px"></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Current Nova scheduler is so deeply bind to nova data models, that it is useless for every other project. </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">So I don't think that forkit in such state of Nova Scheduler is useful for any other project. </span></div>
<div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Best regards,</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">Boris Pavlovic</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><br></div></div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Mon, Jan 6, 2014 at 11:30 PM, Vishvananda Ishaya <span dir="ltr"><<a href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Jan 6, 2014, at 11:02 AM, Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
<br>
> Hello Stackers,<br>
><br>
> I was hoping to get some answers on a few questions I had regarding the<br>
> Gantt project [1]. Specifically, here are my queries:<br>
><br>
> 1) Why was Nova forked to the <a href="http://github.com/openstack/gantt" target="_blank">http://github.com/openstack/gantt</a><br>
> repository? Forking Nova just to then remove a bunch of code that<br>
> doesn't relate to the scheduler code means that we bring 10K+ commits<br>
> and a git history along with the new project... this seems to be the<br>
> wrong origin for a project the aims to be a separate service. There's a<br>
> reason that Cinder and Neutron didn't start out as a fork of Nova, after<br>
</div>> all…<br>
<br>
Authorship history is nice, but this does seem a bit excessive. The cinder<br>
strategy of a single squashed fork would have been/still be fine I’m sure.<br>
<div class="im">><br>
> 2) Why is Gantt in the /openstack GitHub organization? Wouldn't<br>
> the /stackforge organization be more appropriate for a project that<br>
> isn't integrated? If I understand some of the backstory behind Gantt,<br>
> the idea was to create a scheduler service from the existing Nova<br>
> scheduler code in order to "complete the work sometime in our lifetime".<br>
> While I understand the drive to start with something that already exists<br>
> and iterate over it, I don't understand why the project went right into<br>
> the /openstack organization instead of following the /stackforge<br>
> processes for housing code that bakes and gets iterated on before<br>
> proposing for incubation. Some explanation would be great here.<br>
<br>
</div>This is split-out of existing code so it is following the same path as<br>
cinder. The goal is to deprecate the existing nova scheduler in I. It currently<br>
a new project under the nova program I believe.<br>
<div class="im"><br>
><br>
> 3) Where is feature planning happening for Gantt? The Launchpad site for<br>
> Gantt [2] is empty. Furthermore, there are a number of blueprints for<br>
> improving the Nova scheduler, notably the no-db-scheduler blueprint [3],<br>
> which even has code submitted for it and is targeted to Icehouse-2. How<br>
> are improvements like this planned to be ported (if at all) to Gantt?<br>
<br>
</div>Not sure about the launchpad site. There is a regular scheduler group meeting<br>
and as I understand it the hope will be to do the no-db-scheduler blueprint.<br>
There was quite a bit of debate on whether to do the no-db-scheduler stuff<br>
before or after the forklift and I think the consensus was to do the forklift<br>
first.<br>
<div class="im"><br>
><br>
> 4) Is the aim of Gantt to provide a RESTful HTTP API in addition to the<br>
> RPC-based API that the existing Nova scheduler exposes?<br>
<br>
</div>In the short term the plan is to just replicate the rpc api, but I think<br>
a REST api will be considered long term.<br>
<br>
Vish<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Thanks much in advance for answers, and apologies if these have been<br>
> answered before and I missed the ML threads or design summit<br>
> discussions.<br>
><br>
> Best,<br>
> -jay<br>
><br>
> [1] <a href="https://github.com/openstack/gantt/" target="_blank">https://github.com/openstack/gantt/</a><br>
> [2] <a href="http://blueprints.launchpad.net/gantt" target="_blank">http://blueprints.launchpad.net/gantt</a><br>
> [3] <a href="https://blueprints.launchpad.net/nova/+spec/no-db-scheduler" target="_blank">https://blueprints.launchpad.net/nova/+spec/no-db-scheduler</a><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>