CloudStack is currently limiting the number of data volumes, that can be attached to an instance, to 14. More specifically, this limitation relates to the device ids that CloudStack considers valid for data volumes. In method VolumeApiServiceImpl.getDeviceId(long, Long), only device ids 1, 2, and 4-15 are considered valid. What I would like to know is: is there a reason for this limitation? (of not going higher than device id 15)
Note that the current number of attached data volumes is already being checked against the maximum number of data volumes per instance, as specified by the relevant hypervisor’s capabilities. E.g. if the relevant hypervisor’s capabilities specify that it only supports 6 data volumes per instance, CloudStack rejects attaching a seventh data volume. Friðvin Logi Oddbjörnsson Senior Developer Tel: (+354) 415 0200 | frid...@greenqloud.com <jaros...@greenqloud.com> Mobile: (+354) 696 6528 | PGP Key: 57CA1B00 <https://sks-keyservers.net/pks/lookup?op=vindex&search=frid...@greenqloud.com> Twitter: @greenqloud <https://twitter.com/greenqloud> | @qstackcloud <https://twitter.com/qstackcloud> www.greenqloud.com | www.qstack.com [image: qstack_blue_landscape_byqreenqloud-01.png]
