<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 16, 2014 at 4:42 PM, Dugger, Donald D <span dir="ltr"><<a href="mailto:donald.d.dugger@intel.com" target="_blank">donald.d.dugger@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OK, it looks like the concensus is that we don't try and keep the gantt tree in sync with nova instead we:<br>
<br>
1) Get the current gantt tree to pass unit tests<br>
2) Get gantt to pass integration tests (e.g. get it working as the nova scheduler)<br>
3) Modify devstack to optionally use gantt<br>
4) Freeze scheduler changes to nova as we:<br></blockquote><div><br></div><div>This should be covered the the standard feature freeze for Icehouse<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
a) Extract all the changes that were needed to get gantt working<br>
b) Recreate the gantt tree from the current nova tree<br>
c) Apply all the patches from step 4.a<br>
5) Unfreeze scheduler work but now all work is targeted exclusively to the gantt tree<br></blockquote><div><br></div><div>LGTM, although once we have a working gantt for Icehouse I think we should have another round of discussion about deprecating nova-scheduler in favor of gantt. On I high level that is something I think we all support, but the devil is in the details.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Note that the current gantt tree has already changed the `nova' directory to `gantt' but there are more details for steps 1 and 2 that would be good to explicitly list.<br>
<div class="im HOEnZb"><br>
--<br>
Don Dugger<br>
"Censeo Toto nos in Kansa esse decisse." - D. Gale<br>
Ph: <a href="tel:303%2F443-3786" value="+13034433786">303/443-3786</a><br>
<br>
</div><div class="im HOEnZb">-----Original Message-----<br>
From: Russell Bryant [mailto:<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>]<br>
Sent: Thursday, January 16, 2014 9:42 AM<br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: Re: [openstack-dev] [gantt] Sync up patches<br>
<br>
</div><div class="HOEnZb"><div class="h5">On 01/16/2014 11:18 AM, Vishvananda Ishaya wrote:<br>
><br>
> On Jan 16, 2014, at 6:46 AM, Joe Gordon <<a href="mailto:joe.gordon0@gmail.com">joe.gordon0@gmail.com</a><br>
> <mailto:<a href="mailto:joe.gordon0@gmail.com">joe.gordon0@gmail.com</a>>> wrote:<br>
><br>
>><br>
>><br>
>><br>
>> On Wed, Jan 15, 2014 at 1:29 PM, Dugger, Donald D<br>
>> <<a href="mailto:donald.d.dugger@intel.com">donald.d.dugger@intel.com</a> <mailto:<a href="mailto:donald.d.dugger@intel.com">donald.d.dugger@intel.com</a>>><br>
>> wrote:<br>
>><br>
>> My thought was to try and get some parallel effort going, do the<br>
>> resync as a continuing task as suffer a little ongoing pain versus a<br>
>> large amount of pain at the end. Given that the steps for a resync<br>
>> are the same no matter when we do it waiting until the end is<br>
>> acceptable.____<br>
>><br>
>> __ __<br>
>><br>
>> From a `just do it' perspective I think we're in violent agreement on<br>
>> the top level tasks, as long as your step 3, integration testing, is<br>
>> the same as what I've been calling working functionality, e.g. have<br>
>> the nova scheduler use the gantt source tree.____<br>
>><br>
>> __ __<br>
>><br>
>> PS: How I resync. What I've done is create a list with md5sums of<br>
>> all the files in nova that we've duplicated in gantt. I then update<br>
>> a nova git tree and compare the current md5sums for those files with<br>
>> my list. I use format-patch to get the patches from the nova tree<br>
>> and grep for any patch that applies to a gantt file. I then use `git<br>
>> am' to apply those patches to the gantt tree, modifying any of the<br>
>> patches that are needed.<br>
>><br>
>><br>
>> So this sync won't work once we start the nova/gantt rename, so we<br>
>> need a better approach.<br>
>><br>
>> Syncing the gantt tree with nova sounds like a daunting task.<br>
>> Perhaps it would be easier if we use the current gantt tree as a test<br>
>> to see what is involved in getting gantt working, and then redo the<br>
>> fork after the icehouse feature freeze with the aim of getting the<br>
>> gantt tree working by the start of juno, so we can have the freeze<br>
>> nova-scheduler discussion. Syncing nova and gantt during feature<br>
>> freeze should be significantly easier then doing it now.<br>
><br>
><br>
> I would personally just vote for the nuclear approach of freezing nova<br>
> scheduler and doing work in gantt. If close to icehouse 3 we see that<br>
> gantt is not going to be ready in time we can selectively backport<br>
> stuff to nova-scheduler and push gantt to juno.<br>
<br>
That sounds OK to me, but I would really just like to see gantt running before we freeze nova-scheduler.<br>
<br>
Joe's idea might work for this too, which would be something like:<br>
<br>
1) Go through the exercise of making the current thing running using the current repo (without keeping it in sync). This includes devstack integration.<br>
<br>
2) Once we see it working and are ready for the nuclear freeze and switch, re-generate the repo from nova master and apply everything needed to make it work.<br>
<br>
--<br>
Russell Bryant<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>
_______________________________________________<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>
</div></div></blockquote></div><br></div></div>