<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 16/01/2014 17:18, Vishvananda Ishaya
a écrit :<br>
</div>
<blockquote
cite="mid:626DBE09-B315-41A1-B313-B344D3D179F9@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<br>
<div>
<div>On Jan 16, 2014, at 6:46 AM, Joe Gordon <<a
moz-do-not-send="true" href="mailto:joe.gordon0@gmail.com">joe.gordon0@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jan 15, 2014 at 1:29 PM,
Dugger, Donald D <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:donald.d.dugger@intel.com"
target="_blank">donald.d.dugger@intel.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px
0px 0.8ex; border-left-width: 1px; border-left-color:
rgb(204, 204, 204); border-left-style: solid;
padding-left: 1ex; position: static; z-index: auto;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.</span></p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>So this sync won't work once we start the
nova/gantt rename, so we need a better approach.</div>
<div><br>
</div>
<div>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.</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
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.</div>
<div><br>
</div>
<div>Vish</div>
<br>
</blockquote>
<br>
<br>
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).<br>
<br>
The main issue is that we need to estimate the duration for all
'necessary works', ie. <br>
- renaming nova to gantt in the gantt repo<br>
- having unittests in place<br>
- 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)<br>
<br>
-Sylvain<br>
</body>
</html>