Hi, I started to do the work – https://review.openstack.org/#/c/65691/. From the comments on the review it did not seem the right way to go. So I gave up on it. Sorry to not have updated. I personally think that the scheduler should use objects, the reason for this is as follows:
1. One of the aims of the objects is to enable seamless upgrades. If we have this in the gannet, that starts with using only the nova database then we can upgrade to using another database. The object interface will do the translations 2. We may be able to leverage objects to interface with different types of services. That will enable us to provide cross service features far quicker. Thanks Gary From: <Murray>, "Paul (HP Cloud Services)" <pmur...@hp.com<mailto:pmur...@hp.com>> Date: Thursday, January 30, 2014 11:41 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Cc: Administrator <gkot...@vmware.com<mailto:gkot...@vmware.com>>, Dan Smith <d...@danplanet.com<mailto:d...@danplanet.com>> Subject: [Nova][Scheduler] Will the Scheuler use Nova Objects? Hi, I have heard a couple of conflicting comments about the scheduler and nova objects that I would like to clear up. In one scheduler/gantt meeting, Gary Kotton offered to convert the scheduler to use Nova objects. In another I heard that with the creation of Gantt, the scheduler would avoid using any Nova specific features including Nova objects. I can see that these things are evolving at the same time, so it makes sense that plans or opinions might change. But I am at a point where it would be nice to know. Which way should this go? Paul. Paul Murray HP Cloud Services +44 117 312 9309 Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN Registered No: 690597 England. The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL".
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
