Open Stack

2014/1/22 Joe Gordon <joe.gordon0 at gmail.com>

>
>
>
> On Tue, Jan 21, 2014 at 7:35 PM, Dugger, Donald D <
> donald.d.dugger at intel.com> wrote:
>
>> Well, the first goal is to get the scheduler code into a separate tree,
>> even though that code is still utilizing common code from nova.  Right now
>> just about every scheduler file includes some nova modules.  Ultimately
>> yes, we want to remove the depency on nova but that is a future effort and
>> would create way too many changes for the immediate future.
>>
>
> The nova code you are trying to use isn't a public API and can change at
> any time. Before considering using gantt we would have to fully remove any
> nova imports in gantt.
>
>
>>
>> When we want to cut the cord from nova it'll be easy, just remove that
>> line from the `test-requirements.txt' file and we'll be forced to replace
>> all of the nova code.
>>
>
> I'm not sure it will actually be that easy.
>
>
>
Well, I think we should review all the imports in order to make sure all of
the needs can be addressed thanks to the Nova API (flavors, instances and
others). If yes, instead of importing classes, Gantt should only have
dependency on novaclient so it would use it to get objects.

The main problem is about objects synchronization, if Gantt does have its
own models for the objects it has to handle. That's why I think the most
difficult thing for Gantt is to play with abstract concepts on its side.

My 2 cents,
-Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140122/5061ef62/attachment.html>