[openstack-dev] [gantt] Sync up patches

Sylvain Bauza sylvain.bauza at bull.net
Thu Jan 16 16:45:10 UTC 2014

Le 16/01/2014 17:18, Vishvananda Ishaya a écrit :
> On Jan 16, 2014, at 6:46 AM, Joe Gordon <joe.gordon0 at gmail.com 
> <mailto:joe.gordon0 at gmail.com>> wrote:
>> On Wed, Jan 15, 2014 at 1:29 PM, Dugger, Donald D 
>> <donald.d.dugger at intel.com <mailto:donald.d.dugger at intel.com>> wrote:
>>     My thought was to try and get some parallel effort going, do the
>>     resync as a continuing task as suffer a little ongoing pain
>>     versus a large amount of pain at the end.  Given that the steps
>>     for a resync are the same no matter when we do it waiting until
>>     the end is acceptable.
>>     From a `just do it' perspective I think we're in violent
>>     agreement on the top level tasks, as long as your step 3,
>>     integration testing, is the same as what I've been calling
>>     working functionality, e.g. have the nova scheduler use the gantt
>>     source tree.
>>     PS: How I resync.  What I've done is create a list with md5sums
>>     of all the files in nova that we've duplicated in gantt.  I then
>>     update a nova git tree and compare the current md5sums for those
>>     files with my list.  I use format-patch to get the patches from
>>     the nova tree and grep for any patch that applies to a gantt
>>     file.  I then use `git am' to apply those patches to the gantt
>>     tree, modifying any of the patches that are needed.
>> So this sync won't work once we start the nova/gantt rename, so we 
>> need a better approach.
>> Syncing the gantt tree with nova sounds like a daunting task. Perhaps 
>> it would be easier if we use the current gantt tree as a test to see 
>> what is involved in getting gantt working, and then redo the fork 
>> after the icehouse feature freeze with the aim of getting the gantt 
>> tree working by the start of juno, so we can have the freeze 
>> nova-scheduler discussion. Syncing nova and gantt during feature 
>> freeze should be significantly easier then doing it now.
> I would personally just vote for the nuclear approach of freezing nova 
> scheduler and doing work in gantt. If close to icehouse 3 we see that 
> gantt is not going to be ready in time we can selectively backport 
> stuff to nova-scheduler and push gantt to juno.
> Vish

I would also personnally prefer that we freeze Gantt, then do all 
necessary works, and only then backport all commits to Gantt (even if 
it's hard work).

The main issue is that we need to estimate the duration for all 
'necessary works', ie.
  - renaming nova to gantt in the gantt repo
  - having unittests in place
  - defining what the dependency with Nova will be : either having nova 
eggfile in requirements.txt, or (way more longest task) using novaclient 
for requesting Nova objects (like flavors or instances)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140116/aded1da3/attachment.html>

More information about the OpenStack-dev mailing list