On Mon, May 05, 2014 at 01:40:43PM -0400, Solly Ross wrote: > One thing that I was discussing with @jaypipes and @dansmith over > on IRC was the possibility of breaking flavors down into separate > components -- i.e have a disk flavor, a CPU flavor, and a RAM flavor. > This way, you still get the control of the size of your building blocks > (e.g. you could restrict RAM to only 2GB, 4GB, or 16GB), but you avoid > exponential flavor explosion by separating out the axes.
Splitting up flavours in that way doesn't really fly, especially for CPU & RAM, because the properties you want to configure for NUMA policies cross both CPU & RAM so cannot be sensibly separated. 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
