Flavor naming feedback

[noonedeadpunk]

Description

As for reqeust in OpenStack Mailing List [1], filling in issue to gather feedback that has been said out during discussion.

1. Raised concern, that suggested in [2] naming convention is not readable at glance and in order to understand it cloud users will require to read and remember that spec, which is not convenient/acceptable from UX prespective.
   As alternatives to it, following examples were mentioned for the following sample:

- nvt4: nvidia T4 GPU
- a8: AMD VCPU 8 (we also have i4 for example, for Intel)
- ram24: 24 GB of RAM
- disk50: 50 GB of local system disk
- perf2: level 2 of IOps / IO bandwidth

• nvt4-a8-ram24-disk50-perf2
• 8vCPU-24576RAM-50SSD-pGPU:T4-10kIOPS-EPYC4

2. Raised opinion, that flavor naming should not be standardized/regulated at all. For the following reasons:

• before creating instance people should reference flavor specs at the first place and not flavor names
• during Sydney summit present operators agreed upon impossiblity to come to consensus for standard naming for flavors, because many of them used higly tuned flavors. So it is space that we might want to avoid from regulating.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023152.html
[2] https://github.com/SovereignCloudStack/Operational-Docs/blob/main/flavor-naming-draft.MD

[tibeer]

@garloff how should we proceed with this?