On Mon, 13 Mar 2017, Chris Dent wrote:
* The scheduler report client in nova, and to a minor degree the
filter scheduler, use some of the same exceptions and ovo.objects
that placement uses, which presents a bit of blechiness with
regards to code duplication. I suppose long term we could consider
a placement-lib or something like that, except that the
functionality provided by the same-named objects and exceptions
are not entirely congruent. From the point of view of the external
part of the placement API what matters are not objects, but JSON
structures.
Reporting here for sake of keeping track: I've made a patch to remove
the use of ResourceProvider from the filter_scheduler and
resource_tracker:
https://review.openstack.org/#/c/452569/
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
