deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (Closed) (JIRA)" <>
Subject [jira] [Closed] (DTACLOUD-92) Validation of fixed hardware profile properties doesn't work
Date Wed, 21 Mar 2012 19:15:43 GMT


Ronelle Landy closed DTACLOUD-92.

Closing the issue as fixed. Using deltacloud git commit version 7e372dfca79c02a799046287e5936129216b781b,
even if I filled in both memory fields for m1.-large and m1.x-large, only the memory for the
selected hardware profile was included in the instance:

m1-xlarge, with memory = 13926 MB, storage = 1024 GB 

m1-large, with memory = 8678 MB, storage = 850 GB, cpu = 1 vcpus 
> Validation of fixed hardware profile properties doesn't work
> ------------------------------------------------------------
>                 Key: DTACLOUD-92
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: deltacloud-core r1181084
>            Reporter: Michal Fojtik
>            Assignee: Michal Fojtik
> Currently we cannot validate fixed values because of UI limitation. 
> In UI we have multiple hwp_* properties which overide each other. When provider have
one 'static' hardware profile and one 'customizable' when user select the static one the UI
also send values from the customizable one (which will lead to a validation error because
validation algorith will think that client want to overide fixed values.
> How to reproduce:
> 1. Use mock driver
> 2. Go to launch new instance page
> 3. Choose m1-large profile
> 4. Enter '8678' as memory value
> 5. Now go to m1-xlarge profile (don't select it)
> 6. Enter '13926' to the memory field
> 7. Launch instance
> Actual Result:
> Instance will have 13926 MB of memory instead of 8678 (or throw an validation error (depends
on version you're using))
> Possible solution:
> Use Javascript to remove/insert content into nested form fields. In this way the field
will not override each other.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message