On Tue, Oct 21, 2014 at 09:41:44PM +0000, Jiang, Yunhong wrote: > Hi, Daniel's & all, > This is a follow up to Daniel's > http://osdir.com/ml/openstack-dev/2014-10/msg00557.html , "Info on XenAPI > data format for 'host_data' call". > I'm considering to change the compute capability to be a nova object, > with well defined field, the reasons are: a) currently the compute capability > is a dict returned from hypervisor, however, different hypervisor may have > different return value; b) currently the compute capability filter make > decision simply match the flavor extra_specs with this not-well-defined > dict, this is not good IMHO.
If by "compute capability" you mean the return value of get_available_resource, then I've already got patches which turn that from a dict into an object which we're discussing https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/virt-driver-get-available-resources-object,n,z http://lists.openstack.org/pipermail/openstack-dev/2014-October/048784.html Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev