Open Stack

Jay-

Those patches are not a problem.  Once they are approved and pushed into the nova tree I will backport them over to gantt.  To re-iterate, the idea is to keep the current development going in nova and only when the gantt tree is functional and provides the same functionality as the scheduler inside the nova will we consider moving all development to gantt.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786

From: Jay Lau [mailto:jay.lau.513 at gmail.com]
Sent: Sunday, January 12, 2014 5:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [gantt[ Patches to sync gantt up to the current nova tree

According to https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg12973.html, it is said that we should not stop nova scheduler working for now.
BTW: I think that we may need to consider the following patches to enable Nova use scheduler from Oslo first to reduce future work before sync up to Gantt.

https://review.openstack.org/#/c/66105/
https://review.openstack.org/#/c/65418/
https://review.openstack.org/#/c/65424/

Thanks,
Jay

2014/1/13 Clint Byrum <clint at fewbar.com<mailto:clint at fewbar.com>>
Excerpts from Doug Hellmann's message of 2014-01-12 14:45:11 -0800:
> On Sun, Jan 12, 2014 at 5:30 PM, Dugger, Donald D <donald.d.dugger at intel.com<mailto:donald.d.dugger at intel.com>
> > wrote:
>
> >  So I have 25 patches that I need to push to backport changes that have
> > been made to the nova tree that apply to the gantt tree.  The problem is
> > how do we want to approve these patches?  Given that they have already been
> > reviewed and approved in the nova tree do we have to go through the
> > overhead of doing new reviews in the gantt tree and, if not, how do we
> > bypass that mechanism?
> >
>
> Why is code being copied from nova directly?
>
I suspect because gantt forked a while ago, but development has been
allowed to continue in nova's scheduler code. Seems like that should be
stopped at some point soon to reduce the extra sync effort.

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto: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/20140113/d76ab1d8/attachment.html>