Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk sizes missing #90

Closed
garloff opened this issue May 10, 2021 · 2 comments
Closed

Disk sizes missing #90

garloff opened this issue May 10, 2021 · 2 comments

Comments

@garloff
Copy link
Contributor

garloff commented May 10, 2021

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 ?

@kisahm
Copy link

kisahm commented May 11, 2021

+1

we need an indicator if local disk / local nvme is in use

@garloff
Copy link
Contributor Author

garloff commented Jun 2, 2021

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.)

@garloff garloff closed this as completed Jun 2, 2021
@itrich itrich transferred this issue from SovereignCloudStack/Operational-Docs Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants