[Fiware-cloud] Flavor metadata in images

[Alex Glikson]

What do you mean by "enough capacity"? Resource requirements typically 
depend on load..

In general, whatever the exact problem is -- the approach you are 
suggesting doesn't seem to be sustainable. For example, in some cases you 
might have many flavors, and they also might change over time (e.g., new 
flavors introduced), so keeping all the relationships as metadata 
key-value pairs introduces a huge overhead on the administrator. 
If you want to couple between flavor and image -- OpenStack Heat template 
might be the answer..

Regards,
Alex

====================================================================================
Alex Glikson
Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab
Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: 
+972-54-6466667 | Fax: +972-4-8296112





From:   Álvaro Alonso <aalonsog at dit.upm.es>
To:     fiware-cloud at lists.fi-ware.org
Date:   08/06/2015 02:41 PM
Subject:        [Fiware-cloud] Flavor metadata in images
Sent by:        fiware-cloud-bounces at lists.fi-ware.org



Hi Kenneth, Alex. 

one the features planned for the Cloud Portal is to, when deploying a VM, 
only show to the users the flavours that has enough capacity to host the 
specific image. 

https://jira.fiware.org/browse/CLD-299

In order to support that, all images should include a metadata field with 
the info about the flavour they need. I don?t know if it make sense to 
really support this feature because I?m aware the work load including this 
field in every images would suppose.

What do you think?

BR
-- 
Álvaro
_______________________________________________
Fiware-cloud mailing list
Fiware-cloud at lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-cloud
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-cloud/attachments/20150608/e16a00d6/attachment.html>