deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Seago (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-326) Storage in RHEV-M hardware profile is advertised but ignored
Date Fri, 21 Sep 2012 15:40:07 GMT


Scott Seago commented on DTACLOUD-326:

Right now, the fact that storage isn't used by all drivers causes difficulty for Conductor.
For vSphere, storage works the same way, and the driver exposes this as a 'nil' value. We'd
previously agreed that a 'nil' value for a HWP param is essentially an opaque value -- i.e.
nil means "we dont' know". The difficulty on the conductor side with this is it means that
(once RHEV-M correctly returns nil for HWP storage) ec2 has valid storage values, but both
vSphere and RHEV-M will return nil. For an end user of conductor, this means that if the user
picks a minimum storage value, this limits launch to ec2 -- to get RHEV/vSphere as a launch
option,  the user must leave storage blank -- which means there's no selection of minimum
ec2 storage size.

One possibility is to add some metadata to the API to indicate whether storage is determined
by HWP, by image selection, or by some other means. Then we can refactor conductor to take
the user-supplied storage value and match to either HWP, or image, or someting else  based
on the provider type/driver.
> Storage in RHEV-M hardware profile is advertised but ignored
> ------------------------------------------------------------
>                 Key: DTACLOUD-326
>                 URL:
>             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:

View raw message