Prachi Damle 6c9383bd76 CLOUDSTACK-3336 AWSAPI - createVolume API with custom size should prefer a non-tagged custom sized disk offering first over a tagged offering ...

Changes:
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.

2013-07-02 15:18:49 -07:00

..

conf

CLOUDSTACK-1825: Update AWSAPI server's XML configuration

2013-03-29 11:12:36 -07:00

resource

Stick to the versions the amazon classes were originally generated with

2012-10-02 11:35:29 -07:00

scripts

Stick to the versions the amazon classes were originally generated with

2012-10-02 11:35:29 -07:00

src/com

CLOUDSTACK-3336 AWSAPI - createVolume API with custom size should prefer a non-tagged custom sized disk offering first over a tagged offering

2013-07-02 15:18:49 -07:00

test

merge master

2013-05-11 15:28:43 +05:30

web

Small fix to satisfy the xml validation requirements

2013-06-17 11:26:13 -07:00

.pydevproject

awsapi license header changes

2012-08-01 09:34:12 -04:00

pom.xml

merge master

2013-05-11 15:28:43 +05:30