----- Original Message ----- > Excerpts from Solly Ross's message of 2014-05-05 08:23:41 -0700: > > Just to expand a bit on this, flavors are supposed to be the lowest level > > of granularity, > > and the general idea is to round to the nearest flavor (so if you have a VM > > that requires > > 3GB of RAM, go with a 4GB flavor). Hence, in my mind, it doesn't make any > > sense to create > > flavors on the fly; you should have enough flavors to suit your needs, but > > I can't really > > think of a situation where you'd need so much granularity that you'd need > > to create new > > flavors on the fly (assuming, of course, that you planned ahead and created > > enough flavors > > that you don't have VMs that are extremely over-allocated). > > I agree with the conclusion you're arguing for, but it is a bit more > complex than that. Flavor defines at least three things, and possibly 4: > RAM, root disk, and vcpu, with an optional ephemeral disk. Because of > that, the matrix of possibilities can get extremely large.
In addition extra specifications may denote the passthrough of additional devices, adding another dimension. This seems likely to be the case in the use case outlined in the original thread [1]. Thanks, Steve [1] http://lists.openstack.org/pipermail/openstack-dev/2013-November/018744.html _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
