<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Was the history filtered out using something like <a href="http://git-scm.com/docs/git-filter-branch">http://git-scm.com/docs/git-filter-branch</a>??</div>
<div><br>
</div>
<div>There seems to be a lot of commit history that isn't related to gantt files (baremetal…)</div>
<div><br>
</div>
<div>Was the plan to figure out which files to keep, then cleanup that commit history?</div>
<div><br>
</div>
<div>I wouldn't expect <a href="https://github.com/openstack/gantt/commit/ff3c9afa35e646b72e94ba0c020ee37544e0e9dc">https://github.com/openstack/gantt/commit/ff3c9afa35e646b72e94ba0c020ee37544e0e9dc</a> (and others) to showup if those histories were removed…</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Boris Pavlovic <<a href="mailto:bpavlovic@mirantis.com">bpavlovic@mirantis.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, January 6, 2014 at 12:08 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Gantt] Looking for some answers...<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div><span style="font-family: arial, sans-serif; font-size: 13px;">Russell, </span></div>
<span style="font-family: arial, sans-serif; font-size: 13px;">
<div><span style="font-family: arial, sans-serif; font-size: 13px;"><br>
</span></div>
It should be pretty easy to do this in gantt though. Right now I would</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family: arial, sans-serif; font-size: 13px;">probably do it against the current scheduler and then we'll port it</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family: arial, sans-serif; font-size: 13px;">over. I don't think we should do major work only in gantt until we're</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family: arial, sans-serif; font-size: 13px;">ready to deprecate the current scheduler.</span><br>
<div><span style="font-family: arial, sans-serif; font-size: 13px;"><br>
</span></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">That make sense. </font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">In couple of they we will try to make some "real" benchmarks using Rally, to ensure that no-db-scheduler works better then previous. So I hope we will get interest from community. </font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><span style="font-family: arial, sans-serif; font-size: 13px;">It's a new repo created with the history filtered out. The history</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family: arial, sans-serif; font-size: 13px;">was only maintained for code kept. That seems pretty ideal to me.</span><font face="arial,sans-serif"><br>
</font></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;">Not sure that nova history is right history for scheduler (Why not Cinder for example? why exactly Nova?).</span></div>
<div><font face="arial,sans-serif">Imho Scheduler aaS for all projects and Nova Scheduler are different things. </font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div>Best regards,<br>
</div>
<div>Boris Pavlovic </div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Jan 6, 2014 at 11:59 PM, Russell Bryant <span dir="ltr">
<<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.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">On 01/06/2014 02:52 PM, Boris Pavlovic wrote:<br>
> Vish,<br>
><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<br>
> forklift<br>
> first.<br>
><br>
> Current Nova scheduler is so deeply bind to nova data models, that it is<br>
> useless for every other project.<br>
><br>
> So I don't think that forkit in such state of Nova Scheduler is useful<br>
> for any other project.<br>
<br>
</div>
It should be pretty easy to do this in gantt though. Right now I would<br>
probably do it against the current scheduler and then we'll port it<br>
over. I don't think we should do major work only in gantt until we're<br>
ready to deprecate the current scheduler.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Russell Bryant<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><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>
</div>
</span>
</body>
</html>