You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In standard OpenStack, flavors come with a disk size. This disk is for the root filesystem.
The disk size (if any disk is provided) should probably be part of the flavor.
"SCS-4V:16:100" would then be a flavor with 4vCPUs(oversubscribed) with 16GiB Ram and 100GB disk.
"...:50L" would be a local disk (lower latency than networked storage) of 50GB
"...:100S" would be a local SSD/NVMe type disk (>10k IOPs) of 100GB.
Standard sizes 10, 20, 50, 100, 200 ?
The text was updated successfully, but these errors were encountered:
Closed with PR SovereignCloudStack/Operational-Docs#8.
Though there is an additional question whether we can't rely on block_device_mapping_v2 much more and have a lot less disk sizes listed in our list of standard flavors. (Local disks are where we really need sizes attached.)
In standard OpenStack, flavors come with a disk size. This disk is for the root filesystem.
The disk size (if any disk is provided) should probably be part of the flavor.
"SCS-4V:16:100" would then be a flavor with 4vCPUs(oversubscribed) with 16GiB Ram and 100GB disk.
"...:50L" would be a local disk (lower latency than networked storage) of 50GB
"...:100S" would be a local SSD/NVMe type disk (>10k IOPs) of 100GB.
Standard sizes 10, 20, 50, 100, 200 ?
The text was updated successfully, but these errors were encountered: