In most providers the volumes are just read only values to inform the user of what will be created when provisioning the VMs. In AWS-EC2 you have very detailed information on the type of the disks, etc, and users may want to pick a hardware profile or another based on that information.
I agree that returning a set of volumes with no information can be useless and confusing, and the purpose of remarking that a disk will be created is of little utility. After thinking a bit more abut this I think the best way to fix the tests is to accept the fact that many providers just don't have the notion of "volumes" at hardware profile level and consider that in the test base class, instead of overriding it. Thanks for the feedback! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/854#issuecomment-140559710
