Open Stack

On 06/04/16 18:36, "Daniel P. Berrange" <berrange at redhat.com> wrote:

>On Wed, Apr 06, 2016 at 04:29:00PM +0000, Fox, Kevin M wrote:
>> It feels kind of like a defcore issue though. Its harder for app
>> developers to create stuff like heat templates intended for cross
>> cloud that recommend a size, m1.small, without a common reference.
>
>Even with Nova defining these default flavours, it didn't do anything
>to help solve this problem as all the public cloud operators were
>just deleting these flavours & creating their own. So it just gave
>people a false sense of standardization where none actually existed.
>

The problem is when the clouds move to m2.*, m3.* etc. and deprecate
old hardware on m1.*.

I think Heat needs more of an query engine along the lines of “give me a
flavor with at least X cores and Y GB RAM” rather than hard coding m1.large.
Core performance is another parameter that would be interesting to select,
“give me a core with at least 50000 bogomips”

I don’t see how flavor names could be standardised in the long term.

Tim

>
>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 Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev