it looks like we still have issues with HDD field.
Steps To Reproduce:
1. Create new environment in MOS 9.0
2. Add 3 controller nodes. Verify that HDD size is "0 bytes" in Fuel UI > env details.
3. Add 2 compute nodes to the environment. Verify that HDD size is "0 bytes" in Fuel UI > env details.
4. Add role Cinder to the compute nodes. Check the size of HDD for the cluster. It is equal to 384 Gb on my environment, 2 compute+cinder nodes have 192Gb+192Gb in total, 384 Gb is the full sum of HDD space of compute + storage nodes (it is actually not true)
5. Update the default configuration for disks partitioning for Cinder nodes. Allocate 40 Gb on each node for Cinder LVM. Check information about HDD size for the environment. It is still unchanged, 384 Gb total. In fact, changes in disks partitioning don't affect the size of HDD for the environment.
Observed Result:
HDD size for the cluster depends only on roles and doesn't depend on size of the real partitions which allocated for storage.
Hi team,
it looks like we still have issues with HDD field.
Steps To Reproduce:
1. Create new environment in MOS 9.0
2. Add 3 controller nodes. Verify that HDD size is "0 bytes" in Fuel UI > env details.
3. Add 2 compute nodes to the environment. Verify that HDD size is "0 bytes" in Fuel UI > env details.
4. Add role Cinder to the compute nodes. Check the size of HDD for the cluster. It is equal to 384 Gb on my environment, 2 compute+cinder nodes have 192Gb+192Gb in total, 384 Gb is the full sum of HDD space of compute + storage nodes (it is actually not true)
5. Update the default configuration for disks partitioning for Cinder nodes. Allocate 40 Gb on each node for Cinder LVM. Check information about HDD size for the environment. It is still unchanged, 384 Gb total. In fact, changes in disks partitioning don't affect the size of HDD for the environment.
Observed Result:
HDD size for the cluster depends only on roles and doesn't depend on size of the real partitions which allocated for storage.