[Fiware-cloud] Flavor metadata in images

[Ezra Silvera]

Hi,

I'm not sure it is aligned or make sense in terms of OpenStack. The 
separation between flavors and images was done by design In OpenStack so 
that you decouple between image and the required resources. I agree it 
would be nice to show only the flavors that can be used but this should be 
decoupled from the image (i.e., if you have max 200GB free mem on all 
hosts don't show flavors with mem > 200MB).

Note that if we add such link it will need to be maintained through out 
flavor life cycle (create, delete, etc..) . Also this will require someone 
who add an image (or someone who define a flavor) to go through ALL 
images/flavors to validate for these matches.


Thanks

Ezra Silvera



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/9d82a2c7/attachment.html>