[
https://issues.apache.org/jira/browse/DTACLOUD-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605792#comment-13605792
]
Dies Koper commented on DTACLOUD-326:
-------------------------------------
Fgcp also returns nil for storage. Either way Conductor needs to be changed to
interpret the additional metadata. Can't it just interpret the nil as storage
being opaque and update its user interface (disable the storage field?)
accordingly?
At least for the Fgcp, although the system storage eventually comes from the
image you pick, you wouldn't be picking an image because of the storage size.
("Ah let's take this Windows image instead of this RHEL image because its
storage size is a better match!" ;)) That's what we have additional
storage_volumes for.
> Storage in RHEV-M hardware profile is advertised but ignored
> ------------------------------------------------------------
>
> Key: DTACLOUD-326
> URL: https://issues.apache.org/jira/browse/DTACLOUD-326
> Project: DeltaCloud
> Issue Type: Bug
> Reporter: Michal Fojtik
>
> The storage parameter in all RHEV-M hardware profiles is just 'fake' and does
> not
> have any value in decision making. Also if client specifies it in request
> (hwp_storage)
> then this value is ignored. RHEV-M does not create any storage but instead it
> just
> re-use the storage defined in Template.
> I suggest to remove this property from all RHEV-M profiles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
