Ed Leafe said on Mon, Jun 01, 2015 at 07:40:17AM -0500: > We need to update our concept of a resource internally in Nova, both > in the DB and in code, and stop thinking that every request should > have a flavor.
If you allocate all the memory of a box to high-mem instances, you may not be billing for all the CPU and disk which are now unusable. That's why flavors were introduced, afaik, and it's still a valid need. I totally agree the scheduler doesn't have to know anything about flavors though. We should push them out to request validation in the Nova API. This can be considered part of cleaning up the scheduler API. Alexis -- Nova Engineer, HP Cloud. AKA lealexis, lxsli. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
