Harikrishna Patnala created CLOUDSTACK-8295:
-----------------------------------------------
Summary: max data volume limits to be updated with new values for
all hypervisors
Key: CLOUDSTACK-8295
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8295
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Doc
Affects Versions: 4.4.0, 4.3.0
Reporter: Harikrishna Patnala
Fix For: 4.6.0
There is discrepancy in doc and the values we support in Cloudstack
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.4/storage.html
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/storage.html
========================
CloudStack supports attaching up to 13 data disks to a VM on XenServer
hypervisor versions 6.0 and above.
For the VMs on other hypervisor types, the data disk limit is 6.
========================
The Manual is wrong.
CloudStack supports attaching up to
a) 13 data disks on XenServer hypervisor versions 6.0 and above and all
versions of VMware
b) 64 data disks on HyperV
c) 6 data disks on other hypervisor types
mysql> select hypervisor_type,hypervisor_version,max_data_volumes_limit from
cloud.hypervisor_capabilities order by hypervisor_type;;
+-----------------+--------------------+------------------------+
| hypervisor_type | hypervisor_version | max_data_volumes_limit |
+-----------------+--------------------+------------------------+
| Hyperv | 6.2 | 64 |
| KVM | default | 6 |
| LXC | default | 6 |
| Ovm | default | 6 |
| Ovm | 2.3 | 6 |
| VMware | default | 13 |
| VMware | 4.0 | 13 |
| VMware | 4.1 | 13 |
| VMware | 5.5 | 13 |
| VMware | 5.1 | 13 |
| VMware | 5.0 | 13 |
| XenServer | 6.1.0 | 13 |
| XenServer | 6.2.0 | 13 |
| XenServer | default | 6 |
| XenServer | 6.0.2 | 13 |
| XenServer | 6.0 | 13 |
| XenServer | 5.6 SP2 | 6 |
| XenServer | 5.6 FP1 | 6 |
| XenServer | 5.6 | 6 |
| XenServer | XCP 1.0 | 6 |
| XenServer | 6.5.0 | 13 |
+-----------------+--------------------+------------------------+
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
