cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Damle (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-3336) AWSAPI - createVolume API with custom size should prefer a non-tagged custom sized disk offering first over a tagged offering
Date Tue, 02 Jul 2013 22:22:20 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prachi Damle resolved CLOUDSTACK-3336.
--------------------------------------

    Resolution: Fixed
    
> AWSAPI - createVolume API with custom size should prefer a non-tagged custom sized disk
offering first over a tagged offering 
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3336
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3336
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: AWSAPI
>            Reporter: Prachi Damle
>            Assignee: Prachi Damle
>             Fix For: 4.2.0
>
>
> For createVolume API with custom size the awsapi component chooses the custom size disk
offering present on CloudStack, sice CS createVolume API needs an offering Id.
> But if there are multiple custom size disk offerings, and some of the offerings have
tags, awsapi should try to choose a non-tagged custom offering first. There is a reason for
people to tag a disk offering and using that on every user API call may not be preferable.
> If all disk offerings are tagged however, awsapi will choose one of them. 

--
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

Mime
View raw message